IN-MMO Agenda IN-MMO. Packages in UML. More UML Modelling. Packages, containment and dependency. Import

Transkript

1 Agenda IN-MMO Forelesning Brian Elvesæter Oblig b Presentation (Group 3 & 5) More UML Modelling Usability and UML Business Modelling Discussion COMET Business Model WesternGeco Survey Booking Reference Example More Objecteering/UML Questions and discussion 2 More UML Modelling Packages in UML Structural modelling Building blocks of UML Classes Attributes/Operations Associations Packages Extension mechanisms Behavioral modelling Use Cases Interactions Sequence diagrams Collaboration diagrams Statecharts Activity Diagrams Geometry Package (from Logical View) + Accuracy + TopologicalGeometry + RepresentationalGeometry + TemporalGeometry + Geometry + Vector{dimension} + SpatialVector A mechanism to group related classes of a model. Packages dependencies summarize dependencies between classes of different Packages. Packages can contain other Packages. Can show the Class/Entities found in a given Package. 3 4 Packages, containment and dependency Import X Y A B +C «import» +E -D X Y A B Y::C +C «import» Y::E +E -D The associations are owned by package X 5 6

2 Common Mechanisms Common Mechanisms: Stereotype, tagged values and constraints Adornments: - Notes Extensibility mechanisms: (stereotypes, tagged value, constraint) Notes: Comments and constraints <<requirement>> Shall conform to. Stereotype <<interface>> Constraint and Comment {Person.employer = Person.boss.employer} Element properties, tagged value {author = Joe Smith, status = analysis} << stereotype >> Subclass of existing modeling element - may have additional constraints and code generators will treat stereotyped element specially. 7 8 Stereotypes Tagged values - properties Used to define derivative modeling concepts based on existing generic modeling concepts Defined by: base (meta-)class = UML meta-class or stereotype constraints required tags (0..) icon A model element can have at most one stereotype Name (tag) separator (=) value (of the tag) properties on an element - relevant for code generation or configuration management (Can be applied to all UML elements) Server {processors = 3} Billing {version=3.2 status=checkedout by=ajb} 9 0 OCL - Object Constraint Language First order predicate logic, for boolean expressions - included in UML. Can be used for: invariants, value restrictions, pre and post conditions Expressions with: and, or, not, implies, exists, forall, Person Collections (select, reject, collect, iterate) self.age > 0 State Models: Simple Some objects have simple interesting states We can draw a state diagram of these states Each state is like a boolean attribute The structure of the states represents an mutually exclusive invariant Transitions between states visually show partial operation specs Gas Pump idle, pumping ready: Boolean inv xor (idle, pumping, ready) attributes + op specs GasPump idle hang up pick up ready Married people are of age >= 8 self.wife->notempty implies self.wife.age >= 8 and self.husband->notempty implies self.husband.age >= 8 and pickup squeeze release hang up pre idle post ready pre ready post pumping pre pumping post ready pre ready post idle release pumping squeeze 2 2

3 Outputs and Actions As the automaton changes state it can generate outputs: Lamp On off Lamp Off on on/print( on ) off Lamp On print( on ) off Lamp Off on on off Activity Diagram Applications Intended for applications that need control flow or object/data flow models... rather than event-driven models like state machines. For example: business process modeling and workflow. The difference in the three models is how step in a process is initiated, especially with respect to how the step gets its inputs. Mealy automaton Moore automaton 3 4 Activity Diagram Swim Lanes Activity Diagram 5 6 Actions and Object Flows Usability and UML 7 8 3

