CSE374
Advance Software Engineering
Unit-3:Lecture 1
Introduction to Requirements Engineering
[Link] needs for system development.
[Link] software meets stakeholder needs.
[Link] avoid scope creep issues.
[Link] gathering, documenting, and analyzing.
[Link] users and development teams.
[Link] software quality and reliability.
Importance of Requirements Engineering
[Link] costly changes post-development.
[Link] alignment with business goals.
[Link] user expectations clearly.
[Link] ambiguity in project execution.
[Link] better project risk management.
[Link] to successful software implementation.
Eliciting Requirements – Introduction
[Link] of gathering user expectations.
[Link] stakeholders, users, and developers.
[Link] system goals and constraints.
[Link] various techniques for collection.
[Link] completeness and requirement accuracy.
[Link] basis for further development.
Techniques for Requirement Elicitation
[Link] with stakeholders and users.
[Link] and questionnaires for input.
[Link] to discuss system needs.
[Link] of existing work processes.
[Link] to clarify user expectations.
[Link] for innovative requirement ideas.
Challenges in Requirement Elicitation
[Link] between stakeholders and developers.
[Link] requirements during development process.
[Link] of stakeholder availability issues.
[Link] business objectives and goals.
[Link] or missing requirement details.
[Link] among different user expectations.
Developing Use Cases – Introduction
[Link] system interactions with users.
[Link] functional requirements systematically.
[Link] user actions and system responses.
[Link] visualize system behavior effectively.
[Link] validation and requirement verification.
[Link] diagrams for better requirement understanding.
Introduction to Analysis Models
[Link] system structure and behavior.
[Link] requirements into graphical representations.
[Link] functional and non-functional elements.
[Link] diagrams for clarity and visualization.
[Link] define relationships between components.
[Link] structured software development process.
Requirements Modeling - Introduction
[Link] requirements into detailed models.
[Link] interactions, structure, and behavior.
[Link] refine and validate system design.
[Link] various modeling techniques effectively.
[Link] development and testing processes.
[Link] misunderstandings and misinterpretations.
Scenario-Based Modeling
[Link] on user interactions and behavior.
[Link] different system usage scenarios.
[Link] storyboards and activity diagrams.
[Link] understand system flow intuitively.
[Link] potential system failure scenarios.
[Link] in testing and validation processes.
Class-Based Modeling
[Link] objects within the software system.
[Link] attributes, relationships, and behaviors.
[Link] class diagrams for representation.
[Link] establish object-oriented software structure.
[Link] modular and reusable design.
[Link] clarity for developers and designers.
Tools for Requirements Modeling
[Link] for structured system representation.
[Link] case diagrams for functional modeling.
[Link] diagrams for interaction flow.
[Link] diagrams for system behavior.
[Link] flow diagrams for process modeling.
[Link] tools for early validation.
Common Pitfalls in Requirements Engineering
[Link] or ambiguous requirement statements.
[Link] stakeholder input and feedback.
[Link] of proper documentation practices.
[Link] requirements without impact analysis.
[Link] validation and verification processes.
[Link] non-functional system requirements.
A startup is developing an AI-powered resume screening system for HR
professionals. Initially, the stakeholders provided a high-level requirement: "The
system should automatically rank candidates based on resume content." However,
after development started, the stakeholders complained that the system was not
filtering candidates based on years of experience and skill proficiency.
Question: What fundamental mistake in requirements engineering led to this
issue?
A) The team focused only on functional requirements and ignored non-functional
ones
B) The team failed to properly define and validate requirements with stakeholders
C) The team gathered too much detail in the requirement, slowing development
D) The team did not prioritize performance testing early in the development
process
A company is building a self-driving car navigation system. After months of
requirement gathering, the engineering team believes they have a complete and
correct requirements document. However, when testing begins, they find several
safety-critical features missing, such as collision avoidance alerts.
Question: What mistake did the team likely make in the requirements validation
process?
A) They did not perform a formal requirements validation step
B) They focused too much on behavioral requirements and ignored class-based
modeling
C) They relied only on user feedback instead of system constraints
D) They documented requirements but did not use UML diagrams