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

COST G9 - Work group 2COST G9 - Work group 2Cadastral science meetingCadastral science meeting

Aalborg, DkAalborg, Dk25. 08. - 26. 08. 200525. 08. - 26. 08. 2005

Modeling methodology for Modeling methodology for real estate transactionreal estate transactionss

Radoš ŠumradaRadoš Šumrada

Faculty of Civil and Geodetic EngineeringFaculty of Civil and Geodetic EngineeringJamova 2, SJamova 2, Sii 1000 Ljubljana, Slovenia 1000 Ljubljana, Slovenia

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

Modeling methodology for real estate transactionsModeling methodology for real estate transactions

ContConteentsnts

IntroductionIntroduction

MMeethodology development (thodology development (main phases and stepsmain phases and steps))

Proficiency acquisition (Proficiency acquisition (expertise and existing modelsexpertise and existing models))

Problem domain analysis (Problem domain analysis (classes and relationsclasses and relations))

Use caseUse case analysis analysis ( (actors and use casesactors and use cases))

AAnalysisnalysis of work flows ( of work flows (activities and rolesactivities and roles))

AAnalysisnalysis of interactions ( of interactions (data flows and time spandata flows and time span))

Diagrams (Diagrams (UMLUML) of a sample real estate transaction case) of a sample real estate transaction case((sale of a whole parcel - Si settingsale of a whole parcel - Si setting))

ConcConcllususiionsons


IntroductionIntroduction

The development of a suitableThe development of a suitable methodologymethodology for conceptual for conceptual modeling in modeling in the real estatesthe real estates domain domain is a demanding process is a demanding process..

TThe he adoptadopted methodology starts ed methodology starts with the with the classificationclassification of objects of objects..

The provenance areThe provenance are detailed detailed use caseuse case descriptions descriptions ((expertnessexpertness) ) for for the sample real estate the sample real estate transactionstransactions..

The proposed The proposed modeling modeling approachapproach uses uses UML UML formalism formalism ((Unified Unified Modeling LanguageModeling Language).).

The outcomes are presented on The outcomes are presented on UML UML packagepackage, , collaborationcollaboration, , classclass, , use caseuse case, , activityactivity and and interactioninteraction diagramsdiagrams..


Main steps of Main steps of problem domain analysisproblem domain analysis (1) (1)

Domain analysisDomain analysis classifiesclassifies objects, defines their properties and relationsobjects, defines their properties and relations and concludes as a formal application schemaand concludes as a formal application schema..

The The static structurestatic structure defines important classes, their defines important classes, theirproperties and relationships between classes.properties and relationships between classes.

The The dynamic behaviordynamic behavior specifies the stable states of specifies the stable states ofclasses, their functionality and the interactions amongclasses, their functionality and the interactions amongthem (them (collaborationscollaborations) in order to accomplish services.) in order to accomplish services.

The applied modeling process should be carried outThe applied modeling process should be carried outincrementallyincrementally and and iterativelyiteratively..

The first phase should be the The first phase should be the proficiency acquisitionproficiency acquisition;;

GatherGather data and expertisedata and expertise on real estate transaction modeling, existingon real estate transaction modeling, existing transaction processing transaction processing systems and detailed users’ requirements.systems and detailed users’ requirements.

:Seller

Sale of awhole parcel

:Buyer

Sale of a whole parcel as a collaboration diagram - Si setting

:Third party


Main steps of Main steps of problem domain analysisproblem domain analysis (2) (2)

The The problem domain analysisproblem domain analysis phase has many steps:

IdentifyIdentify problem domainproblem domain objects objects and and ddrawraw high-levelhigh-level class diagramclass diagramss that introduce that introduce primary primary datadata structure.structure.

Perform Perform classificationclassification ( (classesclasses), generalization and aggregation), generalization and aggregation in order to derive the first cut structure of domain classes. in order to derive the first cut structure of domain classes.

Specify their main Specify their main propertiesproperties ( (attributesattributes) and ) and relationshipsrelationships ( (associations and other dependenciesassociations and other dependencies) among classes.) among classes.

