Chapter 4: Formalizing Business Requirements into Functional Specifications


Overview

In this chapter, you will extend the business requirements into the next phase—the creation of functional specifications. After the initial requirements have been created, functional specifications are created to determine what functionality the final solutions will have. This creation of the functional specifications allows for the further definition and restating of the requirements. Additionally, this process divides the requirements into groups of responsibility.

Next is the development of the technical specifications document. This document details the specifics about how the solution will be created. The design goals of performance, scalability, availability, deployment, security, and maintainability are addressed in this document. A development strategy is decided upon for handling auditing, error handling, integration, localization, and state management. Also in this document is the selection of how to deploy the application and the different strategies available.

After deployment, the operations strategy examines how the solution will be transitioned to the operations team and how the solution will be supported in the future. Included in this plan is how to maintain the data archiving of the information and upgrade strategies.




MCSD Analyzing Requirements and Defining. NET Solutions Architectures Study Guide (Exam 70-300)
MCSD Analyzing Requirements and Defining .NET Solutions Architectures Study Guide (Exam 70-300 (Certification Press)
ISBN: 0072125861
EAN: 2147483647
Year: 2003
Pages: 94

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net