Requirements engineering is the process of interacting with end-users and customers to establish the system requirements, the services that will be provided by the system and the various design constraints. The system requirements mirror the environment upon which the system operates, and it will involve a range of stakeholders, including administrators, end-users, managers, test engineers, system engineers, maintenance engineers, and bank employees. These are the person with direct or indirect influence on the system requirement. The requirement elicitation and analysis had four primary processes.
The process began by collection of the requirements through interviews with existing customers, potential customers, bank employees, and managers. The related requirements into sub-categories prioritized and refined through the removal of unambiguous requirements, which could potentially raise conflicts.
It is the iterative coupled with feedback process with criticism and feedback from all stakeholders taken into consideration. The cycle begins with identification of requirement and terminates with the requirement document. The cycle culminates with the completion of the requirement document.
It is the process of coordinating with clients and collecting requirement about the proposed system and existing system. It was implemented through interviews, and analysis of prototypes, as well as scenarios, which were helpful to stakeholders in comprehending the proposed changes.
The requirement engineering team posed questions to stakeholders regarding the proposed system. The questions posed were both close-ended and open-ended. The former were pre-defined unlike the former, which were more generic and were useful in exploring issues that are less clear in an informal way. The interview incorporated both types of questions and it was a great opportunity to identify the needs of stakeholders, and ways in which they will interact with the system, as well as the challenges they confront with the new system.
Use Case and Scenarios
Scenarios and Use Case were used jointly to identify the interactions between users and the system. Some of the actors identified included administrators, end-users, managers, test engineers, system engineers, maintenance engineers, and bank employees. Use case was efficient in the elicitation of requirements, although not for non-functional requirements.
Requirement Classification and Organization
Some of the issues that were raised in regards to system requirement included but not limited to the following:
- System performance
- Security requirements
- System availability
- Emergent properties
- Safety requirements
- Quality attributes
- Maintenance costs
- Customer satisfaction
System Requirement Document (Outline)
Cite this page
Requirements Engineering Paper Example. (2022, May 09). Retrieved from https://proessays.net/essays/requirements-engineering-paper-example
If you are the original author of this essay and no longer wish to have it published on the ProEssays website, please click below to request its removal:
- Scrum Process Article Analysis Essay
- Paper Example on Legal Issue in Information Security
- Essay Sample on Leadership Matrix
- Team Charters: Roadmaps to Successful Progress - Essay Sample
- Leadership in Nursing: Theories & Application - Essay Sample
- Essay Example on Poorly Articulated Goals/Objectives: Impact on Public Health Programs
- Essay Sample on Microsoft: Leadership & Management for Optimal Benefit