ABSTRACT

The product mission statement or Conops acts as a focal point for all involved in the system, and they allow us to weigh the importance of various features by asking the question 'how does that functionality serve its intent'. This chapter identifies the nature of stakeholders, and more especially the stakeholders for whom the system is being built, the customers. A necessary first step in identifying stakeholders is to create a high-level systems model. A context diagram is a visual representation diagram for a system of interest showing system boundaries and interactions with other systems, people, and the environment. Stakeholders represent the set of individuals who have some interest (a stake) in the success (or failure) of the system in question. A stakeholder/user class subdivision is usually necessary when the classes are large and/or heterogeneous. The primary needs identified for stakeholders will inform the selection and scope of requirements elicitation activities going forward.