pdfreaders.org

Modeling@SAP

Achim D. Brucker

In 1999, SAP started to combine the Unified Modeling Language (UML) and the Fundamental Modeling Concepts (FMC) language. The result is an SAP internal standard for modeling, called Technical Architecture Modeling (TAM). TAM comprises block diagrams, component diagrams, package diagrams, class diagrams, activity diagrams, sequence diagrams, state diagrams, and use case diagrams. TAM is used for both conceptual modeling as well as design modeling

While many works on reasoning on conceptual schemas focus on class diagrams and state diagrams, the most often used diagram type at SAP is the block diagram. For example, class models are used rarely, as they are "too close to real code." In general, developers and architects prefer structural diagrams (e.g., block diagrams), thus we need to ask ourselves the questions, if we can reason over such models and what kind of properties help to improve the software development.

Schlüsselwörter:
Kategorien:
Dokumente:

QR Code for talk:brucker:modeling-sap:2013.Bitte zitieren sie diesen Artikel wie folgt:
Achim D. Brucker. Modeling@SAP. Dagstuhl Seminar 13211 "Automated Reasoning on Conceptual Schemas", 20. may. 2013.
(Folien) (Handout) (BibTeX) (Share article on LinkedIn. Share article on CiteULike.)

BibTeX
@Talk{ talk:brucker:modeling-sap:2013,
abstract = {In 1999, SAP started to combine the Unified Modeling Language (UML) and the Fundamental Modeling Concepts (FMC) language. The result is an SAP internal standard for modeling, called Technical Architecture Modeling (TAM). TAM comprises block diagrams, component diagrams, package diagrams, class diagrams, activity diagrams, sequence diagrams, state diagrams, and use case diagrams. TAM is used for both conceptual modeling as well as design modeling\\\\While many works on reasoning on conceptual schemas focus on class diagrams and state diagrams, the most often used diagram type at SAP is the block diagram. For example, class models are used rarely, as they are ``too close to real code.'' In general, developers and architects prefer structural diagrams (e.g., block diagrams), thus we need to ask ourselves the questions, if we can reason over such models and what kind of properties help to improve the software development.},
author = {Achim D. Brucker},
day = {20},
event = {Dagstuhl Seminar 13211 ``Automated Reasoning on Conceptual Schemas''},
handout = {https://www.brucker.ch/bibliography/download/2013/talk-brucker-modeling-sap-2013-2x2.pdf},
isodate = {2013-05-20},
lecturer = {Achim D. Brucker},
location = {Dagstuhl, Germany},
month = {may},
slides = {https://www.brucker.ch/bibliography/download/2013/talk-brucker-modeling-sap-2013.pdf},
title = {Modeling@SAP},
url = {https://www.brucker.ch/bibliography/abstract/talk-brucker-modeling-sap-2013},
year = {2013},
}