CONCEPT DOMAIN - Software System ArcOps
OpenGroup - OAA - Software Architecture
SAFe© - DevOps
DOMAIN HIERARCHY
DIAGRAM HIERARCHY
-
Application Deployment Architecture
The Application Deployment Architecture domain defines concepts used to organize Applications in Deployable Packages.It comprises:1) software code packages (Deployable Application Packages)2) Data packages (Deployable Data Packages).3) Prescribed type of hosting4) required technical connections (with communication protocols, port numbers...) to communicate with each other.-
Application Deployment Architecture
An Application Deployment Architecture describes one possible deployment configuration of an Application.It contains Deployable Packages to host, prescribed type of hosting and required Software Physical Channels (with communication protocols, port numbers...) to communicate with each other. -
Application Deployment Environment
An Application Deployment Environment describes one possible integration context for an Application Deployment Architecture. It contains the subject application deployment architecture and the partner deployment architectures it must be integrated with, meaning it must communicates with via technical connections (with communication protocols, port numbers...).
-
Application System Deployment Environment
An Application System Deployment Environment describes one possible integration context for an Application System Deployment Architecture. It contains the subject application deployment architecture and the partner deployment architectures it must be integrated with, meaning it must communicates with via technical connections (with communication protocols, port numbers...).
-
Deployable Application Package
A Deployable Application Package is a split of application code according to deployment criteria at runtime. For example, it may be Front End/Back End or GUI/Business Logic etc..Each Deployable Application Package is associated to required Software Technology(ies) (for running) and can host code of several Application Component.Architects can also prescribe a kind of hosting artefact (IaaS/PaaS cloud service or IT server model).
-
Deployable Data Package
A Deployable Data Package represents a data part of an Application that must be hosted and accessed by application services (code) to run.Each Deployable Data Package is associated to Required Software Technologys (for data hosting and access) and can host several data structures.Architect can also prescribes a kind of hosting artefact (IaaS/PaaS cloud service or IT server model).
-
Deployable Package
A Deployable Package is a split of Application code and data according to deployment and runtime purposes.
-
Deployable Software System
Deployable Software System is the super-type of all concepts used to describe the deployment of Business Software Systems.
-
MicroService
A MicroService is a small autonomous unit of software, emphasizing self-management and lightweightness as the means to improve software agility, scalability, and autonomy.1) MicroServices are automous or assembled and orchestrated as components of Applications.2) MicroServices can be directly deployed to Computing Systems. MicroServices are both a logical unit of software and a Deployable Package.3) MicroServices owns their own data store and dot not have any shared stores with other components.MicroService is a Micro enterprise asset that sits at the lower level of Business Software System decomposition.
-
Software Deployment Architecture
-
Software Deployment Environment
A Software Deployment Environment describes a possible integration context for a Software Deployment Architecture.It contains the subject Business Software System deployment architecture and the partner deployment architectures it must be integrated with, meaning it must communicates with via technical connections (with communication protocols, port numbers...).
-
-
Application Functional Architecture (*)
The Application Functional Architecture domain is used to describe the functional structure and behavior of Business Software Systems.SysFEAT provides three level of granularity to represent software systems:2) Mezzo Business Software Systems are represented by Applications, which compose Application Systems.3) Micro Business Software Systems are represented by Application Components and MicroServices which compose Applications.All Business Software Systems provide Functionalitys, expose APIs by means of Application Interfaces, have a data scope defined by Physical Data Domains, perform System Processes and have their interactions described by Software System Scenarios.
-
Application
An Application is a Business Software System that provides a set of Functionality(ies) that End Users see as a single unit.Essentially Applications are architectural constructions resulting from the combinaison of the following four criteria:1) A group of Functionality that End Users see as a single unit.2) A managed asset (Managed Application) associated with a budget line in the context of an Application Portfolio.3) A body of code that is seen by developers as a single unit.4) A group of deployable software units (Deployable Application Packages) that must be installed together on one or multiple execution nodes (Computing System).Application is a Mezzo enterprise asset that sits between Application System and Application Component in the decomposition of Business Software Systems.Example: " Payroll" is an Application that is part an " HR System" which is an Application System.The "Payroll" Application includes, among other things, the "Salary and Wage Calculation" Application Component.
-
Application Component
An Application Component is a functionnal unit of software (java class, COBOL Program, Batch) that is a consistent, indivisible unit of processing of an Application producing and consuming its Information Outcome Events though APIs (Application Interface).a) Application Components are assembled and orchestrated in Applications.b) Application Components cannot be directly deployed to Computing Systems: they need to be organized in Deployable Application Packages.Application Component is a Micro enterprise asset that sits at the lowest level of Business Software System decomposition.Example: the "Salary and Wage Calculation" component is an Application Component that is part of the "Payroll" Application.
-
Application Environment
An Application Environment is an operating context in which an Application defines its interactions with its partners (Partner Application) in the form of API connections (Software Connection).
-
Application Environment Scenario
An Application Environment Scenario is a story involving the partners of an Application (Partner Application) interacting in order to achieve Information Outcome Events in a specific Eco-System (Application Environment).This includes:- A course of events represented by Application Flows depicting the story towards the delivery of expected Information Outcome Events.- Interacting Partner Applications who participate to the story in the considered Application Environment.
-
Application Scenario
An Application Scenario is a story involving the components of an Application (Application Component or MicroService), interacting in order to produce Information Outcome Events.This includes:1) A course of events represented by Application Flows depicting the story towards the delivery of expected Information Outcome Events.2) Interacting Application Components who participate to the story.
-
Application System
An Application System is a Business Software System which is an assembly of multiple Applications or other Application Systems that, together, fulfill a set of Macro Functionality(ies) delivered to Business Operations.Application Systems are used in the context of IT Strategic planning to define and evolve other time the hight level structure of the enterprise IT Architecture.Application System is a Macro enterprise asset that sit at the top of Business Software System decomposition hierarchy.Example: "HR System" is an Application System whereas "Payroll" is an Application that is part of the "HR system".
-
Application System Environment
An Application System Environment is an operating context in which an Application System defines its interactions with its partners (Partner System) in the form of API connections (Software Connection).It also represents End Users that interact with the system.
-
Application System Scenario
An Application System Scenario is a story involving the components of an Application System (Applications), interacting in order to produce Information Outcome Events.This includes:1) A course of events represented by Application Flows depicting the story towards the delivery of expected Information Outcome Events.2) Interacting Applications who participate to the story.
-
MicroService
A MicroService is a small autonomous unit of software, emphasizing self-management and lightweightness as the means to improve software agility, scalability, and autonomy.1) MicroServices are automous or assembled and orchestrated as components of Applications.2) MicroServices can be directly deployed to Computing Systems. MicroServices are both a logical unit of software and a Deployable Package.3) MicroServices owns their own data store and dot not have any shared stores with other components.MicroService is a Micro enterprise asset that sits at the lower level of Business Software System decomposition.
-
Scenario of Application System Environment
A Scenario of Application System Environment presents the flow exchanged between the IT services or the micro-services used by this application. A scenario can represent a specific use case of this application or, globally, the set of all flows exchanged inside this application.
-
Software Module
A Software Module is a Business Software System that is part of an application system.All share the ability to be composed of sub-Application Components and have dependencies to enabling Software Technology(ies).
-
-
Logical Application Architecture
The Logical Application Architecture domain provides means of describing the logical structure and behavior of Business Software Systems of the enterprise.The aim of Logical Application Architecture is to describe an optimal optimal architecture of the enterprise IT systems. It is used to guide how key sub-systems and data domains are to be configured to meet IT systems missions and purposes.A Logical Application Architecture is concerned with how the IT Operating Model should look, not how it does look now.This includes:1) Logical Application as the core building logical blocks for software components.2) Logical Application System as consistent ssembly of Logical Applications.3) Logical Data Domains of data entities.4) Functionality(ies) fulfilled by logical systems.5) Functional APIs exposed and used by applications: Application Interfaces.
-
Logical Application
A Logical Application is an encapsulation of application functionality that is independent of a particular implementation. For example, the classification of all purchase request processing applications implemented in an enterprise.
-
Logical Application System
A Logical Application Architecture is an assembly of other Logical Application Architectures, of Logical Applications and of end users, in order to realize one of more functionalities.
-
Logical Data Domain
A Logical Data Domain is used to define a logical data structure made up of Logical Data Entity(ies) and data views.
-
Logical Data Element
A Logical Data Element represents the logical structure of any kind of data that can be memorized by a Business Software System.A Logical Data Element is either a Logical Data Entity or a Logical Data Property.Only Logical Data Entitys can have identity and can be referenced by Logical Relationships. Logical Data Propertys only handle raw data.
-
Logical Data Entity
A Logical Data Entity is a logical structure of a Data Entity. As any Data Entity, it has an independent existence and can be uniquely identified.A Logical Data Entity is characterized by Logical Relationships it has with other Logical Data Entity(ies) and by its Attributes.
-
Logical Data Map
-
Logical Data Property
A Logical Data Property is an immutable type that is distinguishable only by the state of its properties.
That is, unlike a Logical Data Entity, which has a unique identifier and remains distinct even if its properties are otherwise identical, two Value Objects with the exact same properties can be considered equal. -
Logical Data View
A Logical Data View a collection of filtered Logical Data Entitys.
-
Logical Software System
A Logical Software System is logical specification of a Business Software System, which is independant from the Business Software System physical implementation.For instance, "Human Resource ERP System" is a Logical Application System, while "SAP HR System", "Sage HR System", "Kronos HR System" are Application Systems.
-
-
Software Technology ArcOps
The Software Technology ArcOps domain describes a set of concepts used in practices that combines Software Technology System development (Dev) and Software Technology System operations (Ops).It aims to shorten the development life cycle of Software Technology Systems and provide continuous delivery with high system quality. DevOps is complementary with Agile software development; several DevOps aspects came from the Agile methodology.
-
Cloud Service
A Cloud Service is a Software Technology System that is also a Computing Systems that can run software.
-
Deployed Cloud Service
-
Deployed Software Technology
Instance of a software technoloy deployed on a server or a site
-
Software Technology
A Software Technology is an elementary Software Technology System used as an enabler by Software Modules.Examples :- Application server,- Message server,- Storage,- Business information sharing,- Operating systems,- Navigators, etc
-
Software Technology Capability
A Software Technology Capability is a Technology Capability offered by Software Technology Systems and aimed at producing Software Technology Outcome Events.Software Technology Capabilitys define WHAT Software Technology Systems can do, They are used to understand whether two types of Software Technology Systems are fundamentally doing the same thing.They are also used in Software Technology ArcOps to identify where there are redundancies in Technology Portfolios. -
Software Technology Outcome Event
A Software Technology Outcome Event is a Technology Outcome Event that indicates the availability of an expected change of a software resource, produced by a Software Technology System.
-
Software Technology Stack
A Software Technology Stack is a set of Software Technology(ies) that form a consistent platform backbone.
-
Software Technology System
A Software Technology System is a Technology System that provides Software Technology Capabilitys to other Business Software Systems by producing and reacting to Software Technology Outcome Event.Software Technology Systems are enabler systems. They do not directly deliver Business Outcome Events to internal or external customers.
-