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).

AIFORSE Information Framework — Data Model Map — Level 0
AIFORSE Information Framework — Data Model Map — Level 0
AIFORSE Information Framework — Data Model Map — Level 0

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.

Medium is an open platform where 170 million readers come to find insightful and dynamic thinking. Here, expert and undiscovered voices alike dive into the heart of any topic and bring new ideas to the surface. Learn more

Follow the writers, publications, and topics that matter to you, and you’ll see them on your homepage and in your inbox. Explore

If you have a story to tell, knowledge to share, or a perspective to offer — welcome home. It’s easy and free to post your thinking on any topic. Write on Medium

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store