Wiki Markup |
---|
{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: Technical}
h2. Design: Technical
h3. Service Design and Implementation
h2. Screen Flow Diagram
Layout use cases based on the screen flows indicating navigation between different screens and pop-ups.\\
h1. Security\\
h2. Roles -- list of roles to be defined
h2. Permissions -- list of permissions to be defined
h2. User Profiles -- user profiles that may be applied roles/permissions (also for test/mock purposes)\\
h1. Rules\\
h2. Context & Agendas
h2. Terms & Prepositions
h2. Sample XML file
h1.
h1. Component Design
h1.
h2. OJB.XML
h2. Class Diagram
h2. State Chart Diagram
h4. Service Contracts
h4. Service Implementation
{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. |
Page Comparison
General
Content
Integrations