TOPIC 2 : Requirement Engineering
저자: Nur Khairunisa Iskandar
1. is defined as a systematic and disciplined approach to the specification and management of requirement with specific goals.
1.1. knowing the relevant requirement achieving a consensus among the stakeholder about these requirement documenting.
1.2. is to understand and document the stakeholders desires and needs the specifying and managing requirement to minimize the risk to delivering a system.
2. Requirement
2.1. is a condition or a capability needad by a user to solve a problem or achieve an objective.
3. Stakeholder
3.1. is a person or an organisation that has an (direct or indirect) influence on the requirement of the system.
4. 4 main activities of requirement engineering.
4.1. 1. Elicitation
4.1.1. is all about engaging with stakeholders to elicit and understand their business needs and requirement.
4.2. 2. Documentation
4.2.1. is all about capturing the requirement in documented format which will make clear sense to the business stakeholders as well as the technical teams.
4.3. 3. Validation & Negotiation
4.3.1. is all about ensuring that what your have documented as requirement are valid and agreed by all stakeholders.
4.4. 4. Management
4.4.1. involves managing any changes that might arise in relation to your requirement it is vital that the requirement engineer learn to manage requirement in a systematic and transparent.