ModellingLanguageSummary
From PlugIT Wiki
Overview
Summary
Application System Type Diagram
The ARIS ASTD can be used to indentify the different systems, components, interfaces and modules. It can also be used to capture the functions that are supported by the application systems along with the supported objectives. This model type captures different levels of information for the design and implementation specification.
BMM - Business Motivation Model
The Business Motivation Model BMM defines a set of concepts related to business plans. Besides these built-in concepts, the role of business processes and organisation units is contained in the specification. Important concepts are Ends (e.g. Vision, Desired Result), Means (e.g. Mission, Directive) and Influencers. BMM should especially help developers of business plans to assure completeness and supports a common understanding of the concepts. Further on it provides guidance for more detailed business models and may lead to an integrated framework of an enterprise model with business processes, rules and organisation units. A major goal of the BMM is to support tracability of decisions.
BPDM - Business process definition metamodel
The Business Process Definition Metamodel is a framework which supports the representation of business processes independent from notation or methodology. Thus it may support interoperability between different tools and notations. BPDM also provides a formal extension to BPMN, as the BPMN concepts are represented in an explicit metamodel. A focus of BPDM is its clear semantics to be unambiguously interpreted by humans and machines.
BPEL
The Web Services Business Process Execution Language Version (BPEL) is an XML based language for specifying business process behavior based on Web Services. Business processes can be described in two ways: Executable business processes model actual behavior of a participant in a business interaction. Abstract business processes are partially specified processes taht are not intended to be executed. An Abstract Process may hide some of the required concrete operational details.
BPMN - Business Process Modelling Notation
BPMN is a standardised flowchart based notation for defining business processes. The notation aims to be comprehensible for managers, business analysts as well as developers. BPMN models may be defined on a variable level of detail: from high-level process landscapes down to a detail level allowing the transformation into an executable language.
Business Process Architecture
The business process architecture allows to picture business processes as process maps. Furthermore, it is possible to detail processes using activities. It focuses on the Business Architecture level.
Business Process Model
The business process model is adapted from software development flow diagrams and represents process flows in an organisation. In business process models, the sequence of tasks is modelled with the use of activities that are needed to resolve specific tasks. In addition to flow diagrams that are well-known from conceptual design in programming, control constructs for parallel process execution as well as business-specific attributes (e.g. resources) and references (e.g. to responsible roles or documents) are provided.
Class Diagram
The class diagram provides the possibility to present the structure of the system which should be developed. It can answer the question, how data and the behavior of my system structured.
Company Map
Company maps are used to model an overview of Business Process Models or other company maps. Therefore, a company map can be seen as a navigation help and entry point into the hierarchy of Business Process Models.
Component Diagram
The component diagram is more abstract than a class diagram. It is used to structure a system and to show how these structures are created. The basic elements are components and connectors which shows how the components are linked.
Document Model
The document models contain documents (templates), which are utilised in the process. Document models can be built hierarchically using document sub models to e.g. illustrate a detailed structure of documents.
EERM
With ARIS eERM entitities and their relationships can be modelled (data view).
EPK
With EPK or EPC (event-driven process chains) processes are modelled.
FAD
With ARIS FAD the complexity of EPC is reduced. In this model type the assignments of objects (input and output data) to functions is realized.
Function tree
The ARIS Function tree is used as a top-level model and shows the functions and their relationships.
ICT Infrastructure
The ICT infrastructure models the hardware part of the ICT infrastructure
ILogRules
ILOG provide a Business Rules Management system. Using their JRules, business policies can be expressed and business rules, decision tables and decision trees can be transformed into internal, executable rule expressions.
IT Application Architecture
The application architecture illustrates applications and their interfaces
IT Projects
The modelling language project describes the project phases and its work packages.
IT Service Architecture
In the IT service architecture model, IT services are described in a structured way. As well as documenting the personal responsibilities for services, this modelling language serves to picture a single component of IT services. It also focuses on the Business Architecture level.
IT Service Process
IT service process allows describing IT service processes in detail. One of the most important modelling element is "Activity", which is an elementary tasks executed by an IT service process.
IT Service Process Architecture
The IT service process architecture can be used to model a process map for IT service processes. Using the relation data flow, interfaces and the necessary communication between processes are depicted.
IT Software Architecture
This model is used to describe individual modules of applications (components, their properties, functions and relations) in detail.
IT Strategy
The IT strategy can be modelled in this modelling language and addresses the IT strategy level.
IT System Model
The IT system model gives an overview of the IT system architecture by modelling systems, applications and infrastructure elements. IT system models can be built hierarchically using IT systems sub models to e.g. illustrate a detailed structure of an IT system.
JessRules
Jess is a rule engine and scripting environment written entirely in Java by Ernest Friedman-Hill. Jess can be licensed for commercial use, and is available at no cost for academic use. To use the rule engine, two formats are provided to specify rules: the Jess rule language and XML.
Knowledge Map
With ARIS Knowledge maps the available knowledge of employees or organisational units can be modelled.
Modelling Language Example Page
The Semantics of Business Vocabulary and Business Rules (SBVR) defines the vocabulary and rules for documenting the semantics of business vocabularies, business facts and business rules. (…)
OWL - Ontology Web Language
The OWL Web Ontology Language is designed for use by applications that need to process the content of information instead of just presenting information to humans. OWL facilitates greater machine interpretability of an Information content than that supported by other languages like XML, RDF, and RDF Schema (RDF-S) by providing additional vocabulary along with a formal semantics. OWL has three increasingly-expressive sublanguages: OWL Lite, OWL DL, and OWL Full.
OWL-S
The Semantic Markup for Web Services (OWL-S) (formerly DAML-S) builds on the Ontology Web Language (OWL) and is an ontology of services, that makes it possible to enable discover, invoke, compose, and monitor Web resources offering particular services and having particular properties. The ontology consits of the three main parts: the service profile for advertising and discovery services; the process model, which gives a detailed description of a service's operation; and the grouding, which provides details on how to interoperate with a service, via messages.
Organigram
With the ARIS organigram the hierarchical structure of the organisation with organisational units, roles, persons etc. can be described.
PRR - Production Rule Representation
The Production Rule Representation (PRR) (currently not finalized) specifies a standard platform independent representation production rule representation. Several organisations and tool vendors in the area of production rules supported the development to reach compatibility. The representation should provide a basis for exchange of rules between tools. It should also be possible to map the representation to business rules.
Product model
In the product model an overview of products and product components can be built hierarchically using a product’s sub models to e.g. illustrate a detailed structure of a product.
RDF - Ressource Description Framework
The Resource Description Framework (RDF) is a language for representing information about resources in the World Wide Web. RDF is a very simple language consisting of URI as the buildung blocks and their combination to triples which relates two objects with a property.
RDF/S - RDF Schema
RDF provides a way to express simple statements about resources, using named properties and values. However, RDF user communities also need the ability to define classes of resources and will use specific properties in describing those resources. RDF Schema provides the facilities needed to describe such classes and properties, and to indicate which classes and properties are expected to be used together.
RIF - Rule Interchange Format
RIF specifies a format for rules, so they can be used across diverse systems. This format (or language) will function as an interlingua into which established and new rule languages can be mapped, allowing rules written for one application to be published, shared, and re-used in other applications and other rule engines. Because of the great variety in rule languages and rule engine technologies, this common format will take the form of a core language to be used along with a set of standard and non-standard extensions. RIF comes in different dialects including the production rule dialect, the basic logic dialect, or the core dialects which is a subset of the logic dialect
Requests/Qualities
Qualities of and requests on projects, systems or people are documented in the modelling language requests/qualities. It can be used on the Business Architecture level as well as on the Application Architecture level.
RuleML
The Rule Markup Language (RuleML) is able to represent different rule types: derivation rules, transformation rules and reaction rules. It is based on XML markup and combines several rule sublanguages. It is the aim to "provide a rule language and an iternoperability platform, integrating various business rules languages, inferencing systems and knowledge representation paradigms".
SBVR - Semantics of Business Vocabulary and Business Rules
SBVR is intended to provide the business vocabulary and business rules underpinned by First Order Predicate Logic for transformations by IT staff into information system designs. It is also designed to support interchange of business vocabularies and rules among organizations.
SML
The Servie Modeling Language (SML) is used to model complex services and systems, including their structure, constraints, policies, and best practices. SML uses XML Schema and Schematron.
SWRL
Semantic Web Rule Language (SWRL) aims to combine Ontology Web Languages OWL DL and OWL Lite with the Datalog RuleML sublanguage. SWLR allows users to write rules in terms of ontology concepts and to reason about ontology individuals. Thus SWRL enables the discovery of new knowledge base (ontology) by inferencing.
Technical Term Model
With ARIS technical term models the definitions and the relationsships between the key terms in a company can be described in a simple manner.
Topic Maps
Topic Maps allow to represent topics and their relation. ISO/IEC 13250 (1-7) defines Topic Maps including XML syntax, graphical and textual notation and query language.
UML Activity Diagram
An activity diagram describes workflows and emphasizes the sequence and conditions for coordinating lower-level behaviors.
Use Case Diagram
Use case diagrams are used to specify required usage of a system and are therefore typically used to capture the requirements of a system. The key concepts are actors, uses cases, and subject.
Actors represent users or any other system that may interact with the system. The system itself is described as the subject. The required behavior of the subject is specified by one or more use cases, which are defined according to the needs of actors.
Value-added chain diagram
With ARIS Value-added chain diagrams processes on a top level are modelled.
WS-CDL
The Web Service Choreography Description Language (WS-CDL) is an XML-based language that describes peer-to-peer collaborations of parties by defining, from a global viewpoint, their common and complementary observable behavior, where ordered message exchanges result in accomplishing a common business goal.
The Web Services specification offer a communication bridge between the heterogenous computational environments used to develop and host applications.
WSCL
The Web Service Choreography Language defines a minimal set of concepts in order to describe Web Service choreographies including message types, protocol and service location.
WSDL
The Web Services Description Language (WSDL) provides a model and an XML format for describing Web services. WSDL enables one to separate the description of the abstract functionality offered by a service from concrete details of a service description such as "how" and "where" that functionality is offered.
WSML
The Web Service Modelling Language is intended to describe semantic web services. There exists a relatively comprehensible syntax as well as XML based syntaxes for exchange and also a mapping to OWL. The language follows the conceptual model of WSMO. WSML is maintained by the ESSI WSML working group and has not yet been accepted from a standardisation body. … further results
