RE_Lecture 11

Introduction to Requirements Engineering

Overview of Sources in Requirements Gathering

• The lecture begins with a greeting and an introduction to the topic of requirements engineering, emphasizing the importance of using multiple sources for gathering requirements.

• Challenges in the process of extracting requirements are highlighted, indicating that there can be issues when relying solely on human sources for information.

Issues with Human Sources

• It is noted that different stakeholders may have varying perspectives and experiences, which complicates the requirement-gathering process.

• The lecturer stresses that not all users share the same understanding or problems related to existing systems, leading to diverse interpretations.

Role of Systems Analysts

• The role of a systems analyst is described as a bridge between developers and users, ensuring clear communication about user needs and developer capabilities.

• Analysts must balance user requirements with technical feasibility while collecting requirements effectively.

User Interaction in Requirement Gathering

Customer Interaction Example

• An analogy is drawn comparing a waiter taking orders at a restaurant to how analysts gather user requirements by asking clarifying questions.

• If customers request something unavailable or difficult to fulfill quickly, it’s crucial for analysts to communicate alternatives effectively.

Documentation and Feasibility

• Analysts must document unrealistic requests from users and communicate these back to developers or relevant parties for clarity on what can be achieved.

• Emphasis is placed on avoiding vague features that lack necessity or clarity in their purpose.

Understanding Functional Requirements

Importance of Clear Specifications

• A snapshot example illustrates how unclear specifications can lead to misunderstandings about system functionalities.

• Users often struggle articulating their exact needs; thus, analysts must help refine these into actionable items.

Hotel Management System Case Study

• A case study on hotel management systems highlights various functional aspects such as reservations and food service tracking.

Detailed Breakdown of Requirements

Reservation Process Insights

• Specific details regarding reservation processes are discussed, including necessary components like cost display and modification options.

Food Service Tracking Features

• The system should allow tracking meals purchased within the hotel context, showcasing another layer of functional requirement documentation.

Learning Requirement Specification Techniques

Writing Effective Requirements

• Students are encouraged to learn how to write precise requirement specifications using formal language techniques.

Clarity in Communication

• The importance of writing unambiguous statements that do not allow multiple interpretations is emphasized throughout the session.

Conclusion

Wrap-Up Remarks

• The session concludes with encouragement for students to apply learned concepts in future projects while maintaining clarity in their written specifications.