Describe the viewpoints approach to requirements discovery, giving the types of viewpoint.(5 Marks)
Question
Describe the viewpoints approach to requirements discovery, giving the types of viewpoint.(5 Marks)
Solution
The viewpoints approach to requirements discovery is a method that involves gathering requirements from various perspectives or "viewpoints". This approach is based on the understanding that different stakeholders will have different perspectives on the system, and these perspectives need to be considered to ensure that the system meets the needs of all users.
-
User Viewpoint: This viewpoint focuses on the needs and expectations of the end-users. It involves understanding how the users will interact with the system, what tasks they will perform, and what information they will need.
-
Business Viewpoint: This viewpoint considers the needs of the business or organization. It involves understanding the business processes that the system will support, the business rules that the system must enforce, and the business goals that the system should help achieve.
-
Technical Viewpoint: This viewpoint focuses on the technical requirements of the system. It involves understanding the technical constraints that the system must operate within, such as the hardware and software platforms that the system will run on, and the performance and security requirements that the system must meet.
-
Legal Viewpoint: This viewpoint considers the legal and regulatory requirements that the system must comply with. This could include data protection laws, accessibility standards, and industry-specific regulations.
-
Social Viewpoint: This viewpoint considers the social and cultural aspects that may affect the system. This could include the social norms and cultural practices of the users, as well as the social impact of the system.
By considering these different viewpoints, the viewpoints approach to requirements discovery can help ensure that the system meets the needs of all stakeholders.
Similar Questions
What methods are commonly used for gathering requirements in software development?Question 15Select one or more:a.Interviews with stakeholdersb.Ignoring stakeholder inputc.Observing user behaviourd.Surveys and questionnairese.Brainstorming sessions
Question 2What is a Requirements Specification?1 pointA process, how the requirements are written (specified)A product, a written specification of the requirementsBothNeither
Comparison of Requirement Gathering Techniques (5 marks)Compare and contrast at least four techniques for gathering software requirements, such asinterviews, surveys, observations, and document analysis. Discuss the strengths andweaknesses of each technique with reference to real-world examples you have encounteredduring your team’s project work (Indicate your Team’s name as reference). Highlightspecific scenarios where one technique might be preferred over another and justify yourchoices based on our coursework.2. Requirement Elicitation for E-commerce Mobile Application (5 marks)You are assigned as a software engineer in a project to develop a mobile application for an e-commerce business. Based on the concepts discussed in our recent lectures and the specificneeds of your project team, describe a detailed plan for eliciting requirements fromstakeholders. Include at least three different techniques, explain why each technique is chosen,how it complements the others, and how it fits the context of your Team’s project. Discusshow you would prioritize requirements and resolve conflicts among them, providing specificexamples from our class discussions and project.3. Communication Strategies in Requirements Engineering (5 marks)Discuss the critical role of communication in each stage of the requirements engineeringprocess. Identify and elaborate on strategies to enhance communication among variousstakeholders (e.g., users, developers, managers) during these stages, using examples from yourTeam’s project experiences. Provide examples of potential communication barriers faced inyour team’s project and propose solutions to overcome them. Include a discussion on the useof collaborative tools and techniques relevant to our course.
3.1 Discuss the significance and use of requirement engineering. What arethe problems in the formulation of requirements?3.2 Requirements analysis is unquestionably the most communicationintensive step in the software engineering process. Why does thecommunication path frequently break down ?3.3 What are crucial process steps of requirement engineering ? Discuss withthe help of a diagram.3.4 Discuss the present state of practices in requirement engineering. Suggestfew steps to improve the present state of practice.3.5 Explain the importance of requirements. How many types ofrequirements are possible and why ?3.7 What do you understand with the term “requirements elicitation” ?Discuss any two techniques in detail.3.8 List out requirements elicitation techniques. Which one is most popularand why ?3.6 Describe the various steps of requirements engineering. Is it essential tofollow these steps ?
Question 13At which stage of the UX design process do you put yourself in the user's situation to get a better understanding of their requirements?1 pointPrototypeDefine the problemEmpathizeIdeation14.Question 14
Upgrade your grade with Knowee
Get personalized homework help. Review tough concepts in more detail, or go deeper into your topic by exploring other relevant questions.