1 / 47

W E L C O M E

W E L C O M E. Griffith University School Of Computing and Information Technology CIT 505 – Master of Information and Communication Technology presented by Ovidiu S. Noran M IEAust PEng. Mapping of ISO12207 and ISO15288 on ISO15704. http://www.cit.gu.edu.au/~noran.

sawyer
Télécharger la présentation

W E L C O M E

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. W E L C O M E

  2. Griffith University School Of Computing and Information Technology CIT 505 – Master of Information and Communication Technology presented by Ovidiu S. Noran MIEAust PEng Mapping of ISO12207 and ISO15288 on ISO15704 http://www.cit.gu.edu.au/~noran

  3. ’Contents’ • Introduction • The Problems and Solutions • Life Cycle Architectures • Standards Used in the Mapping • Concepts • Standards Mapping • Entities Mapping • Conclusions

  4. ’Contents’ • Introduction • The Problems and Solutions • Life Cycle Architectures • Standards Used in the Mapping • Concepts • Standards Mapping • Entities Mapping • Conclusions

  5. ’Introduction’ The Standards. • ISO 15288 – Systems Life Cycle Processes. • ISO 12207 – Software Life Cycle Processes. • ISO 15704 – Requirements for Generalised Enterprise Reference • Architectures and Methodologies. Tasks. • Identify the problems, propose solutions. • Review the life cycle architectures and standards under consideration. • Provide the solutions and justify them. • Draw some conclusions.

  6. ’The Problems and Solutions’ • Introduction • The Problems and Solutions • Life Cycle Architectures • Standards Used in the Mapping • Concepts • Standards Mapping • Entities Mapping • Conclusions

  7. Process 1 Activity 1 Activity 2 Process 2 Activity 1 Activity 2 ‘To-Do list’ ’The Problems and Solutions’ Problems. • Enterprise, software and systems engineering need a common terminology. Aims: Avoid misunderstandings. Provide a common base for discussion. Promote cooperation, compatibility and concept / other resources sharing. • System and software life cycle engineering domains are lacking a suitable architecture. The current Standards resemble process repositories. Solutions. • Provide unique, concise explanations for the common terms. • Use a generalised ref. life cycle architecture and methodology: • holds models and modelling methods from all domains • allows to identify missing modules

  8. ’Contents’ • Introduction • The Problems and Solutions • Life Cycle Architectures • Standards Used in the Mapping • Concepts • Standards Mapping • Entities Mapping • Conclusions

  9. Dedicated phase 2 4 O R I 1 (MF) F Req. Des. Impl. European CIM Architecture Commission of the European Community Research Program 3 Simulation Execution ‘Life Cycle Architectures’ CIMOSA : CIM Open System Architecture. Developed by the AMICE Consortium (a series of ESPRIT projects).

  10. Human Role ‘ility’ lines ‘Life Cycle Architectures’ PERA : The Purdue Enterprise Reference Architecture. • Developed at the Purdue Laboratory of Applied Control, University of Purdue by a team led by Prof. Williams, since 1989. • It is a complete (Purdue) methodology. • Innovative: Models human aspects.

  11. ‘Life Cycle Architectures’ PERA : The Purdue Enterprise Reference Architecture.

  12. GRAI Conceptual Model ‘Life Cycle Architectures’ GRAI - GIM : GRAI Integrated Methodology. Origins: GRAI – Graphs with Results Activities Interrelated – Univ. of Bordeaux – France 1987 (automated manuf. systems modelling / analysis); Merise – IS design and analysis methodology – 1983.

  13. Integrated Manufacturing Planning and Control System (ESPRIT project) ‘Life Cycle Architectures’ GRAI - GIM : GRAI Integrated Methodology. GRAI – GIM provides a modelling methodology … … of which the latest representation is the IMPACS model.

  14. Content, Purpose, Implementation, Manifestation ‘Life Cycle Architectures’ GERA : The Generalised Enterprise Reference Architecture. • Developed by the IFIP / IFAC Task Force (1994 -). • Generalisation of the other architectures. • Models human aspects, enterprise life cycle and life history.

  15. (Life History) ‘Life Cycle Architectures’ GERA : The Generalised Enterprise Reference Architecture. • The life cycle / life history relation in GERA.

  16. ‘Contents’ • Introduction • The Problems and Solutions • Life Cycle Architectures • Standards Used in the Mapping • Concepts • Standards Mapping • Entities Mapping • Conclusions

  17. Project management ‘Standards Used in the Mapping’ ISO 15288: System Life Cycle Processes. • Life cycle is partitioned into processes, which consist of activities. • Systems life cycle composed of a set of essential stages. • Tailoring is allowed for a particular system. • Stages = milestones -> associated temporal dimension.

  18. ‘Standards Used in the Mapping’ ISO 15288: System Life Cycle Processes. • The life cycle stages, objectives and decisions.

  19. ‘Standards Used in the Mapping’ ISO 12207: Software Life Cycle Processes. • Software life cycle composed of a set of primary, supporting and organisational processes. • Uses the concept of views for processes relationships. • Tailoring is allowed for a particular software system. • There is a proposed amendment which is heavily influenced by the systems life cycle ISO 15288.

  20. ISO 12207 Tailoring Example ‘Standards Used in the Mapping’ ISO 12207: Software Life Cycle Processes.

  21. ‘Standards Used in the Mapping’ ISO 15704: Requirements for Enterprise Reference Architectures. • Generally applicable (reference methodology, architecture, supporting toolset). • Must be a type 2 (life cycle) architecture. • Must offer a reference base containing methodologies and supporting technologies. • Specified requirements build (among others) on:  CIMOSA: modelling framework (F I R O views);  GRAI-GIM: mission fulfilment vs. mission control;  PERA: info vs. manufacturing, human role.

  22. ‘GERAM’ GERAM: Generalised Enterprise Reference Architecture and Methodology. • Introduced as an Annex of ISO15704 (a reference architecture example) • The life cycle / life history distinction. • Aimed at designing and maintaining enterprises for their entire life history. • Role of human, views, economic and project management aspects.

  23. The GERA view categories ‘GERA’ GERA: Generalised Enterprise Reference Architecture. • Views – used as filters, complementary, grouped in categories. • Not all views must be present… • … But all aspects have to be modelled in one view or another.

  24. Complete GERA views set ‘GERA’

  25. ‘Contents’ • Introduction • The Problems and Solutions • Life Cycle Architectures • Standards used in the mapping • Concepts • Standards Mapping • Entities Mapping • Conclusions

  26. ‘Concepts’ Concepts. 1. Milestone: used for life cycle stages implies a temporal dimension. Solution: use stage  temporal, process / functions within  non-temporal. 1. Milestone: used for life cycle stages implies a temporal dimension. Solution: use stage  temporal, process / functions within  non-temporal. 2. View: ISO15288: - used for system dynamics rather than architectural ISO12207: - used to group processes by purpose Solution: use the GERA view categories covering all aspects: Content (F I R O),Implementation, Purpose, Physical Manifestation. 2. View: ISO15288: - used for system dynamics rather than architectural ISO12207: - used to group processes by purpose Solution: use the GERA view categories covering all aspects: Content (F I R O),Implementation, Purpose, Physical Manifestation. 3. Model: ISO15288: enterprise, project, technical, etc (similar to views) ISO12207: none (or uses view concept instead) Solution: GERA unique model levels: e.g. metamodel, partial, particular.

  27. ‘Concepts’ Concepts (cont.) 4. Tailoring: ISO15288: select only applicable stages, add new. ISO12207:  first level (add/delete to partial model),  second level (apply to particular). Solution: GERA may accommodate all tailoring concepts: model refining and partial  particular movement. 4. Tailoring: ISO15288: select only applicable stages, add new. ISO12207:  first level (add/delete to partial model),  second level (apply to particular). Solution: GERA may accommodate all tailoring concepts: model refining and partial  particular movement. 5. Modularity: ISO15288, ISO12207 identify life cycle processes using different criteria (hence Primary / Supp. / Org. vs. Enteprise / Project / Technical / Agreement) Solution: GERA modularity concept (std interfaces, max cohesiveness, loose coupling) for reuse and isolation. 5. Modularity: ISO15288, ISO12207 identify life cycle processes using different criteria (hence Primary / Supp. / Org. vs. Enteprise / Project / Technical / Agreement) Solution: GERA modularity concept (std interfaces, max cohesiveness, loose coupling) for reuse and isolation. 6. Life History: ISO15288 and ISO12207 attach a history meaning to life cycle  problems modelling parallel / concurrent processes. Solution: GERA life history concept (unique, made of life cycle activities)

  28. ‘Contents’ • Introduction • The Problems and Solutions • Life Cycle Architectures • Standards used in the mapping • Concepts • Standards Mapping • Entities Mapping • Conclusions

  29. ‘Standards Mapping’ Direct Mapping of ISO15288 and ISO12207. • ISO12207 is a specialisation of ISO15288. • Processes are classified in the two Standards using different criteria. • Some technical processes in ISO15288 are supporting in ISO12207.

  30. ‘Standards Mapping’ Mapping of ISO15288 onto GERA. • A Stage / Phase Mapping. Observations: • Stages in ISO15288 have a temporal implication; GERA phases do not. • Difference in expresiveness: GERA can show concurrent / parallel activities. • Difference in granularity – one GERA phase may cover several stages.

  31. F C ‘Standards Mapping’ Mapping of ISO15288 onto GERA (cont.) • A Mapping using a combination of views. Observations: • Functional view in GERA has a broad coverage. • Use ‘scoping’ views in combination with Functional view. • Example: Entity Purpose view (mission fulfilment vs control)

  32. ‘Standards Mapping’ Mapping of ISO15288 onto GERA (cont.) • There are no information / resources / organisation models provided… • … However there are usable facts about purposes, outcomes, objectives. • Therefore some mappings may be attempted.

  33. ISO15288 Process Organisation ‘Standards Mapping’

  34. ‘Standards Mapping’ Mapping of ISO15288 onto GERA (cont.) Other views: 1. Resource : used in combination with the Physical Manifestation. 2. Implementation : human - Enterprise and Project Management, Design, Verif, Validation, Acquisition, Supply, etc (human decides) automated – Operation, Disposal, etc (fully / partially automated) 3. Physical Manifestation : hardware – Acq, Supply, Investment, Res. Mgmt, etc software - QA, Operation, Acq, Supply, Res. Mgmt, etc. 4. Purpose: control - Enterprise and Project Management, Tailoring. fulfilment - Technical Processes.

  35. ‘Standards Mapping’ Mapping of ISO12207 onto GERA. • A partial process model. • No explicit life cycle provided (e.g. like ISO15288) • Basic Functional and Organisational structures provided. • Information and Resource mappings may be attempted from available info.

  36. Information mapping derived from facts provided by ISO12207 Annex H ‘Standards Mapping’

  37. ‘Standards Mapping’ ISO12207 Functional model with organisational and mngment aspects

  38. ‘Standards Mapping’ Mapping of ISO12207 onto GERA (cont.) Other views: 1. Resource : used in combination with the Physical Manifestation. 2. Implementation : human - Joint Rev, Acq, Supply, Mgmt Improvement automated - Development, Prob Res, ConfMgmt, Maint, Mgmt (partially automated / support from machine) 3. Physical Manifestation : hardware - Training, Infrastructure software - Development, Maintenance, Documentation. 4. Purpose: control - Management, Conf Mgmt, QA, Audit. fulfilment - Operation, Maintenance, Prob Res, Development.

  39. ‘Contents’ • Introduction • The Problems and Solutions • Life Cycle Architectures • Standards used in the mapping • Concepts • Standards Mapping • Entities Mapping • Conclusions

  40. Manufacturing Entity (Type 3) Identification Strategic Management Entity (Type 1) Product: Enterprise Concept Engineering Entity (Type 2) Product: Enterprise Design Construction Entity (Type 2) Product: Enterprise Installation Manufacturing Entity (Type 3) Operation All Enterprise Entity Types Enterprise Product(Type 4) ‘Standards Mapping’ A Mapping on Entity Types. • Processes belong to different organisations (entities) . • ISO15288 and ISO12207 use different concepts to identify these entities. • Unify the approach by using the GERA entity types:

  41. Customer / Acquirer Infrastructure Providers Product may be an enterprise F Product Define Product C Engineering Project Enterprise Issue Tender Provide Logistic / Infrastructure Services Create Project Enterprise Do Engineering Design Engineering Contractor Build Product Contribute to Project Engineering Construction Company Engineering Subcontractors ‘Standards Mapping’ Enterprise Entities Contributions to a Product’s Life Cycle. • A project enterprise may be formed (VE) for the purpose of the product. • The product may be an enterprise, having products of its own … • … or it can simply be an e.g. software product.

  42. C/A EC, ES EPE ECC EPE, P(E) EPE, P(E) C/A C/A EPE, P(E) EC, ES, ECC, EPE P(E), EC ‘Standards Mapping - 15288’ ISO 15288 Entities Mapping. • Shows what processes may belong to which entity. • Some processes involve all participants. • Some involve only the participants in the VE.

  43. C/A EPE EC, ES, ECC, IP EPE,ECC EC, ECC EC C/A P, IP ECC,EPE EC EC,EPE ECC,EPE IP, ECC EPE EPE EPE ‘Standards Mapping - 12207’ ISO12207 Entities Mapping. • Uses the GERA entity types definition – consistent with the ISO15288 Entities mapping. • The product may considered to be a large software project. • Contractor / subcontractors may be designing / implementing modules for the final software system. • Infrastructure provider may provide dedicated / optimised hardware for the design / implementation and operation of the final software product.

  44. ‘Contents’ • Introduction • The Problems and Solutions • Life Cycle Architectures • Standards used in the mapping • Concepts • Standards Mapping • Entities Mapping • Conclusions

  45. GERAM may be used as an unifying platform for ISO15288 and ISO12207 • GERAM is able to cover all aspects of the two Standards, including • essential concepts, tailoring, life cycle / life history, etc. • The GERA ‘main’ content (F I R O) view used for ‘the big picture’. • Purpose, Implementation, Physical Manifestation ‘scoping’ views used for • emphasizing specific aspects. • Entities Mapping used to show the processes mapping on various entities contributing to the life cycle of a product ‘Conclusions’ Conclusions.

  46. ‘Conclusions’ Conclusions from the Mapping. • ISO15288 and ISO12207 are partial activity models (process  time, sequence). • No organisational, information or resources models are provided… • … however, mappings may be achieved using purposes, outcomes, objectives. • Two main issues must be resolved to promote consistency, sharing, reuse: 1. Unification of ISO15288 and ISO12207 terms and classification criteria 2. An architecture for both standards – maybe a how-to use guide using GERA(M). • This work has aimed to show what could be achieved by using a generalised • reference life cycle architecture covering both standards.

  47. ‘The End’ T H E E N D

More Related