Data/term-model. 2 Copyright e-Government Program (Yesser) Data/term-model - Summary Slide ...

Data/term-model

Copyright e-Government Program (Yesser) 2

Data/term-model - Summary Slide

Definition of a data/term modelTerm Analysis and Modeling – the process

Term Analysis and Modeling Collection of terms and definitions

Term analysis Term analysis – Rules of thumb Documentation of terms

Modeling Draw the data/term model

Verification

Audit Use Cases and Service DescriptionThe YEFI standardization process


Definition of a term model

“A set of terms and relations, which describes a concrete or abstract part of the world”

…or put in another way:

”Terms and relations that describe all,or part of, the business, depending on the context”


Term Analysis and Modeling – the processA

gen

cy

Collectionof terms anddefinitions

Termanalysis

Plan TermAnalysis andModeling

Initial state:- e-Service provisional budget approved

Final state:- the term model finished within defined scope

VerifyModel

TermModel

Finished ?

yes

no

Audit Use Casesand Service description

Link to:- Use Case- Service Description

YEFI StandardizationProcess

TermModeling

Link to:- YEFI


List of relevant terms The level of detail depends on the purpose of the term model

Mapping of the company’s language – may be less detailed RFP for new system – requires more detail

Method: Search various, complementing sources

YEFI data-catalogue for reusable business objects Interviews with company, users, professional experts, domain experts Thesauruses in the domain Websites on the topic – both that of the organisation and others that might be relevant Similar system Any requirements documentation Process descriptions Use cases …

Collection of terms and definitions


Collection of terms and definitions

Collect and sort! Initial review Identify terms Re-review Qualify terms for use cases


Term analysis

The terms have been selected and grouped The central terms have been selected The terms have been sorted in smaller groups Objects have been identified and attributes placed - any values have

been identified The selected terms have been describedThe relations have been identified

Method: Look up YEFI for data and metadata standards Get help from domain specialists. Let them do the grouping and

describing Read about the terms, in the collected materials The domain specialists can point out relations during the process.

Furthermore, the relations will appear in the descriptions


Too many is better than too few. Many are cut along the process. Choose terms aimed at the goal for the term model – for RFP, look at the system

vision Object and attribute names are nouns - if in doubt if the object is an object or an

attribute, make it an object, at least at first Attributes are object properties, i.e. they describe the object - typically dates,

numbers, texts Make an attribute an object if it is it is in fact several attributes The model is easier to understand and use if you note the object roles

(”governing object”, goal, recipient, source, performing instrument, etc.). Enter into description

Add relations where connections between terms must be remembered However, too many relations make the model chaotic! Relation names are verbs Name the relations according to their modality, i.e. specify using; shall, will,

should or another of the so-called modal verbs, in order to help specify status for the used relations

Term analysis – Rules of thumb


Documentation of terms

Link to example


Modeling

First draft of the term model has been drawn and is ready for validation

Method: Establish final terms:

Objects: Use nouns, composite nouns if necessary, should they better describe the term

Attributes: Use as specific nouns as possible. Indicate type of data, e.g. ”Date of car purchase” = Car purchase date

Values: Use those of the business Establish final relations (and their types) between objects

The types are reviewed in the following Insert into modelling tool

If UML class chart – insert the objects as classes and add attributes If other tool – agree on form of notation for objects, attributes, values and

relations


Modeling


YEFI Standardization Process


YEFI example


Verification

Operations / domain professionals have been queried

Relevant external parties have been queried

The term model has been used in real-life situations (in this case, described in use cases)

Method: Hearings are done, either in writing or spoken (the model may take some

explaining to outsiders) Use use cases or other descriptions of operational situations to test scenarios

– does the model express what the use case indicates?


Audit Use Cases and Service Description

Revise Use cases If there is a need for use case changes, these are re-vised on the go Make use of professional specialists

Revise Service specifications Change the specifications to match the changes made in the term

model

Data/term-model. 2 Copyright e-Government Program (Yesser) Data/term-model - Summary Slide ...

Documents

Transcript of Data/term-model. 2 Copyright e-Government Program (Yesser) Data/term-model - Summary Slide ...