Page History

{scrollbar:icons=false}
h1. {page-info:title}
{anchor:ContentsofthisPage}{panel:title=Contents of this Page}
{toc:minLevel=2}
{panel}

h2. Create form module

|| *Use Case Number* \\ | Init8pm25.pm24.1 \\ |
|| *Brief Description* | A form module is a reusable section of a form that contains one or more questions/CDEs.  These can be created from a set of existing questions or from scratch. \\ |
|| *Actor(s)* for this particular use case | Forms Curator \\ |
|| *Pre-condition* \\
The state of the system before the user interacts with it \\ | None. \\ |
|| *Post condition* \\
The state of the system after the user interacts with it \\ | A form module is created. \\ |
|| *Steps to take* \\
The step-by-step description of how users will interact with the system to achieve a specific business goal or function \\ | # A Forms Curator creates a new form module from scratch.
# The Forms Curator updates the form module metadata, including its name, visibility, etc.
# The Forms Curator associates a number of CDE questions to the form module.
# The Forms Curator saves the form module. |
|| *Alternate Flow* \\
Things which would prevent the normal flow of the use case \\ | The Forms Curator could select a number of existing CDEs (whether on a form or not) for which to create a form module.  This essentially combines steps #1 and #3 above. \\ |
|| *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. \\ | None. \\ |
|| *Fit criterion/Acceptance Criterion*  \\
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement? \\ | None. \\ |

h2. Copy form module into a form

|| *Use Case Number* \\ | Init8pm25.pm24.2 |
|| *Brief Description* | In order to reuse a form module, which is a set of CDE questions, the form module is copied/referenced in the form.  It is copied because it is allowable for changes to be made to the module that do not propagate to other users of the module, e.g. removal of a CDE.  However, it is also referenced in the sense that changes to the original form module are propagated to all instances of the form module.\\ |
|| *Actor(s)* for this particular use case | Forms Curator |
|| *Pre-condition* \\
The state of the system before the user interacts with it \\ | A form module is available for copying into a form\\ |
|| *Post condition* \\
The state of the system after the user interacts with it \\ | The form module has been copied into the form\\ |
|| *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 Forms Curator creates a new form or selects an existing form within which to include a form module
# The Forms Curator searches for the form module to include and selects it
# The form module is copied into the form while keeping a reference to the parent form |
|| *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. \\ | None. \\ |
|| *Fit criterion/Acceptance Criterion*  \\
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?  \\ | None. \\ |

h2. Update form module

|| *Use Case Number* \\ | Init8pm25.pm24.3 |
|| *Brief Description* | After an original form module is copied into a form, any changes to the original form module are propagated to the instances of that form module.  These include removal and addition of CDE questions.\\ |
|| *Actor(s)* for this particular use case | Forms Curator |
|| *Pre-condition* \\
The state of the system before the user interacts with it \\ | A form module is available and has been copied into one or more forms.\\ |
|| *Post condition* \\
The state of the system after the user interacts with it \\ | The form module has been updated and changes are propagated to all instances of the form module in existing forms.\\ |
|| *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 Forms Curator selects the form module to edit (independently of any form)
# The Forms Curator updates the form module, such as adding and/or removing CDE questions
# The Forms Curator saves the updates
# The Forms Curator propagates the updates to all instances of the form module in existing forms |
|| *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. \\ | None. |
|| *Fit criterion/Acceptance Criterion*  \\
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement? \\ | None. \\ |

h2. Update form module copy

|| *Use Case Number* \\ | Init8pm25.pm24.4 |
|| *Brief Description* | Once a form module has been copied into a form, any changes to the copied instance are not reflected on the original form module or any other instances of the form module.  These include removal and addition of CDE questions. |
|| *Actor(s)* for this particular use case | Forms Curator |
|| *Pre-condition* \\
The state of the system before the user interacts with it \\ | A form module is available and has been copied into one or more forms. |
|| *Post condition* \\
The state of the system after the user interacts with it \\ | The form module instance has been updated and those changes are only reflected in the form in which the form module instance is included.\\ |
| *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 Forms Curator selects a form to update
# The Forms Curator selects the form module instance within the form to update
# The Forms Curator updates the form module instance, such as adding and/or removing CDE questions
# The Forms Curator saves the form module instance and the form |
|| *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. \\ | None. |
|| *Fit criterion/Acceptance Criterion*  \\
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement? \\ | None. |

h2. Retire form module

|| *Use Case Number* \\ | Init8pm25.pm24.5 |
|| *Brief Description* | A publicly accessible form module can be retired from further copying into a form or updating.  This retiring does not remove the form module instances that have previously been copied.\\ |
|| *Actor(s)* for this particular use case | Forms Curator |
|| *Pre-condition* \\
The state of the system before the user interacts with it \\ | A form module exists and has been reused in zero or more forms\\ |
|| *Post condition* \\
The state of the system after the user interacts with it \\ | The form module is retired (cannot be copied or updated) and all existing form module instances remain unchanged \\ |
|| *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 Forms Curator selects the form module to retire
# The Forms Curator marks the form module as retired
# The Forms Curator saves the form module in a retired state |
|| *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. \\ | None. \\ |
|| *Fit criterion/Acceptance Criterion*  \\
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement? \\ | None. |
\\
{scrollbar:icons=false}