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.
User Stories
Priority Rank Order
1.The Deliver/Circulations modules caters to the loaning, returns, over-dues, circulation policies and Patron management.
Design Technical
Service Design and Implementation
Screen Flow Diagram
Layout use cases based on the screen flows indicating navigation between different screens and pop-ups.
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)
Rules
- Context & Agendas
- Terms & Prepositions
- Sample XML file
Component Design
- OBJ.xml
- Class Diagram
- State Chart Diagram
Service Contracts
Service Implementation
UI Screen 
l
Data Model
Entity : Loan
Name |
Max |
Data Type |
Default Value |
Input Type |
Action Event |
Action Event Function Name |
Validation |
Tab Index |
Remarks |
Load_ID |
|
|
|
|
|
|
|
|
System Generated |
Patron_ID |
|
|
|
|
|
|
|
|
Foreign Key from Patron Record |
Item_ID |
|
|
|
|
|
|
|
|
Foreign Key from Item Record |