Topic 13 Object-oriented Analysis

Transcription

1 Topic 3 Object-oriented Analysis a) f) DAAD Project Joint Course on Software Engineering Humboldt University Berlin, University of Novi Sad, University of Plovdiv, University of Skopje, University of Belgrade, University of Niš, University of Kragujevac Parts of this topic use material from the textbook H. Balzert, Software-Technik, Vol., 2nd ed., Spektrum Akademischer Verlag, 200 Version: July 30, 2003 (D May 4, 2003)

2 3. Object-oriented Analysis a) Overview: approaches, history, literature b) Object-oriented paradigm: basic notions c) Sub-models in UML d) How to read a given static OOA model? (Class diagram: example seminar organization ) e) Detailed specification: DD, pseudocode f) Packages 2 2

3 Classical waterfall model: the place of OOA Analysis and and Definition Design Design Balzert (200) Implementation Implementation Planning phase Feasibility study glossary preliminary requirements specification cost estimation project plan Definition phase Product definition requirements specification product model user interface user manual Test Test Usage Usage and and Maintenance Maintenance 3 3

4 Aspects of OOA Model paradigm: Decomposition of the SW systems into objects static / dynamic model (different views) Modeling language: UML: diagrams Methodology: How to develop a model? Tools: Together, Rational Rose, Paradigm Plus 4 4

5 Approaches, literature, systems of OO analysis: early works P. Coad, E. Yourdon. Objekt-orientierted Analysis. Prentice Hall, 990 J. Rumbaugh, M. Blaha, W. Premerlani, F. Eddy, W. Lorensen: Object-Oriented Model and Design. Prentice Hall, 99 OMT Object Modelling Technique Tool OMTool G. Booch: Object-oriented Analysis and Design with Applications. The Benjamin/Cummings Publishing Company, 994 Tool Rational Rose I. Jacobson, M. Christerson, P. Jonsson, G. Övergaard. Object-Oriented Software Engineering: A Use Case Driven Approach. Addison-Wesley, 994 Use Case Model Situation in more than 50 OOA methods - differences: notations, described aspects - Paradigm Plus: 996, tool supports methods 5 5

6 UML Unified Modeling Language authors: Rumbaugh, Booch, Jacobson Sept. 999: version.3 industry standard March 2003: Version.5 graphical language: collection of different diagram types for different views on the SWsystem critics: UML = mixture of methods UML only with syntax, without defined semantics 6 6

7 Approaches, literature, systems of OO analysis: the official UML literature J. Rumbaugh, I. Jacobson, G. Booch: The Unified Modeling Language Reference Guide, Addison Wesley, 999 G. Booch, J. Rumbaugh, I. Jacobson: The Unified Modeling Language User Guide, Addison Wesley, 999 I. Jacobson, G. Booch, J. Rumbaugh: The Unified Software Development Process, Addison Wesley,

8 History () Peter Coad in San Francisco His book»object-oriented Analysis«(990) (with E. Yourdon) helped to get OOA accepted. Introduced OOA patterns (995) 8 8

9 History (2) Dr. James Rumbaugh in Bethlehem, PA, USA Fellow, Rational Software Corporation Chief developer of the OMT method (Object Modeling Technique). 9 9

10 Goal of OOA like in case of structured analysis: produce a formalised product model (as part of product definition) with it: specialize requirements document combination of basic concepts: description of a system from different views 0 0

11 Combination of basic concepts in object-oriented analysis Data Dictionary (Balzert: attribute structure) Data flow diagram (Rumbaugh: functional model, 99) OOA 990 sequence diagram ER (Entity Rlationship) class diagram pseudo code state automaton collaboration diagram use case diagram entities & relations class structures control structures finite automaton interaction structures work flow

12 Basic concepts of software development Balzert vol., 2nd edition 200 Concepts and Views Alternative Notations Often used Rarely used nearly all concepts allowed Box diagram 973 Program flowchart 966 Decision tables 957 Activity diagram 997 Collaboration diagram Function tree Functional hierarchy Use Case Diagram 987 Business Process Data flow diagram 966 Information Flow Data- Dictionary 979 Data Structures Entity Relationship Model 976 Entity types and relations Class diagram 980/ 990 Class structures Functional View Data-Oriented View Object- Oriented View Pseudo code Control structures Algorithmic View Rules If-Then structures Rule- Based View State automat on 954 Finite State Automaton Petri Net 962 Concurrent structures State-Oriented View Sequence diagram 987 Interaction structures Scenario- Based View 2 2

