1. CSE Senior Design I Senior Design Specifications: A Guide Instructor: Vassilis Athitsos Several of the slides in this module are a modification and amplification of slides prepared by Mr. Tom Rethard for use in a prior Senior Design Class. They were originally for use with A Discipline for Software Engineering (Watts S. Humphrey), sponsored by the U.S. Department of Defense. Original slides are copyright SEI; modifications are Copyright © 2002, T. Rethard. Further modifications by Mike O’Dell and Vassilis Athitsos. All Rights Reserved.

2. 1 CSE 4316 2 Product Specifications what  Provide the details of what will be done:  Requirements (SRS)  Architecture (ADS) how  Detailed Design Documentation (more of the how at this stage)  Provides the basis for system testing and acceptance

3. 1 CSE 4316 3 Stakeholders  Any person or organization that has a vested interest in the success of you project  Your customer or sponsor  Your company  Your company’s owners/stockholders  Your management

4. 1 CSE 4316 4 What is a System Requirements Specification (SRS)? detailed description  A detailed description of the features and functions of a product, incorporating:  End-user and sponsor input  Developer input  Management input  Standards and processes commitment  Your documented commitment to deliver contract  Your contract with your stakeholders that identifies WHAT you will create (See SRSs from prior teams on class website.)SRSs

5. 1 CSE 4316 5 Characteristics of a Good Requirement  Verifiable  Verifiable: stated in a way that allows for independent verification that the system meets or exceeds the stated requirement.  Justifiable  Justifiable: necessary, rather than simply desirable  Unambiguous  Unambiguous: stated such that multiple interpretations are precluded

6. 1 CSE 4316 6 Characteristics of a Good Requirement  Consistent  Consistent: no conflict with any other requirement  Modifiable  Modifiable: should be stated in a way that allows for change based on technical/business considerations.  Hierarchically Traceable  Hierarchically Traceable: should define a single attribute, traceable back to a higher level requirement.

7. 1 CSE 4316 7 Tips for Successful Requirement Determination features/functions  Start by establishing what the team thinks the features/functions of the system should be  Brainstorm as team and write everything down  Keep a simple list (such as the requirements worksheet on the website)requirements worksheet on the website sponsor  Meet with your sponsor to review/modify your list and discuss alternatives  Add any features/functions that the sponsor believes are required

8. 1 CSE 4316 8 Tips for Successful Requirement Determination ancillary requirements  Consider and add ancillary requirements  E.g., performance, packaging, look and feel “non- functional” requirements  Discuss and add as necessary any “non- functional” requirements  E.g., standards that you must adhere to, maintenance and support, safety analyze the feasibility  Discuss and analyze the feasibility of meeting or exceeding each requirement within the budget, time and skills allowed.

9. 1 CSE 4316 9 Tips for Successful Requirement Determination DO NOT DO NOT collect requirements by attempting to fill out the SRS Guide!  List and understand them, THEN write the document

10. 1 Resources  On course website:  Guide and template for Systems Requirements Specification, accessible from the "Useful Documents" link.  Document libraries from previous senior design projects. Also accessible from the "Useful Documents" link. CSE 4316 10