4 Definition of Usability Why usability? A concept comprising the effectiveness, efficiency and satisfaction with which specified users can achieve specified goals in a particular environment (ISO 924 v 2.5) The extent to which a product can be used effectively, efficiently and with satisfaction by specified users, for specified tasks in specified environments (ESPRIT 5429: MUSIC project) a measure of ease with which a system can be learned or used, its safety, effectiveness and efficiency, and attitude of its users towards it (Preece, 994, pp 722) shortening the time to accomplish tasks reducing the number of mistakes made reducing learning time improving peoples satisfaction with a system reduce development time 9 20 Rational for introducing usability User-centred design implies IBM gained a 400% increase in online sales (and an 84% decrease in help button usage) after redesigning their web site according to usability principles (Tedeschi, 999). Productivity within the service sector would rise 4% - 9% annually if every software program were designed for usability. (Landauer, 995) According to a 995 study by The Standish Group the three main factors in a successful software project are; user involvement, support from executive management and clearly formulated requirements ( The implementation of usability engineering techniques has demonstrated a reduction in the product development cycle by 33% - 50%. (Bosert, 99) Every $ invested in user-centred design returns between $2 and $00. (Pressman, 992) early focus on users, tasks and environment; the active involvement of users; an appropriate allocation of function between user and system; the incorporation of user-derived feedback into system design; iterative design whereby a prototype is designed, tested and modified; 2 22 Development process Phases - organisation along time Why modeling? Activity organization by work type Process activities Inception Elaboration Construction Business analysis Requirements capture Analysis & design Implementation Test Supporting activities Project management Transition Evaluation of the product with real users to see if it meets user requirements Communication with developers Users have mental models of their world ( user model ) Work product management Iterations: preliminary iteration(s) # #2 #n #n+ #n+2 #m #m+ Review milestones: User-centered techniques which give input to the design prosess Inception Review Prototype Iteration Launch Technical Audit Product Commit Demonstrator Iteration Launch Demonstrator Iteration Launch Demo / Delivery Beta Test Launch Acceptance Meeting

5 Target audience and description format The user and the designer Designers' world users The description of the Visual designers results should foster communication with the target audience Software developers Users Goals Tasks Referents Users' world guide Prototype Implementation Implementation Referents inform Designers specify produce and use specify Descriptions Models of the users world Handbooks User' World 0.. Referent Descriptions describes involves Referent.. uses.. used in task performance User Profile.. describes involves User Task performs.. description describes 0.. Task describes correspondence describes Use Case illustrated by Scenario illustrated by Pen-case used for paper prototyping and requirement sessions Viktige ting å tenke på når en skal planlegge bruk av brukersentrerte teknikker Brukere få med alle viktige brukergrupper: Ledelse, sluttbrukere, support,. Kritiske oppgaver finnes det noen oppgaver som MÅ støttes Hvor mye ressurser og tid er tilgjengelig? Lokal organisering og eksisterende metodikk

6 Hva er oppgaveanalyse? Hierarkisk Oppgaveanalyse Teknikker som har til hensikt å beskrive forutsetninger for og konsekvenser av å utføre en gitt oppgave. Særlig vekt på faktorer i arbeidsomgivelser, organisasjon og egenskaper ved brukere. Arbeidsoperasjoner brytes gjerne ned i deloppgaver for videre analyse. Sett inn kortet 2 Tast inn pinkode 0 Ta ut penger fra minibank 3 Velg beløp 4 Ta kortet 5 Ta pengene Sjekk saldo på konto 2 Sjekk saldo i kortet 3 Bestem beløp 4 Tast inn beløp Plan Hvis penger på konto Plan 3 hvis saldo > 0 gå videre ellers gå til 06 2 hvis saldo > 0 gå videre ellers gå til Avslutt transaksjon Trykk avslutt Velg skjerm/utskrift Les ny kontostatus på skjerm Mo tta kvitte ring 3 32 Avgjøre sak i høyesterett. Forberede 2. Behandle 3. Forberede 4. Forhandle 5. Etterarbeid 6. Postbehandling på direkte HRs sammen- statistikk 7. Svare 8. Utarbeide 9. Utarbeide for kjæremålsutvalutvalbehandling avdeling sak henvendelser setning og tablå sak i kjæremåls- for avdelings- sak i med avgjort PLAN Sivile saker PLAN Straffesaker : Når posten er fordelt (2 g/dag + bud fra : Når posten blir fordelt eller saken kommer med bud til adv. / statsadvokaten) straffesaksfunksjonær (2: Ikke aktuelt) 2: Når saken er mottatt - Fengslingskjæremål først, andre 3: Når saken er mottatt saker når fengslinger er ferdig fordelt til kjæremålsutvalget 4: Når saken er registrert (3: Ikke aktuelt) 5: Når saken er tildelt fra utredingsleder 4: Når saken er fordelt til kjæremålsutvalg 6: Når saken er ferdig utredet 5: Når saken er tildelt fra utredingsleder 6: Når saken er registrert. Motta sak.2 Registrere.3 Registrere.4.5 Utrede sak.6 Fordele til fra underrett ny straffesaksak ny sivil sak Planlegge kjæremålsutvalg eller utredning Se detaljering riksadvokat Se detaljering Se detaljering Samme som.2.2 Spørreteknikk Hierarkisk oppgaveanalyse Hva går forut? Hvorfor? Hva er oppgaven? Hva følger etter? NB! Begjæring om omgjøring av beslutning Hvordan?.4. Definere hva saken gjelder.4.2 Fordele til utreder Tabularisk oppgaveanalyse Fra brukersentrert teknikk til UML diagram Oppgavens Valg Kan Resultat av Bivirkninger Oppgave Oppgaven Oppgavens Fysiske og Sikkerhet mål Hva er brukeren oppgaven Kan det at frekvens s varighet fleksibilitet mentale Er oppgaven hovedmålet velge om Hva er oppgaven Hvor ofte Hvor lang Må brukeren krav ved å utføre de vil resultatet av blir utført er det tid vil følge en Faktorer skadelig denne bruke oppgaven? resultere i vanlig å brukeren bestemt som gjør eller oppgaven? produktet uheldige utføre vanligvis handlingsrekke for å krevende. brukeren oppgaven farlig for til å oppnå bivirkninger oppgaven bruke på det de?? oppgaven utføre eller ønsker?? oppgaven? andre? 0 Ta ut Få mere Ja, i Brukeren får Noen brukere til 5 5 min Ikke fleksibel Forstyrrelser Sjansen penger kontanter bankens mere vil bruke ganger per fra andre i for å bli fra åpningstid. kontanter og mere penger mnd. køen. Huske ranet er minibank lavere saldo enn ved uttak pin-kode. større enn på konto. i bank. Lesbarhet av ved uttak i skjermen. bank. (?) Skinn i skjermen. Stikke Starte Nei Adgang til Brukeren kan Hver gang 0 sek. (?) Ikke fleksibel Vanskelig å Nei inn kortet transaksjon, neste være usikker sette kortet identifisere deloppgave. på om riktig inn. seg. automaten Noen vil ha "sluker" problemer kortet. med å rekke opp. 2 Taste Identifisering Nei Adgang til Mulighet for Hver gang 20 sek. (?) Ikke fleksibel Man må (Se inn pinkode deloppgave. pin-koden? koden. neste at andre ser huske pin- bivirkning er) En oppgave i oppgaveanalysen kan brukes for å identifisere ett use case (systemnivå). COMET kravmodellering. Use casene kan videre analyseres med tanke på brukeropplevelse og grafisk brukergrensesnitt. En oppgave i oppgaveanalysen kan brukes for å identifisere en aktivitet i en prosess (virksomhetsnivå) COMET virksomhetsmodellering. Aktivitetsgrafene analyseres videre for å identifisere krav til systemet

7 Activity: Model the User-Experience Activity: Model the User-Experience Artifact: User-Experience Model (Use-Case Storyboards) Artifact: User-Experience Model (Use-Case Storyboards) Activity: Model the User- Experience Business Modelling Discussion Artifact: User-Experience Model Diskusjon Virksomhetsmodellering Sett dere sammen i grupper a 2-3 og diskuter begrepene: Virksomhet og virksomhetsmodellering Spørsmål i diskusjonen Hva er en virksomhet? Hvordan skal vi beskrive/modellere virksomheten? Hva er hensikten med virksomhetsmodellering? Hvordan kan vi bruke virksomhetsmodeller i systemutviklingen? COMET Business Model with WesternGeco Survey Booking Reference Example

8 Survey Booking Reference Example High-Level System Boundary The survey-booking tool will help to administer the utilization of our vessels. It will mainly benefit three user groups; Sales, operations and marine management. Sales will use it to book a survey or tender onto a vessel. The surveybooking tool will give an overview over the current workload and also which vessel qualifies for the job. Sales will make booking suggestions to management, which then need to be confirmed by the global marine management. For operations the booking tool should work as a planning aid. It will automatically warn about changes and it will have detailed job information available on-line. Marine management will be able to use the booking tool to assess the current resource usage, confirm survey bookings and to reschedule jobs. <<description>> The sales department is responsible for costing a survey and to initially book it on a vessel or region in case of a lead. Sales account managers, sales supervisors and sales managers are members of t his group. <<description>> M arine management will be responsible to confirm the booking of surveys onto a vessel. Regional marine management, business managers and global marine management are part of this group. Marine Management <<description>> Operations will be resp onsible for the survey prep arat ion and execution. Operations managers, vessel supervisors and party chiefs are the main members of this group. In addit ion t here are several service groups Operations which will also be included in this group: Operational supp ort (T echnical services), personnel management, accounting. <<descrip tion> > Introspection has two tasks. For the booking and booking validation process it shall inform about vessel configurations, which it can get from the vessel descrip tions. In addit ion the actual progress is ext ract ed from Introspection to keep the schedule up to date. Introspection Sales <<descript ion> > A person with administrator rights is needed to keep the system updated with regards to user names and rights and vessel names. SurveyBooking Administrator <<description>> A support role is needed to promote the input of competitor information. This role needs to access the system to obtain status Sup port on what is being added and by who Subsystem Grouping Component Structure Bus Pattern BookingEditor. Book tender/lead Introspection GlobalScheduleService BookingEditor BookingViewer S ubscriptioneditor 7a. View local s chedule 8. Assemble and deliver schedule 5. Reschedule job 2. U pdate booking status <<include>> 7. Synchronize and save schedule ActivityInfo Sales 5. Import from global schedule <<include>> 0. Add/remove users & rights Component Infrastructure 6. Export to global schedule <<include>>. Add/remove vessels BookingViewer <<include>> Administrator BookingService SubscriptionS ervice Sub scrip tio nservice 7b. View gl obal schedule Marine Management 9. Check for subscriptions & notify SubscriptionEditor 2. Subs cribe t o not ificat ion <<include>> 20. Update list of available subscriptions Subscrip tioninfo ActivityInfo SubscriptionInfo Op erat ions 2. Save/remove subscrip tions Business Model The Business Model is used to express the part played by the Product (system or component) being developed in the context of the business that will fund its development (or purchase it) and use it. The Business Model includes goals, business processes, steps within business processes, roles and resources. The scope (or domain) of the model is any part of the world defined as interesting for a company, organisation or others, and which has some impact on the required behaviour or other characteristic of the Product. The business model might be broadly or narrowly scoped, e.g. describing the entire business of a company or describing the immediate environment and context of a Product under consideration

9 Scoping statements Context statement The context statement, which defines the scope and positions this business model in its context. Vision for change, which describes what to improve, the motivation (i.e. what is wrong with the current situation), a description or indication of what the improvements might be and a gap analysis. Risk analysis, which identifies the business and technical risks related to a development project for the proposed Product. Methods and Techniques The first step in developing any business model is to identify and record the names of all people who will have an interest in having the Product developed or in its use, the business stakeholders, together with the nature of their interest. The following are examples of business stakeholders who should be involved: people who will authorise funding for development of the Product; people who are responsible for design and maintenance of the business processes to be supported by the Product; people who will use the Product; people who will be responsible for the acceptance of the Product; people who will be responsible for managing operation of the Product Scope and stakeholders Client contacts M arketing Liase with client Liase with sales Global fleet p lan Coordinate review review Issues tender Compile tender Issue award/loss Monitor vesel availability Monitor competitor activity Marketing Tender Bid Context Diagram [no bid] :Sales & Marine M anagement PreSales [qualified bid] <<ResourceAsArtefact>> :ITT :Op erat ions Tender Bid Review work specifications Propose technical solutions Oil Company Corporate Manager AccountManager Marketing [lost] [won] <<ResourceAsArtefact>> :SWO Technical Support Marine acquisition Produce a timeliy, quality image service to help clients find, p roduce and manage oil assets. Survey Preparation Op eration M anagement Data Processing Review op erational risks Monitor marine activity OBP proposals Legal Maritime Manager Optimize revenue Review contract Position vessels Assess risk Upgrade vessels Insurance Report Survey Execution Survey Close 5 52 Vision for change The vision for change document is short and describes what the Product will be and why it is needed. It will consist of some or all of the following elements: General business/product vision and goals, including background explaining why the Product is needed; Business opportunities and business benefits; Product description and technical business vision how the Product might be deployed and used; Presentation material summarising the above. Vision for change (/2) Beginning 2000 it was decided to phase out and replace the suite of business support tools used in the Tender bidding process in the Marine Acquisition Business segment. These tools were based on Excel technology and did not support the needs in a distributed 7by24 organization. Also after 0 years of evolution, pushing spreadsheet functionality beyond its limits, these tools were hard to maintain. The decision was to reengineer this tool-suite based on the Introspection business tool platform, which was based on Web and Java technology. The first priority was to look at The Survey Booking Tool and The Survey Costing Tool. The Survey Booking tool will help to administer the utilization of the seismic vessels and will be used to book a survey or tender onto a vessel. It will give an overview over the current workload and also which vessel qualifies for the job. The Survey Costing tool is used to calculate the cost and revenue of a potential survey

10 Vision for change (2/2) Goal Model The survey-booking tool is a web-based and highly automated tool to support the process around booking of vessel time for potential surveys. Its main task will be: Schedule leads and surveys Send automatic warnings on changes and conflicts Inform about current resource usage and potential backlog The goal model describes a loose hierarchy of goals of the business within the particular area of concern, starting with the goals of a Business Stakeholder in developing or buying the Product, and leading to the detailed business goals met by the Product or its users when using it. The Goal Model is discovered by a process of workshops and interviews involving all stakeholders (as identified in development of the Context Statement). Goals must be achievable, preferably measurable, and not selfevident, and should have clear and detailed implications. It should be reasonable (but not necessarily appropriate, and almost certainly not correct) to assert an alternative. The implications should be expressible in terms of a set of sub-goals or enabling processes Goal Model Business Process & Role Model Make a profitable bid Proper legal assesment S ound cost estimates Proper technical assesment Optimize fleet utilization Easy access to historical information Updated cost-models Updated own schedule Updated competitor schedule Purpose The objective of the Business Process Model is to identify and detail all the business processes supported by the Product to the extent necessary to detail the roles of the Product (and its components, i.e. Application Components, Business Service Components and Tool Components). Methods and Techniques The Business Process Model is derived through a set of activities that encompass brain-storming sessions, structured workshops, interviews and feed-back sessions, and detailed modelling using a UML tool Work Element Analysis (WARM) Tender Bid Process Overview In WARM refinement of the Business Process model, the kinds of step performed by resources in the model are further categorised as follows: A Human Step is a step performed by a human with no involvement of the Product being modelled. A Tool Step is a step performed by a human user interacting with a tool that is part of the Product. The human user will use some form of interactive device (e.g. a GUI) to interact with the Product. A Tool Step is a candidate for realisation by a Tool Component. An Immediate Step is a step that is required to complete as soon as possible, and whose intermediate states are of no concern to the business. It is performed autonomously, with no intervention from a human. An Immediate Step may be mapped to an Operation on a Business Service Component (Process) in the Architecture Model. [stop] Receive ITT & Prepare for bidding [continue] M ake Tender [continue] Submit Tender [stop]

11 Receive ITT & Prepare for bidding :Oil Company :Secretary :AccountManager :Manager Send ITT itt:itt Archive ITT ITT received Check ITT Make Tender :AccountManager :Manager :Reviewer {Surv Costin {Oth tool} Survey Costing Distribute ITT for review Part_of:ITT cpp:costpriceproposal Approve cost [? cost too high] [?Not approved] [?cost approved] booking:booking Create or update booking Check Competitor Schedule {Surve Bookin {Othe tool} Evaluate feedback [No issues] [Too high cost] feedback:reviewfeedback Review ITT Resolve issues [c ost issues] {Surve Bookin Create business review form recalculate cost brf:businessreviewform Bid approval {Surve Costin [cost ok] Compile Tender Make Tender [Cancel bid] {End of survey booking} tende r:tender Approve Tender Submit Tender [decide to send] [decide not to send] {End of survey booking} 6 62 Submit Tender Business Resource Model :Oil Company :AccountManager :Operations Review Tender tender:tender response:bidresponse Update booking status to tender sent Update booking status to bid won or lost Survey Preparation The Business Resource Model is an information model that identifies and defines the main things (and concepts) of the domain that are relevant to the Product. The Business Resource Model is generally prepared at the same time as the associated Business Process & Roles model, and methods and techniques used are similar, i.e. activities that include brain-storming sessions, structured workshops, interviews and feed-back sessions, and detailed modelling using a UML tool. Object flows in the activity diagrams are candidates for business resources Business Resources LocalS chedul e GlobalS chedule Configuration <<shall use>> SWO Schedule Client corp_code : undefined More Objecteering/UML Questions and discussions Crew Booking start : undefined end : undefined summary : undefined <<located in>> <<located in>> Vesse l <<owns>> Capacity Company Job Country Area/region Tender/Lead Survey Phase WesternGeco Competitor 65 66