13 from state automaton: Mealy automaton Moore automaton Harel automaton from time diagrams: sequence diagram OOA Sources of OOA from OOP: object operation class inheritance attribute message from semantical data modelling: aggregation (generalization type/ specialization type) from business processes: use case from ER model: associaltion with cardinalities (attribute) (entity type) 3 3

14 3. Object-oriented Analysis a) Overview: approaches, history, literature b) Object-oriented paradigm: basic notions c) Submodels in UML d) How to read a given static OOA model? (Class diagram: example seminar organization ) e) Detailed specification: DD, pseudocode f) Packages 4 4

15 OO paradigm: basic notions basic idea: decomposition of a SW system into objects and (object) classes basic notion: object used in all phases of SW development many definitions 5 5

16 Basic concepts of OO originally: on the level of programming (970,985) later: OOA, OOD (990) Object Class (collection of similar objects) Attribute (state, data of an object) Operation (behaviour) Message (sending messages to objects) Inheritance (class hierarchy) Polymorphism (overlaying of operations) known from OOP basic concept class diagram encompasses these OO concepts 6 6

17 Object-oriented analysis due to Booch (994) Object-oriented analysis is a method of analysis that examines requirements from the perspective of the classes and objects found in the vocabulary of the problem domain. Source: G. Booch: Object-oriented Analysis and Design with Applications, 994, page

18 The notion of object What is is an object? The official definition...? In the literature we find very different definitions! 8 8

19 Hopkins, Smalltalk: The notion of object () An Object is a combination of two parts:. Data the state of the object is maintained within that object 2. Operation all mechanisms to access and manipulate that state. ParcPlace VisualWorks Tutorial: Objects (are) software units that contain collections of related data plus operations for manipulating that data Rumbaugh: An object combines both data structure and behavior in a single entity. 9 9

20 The notion of object (2) Booch: Objects... are data abstractions with an interface of named operations and a hidden local state (994, page 38). A. Goldberg, Smalltalk 80: An object consists of some private memory and a set of operations. Booch: An object has state, behavior, and identity; the structure and behavior of similar objects are defined in their common class; the terms instance and object are interchangeable (994, page 83)

21 3. Object-oriented Analysis a) Overview: approaches, history, literature b) Object-oriented paradigm: basic notions c) Submodels in UML d) How to read a given static OOA model? (Class diagram: example seminar organization ) e) Detailed specification: DD, pseudocode f) Packages 2 2

22 Statical and dynamical model associations use case scenario static concepts dynamic concepts inheritance package message stateautomaton also also static? static? attribute operation static model also also dynamic? dynamic? object basic concepts class dynamic model 22 22

23 Statical and dynamical model: used UML diagrams associations use case? szenario inheritance static concepts class diagrams package diagrams component diagrams use casediagrams?? package attribute dynamic concepts stateautomaton message state automaton activity diagrams sequence diagrams collaboration diagrams operation static model object basic concepts class dynamic model 23 23

24 Diagrams in UML use case diagram: interaction of persons with systems class diagram: classes and their static relations sequence diagram: time-dependent flow of messages collaboration diagram: the same as sequence diagram package diagram: modularisation state diagram: dynamical behaviour of objects activity diagram: parallel processes component diagram: compilation units, hardware structure object diagram: objects and their relations 24 24

25 Application of UML diagrams in the phases of SW development (source: Informatik Spektrum, April 998) static model dynamic model use case diagrams Requirements activity diagrams class diagrams package diagrams Analysis sequence diagrams class diagrams (refined, with inheritance and associations) Design collaboration diagrams state-automaton component diagrams code classes definitions Implementation code methods object structure object behaviour 25 25

