MODELING - REQUIREMENTS ENGINEERING, ANALYSIS AND SPECIFICATION OF SOFTWARE REQUIREMENTS

Question 1

Define Modeling in terms of Software Development.

Answer 1

1. Modeling involves creating abstract representations of a system to better understand its structure, behavior, and interactions.
2. Various models, such as diagrams and charts, help in visualizing different aspects of the software.

Question 2

What is the Requirements Engineering?

Answer 2

1. Requirements engineering is the systematic process of gathering, documenting, and managing software requirements.
2. It involves communication with stakeholders to understand their needs and expectations, in order to overcome communication barriers between the customers, users and analysts.

Question 3

What are the key steps of the Requirements Engineering?

Answer 3

1. Elicitation - gather requirements from stakeholders,
2. Analysis and Prioritizing Requirements,
3. Specification - clear and unambiguous formatting of requirements,
4. Validation - requirements meet stakeholders’ needs.

Question 4

Why is it important to have clear requirements?

Answer 4

1. Facilitate effective communication between stakeholders, devolopers and testers,
2. Help in identifying potential risks early in the development process,
3. Trace and track changes throughout the development lifecycle.

Question 5

What are the two types of requirements?

Answer 5

Functional Requirements - What should the system do?
Non-Functional Requirements - What describes the system’s capabilities and constraints?

Question 6

What are the main challenges in Requirements Engineering?

Answer 6

1. Ambibity - vague or unclear requirements can lead to misunderstangings,
2. Changing Requirements - those changes may disrupt project timelines,
3. Stakeholder Involvement - if they don’t participate actively, the final delivery may not meet their expectations, leading to decreasing productivity, satisfaction and other problems.