Client Company

From UG

Revision as of 22:17, 1 April 2010 (edit) Alex (Talk | contribs) (→History) ← Older edit		Revision as of 22:19, 1 April 2010 (edit) (undo) Alex (Talk | contribs) (→Detailed Design) Newer edit →
Line 32:		Line 32:
	== Detailed Design ==		== Detailed Design ==
-	* ''This section is defined by [[Systems Analyst]]. ''
-	* ''It contains detailed technical design is written after [[#Business Requirements]] and [[#Technical Requirements]] are defined.''
-	=== Summary ===	+	=== Commissions functionality ===
-		+
-	=== User Interface ===	+
-		+
-	=== Functionality / Use Cases ===	+
-	* '' This section you could spit into two. But often it is hard to do since often most of functionality is UI related''	+
-		+
-	=== Special Cases and Misc ===	+
-	* '' If any exist''	+
	== QA ==		== QA ==

---

Revision as of 22:19, 1 April 2010

Contents 1 General Info and Scope 1.1 Scope 2 Business Requirements 3 Notes from Systems Architect 4 Rapid Design 5 Detailed Design 5.1 Commissions functionality 6 QA 6.1 Test Cases 7 Look and Feel 8 Figures 8.1 Figure 1: 9 Misc 9.1 Link to User Guide 9.2 Questions 9.3 Request For Comments (Suggestions and Ideas) 9.4 Known Non Critical Bugs 9.5 Implementation: Link To DB 9.6 Implementation: Link To Front End Code 9.7 Implementation: Link To Back End Code 10 History 10.1 m780 10.2 m1878

General Info and Scope

• Classified As: (large) component
• Parent Mantis: 601
• Prerequisites: any articles that must be read before to understand this?

Scope

• List what it covers and what it does not

Covers everything under: Admin > Client Companies:

• Client company tab
• Client company groups tab
• Credit Limits/Terms/Statuses

! It is up to System Analyst to have separate wiki/parent mantis for every/some items on the list above. --Alex 00:47, 31 January 2010 (UTC)

Business Requirements

• This section is defined by Business Analyst
• In this section this component/feature is defined from the business standpoint. All important points are listed. It could include some design details if business insists on specific design.

BR to be updated

Notes from Systems Architect

• This section is defined by Systems Architect. It is written after #Business Requirements are defined.
• The purpose of this section is to give direction to System Analysts who will write detailed specification.

Rapid Design

• In some cases (component is non standard) we need to do preliminary not so detailed design before detailed final. And maybe even code it to create Prototype
• This section does not have to be too detailed or too formalized. We shall not spend too much time on Prototypes - they can change many times.

Detailed Design

Commissions functionality

QA

This section is to be written by QA Engineer or QA Manager or Systems Analyst.

Test Cases

• List unusual scenarios - things that user most of the time would not do but system must handle well
• Do not list Common Test Cases - link to them

Look and Feel

• This section is to be written / defined by Graphic Designer and UI Designer.
• This includes: final graphics, final layout
• Layout defined here should refine, provide more detials to "functional definitions" of UI as defined in #User Interface and Functionality section above

Figures

Figure 1:

Misc

Link to User Guide

Questions

Request For Comments (Suggestions and Ideas)

Known Non Critical Bugs

• Critical bugs must be posted into Mantis

Implementation: Link To DB

Implementation: Link To Front End Code

Implementation: Link To Back End Code

History

m780

• 0000780: (*ph1)(Admin Client Companies) Implement "archive" function feature
• implement "standard CT2 archive functionality"
• if Client Company is archived then hide it everywhere (where we have Clients lists, for example Create CT page)

m1878

• see #Commissions functionality