Presentation is loading. Please wait.

Presentation is loading. Please wait.

Introduction to Software Requirements.  It depends who you ask…  Requirements try to describe the whole system you are creating.  You need to decide.

Similar presentations


Presentation on theme: "Introduction to Software Requirements.  It depends who you ask…  Requirements try to describe the whole system you are creating.  You need to decide."— Presentation transcript:

1 Introduction to Software Requirements

2  It depends who you ask…  Requirements try to describe the whole system you are creating.  You need to decide on a definition with all project stakeholders…your requirements document will be based on that definition.

3  Intersection of interests of stakeholders:  Customers (acquire the software)  Users  Analysts, developers, testers  Legal staff  And so on…

4  Foundation for the software system  Define them well  terrific product, happy customers/stakeholders  Define them poorly  disaster

5  Business Organization  vision/scope  User  use cases  Functional  software specs

6  Nonfunctional  Business rules  Quality attributes  External interfaces  Constraints  And so on…

7  Foundation for the software system  Define them well  terrific product, happy customers/stakeholders  Define them poorly  disaster

8  Business Organization  vision/scope  User  use cases  Functional  software specs

9  We will produce a Requirements Document as per a given template (posted to the bts330 site)

10  Develop Requirements  Elicitation  Analysis  Specification  Validation

11  Manage Requirements  Define baseline—SCOPE  Manage changes (**NOT EASY)  Manage project activity  Manage project plan

12  Detailed requirements are difficult!!!  “…no other part of the work so cripples the resulting system if they’re wrong. No other part is more difficult to rectify later.”  (text, p. 15)

13 RequirementsDesignCodeTestOperation Relative Cost Source: Text, p. 17

14  Insufficient user involvement  Scope creep  Ambiguous requirements  Gold plating  “Paper Napkin” syndrome  Overlooked users  Inaccurate planning (bad promises)

15 Pain Time Good Requirements Poor Requirements

16  Take responsibility for ensuring understanding  Be respectful  Give honest/correct information ▪ See text pg 32, “bill of rights”

17  Signing off requirements  is NOT a weapon but a milestone  establishes a baseline  provides the basis for change management


Download ppt "Introduction to Software Requirements.  It depends who you ask…  Requirements try to describe the whole system you are creating.  You need to decide."

Similar presentations


Ads by Google