Glossary and keywords
| Term | Definition |
|---|---|
| BPMN 2.0 | Unified Modeling Language |
| UML 2 | Unified Modeling Language |
| AD | Active Directory |
| DN | Distinguished Name |
| CN | Common Name |
| ITAN | Elerings IT Architecture Advisory Board |
| BDD | Behavior-Driven Development |
| MUST | This word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification. (See: http://tools.ietf.org/html/rfc2119.) |
| MUST NOT | This phrase, or the phrase "SHALL NOT", mean that the definition is an absolute prohibition of the specification. (See: http://tools.ietf.org/html/rfc2119.) |
| SHOULD | This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. (See: http://tools.ietf.org/html/rfc2119.) |
| SHOULD NOT | This phrase, or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label. (See: http://tools.ietf.org/html/rfc2119.) |
| Common product | Off the shelf products; products that have not been developed solely for Elerings use |
| CI/CD | Continuous integration (CI) and continuous delivery (CD). |