Requirement_engg3_MscIt2
Good evening students!!
The requirement engineering tasks we have already discussed are
-
Inception
-
Elicitation
-
Elaboration
-
Negotiation
-
Specification
-
Validation
-
Requirement Management
We will be discussing the next two topics here
3.Elaboration:
The information obtained from the customer during inception and Elicitation is expanded are refined during elaboration.This requirements engineering activity focuses on developing a refined technical model of software functions, features and constraints.Elaboration is an analysis modeling action that is composed of a number of modeling and refinement tasks.Elaboration is driven by the creation and refinement of user scenarios that describes how end users will interact with the system. Each user scenario is parsed to extract analysis classes business domain entities that are visible to the end user. The end result of elaboration is an analysis model that defines the informational, functional and behavioral domain of the problem.
4. Negotiation
Since the normal circumstances do reveal that customers and users face conflict regarding the achievement through the software engineering practices because of limited business resources. So requirement engineer must reconcile these conflicts through the process of negotiation. Customers, users and other stakeholders are asked to rank the requirements and then discuss conflicts in priority. Risks associated with each requirements are identified and analyzed. Rough estimates are made and used to assess the impact of each requirement on project cost and delivery time. Requirements are eliminated, combined and modified so that each party achieves some measure of satisfaction.