AIFORSE Framework

AIFORSE Information Framework - Data Model - L0

Software Engineering Artifacts — Let’s agree on Terminology

By | AIFORSE Framework, Software Architecture, Trending

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.

Read the full Article here:

DRYML Example: James loves Mary

Introducing DRYML

By | AIFORSE Framework, Trending

“If you can’t describe what you are doing as a process, you don’t know what you’re doing.” — Edwards Deming

DRYML (an acronym for “DRY Modeling Language”) is both a human- and machine-readable software modeling language.

DRY (an acronym for “Don’t repeat yourself”) is a principle of software development aimed at reducing repetition of software patterns, replacing it with abstractions or using data normalization to avoid redundancy. [Wikipedia]

Read the full Article here:

AIFORSE Framework – Software Engineering Enterprise Processes Map (08/Jan/2019)

By | AIFORSE Framework, Trending | No Comments
AIFORSE Framework - Software Engineering Enterprise Processes Map (08/Jan/2019)

AIFORSE Framework – Software Engineering Enterprise Processes Map (08/Jan/2019)


AIFORSE Framework (AIFORSE_xF) is a suite of best practices and standards that enables and utilizes artificial intelligence for effective and efficient software engineering.

It enables you to assess and optimize performance using a proven, data-oriented approach to operations and integration. The practical tools available in AIFORSE_xF help improve end-to-end management of services across complex environments.

AIFORSE_xF is aimed to improve agility in product development, solution delivery, and outsourcing Processes, resulting in increased margins, lower costs, and optimal customer experience. AIFORSE_xF is created and evolved by AIFORSE Community members.

AIFORSE_xF also includes adoption best practices to help companies implement and use the standards and management best practices to ensure ongoing conformance.

Software Engineering Enterprise Processes Map

This is the high-level (L0) Map of all the main processes, related to production and delivery of software solutions by companies of a different type, size and specialization, independent on a software type, chosen methodologies and implementation practices. It can be used by both Product and Outsourcing Software Companies to align internally as well as with Customers, Partners, and Investors on the main Software Engineering related activities, which shall be planned, organized, run and managed.

Main Layers: Software Engineering and Solution Delivery

The main Layers of the AIFORSE Framework Software Engineering Process Map, which are the most related to the Software Production Operations are:

  • Project Layer
  • Product Layer
  • Service Layer
  • Resource Layer

They define the levels at which Organizations operate, and provide capabilities to synchronize the corresponding activities.

Project Layer

It combines Elements of lower level Layers (Products, Services, Resources) for a defined Customer, Timeline, Scope, and Budget.

Product Layer

It covers any Software with defined Users, Business Cases, and Functional Capabilities.

Service Layer

The Service Layer is responsible for any Operations (Manual or Automated), related to the creation or maintenance of Software (Design, Coding, Testing etc.).

Resource Layer

It holds everything related to used or produced Resources (Logical or Physical), related to the creation, use or maintenance of Software (Workforce, Infrastructure, Artifacts etc.).


Start using the Map right now – self-check if all the operations are covered in your Company.
Click on the picture and download the file in high-resolution.
The next release will describe each element in more details and provide the definition of processes at the next (L1) Level of Decomposition.