Requirements engineering tasks:
1.Inception: - Inception means beginning. It is usually said that requirement engineering is a communication intensive activity. The customer and developer meet and they the overall scope and nature of the problem statements. By having proper inception phase the developer will have clear idea about the system and as a result of that better understanding of a system can be achieved. Once the system is clear to the developer, they can implement a system with better efficiency.
2. Elicitation: - Elicitation task will help the customer to define the actual requirement of a system. To know the objectives of the system or the project to be developed is a critical job. This phase will help people to determine the goal of a system and clear idea about the system can be achieved.
3.Elaboration: - The information obtained from the customer during inception and elicitation is expanded and refined during elaboration. This requirement engineering activity focuses on developing a refined technical model of software functions, features and constraints.
4. Negotiation: - This phase will involve the negotiation between what user actual expects from the system and what is actual feasible for the developer to build. Often it is seen that user always expect lot of things from the system for lesser cost. But based on the other aspect and feasibility of a system the customer and developer can negotiate on the few key aspects of the system and then they can proceed towards the implementation of a system.
5. Specification: - A specification can be a re-written document, a set of graphical models, a formal mathematical model, a collection of usage scenario, a prototype, or any combinations of these. The specification is the final work product produced by the requirement engineers. It serves as the foundation for subsequent software engineering activities. It describes the function and performance of a computer-based system and the constraints that will govern its development.
6.Validation: - The work products produced as a consequence of requirements engineering are assessed for quality during a validation step. Requirements validation examines the specification to ensure that all software requirements have been stated unambiguously; that inconsistencies, omissions and errors have been detected and corrected, and that the work products conform to the standards established for the process, the project, and the product.
7. Requirements management: - Requirement management begins with identification. Each requirement is assigned a unique identifier. Once requirement have been identified, traceability tables are developed.
0 Comments