1 / 16

Prepared by Stephen M. Thebaut, Ph.D. University of Florida

Robertson & Robertson: Chapter 16, Communicating the Requirements Software Specification Lecture 33. Prepared by Stephen M. Thebaut, Ph.D. University of Florida. Formality Guide. Software Specification: R&R Chapter 16. Turning Potential Requirements into Written Requirements.

lyndaw
Download Presentation

Prepared by Stephen M. Thebaut, Ph.D. University of Florida

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Robertson & Robertson:Chapter 16, Communicating the Requirements Software SpecificationLecture 33 Prepared by Stephen M. Thebaut, Ph.D. University of Florida

  2. Formality Guide Software Specification: R&R Chapter 16

  3. Turning Potential Requirements into Written Requirements Software Specification: R&R Chapter 16

  4. The Requirements Knowledge Model Software Specification: R&R Chapter 16

  5. Capturing Requirements in Written Form Software Specification: R&R Chapter 16

  6. Writing the Requirements • Written for the client, using the client’s language, in a consistent format. • A “fit criterion” is also provided to quantify the requirement for designers and to ensure testability. • Tools: Requirements Specification Template (ala IEEE Guideline) and Shells (template for individual requirements) Software Specification: R&R Chapter 16

  7. Volere Shell in its Snow Card Form Software Specification: R&R Chapter 16

  8. Customer Satisfaction and Dissatisfaction Scales Software Specification: R&R Chapter 16

  9. A complete (atomic) functional requirement written on a snow card Software Specification: R&R Chapter 16

  10. A complete (atomic) non-functional requirement written on a snow card Software Specification: R&R Chapter 16

  11. Using a snow card as the container for a User Story Software Specification: R&R Chapter 16

  12. Requirements Specification Template Table of Contents • Purpose of Project • Stakeholders • Mandated Constraints • Naming Conventions & Terminology • Relevant Facts & Assumptions • Scope of Product • Business Data Model & Data Dictionary • Scope of the Work Functional Reqmts Look & Feel Reqmts Usability & Humanity Reqmts Performance Reqmts Operational & Environ. Reqmts Maintainability & Support Reqmts Security Reqmts Cultural Reqmts Software Specification: R&R Chapter 16

  13. Requirements Specification Template Table of Contents (cont’d) • Legal Reqmts • Open Issues • Off-the-Shelf Solutions • New Problems • Tasks • Migration to New Product Risks Costs User Documentation & Training Waiting Room (reqmts for future releases) Ideas for Solutions Software Specification: R&R Chapter 16

  14. Assembling the Specification Software Specification: R&R Chapter 16

  15. Considering the specification as a whole Software Specification: R&R Chapter 17

  16. Robertson & Robertson:Chapter 16, Communicating the Requirements Software SpecificationLecture 33 Prepared by Stephen M. Thebaut, Ph.D. University of Florida

More Related