1. BTS330: Business Requirements Analysis using OO Lecture 5: The Importance of Stakeholders

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

3. Identifying Requirements  Objective of the requirements capture and 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. * Use Case Modeling, by Bittner & Spence, page 5.

8. The Problem Statement  “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.

9. 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.

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

12. Identifying System Requirements  Features: –“Informal statements of capabilities of the system used often for marketing and product-positioning purposes as a shorthand for a set of behaviors of the system.” Use Case Modeling, by Bittner & Spence, pages 5 - 6.

13. 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.

15. 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.

16. 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.

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

18. What is project scope? A definition of the boundaries of the project

19. 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

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

21. Take orders via phone, fax, email. Orders are from U.S. and Canada Payment by credit card only. Customers are companies, not individuals Report on orders for a given time frame ($ ordered, qty ordered, products ordered—most/least popular) Sales Sales People Packaging & Shipping Shippers Orders picked, packaged with packing slip, labeled with shipping address Shipping outsourced—use only UPS/Fedex (US) Shipping reports generated for a given timeframe Product Promotion Promotion Staff For new products: photograph, add product to database, create pricing Create quarterly product catalogue Maintain a list of potential customers Maintain actual customers with customer preferences. Manage ads—mailings, emails, web??? Track competition Materials Purchasing Purchasers Manage Materials List Order Materials—create a PO (may be from a purchase requisition) Receive materials—receive against the PO. Generate quarterly reports—materials purchased and received, materials list. Production Potters Scheduled by production manager Create regular products Create and test new products and materials Use materials but don’t track them Updates production daily—what is in progress and what is completed. For completions, inventory of finished product is updated. Needs to be aware of daily orders Creates purchase requisition for materials on an as needed basis. Reports on and disposes of unused materials. Production Manager Planning Sales People Potters Meet each quarter to discuss: what products should be continued/discontinued; what products should be added; what the competition is doing; product pricing. Create a product list for next quarter Create a preliminary materials list for next quarter (based on products) Promotion Staff Production Manager GANDELF POTTERY & CERAMICS

22. 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 Use Case Diagrams –Ask, “Is problem understood?”

23. 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!

24. What defines project success?  On time  Within budget  Expected results achieved

25. The Reality  Only 16.2% of all IT projects succeed! –Fully functional, on time, within budget  Some studies show this as low as 10%.

26. 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.

27. 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.

28. 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.

29. Categories of Stakeholders  Five primary categories –Users –Sponsors –Developers –Authorities –Customers

30. 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

31. 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

32. User Stakeholders  Non-human users –Mechanical devices that the system must interact with –Other business areas –Other systems

33. 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

34. Developer Stakeholders  Those involved in the production and maintenance

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

36. Customer Stakeholders  Those doing business with the company

37. 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.

38. 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.

39. 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 63 - 64.

40. 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.

41. Constraints: The Grim Reality  Developers are not given all the time in the world, all the money in the world, and all the best resources that money can buy so that they can build the best system ever built!

42. Constraints  “ are restrictions on the degree of freedom the developers have in providing a solution….” *  come directly from the economic, technological, political, and business environment into which the system will be introduced * Use Case Modeling by Bittner and Spence, page. 16.

43. More Reasons to Involve Stakeholders and Users  “…you must understand the economic, technological, political, and business environment into which the system will be introduced and how that environment will be changed by the new system.” * * Use Case Modeling by Bittner and Spence, page. 15.

44. Stakeholders & Users are the ones who can tell you the economic, technological, political, and business environment into which the system will be introduced and how that environment will be changed by the new system.

45. Constraints  “Constraints are not related to the fulfilling the stakeholders’ needs; they are restrictions imposed on the project by external forces.” Use Case Modeling by Bittner and Spence, page. 77.

46. Constraints Include Business and Economic: Cost and pricing, availability, marketing and licensing issues Use Case Modeling by Bittner and Spence, page. 77.

47. Constraints Include Environmental: External standards and regulations that are imposed on the development project Use Case Modeling by Bittner and Spence, page. 78.

48. Constraints Include Technical: The technologies that the project is forced to adopt or the processes that the project has to follow Use Case Modeling by Bittner and Spence, page. 78.

49. Constraints Include System: Compatibility with existing systems and operating environments Use Case Modeling by Bittner and Spence, page. 78.

50. Constraints Include Schedule and Resources: Dates the project has been committed to or limitations on the resources that the project must use Use Case Modeling by Bittner and Spence, page. 78.

51. Why Stakeholders Impose Constraints Politics Constraints my be placed on the project by the relationships among the stakeholders rather than the technical or business forces shaping the project Use Case Modeling by Bittner and Spence, page. 78.

52. Why Stakeholders Impose Constraints Organizational Policies may be in place that constrain the way that the product can be developed. A company may have made a policy decision to move toward specific techniques, methodologies, standards, or languages Use Case Modeling by Bittner and Spence, page. 78.

53. Why Stakeholders Impose Constraints Strategic Directions may be in place that constrain the way that the project is to use specific technologies and suppliers (such as the decision by the Dealer Principal to outsource all IT to your company) Use Case Modeling by Bittner and Spence, page. 78.

54. Why Stakeholders Impose Constraints Organizational Culture may itself constrain the project by limiting the way that the project must address the project must address the problem. (There is a limit to the amount of change that people can cope with at any one time.) Use Case Modeling by Bittner and Spence, page. 78.

55. Constraints  Constraints = Reality Checks!