Physical Design Phase

Physical Design Phase

In this phase, the team completes the technical blueprints for the new system, based on the implementation platform. Any questions or issues that have not yet been resolved about the platform must be resolved in this phase. If necessary, the team may be changed at this point to take advantage of specific platform expertise.

Deliverables

Full Object Model (Technical Level) The full, technical-level object model includes aggregates and inheritance, messaging, and complete object class definitions.This model is updated or created in Visio. Note: Clicking on the Template button will open a new entity object model diagram in Visio. To update an existing model, you must open the file in Visio, not from here. There is no sample of the Full Object Model available at this time.
Internal Specifications This document includes the technical blueprint for the system design, including all requirements for coding the system. Where the External Specifications describe the system from the user's perspective, the Internal Specifications describe the system from the programmer's perspective. Neither sample nor template is available for this document yet.
Transition Plan This document describes the process for moving the application from development to production, including estimates of resources and work effort, and a preliminary schedule for the transition. If this document has not been completed already, it must be completed by the end of this phase.
Updated Test Scripts The test scripts are updated as needed, based on any changes or additions mandated during physical design. No sample or template is available at this time.
Updated Test Plan The test plan is updated as needed, based on any changes or additions identified during the physical design phase. No sample or template is available at this time.
Updated Project Plan The project plan is updated as needed, and a phase section containing the work breakdown structure and schedule for the next phase is added. At this time, no sample is available.
Methodology Compliance Form This form is initialized by the project team, and completed by a methodology representative who has reviewed the project documentation and found it acceptable. It is completed in Word. At this time, no sample is available.
Recommendation Form This form is completed by the project team, and contains the recommendation to the approving authority on whether or not the project should continue. The form is completed in Word. At this time, no sample is available.

Steps

The core team recommends a new extended team, if necessary. Be sure that at least one client who is representative of the average user is still on the extended team.

The team meets to review the documentation from the previous phase. Any new team members should be given copies of the documentation before the meeting.

The team builds the physical database model, mapping entities and relationships to files, groups, and records, mapping data elements to fields and records, identifying files, and describing integrity rules.

The team builds the physical object model, mapping objects to implementation items, specifying message protocols, and identifying data structures.

The team extends the object model with physical design needs, specifying data views and access paths, and testing against the data model. A representative of the team updates the System Level Object Model, created or updated in Visio in the previous phase, with the technical level information generated in these meetings, creating the Full Object Model (Technical Level).

A representative of the team writes the internal specifications based on the physical object model and all other pertinent information, keeping in mind that this document is intended for the programmer. The internal and external specifications give the programmers a complete view of the system, from which they can code the objects. The team reviews the specifications to be sure they are complete and accurate.

If the transition plan has not been completed in previous phases, the business and technical project managers meet with a representative from Production Support to create a plan for moving the system from development to production. Complete details on this process can be found in the Application Transition Handbook, available from the Configuration Manager.

Update the test scripts with any additional steps or functions required based on the technical requirements developed in this phase.

Update the test plan, if necessary.

The team reviews the documentation created or updated during this phase, and makes any necessary changes.

The documentation packet is forwarded to the methodology unit representative with the compliance form (use the Compform template), and a methodology walkthrough is scheduled with the core team and the methodology representative. At the walkthrough, the methodology representative can ask any questions and raise any issues about compliance with the methodology, or suggestions for improvement.
If any changes are required, the team must complete the required step(s) and schedule a follow-up walkthrough with the methodology representative. When the walkthrough is completed successfully, the methodology representative completes the compliance form, and the project continues with the next step.

The core team writes a recommendation on whether or not to proceed. Use the RECOMEND template, which includes space for the actual recommendation, and for the pros and cons associated with the recommendation.

The recommendation is forwarded to the project sponsor with the project plan and supporting documentation for review, and the project sponsor decides whether or not to refer the project to the approving authority for approval. (This would be necessary if the project schedule or budget has changed significantly.)