Lecture 3

Process model, Role model, Artifact/Product Model, (Quasi) standards, methods, and tools

Business analysis, requirements engineering, system architecture

Project planning, risk management, quality assurance

User stories, use cases, functional requirements

Clearly defined roles and responsibilities within the development team.

A documented and validated engineering procedure for handling requirements.

Implementation of a project management tool for tracking tasks and deadlines.

Systematic monitoring and documentation of the implemented requirements throughout the project.

Implicit requirements engineering focuses on capturing requirements as they emerge during development, while explicit requirements engineering emphasizes defining requirements beforehand.

Explicit requirements engineering relies on programmers' interpretations during implementation, while implicit requirements engineering prioritizes documented specifications.

Implicit requirements engineering involves a thorough and structured approach to defining requirements, while explicit requirements engineering is more informal and flexible.

Explicit requirements engineering prioritizes code over documentation, while implicit requirements engineering emphasizes clear and concise documentation.

To provide a detailed explanation of the course material.

To give students a roadmap of the course content and its progression.

To assess students' prior knowledge of the subject.

To introduce complex concepts in a simplified manner.

Provides a detailed description of the work process.

Facilitates flexibility in the project execution.

Offers a clear view of the artifacts' contents and dependencies.

Allows for easy measurement of the quality of the results.

The standards provide detailed, prescriptive guidelines for each step of the requirement engineering process.

The standards are deliberately vague, making it difficult to apply them to specific project contexts.

The standards are not widely recognized or adopted within the industry.

The standards are outdated and do not reflect modern software development practices.

Business Analysts, Domain Experts, Requirements Engineers, System Architects, and Developers

Only Business Analysts and Domain Experts

Only Requirements Engineers and System Architects

Only Developers

Artifact models lead to less clear roles and responsibilities within a project.

Artifact models allow for a high degree of flexibility in the development process.

Artifact models are inherently complex and require a lot of effort to develop and maintain.

Artifact models lead to less precise and testable specifications.

Explicit requirements engineering prioritizes clear and documented requirements, while implicit requirements engineering relies on assumptions and interpretations during development.

Implicit requirements engineering involves explicitly defining all requirements upfront, while explicit requirements engineering allows for flexibility and adaptation during development.

Explicit requirements engineering is considered the more efficient approach, as it minimizes ambiguity and potential misunderstandings.

Implicit requirements engineering encourages programmers to make decisions related to requirements during implementation, whereas explicit requirements engineering emphasizes clarification and pre-defined decisions.