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 o an opportunity for the customer's management to understand the proposed system.The communication of the vision in a simple straight forward manner provides: There will be time to choose the most cost effective option later in the process. For example, if the Blueprint indicates that a UNIX file server will be used, it may not have to indicate which version of UNIX or vendor's server will be used. The objective of the Blueprint is to communicate the system 'vision' without committing to very specific implementation details over which we should have control. O we want to give ourselves the flexibility to change components as technology provides new options. O the team working on the detailed definition of requirements needs a defined scope and environment in which to work O we should not be too specific or constraining until we have defined the requirements in detail, yet o an iterative, top-down, phased refinement approach is the best way to conduct systems analysis and design.The System Blueprint (Blueprint) evolves throughout the project and becomes a key component of the final documentation for the system. The complete configuration includes hardware, system software, packages, custom software, and communications. The term blueprint is also used less formally to refer to any plan.The purpose of the System Blueprint is to provide a complete description of the system configuration and how its components fit together. The process has been largely displaced by the diazo whiteprint process and by large-format xerographic photocopiers, so reproduced drawings are usually called "prints" or just "drawings". To combat this problem, printing on imitation vellum and, later, polyester film was implemented. Paper was a common choice for more durable prints linen was sometimes used, but with time, the linen prints would shrink slightly. Various base materials have been used for blueprints. The process was unable to reproduce color or shades of grey. The blue-print process was characterized by light colored lines on a blue background, a negative of the original. Introduced in the 19th century, the process allowed rapid and accurate reproduction of documents used in construction and industry. Blueprint A blueprint is a reproduction of a technical drawing, documenting an architecture or an engineering design, using a contact print process on light-sensitive sheets.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |