Modeling methodology for real estate transactions

1
Modeling methodology for real estate transactions

• Radoš Šumrada
• Faculty of Civil and Geodetic Engineering
• Jamova 2, Si 1000 Ljubljana, Slovenia

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

• Modeling methodology for real estate transactions
• Contents
• Introduction
• Methodology development (main phases and steps)
• Proficiency acquisition (expertise and existing
  models)
• Problem domain analysis (classes and relations)
• Use case analysis (actors and use cases)
• Analysis of work flows (activities and roles)
• Analysis of interactions (data flows and time
  span)
• Diagrams (UML) of a sample real estate
  transaction case(sale of a whole parcel - Si
  setting)
• Conclusions

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.
4

• Main steps of problem domain analysis (1)
• Domain analysis classifies objects, defines their
  properties and relations and concludes as a
  formal application schema.
• The static structure defines important classes,
  theirproperties and relationships between
  classes.
• The dynamic behavior specifies the stable states
  ofclasses, their functionality and the
  interactions amongthem (collaborations) in order
  to accomplish services.
• The applied modeling process should be carried
  outincrementally and iteratively.
• The first phase should be the proficiency
  acquisition
• Gather data and expertise on real estate
  transaction modeling, existing transaction
  processing systems and detailed users
  requirements.

5

• Problem domain analysis
• Use case analysis
• Analysis of work flows
• Analysis of interactions

• Main steps of problem domain analysis (2)
• The problem domain analysis phase has many steps
• 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.
• Specify their main properties (attributes) and
  relationships (associations and other
  dependencies) 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.

6
UML package and general class diagrams outline
the sale of a whole parcel example (Si setting).
7

• Problem domain analysis
• Use case analysis
• Analysis of work flows
• Analysis of interactions

• Use case analysis (1) - Actors and use cases
• A use case is a sequence of actions that an
  actorperforms 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 activitiesthat 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.
• Develop use cases from the general to the
  detailed descriptions.

8
(No Transcript)
9

• Use case analysis (2)
• Define priorities of use cases.
• 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.
• Organize use cases into the suitable groups.
• Present the organization of use cases and their
  hierarchy on package diagrams.

10
(No Transcript)
11

• Problem domain analysis
• Use case analysis
• Analysis of work flows
• Analysis of interactions

Analysis of work flows - Activities and
roles Objects work together (collaborate and
interact) in orderto 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.
12
(No Transcript)
13

• Problem domain analysis
• Use case analysis
• Analysis of work flows
• Analysis of interactions

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.
14
(No Transcript)
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.

16
Questions and opinions?

• Tuesday, June 09, 2015 - 001133