1. Our Process
CMSC 345, Version 1/04

2. Artifacts
CMSC 345, Version 1/04

3. Process Basically, waterfall. Why?
First time through the entire life cycle
Semester is very short
I must give you hard deadlines
Prototyping strongly suggested for requirements elicitation
May be ways to integrate some iteration into the process
CMSC 345, Version 1/04

4. Requirements Phase Activities
Requirements elicitation
Customer meetings
Prototyping (?)
Documentation
Systems Requirements Specification (SRS)
Product scope definition
Requirements specification
Functional (use cases)
Non-functional
Deliverables, open issues
User Interface (UI) Design Document (preliminary only)
User interface walkthrough
Peer Review of SRS and preliminary UI Design Document
CMSC 345, Version 1/04

5. Design Phase Activities
System Design Document (SDD)
System architecture (structure)
Decomposition
components
interfaces
Persistent data storage
files
databases
Hardware, software, procedural/OO decisions
Requirements traceability
Final UI Design Document
Peer review of SDD and UI Design Document
CMSC 345, Version 1/04

6. Implementation Phase Activities
Code and compile
Code inspection
Error correction
Unit test
Code Inspection Report (CIR)
Coding and commenting standards
Code inspection process description and opinion
Defect check list
Code inspection results
Peer review of CIR
CMSC 345, Version 1/04

7. Testing Phase Activities
Integration testing
System testing
Testing Report
Testing process description and opinion
Specification-based (black box) tests and test results
Program-based (white box) tests and test results
Peer review of Testing Report
CMSC 345, Version 1/04

8. Delivery and Demo Activities
Delivery and demo arrangements (time/date, location, equipment)
Dry run
Final delivery and demo
Deliver final artifacts
Conduct demo
Documentation
User Manual
Administrator Manual
Peer review of User and Administrator Manuals
CMSC 345, Version 1/04