welcome to the course tdt4250 model driven development of
play

Welcome to the course TDT4250 Model-Driven Development of - PowerPoint PPT Presentation

Welcome to the course TDT4250 Model-Driven Development of Information Systems Hallvard Trtteberg, Associate Professor IDI, NTNU This week chap B1 Information about the course Motivation Why model? Why take this


  1. Welcome to the course TDT4250 Model-Driven Development of Information Systems Hallvard Trætteberg, Associate Professor IDI, NTNU

  2. This week chap B1 � � Information about the course � � Motivation � � Why model? � � Why take this course ? � � Clarification of the scope of the course � � Overall picture of the use of modeling approaches in information systems development and evolution NB! The course is part of several study programs, including an International Master program and will be lectured in English. Please feel free to ask questions in Norwegian (or English)

  3. Background on me � � Siv.ing (Master) and PhD IDI, NTNU (1991, 2002) � � Employed 5 years in SINTEF ICT (Oslo) � � Started as Associate Professor at IDI 2002 (after finishing PhD) � � Married, 2 children � � http://www.idi.ntnu.no/~hal Modeling Software Engineering UI design

  4. Background on the course TDT4250 � � Have been a course on modeling techniques within the information systems (IS) group last 20 years � � Content changed regularly (yearly), emphasis has changed as the application of modeling in practice change: � � process modeling with industry-standard BPMN � � practical modeling with Eclipse-based tools � � Follow-up course: TDT4252 - Modelling of information systems � � Spring, more research-oriented

  5. ”Prerequisites” for TDT4250 OO (UML) modeling Class diagrams Collaboration diagrams Sequence diagrams Use-Case diagrams Activity diagrams Process modeling DFD or sim. ER modeling

  6. Your background ? � � Study program � � Earlier courses � � Modeling experience � � Learning expectations � � Short survey in the end � � Reflection note

  7. Learning goals ( From study plan) � � theoretical insights into different languages and techniques used in industry for model-driven information systems development � � BPM – Business Process Management � � MDA / MDD – Model-driven development � � EA – Enterprise Architecture � � DSL/DSM – Domain specific languages / modeling � � practical skills in making good models in central parts of the above areas

  8. Course information: Curricula, lectures Curriculum � � Michael Havey: “Essential Business Process Management”, � � published by O’Reilly Parts of another book (under revision) � � Collection of articles � � � � Do NOT plan to print these centrally � � Available on the net (through it’s learning) Lectures and assignments are also part of the curriculum � � Persons � � Main responsible: Hallvard Trætteberg � � Assignments: Hong Guo and Gustav Aagesen � � Lecturer: Hallvard Trætteberg � � Some guest lectures � � Lecture time (but expect changes) � � Lectures: Tuesdag 12-14 in F4 and Thursday 14-15 in F3 � � Exercises: Wednesday 17-19(!) in F3 � �

  9. Course information: Assignments � � Some of the assignments counting on the final grade (portfolio evaluation) � � Assignments counts 30%, 70% on written exam � � Points from both assignements and exam put together to calculate the final grade � � Assignments both on the computer (using various tools),on paper, and on the web � � Assignments done in groups You are expected to form own groups (3-4 people) � � � � More information on the assignments/exercises on Thursday 20/8 14:15-15:00 � � Please also nominate 2-3 people to reference group

  10. Overall terminology Information systems � � Both the automated part and � � information processing performed by humans (alone or supported by � � information systems) Model: can be almost anything � � Representation of the past, current, or potential future � � More abstract, usually less comprehensive, and normally cheaper to make � � than what it models Important to select which parts to represent � � In TDT4250: Modeling across the areas of analysis, design and use, focus on � � Models directly used as part of the (executable) information system � � Models transformed into the (executable) information system � � Analysis: Understand a problem (descriptive mod.) � � Requirements specification: indicate a solution (prescriptive mod.) � � Design specification: Detail a technical solution (prescriptive mod.) � � Modeling of work in work (reflexive mod.) � �

  11. Information systems come in many forms Windows 3.1/ 4.x FCP 2.4 Filserver/DBserver NTAS FCP V2.4 Local office Oracle NTAS/LM TCP/IP IP WAN Customer system BULL DPS 9000 FCP V 2.4 AIX Foundation FCP 2.4 BULL Gateway Oracle NTAS/LM TCP/IP AIX

  12. Motivation (1) � � IS development is ripe with modeling tasks � � A model represents how people perceive an area (domain) � � Important to understand the mechanisms that are in play when modeling (alone or in a large group of people) � � Important to be able to say if a model is (sufficiently) good or not, and how good models and modeling languages can be made � � Modeling (in e.g. analysis and requirements specification) is difficult

  13. Motivation (2) � � Many large IS projects with overruns � � Potential of model-driven approaches � � Quicker development of information systems � � Development of more flexible information systems � � Program code � � Detailed, expensive to write and maintain � � Implicit model/requirements, poor overview � � Difficult to discuss with end-user � � What if there is a buy or make decision? � � What if there is an automate or support decision?

  14. Motivation (3) � � Models are � � Quicker and cheaper to make than the full artifact, but � � similar so that it is often possible to spot consequences of decisions e.g. by means of analysis, simulation, inspection etc. � � Risk-free testing � � What-if scenarios � � Accident simulation � � Avoid costly mistakes � � Produce more innovative results of better quality

  15. Motivation (4) Who can benefit from the material lectured in the course? Everyone involved with system development, especially those involved � � in model-driven development (e.g. use EA, MDD/MDA, BPM or SOA) Especially those working with database systems, web application, � � telecommunications and mobile systems, workflow/BPM systems, ERP-systems – These are areas where modeling is used a lot Those working with choice and adaptations of development � � methodology, modeling language or modeling tool in an organization Those working with the development of modeling tools � �

  16. Scope of the course(1): What kind of models? � � Modeling of the current situation � � Analysis � � Perceived future information system (IS) � � Perceived future computerized IS (CIS) � � Requirement specification � � Design of future CIS � � Design � � Change of operative solution � � Interactive model, model as configuration

  17. Scope of the course (2) � � A large number of modeling languages (>500), methodologies and tool, new are developed constantly � � Not possible to cover everything � � More emphasis on � � Learning for future learning � � Application of general frameworks � � A selection of a limited number of modeling languages and methods to work with in more detail � � Try to avoid too much fragmentation � � Several articles on the same languages, some overlap between articles

  18. Overall time schedule for lectures (may change) Week 34: Introduction and overview � � Week 35: BPM and workflow � � Week 36: Process modeling languages � � Week 37: BPMN � � Week 38: Process patterns/BPEL/WFMC � � Week 39: Quality of models and languages � � Week 40: Enterprise modeling/Enterprise Architecture � � Week 41: Guest lecture Accenture (EA->BPM->SOA) � � Week 42: MDA, EMF and model transformations � � Week 43-44: Application of MDA � � Week 45: Meta-modelling and Domain Specific Modeling and � � Modeling Languages Week 46: Course summary and wrap-up � �

  19. Questions and clarification? Please use last minutes to answer the survey and return to me

Recommend


More recommend