26 3. Object-oriented Analysis a) Overview: approaches, history, literature b) Object-oriented paradigm: basic notions c) Submodels in UML d) How to read a given static OOA model? (Class diagram: example seminar organization ) e) Detailed specification: DD, pseudocode f) Packages 26 26

27 Static OOA model: seminar organisation Company Shortname: String <0> Name: NameT Contact: ContactT Contact person: NamtT Sector: String <30> Contact person birthday: Date Function: String <30> Short information: String <200> Notices: String <200> Business volume: Float Client since: Date Booking Registered: Date Confirmation: Date Bill: Date Checked out: Date Notification: Date Register() Check out() Produce notification() Prove payment() Person Number: Serial Name: NameT Contact: ContactT Birthday: Date First registered: Date Short information: String <200> Notices: String <200> Produce address lable() Lecturer Biography: String<400> Daily honorar: Float Employer Associate 0.. Contractor Associate Entitlement: RoleET Password: String <6> Occupation: String <30> Is able to conduct Client Function: String <50> Business volume: Currency Participant Substitute paricipant Produce Notification() Client booking Customer Public seminar Cooperation partner: String<00> Cancel fee: Float Participant min: Short Participant actual: Short Produce participant list() Produce participant certificate() Company booking Company internal seminar All-inclusive price: Float Participants max: Short Presentation Number: Short Duration: Short From: Date To: Date Daily schedular start: Time Daily schedular stop: Time Start first day: Time End last day: Time Place: String <50> Participant max: Short Canceled: YesNoET Cancel() Produce honorar information() Register() Check out() Is free() Alternative seminars() Seminar supervisor Referent Seminar type Short titel: String<0> Titel: String <50> Purpose: String<400> Method: String<400> Overview: String<400> Daily procedure: String<20> Durance: Short Documents: String<200> Target group: String<200> Preconditions: String<200> Charge without tax: Float Participant number max: Short Participant number min: short 27 27

28 6 Read invoice data 4 Manage customers comp. booking data invoice data sets 3 Record paying delay 5 Manage companies Manage lecturers 2 Manage seminars DFD 0: Manage Seminars and Customers invoice information information booking data notific. letter notification letter request data requests request data requests info to lecturer lecturer data seminar short title lecturer data presentationno invoice certificates list of participants data base seminars and customers invoice data paying delays seminar requests seminar data invoice data invoice data invoice copies paying delays seminar information

29 Correlations requirements specification product model : structured analysis relation? product model 2: OO analysis Problems:. Is the information included in PM also included in PM2 (and vice versa)? 2. What about the understandability of the models? (readability, problem adequacy) 3. Is there a methodology to develop the corresponding model (easy to establish)? 29 29

30 Interface: Interface: comparable comparable with with a class class Client information booking data notific. letter bill 6 read invoice data comp. booking data invoice data sets information notification letter request data 4 requests manage customers Data Data flows: flows: collected collected sets sets of of attributes attributes billing data invoice data invoice copies invoice invoice data 3 record paying delay 5 manage companies lecturer data presentationno data base seminars and customers paying delays paying delays request data requests manage lecturers seminar short title certificates 2 manage seminars info to lecturer lecturer data list of participants seminar requests seminar data seminar information Some relations to OOA Product Product function function (F): (F): comparable comparable with with use use cases cases (general (general F) F) operation operation of of a class class (specific (specific F) F) 30 30

