Business Level 3 Unit 2 P1

3. A Use Case is developed to support requirement specification. It is a detailed description of specifications in its simplest form using Realtime scenarios of the functionality requirements between the actors and

2. In consultation with users and stakeholders, establish the need for, and identify the requirements of, the new or modified administration system. System requirements and considerations may include, for example:

Gurjeet -kindly help to answer any questions raised by business since you are closer to Reg W

Fact-Finding and Reviewing existing system are the first step to get the requirement, after review the interview summaries, which include the main problems, unsystematic record keeping and standard in putting data into the system. According to the role system analyst (Rosenblatt, 2014), system analyst will associate with project manager in order to investigate and identify the issues that need to fix. Moreover, they will transform the business requirements into IT implementation, which will pass the requirement to the design process and prototype respectively.

To ensure a successful implementation, Clients are moved through several phases. Each phase allows Athreon and the Client to reach a series of milestones that culminate in achieving a mutually agreed upon objective. Each phase is distinct and clearly delineates specific steps, while allowing room for

Develops custom solutions to business problems or customer engagements through in-depth analysis, coordination and negotiation with key decision makers

Requirements Engineering (RE) is and very important phase in the software development because it is this process that gives us a base for the overall software development process. This process gets even difficult and it requires more attention when the stakeholders are separated in different geographical location and have different languages and live different cultures. Requirements engineering deals with getting the needs of the customer understand the requirements of the system to be developed. In this process we also have to understand the constraints and adapt to those constraints during the process. Global Software Development is making the practice of requirements engineering a vital one. D. Zowghi, (2003) states that as software development has progressed today, it can be said that

Building rapports with customers in order to keep loyal customers and gain more new customers for the business;

User involvement is a widely accepted principle in development of usable systems. However, it is a vague concept covering many approaches. An analysis of various UCD sources suggests that user involvement has generally positive effects, especially on user satisfaction, and some evidence exists to suggest that taking users as a primary information source is an effective means of requirements capture. However, the role of users must be carefully considered and more cost-efficient practices are needed for gathering users' implicit needs and requirements in real product development contexts.

User Requirements is where the client decides and specifies what the use want to be done. This is where the client lists a set of requirements that need to be met for the software. This is then put into stages to be completed.

The first step in requirement engineering process is requirements elicitation. Requirements should be gathered first then it can be analyzed, modeled and documented. In the requirement elicitation process, requirements are gathered through interviews, questionnaires, workshops, user observations, prototyping, brainstorming, use cases etc. Requirement elicitation practice can be used to the fullest extent when we follow some guidelines; some of those guidelines are,

2. ANALYSIS – This phase involves end users and IT specialists working together to gather, understand, and document the business requirements for the proposed system.

Through the phase of requirements determinations, requirements are gathered by the analysts to determine how system should behave/do from different ways. These different ways of gathering requirements include, gathering from current system users, from existing reports, from monitoring existing users and from existing procedures followed in the system. All these requirements which are gathered in different ways are cautiously documented and arranged for structuring.

In other words, Requirements traceability is the ability to capture the traces of requirements within a system or between the integrated systems during its development life cycle. Traceability is required to manage changes at various stages of the SDLC and is a part of Requirements Management

The term “Requirement Engineering” can be broken into parts and reviewed. ‘Requirements’ brings out the idea of meeting the user expectation in order to create a