Language and Metamodels for SEMAT Arne J Berre
Language and Metamodels for SEMAT Arne J. Berre Shihong Huang Brian Elvesæter
Layer 1 - Core
Layer 2 - Practice. And. Alpha
Layer 3 Activity Space and Activity elements
Layer 3 Competency and Skill elements
Layer 3 Pattern elements
Layer 4 Method. And. Library
SEMAT Diagrams – Graphical Notation
SEMAT – Textual Notation
Introduction to ISO/IEC 24744 Cesar Gonzalez-Perez Brian Henderson-Sellers
SPEM Process ISO 24744 aspects only Process, product and quality aspects Method domain only Method and endeavour domains Obscure and informal Easy and intuitive extension mechanisms Unable to express non Copes with complex -trivial scenarios Highly dependent on Self-contained UML Comparison at a glance
abstraction 24744 SPEM UML scope Comparison, graphically
ISO/IEC 24744 is an international standard Based on experience: ◦ Fujitsu, Microsoft, SQI, JPL, plus other 20 ◦ Input from 25+ countries ◦ Australian AS 4651 (2004) ◦ Field consulting from UTS, Neco ◦ Top-notch academic research ◦ Errors of previous attempts Led from academia 2003 -2007 Submission to OMG, February 20 th, 2012 History of 24744
Task Kind Task powertype Name Purpose Min. Cap. Lev “Code Writing” “To write code…” 1 clabject Start End Duration partitioned type Code Writing Language 12 -Sep-07 15 -Sep-07 3 “C#” Moving on to metamodelling
Task Kind Name Purpose Min. Cap. Lev “Code Writing” “To write code…” 1 Task Start End Duration Code Writing metamodel method Language 12 -Sep-07 15 -Sep-07 3 “C#” Putting things in context endeavour
Methodology elements Templates Endeavour elements Metamodel areas Resources
Metamodel overview
24744: ◦ Captures what developers do (endeavour) by enhancing expressiveness ◦ Integrate endeavour and method domains (powertype patterns) ◦ Integrate process and product ◦ Address quality and capability issues (Min. Capability. Level attribute) ◦ Support for affordable extensibility (regular OO mechanisms) Summary
Lifecycle diagrams, which represent the overall structure of a method (or part of it). Enactment diagrams, which represent a specific endeavour (or part of it) and its relationship to the corresponding method. Dependency diagrams, which represent the abstract support/dependency relationships among the major components (i. e. producer kinds, work unit kinds and work product kinds) of a methodology. Process diagrams, which describe the details of the process kinds used in a method. Action diagrams, which show the detailed usage interactions between task kinds and work product kinds. SEMDM Diagrams – Graphical Notation
Stage. With. Duration. Kind Build. Kind Process. Kind Time. Cycle. Kind Instantaneous. Stage. Kind Process. Kind Phase. Kind Milestone. Kind Technique. Kind
Out. Come Model. Kind Work. Product. Kind Software. Item. Kind Composite. Work. Product. Kind Producer. Kind Document. Kind Hardware. Item. Kind Team. Kind
Role. Kind Pre. Condition Guideline Tool. Kind Post. Condition Person Conglomerate
A dependency diagram based on a refinement
An action diagram showing how requirements-related task kinds interact with requirements- related work products.
- Slides: 30