Software Engineering Artifacts — Let’s agree on Terminology
If you’ve ever had a hard time understanding your colleagues or other stakeholders when developing or delivering software, speaking in different “languages” or using the same terms while meaning completely opposite things, this material might be useful for you.
Commonly-used “Epic” or “User Story” cover just a fraction of the entire picture, and it worth understanding that software design and development is not so flat and goes beyond these two primitives.
The presented diagram covers just the highest level of details — so-called “Level 0”, to denote the “width” of the model, not yet paying much attention to its “depth”.
If you need more information on the Layers — take a look at the AIFORSE Framework — Software Engineering Enterprise Processes Map (08/Jan/2019).
If you can help describe each and every block on this diagram or want to contribute to the definition of the next Levels, please visit the AIFORSE Framework Repository.
