Skip to content

Commit a84458d

Browse files
committed
cleaned stuff
1 parent 826bffa commit a84458d

File tree

2 files changed

+3
-15
lines changed

2 files changed

+3
-15
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# OpenArchitecureModel Specification
2-
The OpenArchitecureModel specification describes the standard model for defining and querying software architecture elements.
2+
The Open Architecure Model (OAM) specification describes the standard model for defining and querying software architecture elements.
33

44
The sources can be browsed from [document](document/core/intro/introduction.rst).
55

document/core/intro/overview.rst

Lines changed: 2 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ Overview
77
Concepts
88
~~~~~~~~
99

10-
OpenArchitectureModel is a high-level, SQL-like programming language.
10+
Open Architecture Model (OAM) introduces a high-level, SQL-like programming language.
1111
This language is structured around the following concepts:
1212

1313
.. _organisation:
@@ -30,10 +30,6 @@ An application is a distinct software component or module that resides within a
3030
**Framework**
3131
A framework is an architectural structure that establishes how an application is represented, organized, and managed within the system. It provides a set of conventions, principles, and practices to ensure consistency and clarity in architectural design. A framework can follow standard models such as TOGAF, C4, or Zachman, offering predefined methodologies to address various organizational or technical needs. Alternatively, it may be a custom framework tailored to meet specific requirements or workflows within the system, ensuring flexibility and adaptability for unique use cases.
3232

33-
.. _profile:
34-
35-
**Profile**
36-
3733
.. _element:
3834

3935
**Element**
@@ -44,19 +40,11 @@ An element is the fundamental building block of an architectural structure, repr
4440
**Extensions**
4541
Extensions are modular add-ons to the system designed to enhance its functionality and adaptability. They achieve this by either extending the capabilities of existing models or introducing entirely new models to the architecture. Extensions allow for system customization without altering the core framework, enabling seamless integration of additional features or workflows. They are often developed to address specific requirements, provide scalability, or support future enhancements, ensuring that the system remains flexible and capable of evolving alongside organizational needs. Additionally, extensions can interact with the core components and other extensions through well-defined interfaces, maintaining consistency and reliability within the overall system.
4642

47-
.. _release:
48-
49-
**Release**
50-
51-
.. _deployment:
52-
53-
**Deployment**
54-
5543
.. _adr:
5644

5745
**Architecture Decision Records**
5846

5947
.. _fitness:
6048

6149
**Fitness Functions**
62-
Fitness Functions are measurable, objective criteria used to evaluate and validate the quality and alignment of a software system's architecture with its desired outcomes.
50+
Fitness Functions are measurable, objective criteria used to evaluate and validate the quality and alignment of a software system's architecture with its desired outcomes.

0 commit comments

Comments
 (0)