Page Comparison

{composition-setup}

{deck:id=Kuali OLE}

{card:label=Overview}

{section}
{column:width=50%}




h3. Description

"This section describes the high level goal of the feature."

The technical design document shall lay out the high level design of how the module is to be implemented. The details laid out shall include the Wire-frames for User Interface design, Data Element Layout, including the logical Database Design, Component Spefications including artifacts such as Class Diagram, State Chart Diagrams, OJB.xml specifications, KRMS Rules specifications including brief description of the context, agenda, terms and other relevant information.

{card}
{card:label = Design: Business}

h3. User Stories

h4. Priority Rank Order

1.The Deliver/Circulations modules caters to the loaning, returns, over-dues, circulation policies and Patron management. 
{card}
{card:label = Design: Techinical}
\\
h2
h6. Design:  Technical


h4h6. Service Design and Implementation


h3h4.


h4h6. Screen Flow Diagram


h3.

Layout use cases based on the screen flows indicating navigation between different screens and pop-ups. 

h6. Security

Roles -- list of roles to be defined


Permissions -- list of permissions to be defined


User Profiles -- user profiles that may be applied roles/permissions (also for test/mock purposes) 

h6. Rules

Context & Agendas


Terms & Prepositions


Sample XML file


h1.  


h1h6. Component Design


h1OBJ.xml
 
Class Diagram
h2.
OJB.XML


h2. ClassState Chart Diagram


h2h6. StateService ChartContracts
Diagram

h4h6. Service ContractsImplementation


h4h1.
Service

Implementationh4.

{card}
{card:label = Data Model}

h2. Data Model


h2. Entity : Loan\\

| *Name* | *Max* \\
*Len* | *Data Type* | *Default Value* | *Input Type* | *Action Event* | *Validation* \\
*Type* | *Tab Index* | *Remarks* |
| | | | | | | | | |


h2.