Use Case Number
The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

<!-- /* Font Definitions */ @font-face

/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal

.MsoChpDefault

@page Section1

div.Section1

-->CAI2SD1

Brief Description

<!-- /* Font Definitions */ @font-face

/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal

.MsoChpDefault

@page Section1

div.Section1

-->This use case describes the sequence of events that follow when an actor is looking for CDE of interest from caDSR

Actor(s) for this particular use case

<!-- /* Font Definitions */ @font-face

/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal

.MsoChpDefault

@page Section1

div.Section1

-->Study Manager

Pre-condition
The state of the system before the user interacts with it

1. caIntegrator has the necessary API to connect to caDSR and import the relevant data in caDSR
2. Along with results, the API should provide data such as frequency of use, Actor populations, applicability across domains, diseases etc.

Post condition
The state of the system after the user interacts with it

<!-- /* Font Definitions */ @font-face

/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal

.MsoChpDefault

@page Section1

div.Section1

-->Actor is able to view data that shows up in order of relevance

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function

<!-- /* Font Definitions */ @font-face

/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal

.MsoChpDefault

@page Section1

div.Section1

/* List Definitions */ @list l0

@list l0:level1

ol

ul

-->

1. Actor clicks on change assignment hyperlink
2. Actor gets to select if he wants to see 'Draft new CDEs as a part of the result
3. The system fetches a list of local CDEs and CDEs from caDSR that show up in the following order of prioritization/relevance
   <!-- /* Font Definitions */ @font-face
   Unknown macro: {font-family}
   /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal
   Unknown macro: {mso-style-unhide}
   p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
   Unknown macro: {mso-style-priority}
   p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
   Unknown macro: {mso-style-priority}
   p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
   Unknown macro: {mso-style-priority}
   p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
   Unknown macro: {mso-style-priority}
   .MsoChpDefault
   Unknown macro: {mso-style-type}
   @page Section1
   Unknown macro: {size}
   div.Section1
   Unknown macro: {page}
   /* List Definitions */ @list l0
   Unknown macro: {mso-list-id}
   @list l0:level1
   Unknown macro: {mso-level-number-format}
   ol
   Unknown macro: {margin-bottom}
   ul
   Unknown macro: {margin-bottom}
   -->       I.           Standards CDE
        II.           CDE displayed according to frequency of 
             use, Actor populations, applicability
             across domains, diseases.
4. <!-- /* Font Definitions */ @font-face
   Unknown macro: {font-family}
   /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal
   Unknown macro: {mso-style-unhide}
   .MsoChpDefault
   Unknown macro: {mso-style-type}
   @page Section1
   Unknown macro: {size}
   div.Section1
   Unknown macro: {page}
   --> The result is displayed as
               I.           via indentation, like Google                          II.         Brother and sister CDEs (within same object class)
                           III.       Similar CDEs with differences highlighted
   

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

High

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.

Fit criterion/Acceptance Criterion 
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?

<!-- /* Font Definitions */ @font-face

/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal

.MsoChpDefault

@page Section1

div.Section1

-->The actor must be able to import most relevant CDE into his study with reasonable ease, and these must be represented fully.

Use Case Number
The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

<!-- /* Font Definitions */ @font-face

/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal

.MsoChpDefault

@page Section1

div.Section1

-->CAI2SD2

Brief Description

Actor(s) for this particular use case

Pre-condition
The state of the system before the user interacts with it

Post condition
The state of the system after the user interacts with it

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function

1.
2.

Alternate Flow
Things which would prevent the normal flow of the use case

Priority
The priority of implementing the use case: High, Medium or Low

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.

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...

Use Case Number
The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

n.n

Brief Description

Actor(s) for this particular use case

Pre-condition
The state of the system before the user interacts with it

Post condition
The state of the system after the user interacts with it

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function

1.
2.

Alternate Flow
Things which would prevent the normal flow of the use case

Priority
The priority of implementing the use case: High, Medium or Low

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.

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...

Use Case Number
The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

n.n

Brief Description

Actor(s) for this particular use case

Pre-condition
The state of the system before the user interacts with it

Post condition
The state of the system after the user interacts with it

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function

1.
2.

Alternate Flow
Things which would prevent the normal flow of the use case

Priority
The priority of implementing the use case: High, Medium or Low

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.

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...

Use Case Number
The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

n.n

Brief Description

Actor(s) for this particular use case

Pre-condition
The state of the system before the user interacts with it

Post condition
The state of the system after the user interacts with it

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function

1.
2.

Alternate Flow
Things which would prevent the normal flow of the use case

Priority
The priority of implementing the use case: High, Medium or Low

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.

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...