2014 Pre-MSc-IS-0 Information Systems Modelling and Design

A431c87236a21a7bebf38de6bd12a67b?s=47 andreasmartin
September 11, 2014

2014 Pre-MSc-IS-0 Information Systems Modelling and Design

Programme: Master of Science in Business Information Systems FHNW
Course: Pre-Master Information Systems
Topic: Information Systems Modelling and Design

A431c87236a21a7bebf38de6bd12a67b?s=128

andreasmartin

September 11, 2014
Tweet

Transcript

  1. 1.

    Andreas Martin - Page 1 Master of Science in Business

    Information Systems FHNW Pre-Master Information Systems Information Systems Modelling and Design Andreas Martin Information Systems Modelling and Design http://www.flickr.com/photos/dirk_hofmann/4200450207
  2. 2.

    Andreas Martin - Page 2 Overview - Information Systems Modelling

    and Design Information Systems Modelling and Design
  3. 3.

    Andreas Martin - Page 3 1. Process Modelling 1.1 Process

    Graph Information Systems Modelling and Design
  4. 4.

    Andreas Martin - Page 4 1.1 Process Graph  To

    represent the targeting situation including all the stakeholders, a process model will be created.  The process graph is suited to model process with non IT- related people.  This means that IT related details are skipped. Information Systems Modelling and Design
  5. 5.

    Andreas Martin - Page 5 1. Process Modelling Process Layering

    - Business, Workflow and Execution Graph Information Systems Modelling and Design
  6. 6.

    Andreas Martin - Page 6 Business, Workflow and Execution Graph

    Information Systems Modelling and Design Petzmann, A., Puncochar, M., Kuplich, C. and Orensanz, D., 2007. Applying MDA ® Concepts to Business Process Management. In: L. Fischer, ed., BPM AND Workflow Handbook. Future Strategies Inc., pp.103–116.
  7. 7.

    Andreas Martin - Page 7 BP- Graphs and Technologies Information

    Systems Modelling and Design Business Process Modelling Languages: e.g. EPK, Petri Net, BPMN Extended Business Process Modelling Languages: e.g. BPMN, etc. Workflow Modelling Languages: e.g. BPMN, XPDL, BPEL Executable Code: e.g. Java, Services, BPEL4WS, XPDL Process Graph Workflow Graph Execution Graph Adapted from: Petzmann, A., Puncochar, M., Kuplich, C. and Orensanz, D., 2007. Applying MDA ® Concepts to Business Process Management. In: L. Fischer, ed., BPM AND Workflow Handbook. Future Strategies Inc., pp.103–116.
  8. 8.

    Andreas Martin - Page 8 1. Process Modelling 1.2 Workflow

    Graph Information Systems Modelling and Design
  9. 9.

    Andreas Martin - Page 9 1.2 Workflow Graph  The

    process graph will be extended with IT- related information or activities.  It is often the case that the workflow graph will be modelled directly (without modelling a process graph). Information Systems Modelling and Design
  10. 11.

    Andreas Martin - Page 11 2. Use Case Modelling 

    A use case model can be derived from a workflow model.  The use case model shows clearly what a prospective system has to fulfil.  It is still a common practice, that the process modelling step is skipped (starting with use case modelling) – but this is not recommended. Information Systems Modelling and Design
  11. 12.

    Andreas Martin - Page 12 3. Data / Domain Modelling

    3.A.1. Conceptual Model Information Systems Modelling and Design
  12. 13.

    Andreas Martin - Page 13 3.A.1. Conceptual Model  A

    conceptual model can be derived from use case model.  A good stating point is to represent the NOUNS of the use cases as concepts in the conceptual model.  The conceptual model contains entity names and entity relationships. Information Systems Modelling and Design
  13. 14.

    Andreas Martin - Page 14 3. Data / Domain Modelling

    3.A.2. Logical Model Information Systems Modelling and Design
  14. 15.

    Andreas Martin - Page 15 3.A.2. Logical Model  A

    logical model can be derived from conceptual model.  The logical model extends the conceptual model with attributes, primary keys, foreign keys and it is normalized. Information Systems Modelling and Design
  15. 16.

    Andreas Martin - Page 16 3. Data / Domain Modelling

    3.A.3. Physical Model Information Systems Modelling and Design
  16. 17.

    Andreas Martin - Page 17 3.A.3. Physical Model  A

    physical model can be derived from logical model.  The physical model extends the logical model with column data types. Information Systems Modelling and Design
  17. 18.

    Andreas Martin - Page 18 3. Data / Domain Modelling

    3.B. Domain Model Information Systems Modelling and Design
  18. 19.

    Andreas Martin - Page 19 3.B. Domain Model  A

    domain model can be derived from physical model (and vice versa). It is often the case that both models can be synchronized in both ways.  The domain model is represented as UML class diagram and will be used as blueprint for the persistence layer. Information Systems Modelling and Design
  19. 20.

    Andreas Martin - Page 20 3.B. Domain Model  Sometimes

    the domain model is derived directly from use case model. However, it is recommended to have a data model.  The domain model contains additionally technical information for implementing (or generating) the entity classes. Information Systems Modelling and Design
  20. 21.

    Andreas Martin - Page 21 Domain Model – Persistence Layer

     The domain model can be used as a blueprint to create the @Entity beans in a Java EE environment.  There are two options to create the entities:  Writing (or even generate) @Entity beans as Java classes and let the persistence mechanism generate the database schema.  Create SQL scripts that modify the database schema according to the target model (use physical data model instead class diagram). The @Beans can be reverse engineered or mapped using the persistence mechanism. Information Systems Modelling and Design
  21. 22.

    Andreas Martin - Page 22 4. Service / Business (Logic)

    Modelling Information Systems Modelling and Design
  22. 23.

    Andreas Martin - Page 23 4. Service / Business (Logic)

    Modelling  A service / business (logic) model can be derived from use case model.  A good stating point is to represent the VERBS (incl. NOUNS) of the use cases as methods.  Sometimes the business (logic) and the services will be modelled in separated models – it depends on the size of the project and the chosen system layering. Information Systems Modelling and Design
  23. 24.

    Andreas Martin - Page 24 Service / Business (Logic) Model

    – Business and Service Layer  The domain model can be used as a blueprint to create (or generate) business and service classes / interfaces in a Java EE environment.  The logic has to be crated by writing Java code in implementing classes. Information Systems Modelling and Design
  24. 25.

    Andreas Martin - Page 25 5. Workflow Modelling & UI

    Design 5.1. User Interface Information Systems Modelling and Design
  25. 26.

    Andreas Martin - Page 26 5.1. User Interface  The

    user interface (UI) can be derived from use case model in conjunction with the process model. Information Systems Modelling and Design
  26. 27.

    Andreas Martin - Page 27 5. Workflow Modelling & UI

    Design 5.2. Execution Graph Information Systems Modelling and Design
  27. 28.

    Andreas Martin - Page 28 5.2. Execution Graph  The

    execution graph will be derived from workflow graph – usually it has to be remodelled or if available transferred using a round- tripping mechanism.  The execution graph will be extended with technical items  variables,  interfaces to services and  user interfaces… Information Systems Modelling and Design
  28. 29.

    Andreas Martin - Page 29 Execution Graph and UI –

    Process and Presentation Layer  The user interface can be used as a template to create (or extend) the user interface on presentation layer.  The execution graph model will be execution using a process engine on process layer. Information Systems Modelling and Design