ESE extends three existing practices (activities, artifacts) and proposes two new ones. It also uses three existing ones (unchanged).
ESE includes a total of nine agile activities and artifacts, listed in alphabetical order here (which differs from usage flow):
- (new) Story Valuation activity, the entry point for ESE usage
- (unchanged) Acceptance Testing, see entry in Agile Alliance Glossary
- (extended artifact) Definition of Done
- (extended artifact) Definition of Ready
- (new) Ethical Review
- (unchanged) Product Backlog, see entry in Agile Alliance Glossary
- (unchanged) Sprint Planning, see entry in Agile Alliance Glossary
- (unchanged) User Story, see entry in Agile Alliance Glossary
- (extended activity) Value Retrospective
The following UML class diagram shows how these method elements relate to each other:
The inheritance relations (white triangle at arrowhead) indicate whether they are new, enhancing existing ones or used as-is; abstract classes indicate novelty. There are three: "Enhanced Agile Practice," "New Ethical Software Engineering Practice," and "Unchanged Agile Practice".
Note that the Scrum concept of Product Vision is not explicitly featured here. It is integrated in Story Valuation and mapped in the Background Information though.
The following figure shows how the IEEE Std. 7000 concepts are logically connected with each other and with design decisions (yielding a practice usage flow):
EVR stands for Ethical Value Requirement, VBSR for Value-Based System Requirement.
- Roles index
- Frequently Asked Questions (FAQ)
- Glossary
- Method evaluation/validation and experimentation instructions
- Background information with mapping of ESE concepts to and from IEEE Std. 7000
- Literature
Version 1.0 of ESE was supported by the Hasler Foundation.