1 / 16

Requirements specifications

Requirements specifications. Outline of the “Volere Document”. Project Drivers. The Purpose of the Project The Client, the Customer, and Other Stakeholders Users of the Product . Project Constraints. Mandated Constraints Naming Conventions and Definitions

spiro
Download Presentation

Requirements specifications

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. Requirements specifications Outline of the “Volere Document”

  2. Project Drivers • The Purpose of the Project • The Client, the Customer, and Other Stakeholders • Users of the Product

  3. Project Constraints • Mandated Constraints • Naming Conventions and Definitions • Relevant Facts and Assumptions

  4. Functional-Non Functional Requirements • The Scope of the Work • The Scope of the Product • Functional and Data Requirements

  5. Nonfunctional Requirements • Everything that does not have to do with the functionality of the product • Ex: • Look and Feel Requirements • Usability and Humanity Requirements

  6. Project Issues • Every possible issues that might come up after the concretization of the problem • Ex: • Migration to the New Product • Risks • Costs

  7. Functional Requirements • Scope on the Work • Scope on the product • Functional and data requirements

  8. Scope on the Product (pp. 10)

  9. Functional and Data Requirements: Snowcards (pp. 11-15) • Requirement #: 1 F • Description: The system defines and proposes one or more schedules to student • Rationale: To help students select their courses • Originator: ITS, us and students • Fit Criterion: The system provides the user accurate acknowledgement of passed and future courses needed to complete their requirement. Also propose a schedule for the incoming semester that satisfies requirements and constraints • Customer satisfaction: 4 • Customer dissatisfaction: 2 • Priority: 4 (1 highest) • Supporting materials: Ryan report of meeting with ITS • Conflict: None

  10. Functional and Data Requirements: Snowcards (pp. 11-15) When courses are displayed, show the ratio of occupied over available

  11. Functional and Data Requirements: Snowcards (pp. 11-15) Possibility to reserve a certain percentage of the class for certain students (students majoring in the subject)

  12. Functional and Data Requirements: Snowcards (pp. 11-15) Email confirmation to the students is sent whenever a course is added or dropped

  13. Functional and Data Requirements: Snowcards (pp. 11-15) A report should be generated for the registrar indicating when waiting lists for courses become very long

  14. Non Functional requirements (pp.15-18) • Look and Feel • Usability and Humanity • Security • Cultural and political

  15. Functional and Data Requirements: Snowcards (pp. 11-15) Courses taken and courses still to be taken must be set apart in an obvious way

  16. Thank you Alessandro Cardone

More Related