gathering the right requirements

17
GATHERING THE RIGHT REQUIREMENTS Tips for uncovering the ‘real’ requirements Amin Kazemi http://www.linkedin.com/in/aminkazemi

Upload: amin-kazemi

Post on 26-May-2015

340 views

Category:

Technology


0 download

DESCRIPTION

A deep insight into the much neglected non-functional requirements. A categorising effort of requirements order to assist practitioners in their day to day requirements elicitation process.

TRANSCRIPT

Page 1: Gathering the Right Requirements

GATHERING THE RIGHT REQUIREMENTSTips for uncovering the ‘real’ requirements

Amin Kazemihttp://www.linkedin.com/in/aminkazemi

Page 2: Gathering the Right Requirements

Presentation ContentThe content of this presentation is based on the published book, ‘Mastering the Requirements Process – Getting Requirements Right’ by Suzanne Robertson and James Robertson (Addison-Wesley, 2012)

All Information presented today is readily available on the public domain.

Page 3: Gathering the Right Requirements

OverviewSoftware can solve almost any problem. The problem is that we don't always understand what the problem is. Understanding the problem - the real problem - is the role of the requirements process.

Page 4: Gathering the Right Requirements

Functional Requirements Functional requirements are

the fundamental or essential subject matter of the product

They describe what the product has to do or what processing actions it is to take.

Page 5: Gathering the Right Requirements

Volere Snow Card

Page 6: Gathering the Right Requirements

Non-Functional Requirements Non-functional requirements

are the properties that the functions must have, such as performance and usability

They describe how well your product does the things it does

Page 7: Gathering the Right Requirements

Link between functional and non-functional

Page 8: Gathering the Right Requirements

Look and Feel Requirements

The product shall comply with corporate branding standards

Page 9: Gathering the Right Requirements

Usability Requirements

The product shall be useable by users with limited experience of using computers

Page 10: Gathering the Right Requirements

Performance Requirements

The product shall support 2,000 concurrent users

Page 11: Gathering the Right Requirements

Operational Requirements

The product shall be used by Field Staff at night and during rain, heat, and ‘Melbourne’ conditions

Page 12: Gathering the Right Requirements

Maintainability Requirements

The product shall be readily portable to smartphone handhelds as applications and web-based systems.

Page 13: Gathering the Right Requirements

Security Requirements

The product shall ensure that only authorised users have access to the OMS system.

Page 14: Gathering the Right Requirements

Cultural Requirements The product shall not

display religious symbols or words associated with mainstream religions.

The product shall use Australian English spelling, not American.

Page 15: Gathering the Right Requirements

Legal Requirements

The product shall comply with the Australian Privacy Act as amended.

The product shall comply with W3C recommendations

Page 16: Gathering the Right Requirements

Finding the non-functional’s

Like all requirements, the non-functional ones can come to light at any time, Nevertheless, there are certain places where we can look that give us better opportunities to discover them,

Page 17: Gathering the Right Requirements

Amin Kazemi

http://www.linkedin.com/in/aminkazemi