Page History

Versions Compared

Old Version 7

changes.mady.by.user Unknown User (wileyal)

Saved on Jan 22, 2012

compared with

New Version Current

changes.mady.by.user Unknown User (wileyal)

Saved on Jan 22, 2012

Key

This line was added.
This line was removed.
Formatting was changed.

Comment: Migration of unmigrated content due to installation of a new plugin

Scrollbar

icons	false

...

Page info

...

title
title

Anchor

	ContentsofthisPage
	ContentsofthisPage

Panel

title	Contents of this Page

Table of Contents

minLevel	2

Init1bes4.PM10.U1

...

-

...

Assist

...

in

...

Terminology

...

Mappings

Use Case Number	Init1bes4.pm10.U1

...


Brief Description	correct concepts from the correct terminologies can be a time consuming and error prone process. Tooling should be integrated with the metadata modeling process to facilitate the reuse of standard semantics when reusing standard information models or common data elements. This is especially important when deriving a model from a Domain Analysis Model (DAM).
Actor(s) for this particular use case	Information Modeler
Pre-condition The state of the system before the user interacts with it	A model has been created and reuses one or more common data elements and/or is derived from a standard analysis model.
Post condition The state of the system after the user interacts with it	The "correct" semantic concepts are selected for reused data elements.
Steps to take The step-by-step description of how users will interact with the system to achieve a specific business goal or function	The Information Modeler enters the flow for adding semantic concepts from controlled terminologies to the model A list of likely candidate concepts are presented for each data element that is produced from the information model The Information Modeler is able to select those concepts that will be reused, add to them, and remove from the list The Information Modeler saves the concepts into the model
Alternate Flow Things which would prevent the normal flow of the use case	None.
Priority The priority of implementing the use case: High, Medium or Low	Medium
Associated Links The brief user stories, each describing the user interacts with the system for the one function only of the use case. There would potentially be a number of user stories that make up the use case.	Init1bes4 - SIW Enhancement
Fit criterion/Acceptance Criterion How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?	It is highly desirable that this functionality be accessible directly within existing tooling, such as the modeling tool or the SIW The process should be as simple as possible and user friendly

Init1bes4.pm10.U2 - Restrict Terminology Mappings

Use Case Number	Init1bes4.pm10.U2
Brief Description	In addition to providing initial suggestions based on reused metadata, it may also be desirable to restrict the available terminologies for concept selection. For example, specific domains may have terminologies that may be more appropriate than others, and different terminology services may be more appropriate for use when deriving from Domain Analysis Models (DAMs).
Actor(s) for this particular use case	Information Modeler
Pre-condition The state of the system before the user interacts with it	A model has been created and reuses one or more common data elements and/or is derived from a standard analysis model.
Post condition The state of the system after the user interacts with it	The "correct" semantic concepts are selected for reused data elements.
Steps to take The step-by-step description of how users will interact with the system to achieve a specific business goal or function	The Information Modeler enters the flow for adding semantic concepts from controlled terminologies to the model A list of likely candidate terminologies are presented to the user based upon the reused common data elements The Information Modeler is able to select those concepts that will be reused, add to them, and remove from the list The Information Modeler saves the concepts into the model
Alternate Flow Things which would prevent the normal flow of the use case	The Information Modeler is able to broaden his search to other terminologies or terminology services if desired
Priority The priority of implementing the use case: High, Medium or Low	Medium
Associated Links The brief user stories, each describing the user interacts with the system for the one function only of the use case. There would potentially be a number of user stories that make up the use case.	Init1bes4 - SIW Enhancement
Fit criterion/Acceptance Criterion How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?	It is highly desirable that this functionality be accessible directly within existing tooling, such as the modeling tool or the SIW The process should be as simple as possible and user friendly

Init1bes4.pm10.U3 - Review Terminology Mappings

Use Case Number	Init1bes4.pm10.U3
Brief Description	While it is desirable for Information Modelers to have concept selection more easily facilitated, it is also desirable for Compatibility Reviewers to have review of reused concepts and terminologies more easily facilitated. Tooling should exist that performs side-by-side automated and manual comparison of concept reuse.
Actor(s) for this particular use case	Information Modeler
Pre-condition The state of the system before the user interacts with it	An Information Modeler has created an information model, associated terminologies and concepts, and registered the model.
Post condition The state of the system after the user interacts with it	The Compatibility Reviewer completes his assessment of terminology and concept reuse.
Steps to take The step-by-step description of how users will interact with the system to achieve a specific business goal or function	The Compatibility Reviewer enters the portion of the review process related to terminology and concept reuse For each reused data element, the terminologies used are presented by the review system side-by-side with those from the original data element and differences are highlighted For each reused data element, the concepts used are presented by the review system side-by-side with those from the original data element and differences are highlighted A report is automatically generated for the Compatibility Reviewer by the review system The Compatibility Reviewer is able to note potential problems with reuse as it relates to caBIG standards
Alternate Flow Things which would prevent the normal flow of the use case	None.
Priority The priority of implementing the use case: High, Medium or Low	Medium
Associated Links The brief user stories, each describing the user interacts with the system for the one function only of the use case. There would potentially be a number of user stories that make up the use case.	Init1bes4 - SIW Enhancement
Fit criterion/Acceptance Criterion How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?	1. 2...