ITGS-213 هندسة متطلبات البرمجيات

Introduction to Software Engineering (ITGS-213) - Software Requirements Engineering

• Course: Introduction to Software Engineering (ITGS-213)
• Topic: Software Requirements Engineering
• Year: 2020, Fall semester
• Key Topics: Requirements Specifications, Documentation, Requirements Validation, and Requirements Management.

Requirements Specifications

• Requirements Specification Document (RSD): A crucial document detailing all proposed system requirements.
• Purpose: Serves as a foundation for contracts with clients and plays a major role in design and implementation phases.
• Error Source: Studies show 85% of software errors stem from requirements issues.
• Content: Includes a comprehensive description of system functions and quality attributes like performance, memory usage, response time, etc.
• Importance of Documentation: Documentation is essential for proper software development and maintenance.
• Documentation Content: Can involve textual descriptions; diagrams; audio/video files; program comments; etc.

Requirements Validation

• Purpose: Ensuring that the requirements specifications conform to standards and are ready for design.
• Methods:
  • Formal Inspection: Experienced professionals review documents to identify potential errors.
  • Walkthrough: A colleague reviews the requirements.
  • Verification: An independent entity (consultant, analyst) checks if client needs are accurately translated into requirements.
  • Review: Final review involving user and development team for decisions like proceeding, halting, or amending the project.
• Focus: Validation is conducted on documents, not the software itself.

Requirements Management

• Topic: Change Management in Software Development.
• Aim: Addressing and handling changes to requirements throughout the project lifecycle.
• Change Request Process:
  • Submitting Change Requests
  • Analyzing the requests' impact on project costs, schedule, and scope.
  • Approving or rejecting changes.
  • Implementing changes if approved.

Software Configuration Management (SCM)

• Role: Tracking changes (in requirements or technology) in software versions and releases.
• Responsibilities:
  • Managing different versions of the system.
  • Communicating with stakeholders.
  • Determining when changes need to be made.
  • Ensuring timely releases to customers.
  • Recording changes.
• Key Items:
  • Programs
  • Data
  • Documents

Base-Line

• Base-Line Documents: Serve as the final reference after review and are not to be changed unless formally authorized.
• Examples: Requirements specification documents and source code at certain stages of development.