Read Chapter 1 of the CPRE Foundation Level.

Learn the definition of a requirement and note that Requirements Engineering is another term for a role involving Business Analysis competencies.

Note also the different types of requirements and that Quality Requirement is another term for Non-Functional Requirement.

1. Based on your analysis of BrightStar so far, gather the relevant information and identify at least two functional requirements.
2. Identify at least two non-functional (quality) requirements.
3. Review and refine your requirements to identify and address ambiguities, gaps, or missing details.

Read about system boundaries and context diagrams in sections 2.2 “Specifying the system boundary”, including sections 2.2.1.1 “Context diagram” and 2.2.1.2 “Natural language documentation of scope and system boundary”, of the IREB RE@Agile Handbook.

Find some examples of epics, features and user stories. This resource may be helpful.

1. Suggest a list of epics for an improved solution within BrightStar

2. Supposing you had limited resources for a first implementation of these changes, decide which of these epics would initially be in scope and justify this choice

3. For one of your epics derive multiple features

4. Show how your lower-level technical requirements can be traced back to higher-level business needs (traceability)

Read about use cases and use case diagrams as another way of representing the scope of a solution (e.g. in section 2.2.1.3 “Use case diagram” in the IREB RE@Agile Handbook).

Describe in your own words the differences between a use case, a scenario and a user story.

Read Section 3.6 “Requirements Documents and Documentation Structures” of the IREB CPRE Foundation Level Handbook.

Explore different requirements documentation formats and examples:

1. Business Requirements Document (BRD)
2. Functional Requirements Document (FRD)
3. Software Requirements Specification (SRS)
4. Product Requirements Document (PRD)

How do these documents differ in purpose, content, and level of detail? Where do they overlap? How do these differ from your understanding of a product backlog as used in an agile approach? Focus on understanding very well the type of documentation used by the company you are being hired by.

Build the presentation of how you applied the key learnings of this week to the Bright Sparks case study.

The people in class can be the stakeholders and will evaluate your work.

The presentation must be less than 10 minutes long.