Module 12: Introduction to Functional Specifications 428 Module 12: Introduction to Functional Specifications Module Overview Module 3: A Services-based Approach to Solution Design Module 4: Business Solution Conceptual Design Module 5: Business Solution Logical Design Module 6 : Be ginning Physical Design Module 1: Course Overview Module 2: Solution Design Using the MSF Module 7: Selecting Solution Tec hnolo gies Module 8: Solution Design and the Component Object Model Module 9: Designing Solutions with Microsoft Technologies Module 10: Completing the Physical Design Module 11: Designing the Presentation Layer Module 12: Introduction to Functional Specifications Designing Business Solutions Functional Specification Basics Review Functional Specification Validation Activity 12.1: Risk of No Functional Specification Functional Specification Creation Module 12: Introduction to Functional Specifications Module 12: Introduction to Functional Specifications 429 ! !! ! Overview " Functional Specification Basics " Activity 12.1: Risk of No Functional Specification " Functional Specification Creation " Functional Specification Validation " Review In this module In this module The Planning Phase of the MSF Process Model culminates in the Project Plan Complete Milestone. One of the primary deliverables of this milestone is the functional specification. The functional specification describes the solution in sufficient detail for the development team to implement it. In this module, you will learn about the functional specification, its contents and purpose, and how to validate it. After completing this module, you will be able to: " Describe the purpose and benefits of functional specifications. " Describe the contents of a functional specification. " Describe the purpose and methods of validating a functional specification. Slide Objective To provide an overview of the module topics and objectives. 430 Module 12: Introduction to Functional Specifications ! !! ! Functional Specification Basics In this section In this section " Setting the Target " Goals of the Functional Specification " Baseline Early, Freeze Late " Benefits of the Functional Specification As you approach the milestone for the Planning Phase, the focus of the project team begins to shift from design to development. Physical design views the solution from the perspective of the development team. That perspective is ultimately presented in the functional specification. In this section, you will learn about the functional specification — its purpose, its content, and its value. Slide Objective To provide an overview of the topics and activities in this section. Module 12: Introduction to Functional Specifications 431 Setting the Target Alice: “Would you tell me please, which way I ought to go from here?” Cat: “That depends a good deal on where you want to get to.” Alice: “I don’t much care where …” Cat: “Then it doesn’t matter which way you go.” Alice in Wonderland by Lewis Carroll Many projects are started informally and are frequently implemented without a plan. They do not have a well-defined destination. The success of these projects is questionable from the start. To ensure the success of your project, you need not only a design process, but also a method of communicating the details of the desired result — the destination — to the development team. The vehicle for that communication is the functional specification. Slide Objective To illustrate the importance of having a well-defined plan so that the team knows when it has been successful. Lead-in Any successful project must have an agreed upon destination. 432 Module 12: Introduction to Functional Specifications Goals of the Functional Specification " Describe, in explicit detail, the solution to be built " Identify the project scope " Serve as a primary deliverable of the Planning Phase of the MSF Process Model " Provide the basis for other project plan documents, such as the project schedule " Serve as a form of contract within the project team and between the project team and the customer " Function as a living document during development The functional specification is the culmination of the design work accomplished through the Planning Phase of the MSF Design Process. It describes the solution that is to be developed and provides the design details that the developers need. The functional specification also establishes the scope of the project, identifying what should and should not be included in the application. Other planning documents, such as the project schedule and project plan, are created based on the details of the functional specification. Furthermore, because the functional specification requires the approval of the team and the customer, it serves as a form of contract among all the stakeholders. Although the functional specification describes the solution, it is certainly not a static document. It can, and should, be modified during the Developing Phase to reflect any design changes that occur. Slide Objective To describe the functional specification. Module 12: Introduction to Functional Specifications 433 Baseline Early, Freeze Late " Baseline when there is enough information to move forward " Freeze when it is too risky or costly to make additional changes " Avoid analysis paralysis " Allow for an iterative versioning process " Develop a change-control process The project team should baseline the functional specification as soon as there is enough information to move forward and freeze it only when leaving it open to change poses an unacceptable project risk. Due to the constant innovation that occurs on a development project, functional specifications are inherently incomplete. If you spend too much time analyzing requirements, though, no actual development will get done. By baselining the functional specification early, you are creating a fairly stable description of the solution. By freezing it late, you can modify the functional specification as changes occur. Remember to enforce some type of change-control process on the functional specification. Slide Objective To describe how the functional specification should be treated in terms of change control. Lead-in The functional specification must be allowed to change and grow as the project progresses. The recommended way of accomplishing this is by baselining the functional specification as early as is reasonable but freezing it as late as possible. Note 434 Module 12: Introduction to Functional Specifications Benefits of the Functional Specification " Clarifies what should be built at an appropriate level of detail " Communicates the solution to all interested parties " Drives and records the agreement on the proposed solution " Facilitates parallel development " Drives early project trade-offs " Assists in managing change during development The functional specification describes the solution in a clear and precise way so that the development team can build the solution that the project stakeholders expect to be built. The functional specification also serves as a method of communicating the project’s specifics to the team members, the customer, and all other stakeholders. It serves as a written agreement on the specific features that are to be included in this release of the solution. The functional specification facilitates parallel development by describing what the product will be; therefore, it is not necessary for one team to await the output of another team in order to begin building its piece of the solution. To help prevent integration problems, though, parallel development requires a high level of communication among the development teams. The functional specification drives project trade-offs by forcing the team to make hard decisions early in the development process, when changes are less risky and costly. The functional specification is useful as a change-control mechanism during implementation and development of the solution. If all changes to the solution features, and the reasons for the change, are recorded in the functional specification, then it provides a means of tracing changes for the stakeholders. Slide Objective To describe the benefits that a functional specification brings to a project. Lead-in A functional specification is sometimes seen as process overhead, but there are many benefits to having a one. Module 12: Introduction to Functional Specifications 435 Activity 12.1: Risk of No Functional Specification This activity emphasizes the importance of implementing a solution with a functional specification as well as the difficulties that arise when working without a completed functional specification. You will create an origami boat by using the instruments provided to you by the instructor. After completing this activity, you will be able to: " Articulate the value of a functional specification. Slide Objective To introduce this activity. Delivery Tip Remember that only some students should receive the functional specification. 436 Module 12: Introduction to Functional Specifications ! !! ! Functional Specification Creation " Contents of the Functional Specification " Design Process Output " Forms of the Functional Specification " Factors That Determine the Form " Functional Specification Pitfalls In this section In this section Now that you know what a functional specification is, and some of its benefits, you will focus on the process and contents of the functional specification. In this section, you will learn how to create a functional specification and some ways to communicate the functional specification to the development team. Slide Objective To provide an overview of the topics and activities in this section. [...]... project Module 12: Introduction to Functional Specifications 441 Functional Specification Pitfalls Slide Objective To describe some possible pitfalls to avoid when creating functional specifications Lead-in When creating the functional specification, you should be aware of a few potential pitfalls " Failing to involve the whole team in its validation " Failing to provide enough detail " Providing too much... by the functional specification 444 Module 12: Introduction to Functional Specifications Prototypes Slide Objective To explain that prototypes are a useful tool for validating a design " Validate the functional specification by: $ " Generating feedback $ Prototypes can assist in validating the functional specification Mitigating design risks $ Lead-in Achieving consensus Can take many forms $ Storyboard,... percentage of functionality Schedule demos to coincide with milestones Operational prototype Obtain feedback through alpha and beta of the system Convey high percentage of functionality Module 12: Introduction to Functional Specifications 445 Content Review Slide Objective To explain the role that content reviews play in validating the functional specification Lead-in Content reviews of the functional. .. Exams Module 12: Introduction to Functional Specifications Module 11: Designing the Presentation Layer Module 10: Completing the Physical Design Module 9: Designing Solutions with Microsoft Technologies Module 1: Course Overview Designing Business Solutions Module 8: Solution Design and the Component Object Model Module 7: Selecting Solution Technologies Module 2: Solution Design Using the MSF Module. .. functional specification can be communicated through many different forms and styles 439 440 Module 12: Introduction to Functional Specifications Factors That Determine the Form Slide Objective To describe the factors that determine the form of the functional specification Lead-in Several factors affect how the functional specification is presented " Ultimately must meet the needs of the team " Needs... and component topologies The physical user interface design, however, is generally not included here, because it is incorporated into the features section of the document Module 12: Introduction to Functional Specifications Forms of the Functional Specification Slide Objective To help the students understand that the functional specification should be in the form that is best suited to the development... high-priority features for the implementation team 448 Module 12: Introduction to Functional Specifications Review Questions Slide Objective To reinforce module objectives by reviewing key points " Describe the purpose and benefits of functional specifications " Describe the contents of a functional specification " Describe the purpose and methods of validating a functional specification Lead-in The review questions... caution in freezing the functional specification too early, because legitimate changes are often better understood as the product reaches implementation 442 Module 12: Introduction to Functional Specifications ! Functional Specification Validation Slide Objective To explain the purpose of this section and what students will learn in this section " The Search for Consensus " Prototypes " Content Reviews... 12: Introduction to Functional Specifications ! Review Slide Objective To reinforce module objectives by reviewing key points Lead-in In this section, you will learn some practical guidelines for practicing the concepts of this module, and you will test yourself on your understanding of those concepts " Guidelines " Review Questions " Looking Forward In this section In this section Module 12: Introduction. .. Introduction to Functional Specifications 447 Guidelines Slide Objective To present some general guidelines related to the information in this module Lead-in The following are some general guidelines to consider " Understand the requirements of the business and user " Iterate often during creation to encourage feedback " Include mandated project requirements as explicit design goals " Create prototypes to articulate . Module 12: Introduction to Functional Specifications 428 Module 12: Introduction to Functional Specifications Module Overview Module. Specification Creation Module 12: Introduction to Functional Specifications Module 12: Introduction to Functional Specifications 429 ! !! ! Overview " Functional