Ops Admin (supercomponent)

From UG

Contents 1 Prerequisites, Classified As, Parent Mantis 2 Business Needs 3 Business Requirements 3.1 Technical Requirements 4 Technical Specification 4.1 Summary 4.2 User Interface and Functionality 4.3 Entities and Attributes 4.4 Special Cases and Misc 4.5 Look And Feel 4.6 Figures 4.6.1 Figure 1: 5 Questions and RFC 6 Known Non Critical Bugs 7 Links to Archived / Old specs 8 History 8.1 This doc has been created 8.2 Re-design (Tweak) (Spec Update): ..... <summary> ..... 9 DB 10 Code

Prerequisites, Classified As, Parent Mantis

• Classified As: supercomponent
• Parent Mantis: tbd

• Prerequisites:
  • read ...
  • ...

Business Needs

As any large System CT2 should be configurable through the user interface. So that superuser who is not IT specialist could change setting as required during the system operation.

Business Requirements

• We would like to have ideally all dropdowns to be managed through the Admin (create/edit/delete/archive)

• We need different levels of access to different parts of Admin

• Admin is shared by all offices, but some settings / views are office specific

Technical Requirements

• We need to created Look and Feel for this component at some point
• Archived feature needs to be standardized
• For shorter lists I recommend using drop down not combo box

Technical Specification

Summary

User Interface and Functionality

Entities and Attributes

Special Cases and Misc

Look And Feel

Figures

Figure 1:

Questions and RFC

Known Non Critical Bugs

Links to Archived / Old specs

History

This doc has been created

--Alex 18:47, 21 January 2010 (UTC)

Re-design (Tweak) (Spec Update): ..... <summary> .....

<wiki date/signature>

• mantis: <link>
• Biz Req updated? N/Y
• Tech Spec updated? N/Y

DB

Code

http://mantis.jaguarfreight.com/svn/repo2/cybertrax/trunk/java/CyberTrax/proto2.0.1f/admin/