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. Suggest at least two functional requirements for BrightStar based on your analysis up to now
2. Suggest at least two non-functional (quality) requirements.

Read about system boundaries and context diagrams in sections 2.1.4 - 2.1.5.2 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.1.5.3 in the RE@Agile Handbook).

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

Take a look at a software requirements specification template such as one provided by the IEEE.

How does this differ from your understanding of a product backlog, as used in an agile approach?

Read about acceptance criteria and how user stories can be made both more measurable and clearly understandable for developers.

For one of the user stories that you have so far identified for BrightStar, suggest 3 or more acceptance criteria.

Build the presentation of the key learnings of this week.

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

The presentation must be less than 10 minutes long.