31 Static OOA model: seminar organisation Company Shortname: String <0> Name: NameT Contact: ContactT Contact person: NamtT Sector: String <30> Contact person birthday: Date Function: String <30> Short information: String <200> Notices: String <200> Business volume: Float Client since: Date Booking Registered: Date Confirmation: Date Bill: Date Checked out: Date Notification: Date Register() Check out() Produce notification() Prove payment() Person Number: Serial Name: NameT Contact: ContactT Birthday: Date First registered: Date Short information: String <200> Notices: String <200> Produce address lable() Lecturer Biography: String<400> Daily honorar: Float Employer Associate Client 0.. Function: String <50> Business volume: Currency Contractor Participant Substitute participant Produce Notification() Client booking Customer Public presentation Cooperation partner: String<00> Cancel fee: Float Participant min: Short Participant actual: Short Produce participant list() Produce participant certificate() Company booking Company internal presentation All-inclusive price: Float Participants max: Short Associate Entitlement: RoleET Password: String <6> Occupation: String <30> Presentation Number: Short Duration: Short From: Date To: Date Daily schedular start: Time Daily schedular stop: Time Start first day: Time End last day: Time Place: String <50> Participant max: Short Canceled: YesNoET Cancel() Produce honorar information() Register() Check out() Is free() Alternative seminars() Seminar supervisor Referent Is able to conduct Seminar type Short titel: String<0> Titel: String <50> Purpose: String<400> Method: String<400> Overview: String<400> Daily procedure: String<20> Durance: Short Documents: String<200> Target group: String<200> Preconditions: String<200> Charge without tax: Float Participant number max: Short Participant number min: short 3 3

32 Static OOA model: notions Company Shortname: String <0> Name: NameT Contact: ContactT Contact person: NamtT Sector: String <30> Contact person birthday: Date Function: String <30> Short information: String <200> Notices: String <200> Business volume: Float Client since: Date Association Booking Registered: Date Confirmation: Date Bill: Date Checked out: Date Notification: Date Register() Check out() Produce notification() Prove payment() Classes: - name - attribute - operations Employer Associate Client 0.. Function: String <50> Business volume: Currency Produce Notification() 0.. Customer Contractor Cardinality 0.. Participant Substitute paricipant 0.. Role Client booking Generalization / Inheritance Company booking 32 32

33 Static OOA model: problems () Company Shortname: String <0> Name: NameT Contact: ContactT Contact person: NamtT Sector: String <30> Contact person birthday: Date Function: String <30> Short information: String <200> Notices: String <200> Business volume: Float Client since: Date To be able to read a final model Employer Associate Client 0.. Function: String <50> Business volume: Currency Contractor Participant Substitute paricipant Produce Notification() Client booking Most Customer challenging problem: How Public to presentation develop Cooperation just partner: this String<00> model? Cancel fee: Float Participant min: Short Participant actual: Short Produce participant list() Produce participant certificate() Booking Registered: Date Confirmation: Date Bill: Date Checked out: Date Notification: Date Register() Check out() Produce notification() Prove payment() Company booking Company internal presentation All-inclusive price: Float Participants max: Short But: is the model also reasonable? To be able to assess a final model Person Number: Serial Name: NameT Contact: ContactT Birthday: Date First registered: Date Short information: String <200> Notices: String <200> Produce address lable() Associate Entitlement: RoleET Password: String <6> Occupation: String <30> Presentation Number: Short Duration: Short From: Date To: Date Daily schedular start: Time Daily schedular stop: Time Start first day: Time End last day: Time Place: String <50> Participant max: Short Canceled: YesNoET Cancel() Produce honorar information() Register() Check out() Is free() Alternative seminars() Seminar supervisor Referent To be able to produce a model Lecturer Biography: String<400> Daily honorar: Float Are there missing: classes attributes operations? Do we have the choice Is able to conduct Seminar type Short titel: String<0> Titel: of String other <50> Purpose: String<400> Method: classes? String<400> Overview: String<400> Daily procedure: String<20> Durance: Short Documents: String<200> Target group: String<200> Preconditions: String<200> Charge without tax: Float Participant number max: Short Participant number min: short 33 33

34 Static OOA model: problems (2) Company Shortname: String <0> Name: NameT 2 classes: Contact: ContactT Contact person: NamtT Sector: String <30> ones Contact person birthday: ones? Date Function: String <30> Short information: String <200> Notices: String <200> Business volume: Float Client since: Date Employer Associate 2 classes: Why Why just just these these Client 0.. Function: String <50> Business volume: Currency Contractor Participant Substitute paricipant Produce Notification() Client booking Customer Public presentation Cooperation partner: String<00> Cancel fee: Float Participant min: Short Participant actual: Short Produce participant list() Produce participant certificate() Why not? Booking Registered: Date Confirmation: Date Bill: Date Checked out: Date Notification: Date Register() Check out() Produce notification() Prove payment() delay of payment customer bill date amount printdop() Company booking Company internal presentation All-inclusive price: Float Participants max: Short Person Number: Serial Name: NameT Contact: ContactT Birthday: Date First registered: Date Short information: String <200> Notices: String <200> Produce address lable() Associate Entitlement: RoleET Password: String <6> Occupation: String <30> address name street number country ZIP city phone Presentation Number: Short Duration: Short From: Date To: Date Daily schedular start: Time Daily schedular stop: Time Start first day: Time End last day: Time Place: String <50> Participant max: Short Canceled: YesNoET Cancel() Produce honorar information() Register() Check out() Is free() Alternative seminars() Seminar supervisor Referent Lecturer Biography: String<400> Daily honorar: Float Is able to conduct Seminar type Short titel: String<0> Titel: String <50> Purpose: String<400> Method: String<400> Overview: String<400> Daily procedure: String<20> Durance: Short Documents: String<200> Target group: String<200> Preconditions: String<200> Charge without tax: Float Participant number max: Short Participant number min: short 34 34

35 Company Shortname: String <0> Name: NameT Contact: ContactT Contact person: NamtT Sector: String <30> Contact person birthday: Date Function: String <30> Short information: String <200> Notices: String <200> Business volume: Float Client since: Date Employer 0.. additional Associate Client additional attributes attributes and and operations operations Function: String <50> Business volume: Currency Contractor net price: Short Participant Substitute paricipant Produce Notification() Client booking Customer... Public presentation Cooperation partner: String<00> Cancel fee: Float Participant min: Short Participant actual: Short Produce participant list() Produce participant certificate() Static OOA model: problems (3) attributes attributes and and operations: operations: Why Why just just these these ones? ones? Booking Registered: Date Confirmation: Date Bill: Date Checked out: Date Notification: Date Register() Check out() Produce notification() Prove payment() Presentation carried out: Boolean acquire() change() delete() printinfo() Company booking Company internal presentation All-inclusive price: Float Participants max: Short Person 5.2 Seminar data Number: Serial Name: NameT Contact: ContactT Birthday: Date First registered: Date Short information: String <200> Notices: String <200> Associate Entitlement: RoleET Password: String <6> Occupation: String <30> Presentation Number: Short Duration: Short From: Date To: Date Daily schedular start: Time Daily schedular stop: Time Start first day: Time End last day: Time Place: String <50> Participant max: Short Canceled: YesNoET Cancel() Produce honorar information() Register() Check out() Is free() Alternative seminars() Seminar supervisor Referent Lecturer D30 (PD30) Presentation data (max ): Presentation number, duration (in days), from, to, daily period split-beginning, daily period splitend, beginning of the first day, end of the last day, presentation place (hotel/company, address, room), cooperation partner, public Produce address lable() (yes/no), net price, cancel fee, min. participant rate, max. participant rate, actual participant, carried out (yes/no) Biography: String<400> Daily honorar: Float Is able to conduct Seminar type Short titel: String<0> Titel: String <50> Purpose: String<400> Method: String<400> Overview: String<400> Daily procedure: String<20> Durance: Short Documents: String<200> Target group: String<200> Preconditions: String<200> Charge without tax: Float Participant number max: Short Participant number min: short 35 35

36 Static OOA model: inheritance Company Shortname: String <0> Name: 3 NameT Address: generalisation ContactT generalisation AddressT Contact: Contact person: NamtT Sector: classes classes String <30> Contact person birthday: Date Function: String <30> Short information: String <200> Notices: String <200> Business volume: Float Client since: Date Employer Associate Client 0.. Function: String <50> Business volume: Currency Contractor Participant Substitute paricipant Produce Notification() Client booking Customer Public presentation Cooperation partner: String<00> Cancel fee: Float Participant min: Short Participant actual: Short Produce participant list() Produce participant certificate() Booking Registered: Date Confirmation: Date Bill: Date Checked out: Date Notification: Date Register() Check out() Produce notification() Prove payment() Company booking Company internal presentation All-inclusive price: Float Participants max: Short Person Number: Serial Name: NameT Contact: ContactT Birthday: Date First registered: Date Short information: String <200> Notices: String <200> Produce address lable() Associate Entitlement: RoleET Password: String <6> Occupation: String <30> Presentation Number: Short Duration: Short From: Date To: Date Daily schedular start: Time Daily schedular stop: Time Start first day: Time End last day: Time Place: String <50> Participant max: Short Canceled: YesNoET Cancel() Produce honorar information() Register() Check out() Is free() Alternative seminars() Seminar supervisor Referent Lecturer Biography: String<400> Daily honorar: Float has has 3 derived derived classes classes Is able to conduct Problem: Seminar type comprehensible arrangement of classes (automatization is subject of research) Short titel: String<0> Titel: String <50> Purpose: String<400> Method: String<400> Overview: String<400> Daily procedure: String<20> Durance: Short Documents: String<200> Target group: String<200> Preconditions: String<200> Charge without tax: Float Participant number max: Short Participant number min: short 36 36

37 Static OOA model : associations, roles Company Shortname: String <0> Name: NameT Contact: ContactT Contact person: NamtT Sector: String <30> Contact person birthday: Date Function: String <30> Short information: String <200> Notices: String <200> Business volume: Float Client since: Date Booking Registered: Date Confirmation: Date Bill: Date Checked out: Date Notification: Date Register() Check out() Produce notification() Prove payment() Person Number: Serial Name: NameT Contact: ContactT Birthday: Date First registered: Date Short information: String <200> Notices: String <200> Produce address lable() name name of of the the association association Lecturer Biography: String<400> Daily honorar: Float Employer Associate Client 0.. Function: String <50> Business volume: Currency Contractor Participant Substitute paricipant Produce Notification() Client booking Customer Public presentation Cooperation partner: String<00> Cancel fee: Float Participant min: Short Participant actual: Short Produce participant list() Produce participant certificate() several several roles roles in in associations associations between between the the same same classes classes Company booking Company internal presentation All-inclusive price: Float Participants max: Short Associate Entitlement: RoleET Password: String <6> Occupation: String <30> Presentation Number: Short Duration: Short From: Date To: Date Daily schedular start: Time Daily schedular stop: Time Start first day: Time End last day: Time Place: String <50> Participant max: Short Canceled: YesNoET Cancel() Produce honorar information() Register() Check out() Is free() Alternative seminars() Presentation custodian Referent Is able to conduct Seminar type Short titel: String<0> Titel: String <50> Purpose: String<400> Method: String<400> Overview: String<400> Daily procedure: String<20> Durance: Short Documents: String<200> Target group: String<200> Preconditions: String<200> Charge without tax: Float Participant number max: Short Participant number min: short 37 37

38 Static OOA model : cardinalities Company Shortname: String <0> Name: NameT Contact: ContactT some some Contact person: NamtT cardinalities Sector: String cardinalities <30> Contact person birthday: Date Function: String <30> Short information: String <200> Notices: String <200> Business volume: Float Client since: Date Booking Registered: Date Confirmation: Date Bill: Date Checked out: Date Notification: Date Register() Check out() Produce notification() Prove payment() Person Number: Serial Name: NameT Contact: ContactT Birthday: Date First registered: Date Short information: String <200> Notices: String <200> Produce address lable() Lecturer Biography: String<400> Daily honorar: Float? Employer Associate Client 0.. Function: String <50> Business volume: Currency Contractor Participant Substitute paricipant Produce Notification() Client booking Customer Public presentation Cooperation partner: String<00> Cancel fee: Float Participant min: Short Participant actual: Short Produce participant list() Produce participant certificate() Company booking Is Is a : : relation relation between client and public public presentation presentation between client and Company internal presentation All-inclusive price: Float Participants max: Short Associate Entitlement: RoleET Password: String <6> Occupation: String <30> Presentation Number: Short Duration: Short From: Date To: Date Daily schedular start: Time Daily schedular stop: Time Start first day: Time End last day: Time Place: String <50> Participant max: Short Canceled: YesNoET Cancel() Produce honorar information() Register() Check out() Is free() Alternative seminars() Seminar supervisor Referent Is able to conduct Seminar type Short titel: String<0> Titel: String <50> Purpose: String<400> Method: String<400> Overview: String<400> Daily procedure: String<20> Durance: Short Documents: String<200> Target group: String<200> Preconditions: String<200> Charge without tax: Float Participant number max: Short Participant number min: short 38 38

39 3. Object-oriented Analysis a) Overview: approaches, history, literature b) Object-oriented paradigm: basic notions c) Submodels in UML d) How to read a given static OOA model? (Class diagram: example seminar organization ) e) Detailed specification: DD, pseudocode f) Packages 39 39

40 Combination of basic concepts in object-oriented analysis Data Dictionary (Balzert: attribute structure) Data flow diagram (Rumbaugh: functional model, 99) OOA 990 sequence diagram ER (Entity Relationship) class diagram pseudo code state automaton collaboration diagram use case diagram entities & relations class structures control structures finite automaton interaction structures work flow 40 40

41 What is to be specified in more detail for classes? classes general task of a class attributes meaning (Which information is represented?) structure, type: DD operations Customer name: NameT address: AddressT function: String business volume: Currency produce notification() effect, transformational behaviour parameter, types of parameter (signature of operation) 4 4

42 Example: specification of attributes () Class Customer Attribute Name Description: the name of the customer Type: NameT Attribute Address? DD user interface Ergonomic Name: private address Description: the private address of the customer Type: AddressT Optional attribute: yes 42 42

43 Example: specification of attributes (2) Specification of the user defined Type NameT NameT = Salutation + (Title) + First name + Name Attribute Salutation Type: enum Range: Mr., Mrs., Miss Default value: Mr. DD - notation Attribute Title Description: academic degree Type: enum Range: Dr., Prof., Prof. Dr., empty Extendable: yes %new Titles possible Default value: empty Optional Attribute: yes Attribute First name... Attribute Name

44 3. Object-oriented Analysis a) Overview: approaches, history, literature b) Object-oriented paradigm: basic notions c) Submodels in UML d) How to read a given static OOA model? (Class diagram: example seminar organization ) e) Detailed specification: DD, pseudocode f) Packages 44 44

45 Packages Goal: Collect components to a larger unit. Analog notion: Subsystem UML A package collects model elements (e.g. classes) and diagrams A package may contain packages

46 Packages in UML notation Package name Trading system Purchase Sale Stock Dependence 46 46

47 Company Shortname: String <0> Name: NameT Contact: ContactT Contact person: NamtT Sector: String <30> Contact person birthday: Date Function: String <30> Short information: String <200> Notices: String <200> Business volume: Float Client since: Date Package Seminar management : Offers of the company Booking Registered: Date Confirmation: Date Bill: Date Checked out: Date Notification: Date Register() Check out() Produce notification() Prove payment() Person Number: Serial Name: NameT Contact: ContactT Birthday: Date First registered: Date Short information: String <200> Notices: String <200> Produce address lable() Lecturer Biography: String<400> Daily honorar: Float Employer Associate Client 0.. Function: String <50> Business volume: Currency Contractor Participant Substitute paricipant Produce Notification() Client booking Customer Public presentation Cooperation partner: String<00> Cancel fee: Float Participant min: Short Participant actual: Short Produce participant list() Produce participant certificate() Company booking Company internal presentation All-inclusive price: Float Participants max: Short Associate Entitlement: RoleET Password: String <6> Occupation: String <30> Presentation Number: Short Duration: Short From: Date To: Date Daily schedular start: Time Daily schedular stop: Time Start first day: Time End last day: Time Place: String <50> Participant max: Short Canceled: YesNoET Cancel() Produce honorar information() Register() Check out() Is free() Alternative seminars() Seminar supervisor Referent Is able to conduct Seminar type Short titel: String<0> Titel: String <50> Purpose: String<400> Method: String<400> Overview: String<400> Daily procedure: String<20> Durance: Short Documents: String<200> Target group: String<200> Preconditions: String<200> Charge without tax: Float Participant number max: Short Participant number min: short 47 47

48 Package diagram Seminar management Seminar management Person Lecturer Associate Public presentation Presentation Seminar type Company internal presentation 48 48