Describe their basic Describe their basic functionalityfunctionality ( (activitiesactivities) and) and important important messagesmessages ( (communicationcommunication) among classes.) among classes.

Identify packages (Identify packages (subsystemssubsystems) and the general) and the general structure of the system as a whole. structure of the system as a whole.

Problem domain analysisProblem domain analysisUse caseUse case analysis analysis

AAnalysisnalysis of work flows of work flows

AAnalysisnalysis of interactions of interactions


Cadastralauthority

Tax authority

Land registry

Salecontract «subsystem»

Land register(DBMS)

Expert Third Party

Pre-emption holder

UML package diagram for sale of a whole parcel - Si setting

Seller

Buyer

Motgagee

Parcel

Owner

PartOfParcel

1 1..*

Ownership

CadastralMunicipality

Mortgagee

+form : kind

MortgageDeed +form : kind

+type : right+side : list

Easement

<<RRR>>Encumbrance

1 1..*

ThirdParty

*

*

TenantOrUser

LandChargeDeed1

1..*

1 1..*

1..*1

*

*

1

0..*

AdministrativeUnit

1

1..*

*

* *

*

1

+form : kind

ObligationContract

1..*

1

LegalFact

1

1..*

+appurtenant+personnal+commercial

«enumeration»right

+contract+by law

«enumeration»kind

+dominant+servient

«enumeration»list

Partial class diagram for ownership of a whole parcel - Si setting

UML package and general class UML package and general class diagrams outline the sale of a whole diagrams outline the sale of a whole

parcel exampleparcel example (Si setting) (Si setting)..

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

UUse case analysisse case analysis (1)(1) - Actors and use cases- Actors and use cases

A A use caseuse case is a sequence of actions that an actor is a sequence of actions that an actorperforms in order to achieve a particular service.performs in order to achieve a particular service.

ActorsActors are users or other systems that interact with the modeled system. are users or other systems that interact with the modeled system.

Use case analysisUse case analysis defines one or more paths through the activities defines one or more paths through the activitiesthat accomplish an use case and as well all the possible scenarios.that accomplish an use case and as well all the possible scenarios.

The main steps in The main steps in use caseuse case analysis analysis phase are the following: phase are the following:

Identify and describe Identify and describe use casesuse cases, , actorsactors and the and the importantimportant interactionsinteractions among among the actors and use cases. the actors and use cases.

Develop use cases from the general to the Develop use cases from the general to the detailed detailed descriptionsdescriptions..

Problem domain analysisProblem domain analysis

Use caseUse case analysis analysisAAnalysisnalysis of work flows of work flows



UUse case analysisse case analysis (2)(2)

Define priorities ofDefine priorities of use case use casess..

Elaborate each use case in all the required detailElaborate each use case in all the required detail ( (main course and all the alternative scenariosmain course and all the alternative scenarios).).

Present use cases on a set of Present use cases on a set of use case diagramsuse case diagrams..

Organize use cases into the suitable groups.Organize use cases into the suitable groups.

Present the organization of use cases and theirPresent the organization of use cases and their hierarchy on package diagramhierarchy on package diagramss..


Cadastralauthority

Tax authority

Land registry

«subsystem»Land register

(DBMS)

Expert

UML use case diagram for sale of a whole parcel - Si setting

pay real estatetransfer tax

Mortgagee

«subsystem»Cadastraldatabase

registerpurchase

«subsystem»Real estate

value register

updatedatabase

updatedatabase

send dataand decree

Notary

examine parceland check data

contractmortgage

signpre-contract

prepare salecontract

Administrativeauthority

request salepermission

issue salepermission

deny salepermission

checkpre-emptions

submit ownershipregistration

changeownership

sign salecontract

verify salecontract

perform saletransaction

informclaimants

switch ofbuyers

Buyer

Seller

Pre-emption holder

check publicregulations


Analysis of work flows - Activities and rolesAnalysis of work flows - Activities and roles

