= Systematic requirements analysis is also known as requirements engineering
=>The term requirements analysis can also be applied specifically to the analysis proper, as opposed documentation of the requirements, it is also a critical to the success of a development project
Stakeholders – are persons or organizations (legal entities such as companies, standards bodies) which have a valid interest in the system.
It is increasingly recognized that stakeholders are not limited to the organization employing the analyst. <ul><li>Other stakeholders will include: </li></ul><ul><li>anyone who operates the system (normal and maintenance operators) </li></ul><ul><li>anyone who benefits from the system (functional, political, financial and social beneficiaries) </li></ul>
<ul><li>anyone involved in purchasing or procuring the system. In a mass-market product organization, product management, marketing and sometimes sales act as surrogate consumers (mass-market customers) to guide development of the product </li></ul><ul><li>organizations which regulate aspects of the system (financial, safety, and other regulators) </li></ul><ul><li>people or organizations opposed to the system (negative stakeholders) </li></ul><ul><li>organizations responsible for systems which interface with the system under design </li></ul>
System Context Diagram A System Context Diagram (SCD) in software engineering are diagrams that represent the actors outside a system that could interact with that system
System context diagrams are related to Data Flow Diagram, and show the interactions between a system and other actors with which the system is designed to interface and it can be helpful in understanding the context which the system will be part of.