Ops Admin (supercomponent)

From UG

Revision as of 20:02, 21 January 2010 (edit) Alex (Talk | contribs) (→Business Requirements) ← Older edit		Current revision as of 18:04, 11 November 2011 (edit) (undo) Denise (Talk | contribs) (Undo revision 23204 by Denise (Talk))
(3 intermediate revisions not shown)
Line 1:		Line 1:
	[[Category:OpsAdmin]]		[[Category:OpsAdmin]]
-	== Prerequisites, Classified As, Parent Mantis ==	+	== General Info ==
	* Classified As:  [[supercomponent]]		* Classified As:  [[supercomponent]]
	* Parent Mantis: [http://mantis.jaguarfreight.com/mantis/view.php?id=tbd tbd]		* Parent Mantis: [http://mantis.jaguarfreight.com/mantis/view.php?id=tbd tbd]
		+	* Prerequisites: none
-	* Prerequisites:	+	=== Scope ===
-	** read ...	+
-	** ...	+	* This wiki covers overall requirements / design for Ops Admin supercomponent.
		+	* Any details related to specific admin component should be addressed in the article for that component.
	== Business Needs ==		== Business Needs ==
Line 64:		Line 66:
	== DB ==		== DB ==
		+
		+	== Code ==
		+
		+	http://mantis.jaguarfreight.com/svn/repo2/cybertrax/trunk/java/CyberTrax/proto2.0.1f/admin/

---

Current revision as of 18:04, 11 November 2011

Contents 1 General Info 1.1 Scope 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

[edit] General Info

• Classified As: supercomponent
• Parent Mantis: tbd
• Prerequisites: none

[edit] Scope

• This wiki covers overall requirements / design for Ops Admin supercomponent.
• Any details related to specific admin component should be addressed in the article for that component.

[edit] 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.

[edit] 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

[edit] 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

[edit] Technical Specification

[edit] Summary

[edit] User Interface and Functionality

[edit] Entities and Attributes

[edit] Special Cases and Misc

[edit] Look And Feel

[edit] Figures

[edit] Figure 1:

[edit] Questions and RFC

[edit] Known Non Critical Bugs

[edit] Links to Archived / Old specs

[edit] History

[edit] This doc has been created

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

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

<wiki date/signature>

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

[edit] DB

[edit] Code

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