Objects workObjects work togethertogether ( (collaborate and interactcollaborate and interact) in order) in ordertoto produce the functionality that actors require as system services. produce the functionality that actors require as system services. Each object normally provides only a portion ofEach object normally provides only a portion of functionality needed to functionality needed to accomplish certain service.accomplish certain service. CollaborationCollaboration is a set of objects, actors or participants that work together to is a set of objects, actors or participants that work together to achieve some services with meaningful outcome in the context of the system.achieve some services with meaningful outcome in the context of the system.

A A rolerole is the named functionality that a class provides in a collaboration. is the named functionality that a class provides in a collaboration.

ActivityActivity diagrams are used to describe diagrams are used to describe work flowswork flows such as collaborations in such as collaborations in use cases or business flows.use cases or business flows.


Use caseUse case analysis analysis

AAnalysisnalysis of work flows of work flowsAAnalysisnalysis of interactions of interactions


Buyer ought to be informed.

financial transaction (with notary assistance)

Notary examines the sale contract and all parties sign it.

Notary checkes and verifies the sale contract.

Buyer pays real estate transfer tax (2 %) to the tax authority.

Real estate anddata examination

Preparing and signingthe sale contract

Covering the stamp duty

Contract verification

Land cadastre and (new) owner

Purchase sum transfer

Application forownership registration

Registration of ownershipNotification of

changed ownership

Owner decides to sell a parcel

pre-contracting

contracting

registration

General UML activity diagram for a sale of whole parce - Si setting

Buyer must register ownership.


Analysis of interactionsAnalysis of interactions - Data flows and time span- Data flows and time span

InteractionInteraction is a sequence of messages sent between objects in the context of is a sequence of messages sent between objects in the context of a collaboration in order to accomplish the required functionality or service.a collaboration in order to accomplish the required functionality or service.

Processing steps for the realization of each use case should describe the Processing steps for the realization of each use case should describe the required collaboration among the participating classes.required collaboration among the participating classes.

Messages (Messages (and dataand data) that need to pass between objects must be defined.) that need to pass between objects must be defined.

UML sequence diagrams show messages and data exchange among objects.UML sequence diagrams show messages and data exchange among objects.

If needed, UML state diagrams can depict dynamics of (If needed, UML state diagrams can depict dynamics of (importantimportant) objects.) objects.


Use caseUse case analysis analysis

AAnalysisnalysis of work flows of work flows



:Seller :Buyer :SaleContract :Notary :Tax authority

The seller and the buyer receive copies of the signed and verified sale contracts.

prepare sale contract


receive copy ofverified sale contract

examine salecontract

registration

UML sequence diagram for sale of a whole parcel - Si setting


submit real estatesales tax application

sign sale contract

sign sale contract

determinesale taxissue real estate

sales tax bill

pay real estate sales tax bill

contracting

verity sale contract

receive copy of verified sale contract

transfer purchase amount

assist bothparties

transfer purchase sum

check salecontract

start contract verification

:Land registry

submit for ownership registration

send data and title decree


ConclusionsConclusions

At the end we should stress again that fAt the end we should stress again that for modeling or modeling real estatereal estate transactions transactions it it is is crucialcrucial to follow the chosen to follow the chosen methodologymethodology as the guiding process. as the guiding process.

Only the main modeling phases and developing steps have been presented. Only the main modeling phases and developing steps have been presented.

The benefits of the standardized modeling language (The benefits of the standardized modeling language (UMLUML) and its graphical ) and its graphical notation are obvious, although the elaboration of detailed UML diagrams can notation are obvious, although the elaboration of detailed UML diagrams can be a challengingbe a challenging task.task.

The availability of powerful modeling tool (The availability of powerful modeling tool (OOAD OOAD softwaresoftware) is also important.) is also important.

Tuesday, April 18, 2023 - 21:16:26

Questions and opinions? Questions and opinions?

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

Documents

Transcript of COST G9 - Work group 2 Cadastral science meeting Aalborg, Dk 25. 08. - 26. 08. 2005 Modeling...