Client Company

From UG

(Difference between revisions)

Jump to: navigation, search

Revision as of 20:26, 15 April 2010

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

Sales Person

Jag user who receives commissions for this Company's profit.

Sales Person Start Day

Day from which Sales Person receives his commission.

If Sales Person is set then this date must be set. Produce error pop up on save if not: "Error: Sales Person Start Day must be set! [OK]"
If Sales Person is changed but date remains the same (check on Save) produce Warning pop up on save:
- "Warning! Sales Person is changed but Sales Person Start Day remains the same! Are you sure? [Y][N]"
  - [Y] - continue, save
  - [N] - go back to edit mode

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 on Create CT page
- show it with everywhere else (with archive logo or print "archived" next to the name) where we have Clients lists

m1878

see #Commissions functionality

@@ Line 85: / Line 85: @@
 * 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)
+* if Client Company is archived then:
+** hide it on [[Create CT]] page
+** show it with everywhere else (with archive logo or print "archived" next to the name) where we have Clients lists
 === m1878 ===
 * see [[#Commissions functionality]]