Learning Objectives
After these lectures, you will be able to:
- Explain in general terms what software engineering is
- List the requirements for completing the course
- Explain the structure of a user story
- Identify and fix user stories that don’t have the correct structure
- Define the relationship between conditions of satisfaction and user stories, and the difference between essential, desired, and extension conditions of satisfaction
- Identify functional and non-functional requirements, and give examples of each
Important Dates:
- Course survey due Monday, Sept 7th at 11:59pm.
Lecture Slides:
Activity
- Working with User Stories (see slides in: 1-2)
Resources
- INVEST criteria for user stories
- New to agile? INVEST in good user stories — introduction to both user stories and INVEST criteria
- Domain modeling made functional - the first section in Chapter 2, “Interview with a Domain Expert,” has a worked example of soliciting a client’s needs for software.