Principle 16 - Applications Data Sharing
Applications must use a common base of well-defined University data and reference
a common repository.
Note
Although it may span multiple physical locations, this base is logically common in
that the elements have a common definition and may be shared by multiple applications.
This common base would include all University data regardless of which application
creates the data or how many applications use the data.
 Rationale
Uncontrolled data redundancy combined with inconsistent definitions and values
for similar data elements increases the risk of discrepancies and inaccuracies
across applications.
Implications
- The acquisition of any application, regardless of the size of its user
base, should include an evaluation of what data is already defined in the
common base, what data should be added, what data can be shared, and what
data may need to be stored redundantly.
- When data must be stored redundantly within the common base, applications
should retrieve the data from its database of record.
- A limited, supported set of appropriate tools and techniques must be developed
and made available for shared use.
- Wherever possible, comon data access routines should be developed and made
available for shared use.
- The data dictionaries of new and existing applications may need to be modified
to allow integration with a central data repository.
- The application's creation and use of data must conform to the rules for
that data as specified in the University's data architecture.
- Although sharing data across applications increases the complexity of application
development and data security policies and procedures, it also increases the
dependability and accessibility of the data.
|
