database government built, The

OUTSOURCING

Consider a simple software program for drawing a square. It might start with the left side and proceed in sequential order to produce the top, right and bottom sides. Alternatively, it may use various other non-sequential approaches. The specified outcome is still a square. The way in which that outcome is achieved may not be significant. However, sometimes the fact that technology works is not enough. Sometimes, the way in which it works may be equally, or more, important.

Specifications are the cornerstone of software development. The desired outcome is the development of an integrated system that operates to conform to the applicable specifications. Specifications are the criteria which establish what the system can do in teh final analysis to satisfy its users' requirements. This is often expressed as two dimensions: the functional specifications (what things can the software do) and the performance specifications (how many, how quickly and how reliably can the software do those things). But there is a third dimension, which is often overlooked: the design specification.

Design specifications establish the platform, language, architecture and modular structure of software. A specific documented software development methodology may also be prescribed to promote quality assurance. Design has an impact on outcomes including the following:

Testing: Specify an appropriate modular structure to establish functional sub-systems and enable preliminary module testing before attempting integrated acceptance testing;

Interfaces: Specify an appropriate architecture to enable simple and effective interconnections to existing systems;

Expansion: Specify a well-known programming language and an accommodating architecture to enable third parties to develop and connect products that will work with the primary system.

Intellectual Property: Specify the contents of modular objects in a way that separates and enables the clear designation of elements such as preexisting code, which may be owned by the developer; independent code, which is owned by third parties; and, custom code developments which may be owned by the client.

The federal government of Canada human resources database, which was recently ordered to be dismantled, provides a real life example of the importance of design specifications. The database worked effectively, but unfortunately, the manner in which it worked did not provide suitable control features for managing access to personal information.

The database was an unstructured pool of data elements. In fact, the federal privacy commissioner referred to it as "a huge lake of information, almost indiscriminately gathered and dumped in there for possible and undefined future use." To address privacy concerns, the department was ordered to dismantle the database. It also adopted a specific structural approach for future government databases. That database design approach involves segregating personal identifiers such as name, telephone number and other personal information from generic data elements. The personal identifiers will be also be encrypted.

Controlling the ability to decrypt and link personal identifiers with other data elements provides a way of administering access to various levels of information. Correlations of data may range from generic statistics to geographically related information, to age group related information to specific individually identifiable information.

Accordingly, similar design specifications may become a required feature for future government database development projects. Remember the real world is three dimensional. Software that just works may not be enough. Consider whether the manner in which the software works is important, and if so be sure to include a detailed design specification.

By David Robinson

David Robinson, LLB, is the executive director of the TechKnowledgey Group, advisers on negotiating and documenting comples IT transactions. Tel: 800-973-3833. E-mail: info@tkgroup.com.

Copyright Plesman Publications Ltd. Jul 2000
Provided by ProQuest Information and Learning Company. All rights Reserved