| < Day Day Up > |
|
The SDP is a generalized description of a group of specifications and plans for conducting a software development effort. The term development is meant to include the creation of new items, incorporation or update of existing items, or a combination of these approaches. Not all of these specifications and plans are applicable to every project. It is the Core Team's responsibility to work with the requirements requirements analysis team and data analysts and development and/or engineering team leaders to determine the proper level of detail and the scope of effort that is required to complete the SDP. The followign are some items that should be considered for inclusion in the SDP:
Architectural system design standards
Data conversion strategy
File and database backup/recover/reorganization strategy
Functional data model
Functional process model
Physical data model
Physical data storage estimates
Physical process model
Program file/database access patterns
System control requirements
System job flowchart
System Administration Manual table of contents
System processing load estimates
Testing strategy
Remember, the purpose of this book is to describe what is needed to run an effective SPMO in an organization. For our purposes, it is not necessary to go into great detail on the specifics of how to calculate physical storage requirements, determine load estimates, and so on. It is assumed that such resources are available to the project team to get the work done. It is only necessary that a Project Lead or Program Manager knows when it needs to be done in the SEP process and finds resources to do it.
| < Day Day Up > |
|