BTS330

Lecture: The Importance of StakeholdersSYS366

Identifying RequirementsObjective of the requirements capture and analysis phases is to understand business processes and develop requirements for the new system

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.

Categories of StakeholdersFive primary categoriesUsers Sponsors DevelopersAuthoritiesCustomers User StakeholdersThose who actually use the systemTechies Techie is a term, derivative of the word technology, for a person who displays a great, sometimes even obsessive, interest in technology, high-tech devices, and particularly computers. Some techies express a disregard for any technology that could possibly be considered obsolete, even if the technology or process in question might only be considered obsolete within the techie community. Consequently, techies are also often early adopters.Interested in using all of the features of the system; in pushing it to the limit of its capabilitiesUser stakeholdersStandard UsersNot 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

Standard UsersThose in day-to-day business operationsuse and change informationThose using queriesview calculated/collected informationManagement use reports, statisticsdemand controlsExecutivesstrategic issues

Non-human users

Mechanical devices that the system must interact withOther business areasOther systemsSponsor StakeholdersIndirect users Or those actually paying for the development of the systemOr those affected only by the business outcomes that the system influences

Sponsor StakeholdersBusiness Managers, investorsDepartment heads champions

Developer StakeholdersThose involved in the production and maintenanceAuthority StakeholdersThose who are expert in a particular aspect of the problem or solution domainMinistriesTechnical expertsDomain expertsCustomer StakeholdersThose doing business with the companyQuestions 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.

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.

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.

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.More Reasons to Involve Stakeholders and Usersyou 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.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.