adms-bis bouwkundige informatiesystemen adms 2006 uml part 1 jan dijkstra - 9 oktober 2006 adms-bis

Download ADMS-BIS Bouwkundige Informatiesystemen ADMS 2006 UML part 1 Jan Dijkstra - 9 oktober 2006 ADMS-BIS

Post on 21-Dec-2015

218 views

Category:

Documents

5 download

Embed Size (px)

TRANSCRIPT

  • Slide 1
  • ADMS-BIS Bouwkundige Informatiesystemen ADMS 2006 UML part 1 Jan Dijkstra - 9 oktober 2006 ADMS-BIS
  • Slide 2
  • Subjects
  • Slide 3
  • ADMS-BIS UML Introduction
  • Slide 4
  • ADMS-BIS Information system design with UML Having knowledge of the visual modelling language UML in the field of ICT. Gain a clear understanding of applying this knowledge for specifying, constructing, visualizing and documenting software-intensive systems.
  • Slide 5
  • ADMS-BIS Study Matter Ian Sommerville Software Engineering, 6 th edition Ch.6 Addison Wesley Dean Leffingwell & Don Widrig Managing Software Requirements, 2 nd edition Addison Wesley Grady Booch, James RumBaugh & Ivar Jacobson The Unified Modeling Lnaguage Covers UML 2.0, 2 nd edition Addison Wesley Martin Fowler UML Distilled, 3 nd edition Addison Wesley Fowler & Scott UML beknopt, 2 nd edition Addison Wesley Sander Hoogendoorn Pragmatisch modelleren met UML 2.0 Addison Wesley
  • Slide 6
  • ADMS-BIS About UML UML offers a standard way to write a systems blueprints, including conceptual things such as business processes and system functions as well as database schemas. UML is a modelling language, a notation used to express and document designs.
  • Slide 7
  • ADMS-BIS What is the UML? The Unified Modelling Language (UML) is the successor to the wave of object-oriented analysis and design (OOA&D) methods that appeared in the late 80s and early 90s. It unifies the methods of Booch, Rumbaugh (OMT), and Jacobson (3 amigos).
  • Slide 8
  • ADMS-BIS Data and Processes Traditional, the division between data and processes were structured separately, and functions made use of data For OO an object contains data and processes encapsulation information hiding avoiding domino effect adaptations more simple and cheaper maintenance
  • Slide 9
  • ADMS-BIS Domain modelling Traditional, functional decomposition was the strategy adaptations are difficult For OO domain modelling independent of the required functions objects encapsulates functionality It is easier to make adaptations and extensions
  • Slide 10
  • ADMS-BIS UML is for modelling Building models of complex systems because one cannot comprehend such a system in its entirely. At this, a model is a simplification of reality is a set of blueprints of a system is an abstraction of something for the purpose of understanding it before building it may be expressed a different level of expression (no single model is sufficient)
  • Slide 11
  • ADMS-BIS UML is for visualizing An explicit model facilitates communication. UML symbols are based on well-defined semantics.
  • Slide 12
  • ADMS-BIS UML is for specifying and constructing Specifying means building models that are precise, unambiguous and complete. UML addresses the specification of all the important analysis, design, and implementation decisions made in developing and deploying a software system.
  • Slide 13
  • ADMS-BIS UML is for documenting UML addresses the documentation of a systems architecture and all of its details.
  • Slide 14
  • ADMS-BIS UML is a language UML is a visual language for software blueprints with a vocabulary and rules for communication; and a focus on conceptual and physical representations.
  • Slide 15
  • ADMS-BIS UML: graphical notations 1
  • Slide 16
  • ADMS-BIS UML: graphical notations 2
  • Slide 17
  • ADMS-BIS UML Models, Views and Diagrams A diagram is a view into a model presented from the aspect of a particular stakeholder and provides a partial representation of the system
  • Slide 18
  • ADMS-BIS UML Views Design view Interaction view Implementa- tion view Deployment view Use Case view vocabulary functionality behaviour performance scalability throughput system assembly configuration management system topology distribution delivery installation physicallogical
  • Slide 19
  • ADMS-BIS UML Diagrams Structure diagram Class diagram Object diagram Component diagram Composite structure diagram Deployment diagram Artifact diagram Behaviour diagram Use Case diagram Sequence diagram Communication diagram State diagram Activity diagram
  • Slide 20
  • ADMS-BIS Use Case diagram
  • Slide 21
  • ADMS-BIS Class Diagram
  • Slide 22
  • ADMS-BIS Object diagram
  • Slide 23
  • ADMS-BIS Sequence diagram
  • Slide 24
  • ADMS-BIS Activity diagram
  • Slide 25
  • ADMS-BIS Component diagram
  • Slide 26
  • ADMS-BIS Deployment diagram
  • Slide 27
  • ADMS-BIS UML: what we will cover Use case diagrams Documenting the systems behaviour from the users viewpoint, requirements capture Activity diagrams Describing the sequencing of activities with support for both conditional and parallel behaviour Class diagrams Describing the type of objects in a system and the static relationships between them
  • Slide 28
  • ADMS-BIS UML steps 1.Examine the necessities of the information system use cases & use case text with flow description by activity diagram Use Case Diagram & Activity Diagram UML1 2.Object-oriented domain analysis decomposition of the problem field in concepts, attributes and associations that may be of relevance to the information system Class Diagram (including Object Diagram) UML2
  • Slide 29
  • ADMS-BIS Activity Diagram
  • Slide 30
  • ADMS-BIS Example
  • Slide 31
  • ADMS-BIS Activity Diagram: what is it? Describes activities and flows of data or decisions between activities Provides a very broad view of business processes Can be used to break out the activities that occur within a use case Good for showing parallel threads
  • Slide 32
  • ADMS-BIS Activity Diagram: what is it? Describes activities and flows of data or decisions between activities Can be used to break out the activities that occur within a use case
  • Slide 33
  • ADMS-BIS Activity Diagram: when to use it? When describing work flow across many use cases When analysing a use case, and assigning scenarios When dealing with multi-threaded applications
  • Slide 34
  • ADMS-BIS UML Activity symbols
  • Slide 35
  • ADMS-BIS Action State In a conceptual diagram an activity is a task that needs to be done either by a human or a computer In a specification-perspective diagram or an implementation-diagram, an activity is a method on a class
  • Slide 36
  • ADMS-BIS Sequential Branching A sequential branch is represented as a diamond It may have one incoming transition and two or more outgoing transitions Guards are associated with each transition
  • Slide 37
  • ADMS-BIS Branch & Merge
  • Slide 38
  • ADMS-BIS Forking and Joining Concurrent activities within an activity diagram are modelled with the use of synchronised bars Joins and Forks should balance
  • Slide 39
  • ADMS-BIS Forks, Joins & conditional Threads
  • Slide 40
  • ADMS-BIS Exercise 1 Activity Diagram Make an activity diagram of the following situation: At a course administration department a student makes a request for registering a course. Prior to an actual registration, the foreknowledge of the student is checked. Concurrent, there is a check whether the course is full or not. If the foreknowledge of the student is ok, there is a registration if possible. Otherwise, the possibilities for a special regulation will be explored. Is a special regulation possible, there is a registration too (if possible).
  • Slide 41
  • ADMS-BIS Solution Exercise 1
  • Slide 42
  • ADMS-BIS Swim lanes The activities of an activity diagram may be performed by different groups. Each zone or lane represents the responsibilities of a particular group.
  • Slide 43
  • ADMS-BIS Exercise 2 Activity Diagram Make an activity diagram including swimlanes of the following situation: A client places an order for a product at a company. The sales department will process the order and subsequently the stockroom assembles the ordered goods and dispatches the order. As a result of the order and after the message of the stockroom that the order is dispatched, a receipt and an invoice are sending parallel to the client. The sales department prepares the invoice. If, subsequently, the client has paid the invoice, the sales department completes the order.
  • Slide 44
  • ADMS-BIS Solution Exercise 2
  • Slide 45
  • ADMS-BIS Date2date example: scenarios
  • Slide 46
  • ADMS-BIS Use CaseInloggen abonnee Actors Abonnee, bezoeker Description Pre-conditions Checken op geldigheid actor als abonnee ---- Basic flow 1.Valideer aantal ongeldige logins 2.Toon webpagina login 3.Actor voert login en password in 4.Actor bevestigt 5.Applicatie valideert login 6.Markeer actor als abonnee Extension / Exception flow 1a Login ongeldig 1a 1 Aantal ongeldige logins >2, stop 5a Login ongeldig 5a 1 Verhoog aantal ongeldig logins, herhaal 1 Post-conditions Actor is beke