1. Proposed Software Development Process
Medco, Inc.

2. Proposed Software Development Process
Jim Nowotarski:
Relatively complete
“Project Plan” should be “Project Management”
Does not accurately depict overlap among activities, e.g., System Test [planning] begins when Functional Spec is complete
Proposed Software Development Process
Analysis
Review
Design
Review
Project Plan
Development
System Testing
Deployment
Maintenance

3. BEFORE THE ANALYSIS Jim Nowotarski: Appropriate use of rectangle?
How about other high-level outputs:
- architecture
- cost/benefit
- project plan
BEFORE THE ANALYSIS
User Request
Project Scope
Project Approval
Comments
User requests are documented in the project scope document. This document is used to determine whether the project is approved or not by a committee and if approved, the priority for the project is set.
Deliverables
High-Level Functional Requirement
Responsibility
User
High-Level
Functional
Requirements

4. Entity Relationship Diagrams, Functional Decomposition, etc.
Jim Nowotarski:
Standard structured analysis
Notes page should identify “analysts” as being responsible
Notes page identifies “Process flow” as deliverable, but it is not shown here
ANALYSIS
High-Level
Functional
Requirements
Data Modeling
Process Modeling
Comments
This phase is for discussions with the user community and with the team leaders to work through the data and process modeling.
Deliverables
Entity Relationship Diagram
Data Flow Diagram
Functional Hierarchy Diagrm
Process Flow
Responsibility
Project Manager
User
and/or technical leaders designated by the Project Manager
Entity Relationship Diagrams,
Data Flow Diagrams,
Functional Hierarchy,
Functional Decomposition, etc.

5. DESIGN Jim Nowotarski:
No mention of a functional design of other aspects of the system:
- Noninteractive parts
- Conversion
Technical spec does not mention architecture
DESIGN
Entity Relationship Diagrams,
Data Flow Diagrams,
Functional Hierarchy,
Functional Decomposition, etc.
ERD/DFD/FHD/
Process Flow
Review
Prototyping
Discussions
Design - Part I
Comments
During this phase, ptototyping can be used to discuss with the users how the system’s user interface is going to look. This is an iterative process. Once the func spec is written, it needs to be reviewed with the users and the team leaders to clarify how the system is going to work. This also an iterative process. The final version of the func spec, then, receives user sign off. This process removes ambiguity as much as possible.
Deliverables
Functional Specification
Responsibility
Project Manager
and/or technical leaders designated by the Project Manager
Functional Specification.
User Sign Off

6. Design - Part II
Comments
This is still considered design phase. After functional spec is finalized, the same process is repeated with the technical specification. Once the first draft of technical spec is written, it is, then, reviewed with the team, including appropriate resources from System Infrastructure group. Technical specification contains following items:
- pseudo code
- database design (indexes, sequences, views, tables, etc.)
- user security access (CRUD mapping, database roles, etc.)
- project table sizes
- projected growth
- any other system resource requirements
Once it is approved by all participating groups, the process can continue.
Deliverables
Technical Specification
Responsibility
Team/technical leader

7. DEVELOPMENT Jim Nowotarski: Where are databases coded
Ignores development environment issues, e.g., setting up test environment
Functional Specification.
DEVELOPMENT
Technical Specification.
Technical Specification Review
Comments
This is the actual building phase. Once the technical spec is written and approved, the coding phase is the easiest and should be the smallest part in the project plan. During this phase, unit testing is incorporated and therefore, is not part of system testing. Once the development is done, and when ready to be delivered to QA for testing for a release, the accompanying release definition now contains a list of modules and their version control numbers. All other information that is currently contained in the release definition has been already addressed in the technical spec.
Deliverables
(Application System)
Release Definition
Responsibility
Team/technical leader
Developers
Capacity Planning
Write Programs as Specified in Technical Specification**
** Includes unit testing
Application System as Specified

8. SYSTEM TESTING Jim Nowotarski: Relatively simplistic
Ignores “integration testing” that typically occurs between unit test and system test
Application System
Functional Specification.
Test Plans
Functionality Testing to ensure that it meets the specified functions
Performance testing to ensure that it is acceptable
User Guides/Documentation
Comments
While the development is going on, system test plans can be generated at the same time. Once the functional spec is finalized, the building of the system test plan can begin. Technical specifications can be used in the test plan as well.
Deliverables
Test Plans
Responsibility QA
Application System as specified

9. DEPLOYMENT Jim Nowotarski: Deliverables not shown:
- User guides/documentation
- Implementation plan
Application System as specified
User Training
Support Area Training
Incorporate Into Existing Production System
Comments
Once the testing is winding down, and there are not going to be any more changes to the system, Technical Education can start working on their documentation and training. This training includes both the users and the Help Desk. Also, at the same time, the project team is to start preparing for deployment into production. Implementation plan is used to ensure smooth deployment.
Deliverables
User Guides/User Documentation
Implementation Plan
Responsibility
Technical Education
Project Manager/QA
Production System

10. On-Going Support for the System
MAINTENANCE
On-Going Support for the System
Bug Fixes
Enhancements

11. Proposed Software Development Process
Jim Nowotarski:
Note that Implementation Plan and User Guides/Documentation are outputs from Deployment, not inputs
Proposed Software Development Process
High-Level Functional Requirements
Analysis
ERD/FHD/DFD/Process Flows
Review
Approved
Functional Specification
Design
Review/User Sign Off
Technical Specification
Approved
Project Plan
Review
Approved
Test Plans
Development
Release Definition
System Testing
Implementation Plan
Deployment
User Guides/Documentation
Maintenance