software development project plan (sdp)
DESCRIPTION
TRANSCRIPT
1
Software Development
Plan
2
Table of Contents for the SDP (Software Development Plan) General Contents
A. Project Organization
B. Project Deliverables
C. Environment
D. Reviews, measurements, payments, V&V
E. Odds and Ends
3
Table of Contents for the SDP (Software Development Plan)
1. Introduction
2. Resources and Scheduling
3. Organization and Staffing
4. WBS
5. Technical Management and Control
4
Table of Contents for the SDP (Software Development Plan)
6. Standards and Procedures
7. Reviews, Audits, and Walkthroughs
8. Development Environment
9. Technical Performance Measurements
10. Documentation
5
Table of Contents for the SDP (Software Development Plan)
11. Verification and Validation
12. Maintenance
13. Human Factors
14. Delivery, Installation and Acceptance
15. Appendices and References
6
Table of Contents for the SDP
I. Introduction
Summary of Contents of SDP document
Scope and Purpose of SDP Document
System Level Project Description
System Description
7
Table of Contents for the SDP
Summary of Contents of SDP documentTOC
Scope and Purpose of SDP DocumentThis document will be used to plan project
…. Or get funding….. Or write the RFP
System Level Project DescriptionThis project will…….
System Description
This system will
8
Table of Contents for the SDP
2. Resources and Scheduling
How many people needed?
What type of people?
How long will it take to do this project?
How long will each person be needed?
9
Table of Contents for the SDP
2. Resources and Scheduling
This project will need x# users, y# dp staff
There will be one communications specialist, one data specialist, one unix specialist, one capacity manager, one xxxxx user 4 managers, …..
This project will begin …. And end ….. Person A needed during weeks of etc
10
Table of Contents for the SDP
3. Organization and Staffing
Who are the people needed?
How will the Staffing be organized
How are the users organized?
Who pays? Who knows?
11
Table of Contents for the SDP
3. Organization and Staffing
The organizational chart for the project will be as follows:
Contractor will pay for travel, meeting rooms…...
12
Table of Contents for the SDP
4. WBS
Week by week, who will be needed when?
How much time will be devoted?
How much will this cost?
13
Table of Contents for the SDP
5. Technical Management and Control
How will change management be done?
How will risk be managed?
How will cost be contained?
How will issues be resolved?
14
Table of Contents for the SDP
5. Technical Management and Control
Changes to specification will be done by submitting a change report, approval of change by xyz committee, and scheduling of change.
Risk will be reviewed by the xyz committee each month. Formal risk reports are due to jkl committee quarterly.
Cost reports will be given to mno committee each week for review by xxx manager.
All issues will be reviewed at the project management meeting. Issues which delay development schedules will be resolved by the rst committee.
15
Table of Contents for the SDP
2. Risk Models Approach to Risk Assessment
1. Identify areas of potential risk
2. Partition each risk area into manageable factors
3. Examine the Consequences of Failures
4. Determine Management Strategy to Manage Risk
Avoidance
Prevention (control)
TransferKnowledge and Research
16
Table of Contents for the SDP
6. Standards and Procedures
What deliverable standard will be used
What development methodology?
What is the deliverable acceptance standard?
17
Table of Contents for the SDP
6. Standards and Procedures
Deliverables will be prepared according to the Summit methodology. All deliverables will be submitted using standard UML. Deliverables will be reviewed by the developers and upon approvals users, management committee, steering committee and final signature by project sponsor.
18
Table of Contents for the SDP
7. Reviews, Audits, and Walkthroughs
How will deliverables be reviewed?
Who will perform auditing?
Who will perform walkthroughs?
What is the approval process?
19
Table of Contents for the SDP
7. Software ReviewsDesign Reviews
Design and Coding Checks
Management Reviews
Project Checkpoints concerned with costs, plans, schedules
Quality Reviews
Technical reviews of quality of deliverable products,
standards adherence, documentation
End Product of Reviews
No Action, Refer for Repair, Reconsider overall product
20
Table of Contents for the SDP
(Software Development Plan)
8. Development Environment
The system will be developed using the IBM 3090 mainframe running AIX and Dell Pentium micro computers running windows NT. The development environment will be the same except micros will run windows 95.
21
9. Technical Performance Measurements
How fast will response time be?
How fast will database access be?
How many transactions per sec?
How many terminals on at one time?
What is the MTBF?
Table of Contents for the SDP
22
Performance Evaluation
Number of simultaneous users Number of Connections
Number of Files Size of Tables
Number of Open Files Number of Records
Number of Transactions per interval Response Time
Amount of data processed in a time unit Database Accesses per time unit
Reliability Availability
Backup/Recovery CPU Utilization
Memory Utilization I/O Channel Utilization
Software Utilization Terminals Supported
External Devices Supported
Table of Contents for the SDP
23
9. Technical Performance Measurements
Each transaction will have < 10 sec response time.
Each database will be completed within 10 ms.
The system will process 600 transactions per sec
with 4500 terminals on line.
MTBF will be > 1 hour on the average.
Table of Contents for the SDP
24
Table of Contents for the SDP
(Software Development Plan)
10. Documentation
Documentation of existing system
Documentation of attempts to do this
Documentation of all letters, memos
Documentation of deliverables
25
11. Verification and Validation
Deliverables will be verified for conformance with standards using by the QA group. Deliverables will be validated by the xxx user and rmm development committees
Table of Contents for the SDP
(Software Development Plan)
26
12. Maintenance
Approximately 30 hours per month of maintenance is expected approximately one year after turnover. How much maintenance is expected? The system will need 1 Computer Manager, 1 User Manager, and 5 computer programmers assigned. Maintenance environment will be the same as development.
Table of Contents for the SDP
27
13. Human Factors
There are 3000 users in the group who will need training from computer literacy to usage of the system. A culture change management play will be needed to train the people in the new method of doing business and the computer technology to support this new method.
Table of Contents for the SDP
28
14. Delivery, Installation and Acceptance
What is considered delivered?
How will we install?
What is considered accepted?
Table of Contents for the SDP
29
14. Delivery, Installation and Acceptance
The system will be considered delivered when each of applications is validated by the user group. We will roll out installation by each congressional district. The system will be considered accepted when 4 districts are installed and when one billing cycle has been completed.
Table of Contents for the SDP