Q. You are eliciting requirements for a new release of an existing product. For each of the requirements elicitation problems described below, list one elicitation technique that would address well each problem (one technique per problem). Briefly point out why this technique is suitable. You want to understand how users really use the existing system, as opposed to how they tell you they use the system You want to determine which are the most critical and needed features of a new propose

Q. You are eliciting requirements for a new release of an existing product. For each of the requirements elicitation problems described below, list one elicitation technique that would address well each problem (one technique per problem). Briefly point out why this technique is suitable. You want to understand how users really use the existing system, as opposed to how they tell you they use the system You want to determine which are the most critical and needed features of a new propose

Principles of Information Systems (MindTap Course List)

13th Edition

ISBN:9781305971776

Author:Ralph Stair, George Reynolds

Publisher:Ralph Stair, George Reynolds

Chapter12: System Acquisition And Development

Section: Chapter Questions

Problem 3TA: You and your team have been hired to perform a system investigation for a fast food restaurant that...

See similar textbooks

Similar questions

You are eliciting requirements for a new release of an existing product. For each of the requirements elicitation problems described below, list one elicitation technique that would address well each problem (one technique per problem). Briefly point out why this technique is suitable. You want to understand how users really use the existing system, as opposed to how they tell you they use the system You want to determine which are the most critical and needed features of a new proposed system.
Assume you were hired to design a Car Rental System. The system will keep track of the cars and the customers who will rent the cars. The system will be managed by an administrator and will be operated by several employees.consider the above the situation fill the below definations. (1) Identifer and name: (2) Initiator: (3) Goal: (4) precondition:(5) postcondition: (6) Assumptions: (7) Main Success Scenerio:(8) Extensions:
A Software Engineer is responsible for recommending the best strategy for obtaining requirements from your customers. However, your client is prepared to let your team to monitor their daily operations at the clinic in order to get the needs, even if they are not ready to commit to these activities. In this demand elicitation process, what two (2) methodologies do you think your team should use? Please explain your argument.
what are the Non-Functional requirements (performance, useability, availability, security ) from this scenario? The system should be user friendly, technology independent and platform independent. The system service should have availability most of the time in the day. It should be able to complete its on-going operations in spite of any error or problem within defined response time.
Requirements Analysis is the process of defining the expectations of the users for an application that is to be built or modified. It involves all the tasks that are conducted to identify the needs of different stakeholders. Therefore requirements analysis means to analyse, document, validate and manage software or system requirements. High-quality requirements are documented, actionable, measurable, testable, traceable, helps to identify business opportunities, and are defined to a facilitate systemdesign 6.1 Explain why it is important for systems analysts to document user requirements
Requirements Analysis Requirements Analysis is the process of defining the expectations of the users for an application that is to be built or modified. It involves all the tasks that are conducted to identify the needs of different stakeholders. Therefore requirements analysis means to analyze, document, validate and manage software or system requirements. High-quality requirements are documented, actionable, measurable, testable, traceable, helps to identify business opportunities, and are defined to a facilitate system design. . a) Explain why it is important for Systems Analysts to document user requirements. b) . As a Systems Analyst how do you provide a sound foundation for systems design?
The first step in the usability process is to study the intended users and use of the product. At a minimum, developers should visit a customer site so that they have a feel for how the product will be used. Individual user characteristics and variability in tasks are the two factors with the largest impact on usability, so they need to be studied carefully. When considering users, one should keep in mind that they often include installers, maintainers, system administrators, and other support staff in addition to the people who sit at the keyboard. The concept of "user" should be defined to include everybody whose work is affected by the product in some way, including the users of the system's end product or output even if they never see a single screen. Explain four (4) benefits when know the user.
What are various software requirement development activities? You are required to identify the requirement development activities associated with each of the following scenarios (requirement activities include Elicitation, Analysis, Specification and Validation) a. Jones is identifying all security related requirement and separating them from the performance related requirements. b. Merlin a team member is sent to client to observe the business case and collect typical user requirements. c. Leo is team member is working on requirement and ensuring that requirement collected should not be vague and unclear. d. Lee is conducting a facilitated meeting with the stakeholder to capture the requirements e. Amit a team member is distributing questionnaires to stack holder for gathering user requirements.
You are working on a project to develop a new or enhanced system to help people at your college, university, or organization to find jobs. The system must be tailored to your student or work population and be very easy to use. Describe how would you collect requirements for this system, and include at least five requirements in a requirements traceability matrix? Same is given below for RTM.
One of the most significant advantages of creating a prototype during requirements elicitation is that it enables customers and end users to play with the system. They may get a knowledge of how the system can be utilized to assist their job by seeing and interacting with it. In this section, we will discuss three (3) benefits and two (2) drawbacks of utilizing prototypes for requirements elicitation.
You are gathering requirements for a new version of an existing product that is presently being developed. List one elicitation approach that would be successful in resolving each of the following section's needs elicitation problems (one technique per problem). Briefly explain why this technique is suitable in this circumstance. Rather of just listening to what users claim they do with the existing system, you should examine how they really use it.To accomplish so, you must first determine which elements of a new proposed system are the most important and necessary.
A gradual approach to implementing new functionality, beginning with a basic set, then adding more advanced functionality after users have had a chance to adjust to the new system is a good idea because: Group of answer choices Users can get new ideas for advanced functionality once they have a chance to use the basics of the new system. This approach allows for an iterative approach to be taken to fix issues and make improvements to the new system. It sets in motion “the journey” of continuous improvement and process redesign using the new system. All of the above.