• have an active interest in the system because they'll actually use it or are directly involved in processes that the system will change;
• must manage, introduce, operate, or maintain the system after its deployment;
• are involved in developing the system as an architect, developer, tester, quality engineer, or project manager;
• are responsible for the business or process that the system supports or automates;
• have a financial interest (for example, they've ordered the system, paid for it, or are responsible for its sale);
• constrain the system as regulators; or
• are negatively affected by the system (so-called negative stakeholders).
• If neglect might kill the project or render the system useless, the stakeholder's role is critical.
• If neglect would have a significant negative impact on the system, the stakeholder has a major role.
• If neglect would have marginal impact on the system, the stakeholder's role is minor.
Martin Glinz is a full professor of informatics at the University of Zurich. He chairs the steering committee of the IEEE International Requirements Engineering Conference and was program chair of RE '06. His interests include requirements and software engineering, in particular modeling and validation, and software engineering education. He received his Dr. rer. nat. from RWTH Aachen University. Contact him at the Dept. of Informatics, Univ. of Zurich, Binzmühlestrasse 14, 8050 Zurich, Switzerland; email@example.com.
Roel J. Wieringa is a full professor of information systems at the University of Twente. His research interests include value-based requirements engineering and business-IT alignment. He received his PhD in computer science from the Free University Amsterdam. He also served as a program chair and steering committee chair of the IEEE International RE Conference. Contact him at the Dept. of Computer Science, Faculty of Electrical Eng., Mathematics and Computer Science, Univ. of Twente, PO Box 217, 7500 AE Enschede, Netherlands; firstname.lastname@example.org.