1 Identifying System Requirements

2 Agenda Identifying System Requirements –Stakeholder Needs –Features Project Scope Stakeholder Classifications

3 Identifying Requirements Objective of the analysis phases is to understand business processes and develop requirements for the new system

4 Identifying System Requirements “A requirement is a desired feature, property or behavior of a system.” * * Unified Modeling Language

5 Identifying System Requirements A requirement “is either derived directly from stakeholder or user needs Or stated in a contract, standard, specification, or other formally imposed document.” * * Use Case Modeling, by Bittner & Spence, page 5.

6 Identifying System Requirements Stakeholder Need: A reflection of the business, personal or operational problem…that must be addressed to justify consideration, purchase or use of the new system. * Use Case Modeling, by Bittner & Spence, page 72.

7 Identifying System Requirements “If you want to satisfy [Stakeholders’] real needs, you must understand the problem that they are trying to solve.” * *Use Case Modeling by Bittner and Spence, page. 69.

8 Identifying System Requirements Capturing stakeholder needs allows us to understand how and to what extent the different aspects of the problem affect different [categories] of stakeholders. * * Use Case Modeling, by Bittner & Spence, page 72.

9 Identifying System Requirements Stakeholder needs are an expression of the true ‘business requirements’ of the system * * Use Case Modeling, by Bittner & Spence, page 72.

10 Identifying System Requirements Features: –“The high-level capabilities (services or qualities) of the system that are necessary to deliver benefits to the users and that help to fulfill the stakeholders and user needs.” * * Use Case Modeling, by Bittner & Spence, page 74.

11 Identifying System Requirements “Features represent some area of functionality of the system that, at this time, is important to the users of the system” * * Use Case Modeling, by Bittner & Spence, page 75.

12 Identifying System Requirements “The immediate and informal nature of features makes them a very powerful tool when working with the stakeholders and customers in defining what they want from a system’s release.” * * Use Case Modeling, by Bittner & Spence, page 76.

13 Identifying System Requirements “ Features provide the fundamental basis for product definition and scope management ”* * Use Case Modeling, by Bittner & Spence, page 76.

14 What is project scope? A definition of the boundaries of the project

15 When do you define scope? You define scope at the beginning of the project You manage and control scope throughout the life of the project

16 How do you define scope? You talk to your stakeholders!

17 How do you define scope? In addition to talking to your stakeholders, You research and clarify You document Identify expected capabilities of new system –Develop Business Use Case Diagrams –Ask, “Is problem understood?”

18 Why is scope important? One of the biggest factors in project success Good scope definition = good client and IT understanding of what will be delivered and when Ensures you understand WHERE you are going, HOW you will get there and WHEN you will arrive This is where most projects start to fail!

19 To Avoid Disaster “The team must –Establish a good understanding of the stakeholder community –Demonstrate an understanding of the problem to be solved…”* * Use Case Modeling by Bittner and Spence, p. 50.

20 To Avoid Disaster “The team must –Capture the real needs of the stakeholders and the system features required to fulfill them –Ensure that the views of the stakeholder community are actively and appropriately represented throughout the project” * * Use Case Modeling by Bittner and Spence, p. 50.

21 Who is a Stakeholder? “ An individual who is materially affected by the outcome of the system or the project (s) producing the system” * Or the people who suffer from the problem being addressed * * Use Case Modeling by Bittner and Spence, p. 51.

22 Categories of Stakeholders Five primary categories –Users –Sponsors –Developers –Authorities –Customers

23 User Stakeholders Those who actually use the system Technology Adopters –Interested in using all of the features of the system; in pushing it to the limit of its capabilities Standard Users –Not interested in using all of the features of the system. Rather they want a system that allows them to perform their business processes simply and in the same way that they are used to performing them

24 Standard Users Those in day-to-day business operations –use and change information Those using queries –view calculated/collected information Management –use reports, statistics –demand controls Executives –strategic issues

25 User Stakeholders Non-living users –Mechanical devices that the system must interact with –Other business areas –Other systems

26 Sponsor Stakeholders Indirect users Or those actually paying for the development of the system Or those affected only by the business outcomes that the system influences

27 Sponsor Stakeholders Business Managers, investors Department heads “champions”

28 Developer Stakeholders Those involved in the production and maintenance

29 Authority Stakeholders Those who are expert in a particular aspect of the problem or solution domain –Ministries –Technical experts –Domain experts

30 Customer Stakeholders Those doing business with the company

31 Questions to Ask to Determine Stakeholders: Who will be affected by the success or failure of the new solution? Who are the users of the system? Who is the economic buyer for the system? Who is the sponsor of the development? * * Use Case Modeling, by Bittner & Spence, page 63.

32 Questions to Ask to Determine Stakeholders: Who else will be affected by the outputs that the system produces? Who will evaluate and sign off on the system when it is delivered and deployed? Are there any other internal or external users of the system whose needs must be addressed? * * Use Case Modeling, by Bittner & Spence, page 63.

33 Questions to Ask to Determine Stakeholders: Are there any regulatory bodies or standards organizations to which the system must comply? Who will develop the system? Who will install and maintain the new system? Who will support and supply training for the new system? Who will test and certify the new system? * * Use Case Modeling, by Bittner & Spence, pages

34 Questions to Ask to Determine Stakeholders: Who will sell and market the new system? Is there anyone else? Okay, Is there anyone else? * * Use Case Modeling, by Bittner & Spence, page 64.