Note: Access to IEEE Std. 7000 is free after registration for IEEE Xplore (click on "Access via Subscription").
IEEE Std. 7000 advises how to go from context to value to requirements to design:
ADRs and Ethical Reviews are concepts from DPR and ESE (this repository), respectively.
See the Glossary for brief summaries of IEEE Std. 7000 concepts and agile practices. All acronyms are defined there as well.
| Agile Practice | Related IEEE Std. 7000 Concept | Comments |
|---|---|---|
| User Story (as Product Backlog Item) | Functional system requirement | see ESE FAQs |
| Sprint Planning | no direct mapping, parts of all processes executed in each iteration | see ESE FAQs |
| Definition of Ready | EVRs elicited (Clause 9) | V in INVEST widened |
| Definition of Done | Design artifacts produced and reviewed (Clause 10) | from Scrum, many templates/criteria |
| Sprint Review | Verification and validation activities in all processes | Novel practice in ESE: Ethical Review |
| Retrospective | no direct mapping, contributes to Transparency Management Process | many variations |
The Scrum concept of Product Vision can also be mapped, to Clause 7 in particular, but also Clause 8 (the clauses are the chapters of the standard).
| IEEE Std. 7000 | Related Agile Practice | Comments |
|---|---|---|
| Clause 7: Concept of Operations (ConOps)1 and Context Exploration Process 2 | no direct pendant; epics as input | Concepts in HCI/UX community such as personas, Context Diagram in DPR |
| Clause 8: Ethical Values Elicitation and Prioritization Process | User Stories and related practices (e.g., backlog refinement/grooming) | Novel practice in ESE: Story Valuation |
| Clause 9: Ethical Requirements Definition Process | User Stories and related practices | Mapping, splitting; estimation/planning games such as planning poker |
| Clause 10: Ethical Risk-Based Design Process | n/a (implicit, evolutionary/emerging) | Related books: "Domain-Driven Design" (E. Evans), "Just Enough Architecture" (G. Fairbanks), also see related patterns |
| Clause 11: Transparency Management Process | no direct mapping | Ethical Review Meeting/Report, in ESE design decision logs from DPR |
See Frequently Asked Questions (FAQ) page for the time being.
This work was funded by the Hasler Foundation.
Footnotes
-
Note that the term "operations" in ConOps refers to the functioning of an application or system here; it is not to be confused with the Ops in DevOps and systems/service management (superset relation). IEEE Std. 7000 defines ConOps as "verbal and/or graphic statement, in broad outline, of an organization’s assumptions or intent in regard to an operation or series of operations" and then "The concept is designed to give an overall picture of the organization operations". ConOps has its roots in ISO/IEC/IEEE15288:2015. ↩
-
Several existing software engineering methods and tools emphasize context, for instance, the Domain-Driven Design tool Context Mapper and architecture design methods such as those compiled in Design Practice Repository/Reference (DPR). Event storming workshops yield domain model input and other analysis results; walking through an SOI started from an external business trigger may also contribute to ConOps creation and Context Exploration. ↩