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

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.

--

--

--

AIFORSE: Artificial Intelligence for Software Engineering

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
Valentin Grigoryevsky

Valentin Grigoryevsky

System Architect, transforming Software Engineering Industry. Founder @ AIFORSE Community. v.grigoryevskiy@gmail.com

More from Medium

How to make Code Review more effective with Pair Programming

Dear Developer and Stakeholders, Please Take Maintenance into Consideration

The truth is that most software sucks.

3.1 Principles for better Code Reviews

bulletproof code review principles — deanburge.com