Reviewing Concepts

The Agile Methodology

CSE4939
CSE4940


What’s in a Specification?



www.engr.uconn.edu/~steve/Cse4939W/spec.pdf
www.engr.uconn.edu/~steve/Cse4939W/specif.pdf
Software Architecture Diagrams


www.engr.uconn.edu/~steve/Cse2102/finagile.pptx
scrumreferencecard.com/ScrumReferenceCard.pdf
www.engr.uconn.edu/~steve/Cse4939W/SWArchExs.ppt
See More Examples under:


www.engr.uconn.edu/~steve/Cse4939W/TeamDSpec.docx
www.engr.uconn.edu/~steve/Cse4939W/TeamGSpec.docx
OV-1.1
What is Agile Methodology?

CSE4939 
CSE4940






Project management with frequent inspection and
adaptation
Teamwork, self-organization and accountability
Testers need understanding of agile as a whole
Also need to learn how to adapt their current
approach to work within agile efforts
Highest priority is to satisfy the customer through
early and continuous delivery of valuable software
Welcome changing requirements, even late in
development
Deliver working Software Frequently (Increments)
Business people (Domain Experts) and developers
must work together daily through out the project
OV-1.2
Conceptual Viewpoint….
CSE4939
CSE4940
OV-1.3
Characteristics of Scrum…


CSE4939
CSE4940



Self-organizing teams
Product progresses in a series of month-long
“sprints”
Requirements are captured as items in a list of
“product backlog”
No specific engineering practices prescribed
One of the “agile processes”
OV-1.4
Various Backlogs
CSE4939
CSE4940
OV-1.5
Sprint Backlog…
CSE4939
CSE4940
OV-1.6
Sample Product Backlog…
CSE4939
CSE4940
OV-1.7
CSE4939
CSE4940
Requirements
Design
Code
Test
OV-1.8
What’s in a Specification?
CSE4939
CSE4940
OV-1.9
Major Sections in a Specification
CSE4939
CSE4940
OV-1.10
Introduction
CSE4939
CSE4940
OV-1.11
Glossary
CSE4939
CSE4940
OV-1.12
Operating Environment
CSE4939
CSE4940
OV-1.13
Information

CSE4939
CSE4940
What are the Major Pieces of Information?
 Supermarket has Items
 Items could be Dairy, Meat, Produce, NonPerishable, Deli, etc.
 Track the Orders of Shoppers (OrderDB)
 Learn Preferences
 Target Coupons, etc.

Inventory Control Database (ICDB)
 Single Store
 Chain of Stores
OV-1.14
Performance
CSE4939
CSE4940
OV-1.15
Security
CSE4939
CSE4940
OV-1.16
Security
CSE4939
CSE4940
OV-1.17
Software Architecture Examples
Providers
CSE4939
CSE4940
EMR
Medication/Supplement
Interaction Checker
Patients
Medication
Record (TMR) System
Apache/Tomcat
Web/Application
Server
Client Side Technologies
https, html, Ajax, XML
Server Side Technologies
Java, JSP, Hibernate,
Relational Database, XML
MySQL
Database
Server
Personal Health
Record (PHR)
MS Health Vauly
TMR
Database
Pharmacy
System
Pharmacists
Figure 1: Architecture Diagram of the TMR and its Interactions.
OV-1.18
Software Architecture Examples
CSE4939
CSE4940
OV-1.19
Software Architecture Examples
CSE4939
CSE4940
OV-1.20
Original CHIN Architecture
CSE4939
CSE4940
http://publichealth.uconn.edu/CHIN.php
OV-1.21