Logical Design Phase
In this phase, the focus changes to design. The extended team may be changed to take advantage of specific design expertise, and should include both business representatives (management and staff), and technical expertise (data administration, networking, documentation, etc.).
The team reviews the materials from earlier phases and begins the system design, identifying any additional system objects, determining operations and data structures for all objects, validating relationships and interactions between objects, and prototyping user interface objects.
Do not limit design choices based on platform/language decisions made in previous phases. Any constraints resulting from platform/language decisions will be dealt with in the Physical Design phase.
|Full Object Model, System Level
This diagram shows all the entity objects, interface objects, control/process objects, and messages. This is an update of the entity object model completed in the System Analysis phase, therefore, you should open the existing file in Visio rather than opening a new diagram with the Template button.
|Updated Object Life Cycle Models
Any changes to the object life cycles resulting from the work in this phase must be entered in the existing models, and new models must be created for any new objects that go through complex life cycles.
|Object Interaction Diagrams
These diagrams are used to fully define all required messaging between objects based on the transaction sequence diagrams, and each diagram illustrates the flow of control between objects for one transaction sequence. There must be one Object Interaction diagram for each Transaction Sequence diagram. At this time there is neither a sample nor a template for this diagram, although you can find examples in the class materials from the Object Oriented Analysis and Design class.
|System-Wide Behavior Model
This optional diagram presents a high-level picture of the system and its operation. It is based on the subject areas in the object model. This diagram presents the system as a group of subsystems, that can be scheduled, worked on, and delivered separately. It also helps in determining the relationship of the subsystems based on the services they provide. At this time there is neither a sample nor a template for this diagram, although you can find examples in the class materials from the Object Oriented Analysis and Design class.
This document describes the external design of the system in terms that make sense to a user of the system. This includes a description of the screens and reports, explanations of the processes the user must follow to accomplish business functions, and a navigational map of the system. This document should be created in Word, but there is no template available at this time.
|Initial draft of test plan
This document describes the steps to be taken to test the system. These steps should include, at a minimum, expanding or creating use cases for each business function, creating test scripts based on those use cases, creating a test database and other test files, and planning for regression testing. List the business functions that require use cases, indicate where the test data will come from, and estimate when testing milestones will be reached. There is no template or sample for this document at this time.
This document describes each use case in detail. There should be a use case for each business function to be handled by the system. There is no template or sample for this document at this time.
This document describes the user requirements for documentation of the system, and the plan for meeting those requirements. There is no template or sample for this document at this time.
|Initial Draft of Test Scripts
These scripts are step-by-step procedures used to test functionality. Each business function should have one or more test scripts, depending on the number of alternate paths there are for completing the function. There is no template or sample for this document 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 Physical Design 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.
This form is completed by the project team, and contains the recommendation to the project sponsor on whether or not the project should continue. The form is completed in Word.
At this time, no sample is available.
See page 5B-17 of the Object Oriented Analysis And Design class materials for the validation checklist for the full Object Model, and click here to see a sample diagram.