• Unit 5: Fundamentals of Requirements Analysis

    Requirements elicitation is when software engineers interact with the stakeholders, including users, to gather information about what the software system needs to do. In this unit, we examine what the software engineer does to elicit, analyze (or translate), validate, and manage this life cycle phase. Each step requires working with the customer to achieve a common understanding of the customer's goals. This set of activities is called "analysis" and focuses on what the application will do, whereas "design" describes how the application will work.

    There are many ways to elicit and analyze customer requirements. The three most commonly used methodologies are data-oriented, process-oriented, and object-oriented. We will examine the conceptual foundations, activities, and deliverables in each of these methodologies. As you review this unit, focus on the object-oriented methodology and how it applies to software requirements and analysis. You will put it all together later in this course as part of a case study.

    Completing this unit should take you approximately 4 hours.

    • 5.1: Requirements Fundamentals

      This section reviews the requirements terms, concepts, and models presented in earlier units.

    • 5.2: The Requirements Process

    • 5.3: Conceptual Modeling

      Generally, three model types for software engineering are presented in this course: process-oriented, data-oriented, and object-oriented. They have similar processes but different perspectives and emphases concerning data and activities. Since the OO model incorporates aspects of the other two, it is presented in this section.

    • 5.4: Use Case Diagrams

      Use case and sequence diagrams are two key OO modeling diagrams for identifying and communicating requirements. This section explains and illustrates them by creating examples for the Post system.

    • 5.5: Sequence Diagrams

      The second key OO modeling diagram discussed for application in the requirements phase of the SDLC is the sequence diagram. Both use cases and sequence diagrams are behavioral types of diagrams.

    • Unit 5 Assessment

      • Receive a grade