Understanding Requirements Elicitation and Analysis in Software Development

What distinguishes an analysis model from a domain model?

An analysis model outlines how the software will interact with the real world, maintaining insights from the domain model and establishing a boundary for automation.

How does prototyping help in requirements elicitation?

By providing quick mock-ups to validate understanding and stimulate discussions among stakeholders.

Who are considered stakeholders in requirements analysis?

End-users, managers, engineers, domain experts, trade unions, and anyone involved in the system's operation.

What is the Object-Oriented Analysis (OOA) philosophy?

Every program simulates real-world structures and interactions, emphasizing a model-based approach to software development.

What is the focus of interviews in requirements elicitation?

General questions about current roles and problems or specific scenarios to understand desired functionalities.

What is the role of a domain model in OOA?

It describes the current application landscape and ensures developers understand the system's environment.

What are the two main problems in eliciting requirements?

Obtaining information and organizing the information obtained.

Name common methods for obtaining requirements information.

Reading documentation, interviewing stakeholders, facilitated meetings, prototyping, and direct observation.

What are some challenges in requirements analysis?**

Stakeholders may not know what they want, express conflicting requirements, face organizational influences, and see changing requirements during analysis.

What characterizes quality use cases?

They should be written in customer language, validatable, focused on a single goal, and express requirements rather than design.

What components are typically included in a use case?

Title, overview, actors, preconditions, scenarios (main and alternative paths), postconditions, and exceptions.

What is the purpose of eliciting requirements?

To determine what customers need from a proposed system and document that information for formal requirements documentation.

What are use cases and their purpose in requirements organization?

Use cases describe system functionalities and link specific requirements to scenarios.

How do use cases relate to requirements documents?

Use cases serve as a mechanism for gathering details needed to write formal requirements specifications.