![]() ![]() A detailed mapping of requirements to the architecture (if necessary) should be included in an appendix.Ĭoncept diagrams should be included to show the inter-relationships among the various components in the architecture. This section should also provide, in summary form only, a description of how the system will meet the requirements. If appropriate it states in generic terms how the software and hardware of the system evolves through four environments: Development, Test, Conversion and Production. This architecture defines the software and technology which will be used to implement the solution and shows how they will be integrated. This section expresses in general terms, the requirements in a conceptual architecture. Later in the project, long after the Requirements Report is replaced with more detailed statements of functionality, the Blueprint will remain as the documented statement of direction for the project. Note: The intention of this section is to permit the Blueprint to stand alone as a document. This section is included to provide a context for the system. It should provide a brief explanation of the general need or requirement, and the rationale for the implementation of the new system. The reason for the implementation of the system should be stated in this section. O how the report is organized and the purpose and content of each section o the objectives and scope of the Architecture Definition phase and the events that have occurred, and deliverables produced up to the production of this report.The Blueprint should be viewed as the target toward which the analysis and development teams are to direct their efforts. This should have been done in the Alternatives Evaluation Report. It should be noted that the Blueprint is not intended to provide a defense of the chosen components of the architecture. It is not an application design document, and should only include enough information about the structure of the application to show how this fits into the overall architecture. ![]() It will include, in appendices, details such as model and part numbers, and specific location information. The final version of the Blueprint which may be produced at the end of the Design or Facilities Engineering phases, will be explicitly detailed. Or, the customer may dictate a more specific definition of the Architecture. For example it may be necessary to state that the mainframe included in the solution will be a VAX 9000 or an IBM 3090. However, there may be instances where the Blueprint will have to identify vendors or products. This version generally should not identify specific vendors, products or models. Initially, when produced in the Architecture Definition phase, it should be a conceptual document oriented to management, which communicates the overall structure of the proposed system. The Blueprint should be at the level of detail necessary for the phase of the life cycle. O the team with a framework in which to conduct detailed analysis. O the team with a consistent statement of direction O a cost estimate for budgetary purposes, which leaves lots of room for adjustment as the project continues ![]() O a framework in which the customer can make informed decisions
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |