2. COST G9 - Work group 2 Cadastral science meeting Aalborg, Dk 25. 08. - 26. 08. 2005 Modeling methodology for real estate transactions Radoš Šumrada Faculty of Civil and Geodetic Engineering Jamova 2, Si 1000 Ljubljana, Slovenia

3. COST G9 - Work group 2, Cadastral science meeting, Aalborg, Dk, 25. 08. - 26. 08. 2005 2 Modeling methodology for real estate transactions Modeling methodology for real estate transactions Contents Contents Introduction Methodology development (main phases and steps) Methodology development (main phases and steps) Proficiency acquisition (expertise and existing models) Proficiency acquisition (expertise and existing models) Problem domain analysis (classes and relations) Problem domain analysis (classes and relations) Use case analysis (actors and use cases) Use case analysis (actors and use cases) Analysis of work flows (activities and roles) Analysis of work flows (activities and roles) Analysis of interactions (data flows and time span) Analysis of interactions (data flows and time span) Diagrams (UML) of a sample real estate transaction case (sale of a whole parcel - Si setting) Diagrams (UML) of a sample real estate transaction case (sale of a whole parcel - Si setting) Conclusions Conclusions

4. COST G9 - Work group 2, Cadastral science meeting, Aalborg, Dk, 25. 08. - 26. 08. 2005 3 Introduction The development of a suitable methodology for conceptual modeling in the real estates domain is a demanding process. The adopted methodology starts with the classification of objects. The provenance are detailed use case descriptions (expertness) for the sample real estate transactions. The proposed modeling approach uses UML formalism (Unified Modeling Language). The outcomes are presented on UML package, collaboration, class, use case, activity and interaction diagrams.

5. COST G9 - Work group 2, Cadastral science meeting, Aalborg, Dk, 25. 08. - 26. 08. 2005 4 Main steps of problem domain analysis (1) Domain analysis classifiesobjects, defines their properties and relations and concludes as a formal application schema. Domain analysis classifies objects, defines their properties and relations and concludes as a formal application schema. The static structure defines important classes, their properties and relationships between classes. The dynamic behavior specifies the stable states of classes, their functionality and the interactions among them (collaborations) in order to accomplish services. The applied modeling process should be carried out incrementally and iteratively. The first phase should be the proficiency acquisition; Gather data and expertise on real estate transaction modeling, existing transaction processingsystems and detailed users’ requirements. Gather data and expertise on real estate transaction modeling, existing transaction processing systems and detailed users’ requirements.

6. COST G9 - Work group 2, Cadastral science meeting, Aalborg, Dk, 25. 08. - 26. 08. 2005 5 Main steps of problem domain analysis (2) The problem domain analysis The problem domain analysis phase has many steps: Identify problem domain objects and draw high-level class diagrams that introduce primary data structure. Identify problem domain objects and draw high-level class diagrams that introduce primary data structure. Perform classification (classes), generalization and aggregation in order to derive the first cut structure of domain classes. Perform classification (classes), generalization and aggregation in order to derive the first cut structure of domain classes. Specify their main properties (attributes) and relationships (associations and other dependencies) among classes. Specify their main properties (attributes) and relationships (associations and other dependencies) among classes. Describe their basic functionality (activities) and important messages (communication) among classes. Describe their basic functionality (activities) and important messages (communication) among classes. Identify packages (subsystems) and the general structure of the system as a whole. Identify packages (subsystems) and the general structure of the system as a whole. Problem domain analysis Problem domain analysis Use case analysis Use case analysis Analysis of work flows Analysis of work flows Analysis of interactions Analysis of interactions

7. COST G9 - Work group 2, Cadastral science meeting, Aalborg, Dk, 25. 08. - 26. 08. 2005 6 UML package and general class diagrams outline the sale of a whole parcel example (Si setting). UML package and general class diagrams outline the sale of a whole parcel example (Si setting).

8. COST G9 - Work group 2, Cadastral science meeting, Aalborg, Dk, 25. 08. - 26. 08. 2005 7 Use case analysis (1) - Actors and use cases A use case is a sequence of actions that an actor performs in order to achieve a particular service. Actors are users or other systems that interact with the modeled system. Use case analysis defines one or more paths through the activities that accomplish an use case and as well all the possible scenarios. The main steps in use case analysis phase are the following: Identify and describe use cases, actors and the important interactions among the actors and use cases. Identify and describe use cases, actors and the important interactions among the actors and use cases. Develop use cases from the general to the detailed descriptions. Develop use cases from the general to the detailed descriptions. Problem domain analysis Problem domain analysis Use case analysis Use case analysis Analysis of work flows Analysis of work flows Analysis of interactions Analysis of interactions

9. COST G9 - Work group 2, Cadastral science meeting, Aalborg, Dk, 25. 08. - 26. 08. 2005 8

10. 9 Use case analysis (2) Define priorities of use cases. Define priorities of use cases. Elaborate each use case in all the required detail (main course and all the alternative scenarios). Elaborate each use case in all the required detail (main course and all the alternative scenarios). Present use cases on a set of use case diagrams. Present use cases on a set of use case diagrams. Organize use cases into the suitable groups. Organize use cases into the suitable groups. Present the organization of use cases and their hierarchy on package diagrams. Present the organization of use cases and their hierarchy on package diagrams.

11. COST G9 - Work group 2, Cadastral science meeting, Aalborg, Dk, 25. 08. - 26. 08. 2005 10

12. COST G9 - Work group 2, Cadastral science meeting, Aalborg, Dk, 25. 08. - 26. 08. 2005 11 Analysis of work flows - Activities and roles Objects work together (collaborate and interact) in order to produce the functionality that actors require as system services. Each object normally provides only a portion of functionality needed to accomplish certain service. Collaboration is a set of objects, actors or participants that work together to achieve some services with meaningful outcome in the context of the system. A role is the named functionality that a class provides in a collaboration. Activity diagrams are used to describe work flows such as collaborations in use cases or business flows. Problem domain analysis Problem domain analysis Use case analysis Use case analysis Analysis of work flows Analysis of work flows Analysis of interactions Analysis of interactions

13. COST G9 - Work group 2, Cadastral science meeting, Aalborg, Dk, 25. 08. - 26. 08. 2005 12

14. COST G9 - Work group 2, Cadastral science meeting, Aalborg, Dk, 25. 08. - 26. 08. 2005 13 Analysis of interactions - Data flows and time span Interaction is a sequence of messages sent between objects in the context of a collaboration in order to accomplish the required functionality or service. Processing steps for the realization of each use case should describe the required collaboration among the participating classes. Messages (and data) that need to pass between objects must be defined. UML sequence diagrams show messages and data exchange among objects. If needed, UML state diagrams can depict dynamics of (important) objects. Problem domain analysis Problem domain analysis Use case analysis Use case analysis Analysis of work flows Analysis of work flows Analysis of interactions Analysis of interactions

15. COST G9 - Work group 2, Cadastral science meeting, Aalborg, Dk, 25. 08. - 26. 08. 2005 14

16. COST G9 - Work group 2, Cadastral science meeting, Aalborg, Dk, 25. 08. - 26. 08. 2005 15 Conclusions At the end we should stress again that for modeling real estate transactions it is crucial to follow the chosen methodology as the guiding process. Only the main modeling phases and developing steps have been presented. The benefits of the standardized modeling language (UML) and its graphical notation are obvious, although the elaboration of detailed UML diagrams can be a challenging task. The availability of powerful modeling tool (OOAD software) is also important.

17. Friday, June 19, 2015 - 13:19:35 Questions and opinions?