2.3 Development Approach
A great deal of effort in the early part of the project was to
understand the Romania land registry law (Romanian Law
7/1996) so that the appropriate processes could be implemented
within the land/cadastre registry system. It was critical that this
foundational understanding be absorbed by the team so as to
implement not only a functioning system, but one that would
also stand up to legal scrutiny. This legal understanding was
significant in our design and development, as it impacted each
of the following:
1. The purpose and objective of the system
2. The Institutional framework in which the system will
be implemented
3. The processes specific to the Romanian system
4. The workflow and re-engineering of the processes
unique to Romania
5. The report generation and ad-hoc requirements
6. The necessary network scheme required to completely
integrate the various components of the system
2.4 Life Cycle Development
For the development of the project Stewart/Landata used a life-
cycle based methodology to develop this comprehensive
solution. A key component for our team’s success was the
significant involvement of the owners and users of the
cadastre/land registry system. It will be through this successful
participation of the Cadastre and Land Book teams that we will
be able to provide a comprehensive land registry system.
direction of the flows for each of the processes. It should be
noted that the user interaction is a bi-directional flow.
2.5 Quality Control Overview
During the development and implementation of the application,
a robust quality control program has been instituted from
project kick-off to project sign-off. Program libraries,
databases, and a repository are being employed for the efficient
and successful development of the application. Various
versions of the software and other documentation are kept in the
Program Library to assure complete control during the
application development, installation, testing, and maintenance
period.
2.6 Testing
Our approach to testing has been to complete normal software
walk-throughs followed by integration testing of the all of the
modules of software. As the Stewart/Landata team conducted
the integration testing, informal evaluation testing by the end
users of the applications were also being completed, so as to
insure that our functional tests would proceed smoothly. The
functional testing was completed using pre-approved test cases.
These test cases were developed in concert between the client
and the Stewart/Landata team. Upon completion of the
functional testing, acceptance testing begins at the first two pilot
sites (2 Judets).
2.7 Training and Support
An application is only a success if its users are able to
Acceptable
Analysis Users/
Existing Owners Rol-Out
Systems Request for Proposal ———4 «1 —— ——— Installed Syste Vi adis
Cadaste & acaso s ler t Land Book
Land Book cause & Effects — and Boo LE NE PIU ST
— — training, technical support
—
m“ u IS
System Objectives ; d x A f X SS :
realise ents & priorities A N si Operational System
+ / | \ x acceptance^& feedback
pomme | Ne ise eg M
Understand 8 : xs A ; / J \ N Final Acceptance
Refine Business ideas, opinizn. expetiengos \ Test
Requirements |
Z acceptance
f | \ & feedkack
Business Requirements / : /
emonstration
& TS BECK
Configure &
Design /
Application Q
Solution / Ass
Design Specifications/
Construct Functiona
Application &
Integration Test
—
ality
rance
Acceptance &
Validation Test -
Simulated
Conditions
Pilot Installation
\ N
\
\ Test Run (30
\ days) - Pilot Sites
Cadastre &
Xi ; Land Book
demonstration
& feadback
| Tested Functional d
Pilot Installation of
Application -
Cadastre &
Land Book
Validation
Acceptance
Figure 1. Life Cycle Development Approach
Figure 1 details our life cycle development approach. The solid
lines indicate the actual process flow, and the dashed lines are
the user interaction with the system. The arrows indicate the
248
implement the tool into their daily business routine. Therefore,
a key component of any application development effort is the
transfer of knowledge to all levels of users on the specific
functionality of each component. To achieve this, the
Ste
the
Lai
Sys
use
apt
adc
use
trai
ser
en
dat
2.8
Pro
Sm
sig
pro
froi
res
this
pro
clie
ass
Im]
Ste
exe
resi
2.9
sup
an
con
datz
pro