CMPSCI 520/620

Fall 2003

Project II

Assigned: October 20, 2003

Due: November 24, 3003

 

Documents:

  1. Request for Proposal Academic Information System 17 April 2000 UC Santa Cruz
  2. Request for Bid Student Information System #SG97-40 3 March 1997 University of Massachusetts Amherst
  3. Software Requirements Specification Template for SRS for use with projects using use-case modeling by Leslee Probasco and Dean Leffingwell, Rational Software Corporation
  4. Combining Software Requirements Specifications with Use-Case Modeling By Leslee Probasco and Dean Leffingwell Rational Software
  5. Traceability Studies for Managing Requirements with Use Cases by Ian Spence, Rational U.K. and Leslle Probasco, Rational Canada, ©Copyright 1998 by Rational Software Corporation.
  6. IEEE Recommended Practice for Software Requirements Specifications, IEEE Std 830-1998, ©Copyright 1998 by The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street, New York, NY 10017-2394, USA

 

  1. Chose a strategy for developing the Software Requirements Specification:
    1. Features drive the Use Case Modeling
    2. Use Case Modeling to Interpret the Requirements
  2. For your subset of the specifications (either UMass or UCSC or some combination that includes the functions included in MaciaszekÕs example, e.g., course enrollment), select a team member (or two) to define a ÒVision DocumentÓ which describes the user's or customer's view of the product to be developed, specified at the level of key user needs (from the RFP/RFB) and features (to meet these needs) of the system. If you have selected Strategy-b, then you must state requirements associated with each feature. Use a format based on the IEEE Standard Section 3, Template A-2 (requirements) or A-5 (features) as appropriate.
  3. Beginning with the Vision document and using the Template, the remaining team members complete Sections 1 and 2:
    1. Introduction Section: Purpose, Scope, Definitions, Acronyms and Abbreviations, and provide References
    2. Overall Description: a list of names and brief descriptions of all use cases and actors, along with applicable diagrams and relationships
  4. In Section 3, all team members define, for each use case in Section 2, a use-case report, making sure that each feature or requirement is clearly labeled and traceable to the Vision document.
  5. Provide necessary appendices, including: a) Table of contents, b) Index, and c) use-case storyboards or user-interface prototypes, if needed. Explicitly state whether or not the appendices are to be considered part of the requirements