|
|
|
Data Development and Evolution
|
Application integration in data conversion quality Measurement
Possible issues related to application use on GIS Projects
While there are numerous benefits to incorporating applications-based testing into a GIS
implementation project, there are also some problems that could arise to the detriment of the
GIS project. Proper planning, being alert to signs of problems and being proactive in addressing
issues will be major factors in the success of the GIS project. Some of the issues are:
- Use of the applications for quality checking will require the commitment of experienced application users.
- The use of applications for testing may be viewed as superfluous or excessive, and impacting the project schedule
- There may be new applications internal or external to the GIS. Some of these new applications may not be available in time for testing or they may be only partially fieldtested. It may also be difficult to find someone knowledgeable enough to use the new applications as QA tools.
- Management of the GIS project may be more difficult because of the larger number of staff
and departments that will be involved. Key personnel or management outside the core GIS
project may not give sufficient priority to their GIS support role
All of the above items are valid concerns. However, in most cases these issues can be minimized
through proper project set-up, task sequencing, communications, and good project management.
The following provides some thoughts on managing these issues:
- There is a trade-off in having experienced application users involved in the GIS testing
process because of conflicting loyalties and priorities. However, without user involvement,
there is considerable risk that the GIS data or interface may not support an application critical
to the company. If the end users are seen and treated as key members of the GIS team and
they understand why participation is in their best interests, their support should not pose a
problem.
- Often the most rigorous test of data is evaluating its ability to support a complex application.
Conversely if, for whatever reason, the GIS data cannot support the targeted work processes,
the project and its QA processes will be seen as failures. For critical systems, the
consequences of having a discrepancy between the GIS and the application are serious. The
best way to minimize that risk is to validate the GIS/application system as soon as possible.
There should be a limited and manageable number of applications flagged as "key
applications".
- Implementing new GIS applications and migrating to different external applications as part
of the GIS implementation are among the most challenging aspects of the GIS integration.
Compromises will have to be made as to what state of development the target applications
should be in before the GIS project progresses to the full implementation stage. As much as
possible, new applications that support critical requirements should be accounted for in the
testing and integration planning. Applications that cannot be validated in the pre-production
phases may need to have more extensive design reviews and change controls.
- The size of the utility's core GIS implementation team should be as lean as possible, while
ensuring that the significant end-users are represented and involved through all the stages of
the project. Presentation of the overall goals and requirements of the GIS project, the critical
objectives, and the proposed GIS team composition to line managers and supervisors prior to
commencing any significant design can provide a check that adequate representation and
staff involvement occurs.
Suggested Approach
The following provides a synopsis of key activities that should be factored into the GIS
implementation plan in order to coordinate application based testing:
Planning:
- Ensure that a comprehensive list of significant applications, business processes, and systems
that will be affected by the GIS implementation has been compiled. The document should
also include a list of key corporate systems and functions that will not be involved in the
initial implementation, noting which functions are being considered for future integration.
- Have the final list of affected/un-affected systems reviewed and approved by management.
- Rate the applications using factors such as importance in supporting key business functions,
maturity of the application, and the complexity of the data exchange between the GIS and the
application.
- Select approximately ten critical applications that should be rigorously tested and used as a
quality assurance metric during the project.
- Finalize the draft project plan and schedule, accounting for the application testing and
involvement of key functional staff.
- Check that the core project team, supporting staff, application development and testing
requirements, and project objectives are consistent
- Brief functional and executive management on the plan and schedule, emphasizing the roles
that the functional departments and staff will have on the team.
- Obtain buy-in from key managers and sponsors. Identify "champions" for each major area of
functionality.
- Determine what training, documentation, and other services will be required to support
application testing and integration.
|
|
|
|
