Jaguar Software Development Process

From UG

Revision as of 17:45, 24 May 2010 (edit) Alex (Talk | contribs) (→Main idea) ← Older edit

Revision as of 19:29, 24 May 2010 (edit) (undo) Alex (Talk | contribs) m (moved CT2 Development Process v3 to Software Development Process) Newer edit →

---

Revision as of 19:29, 24 May 2010

Contents 1 Workflow 1.1 Main idea 1.2 Players 2 Teams per Component 3 COMMUNICATION OPTIONS

Workflow

Main idea

At the core of workflow above is a sequence of "translations and furtherer elaborations" from MO to BA, from BA to SA and from SA to Developer. Module Owner formulates Core Need. Business Analyst translates it into Detailed Requirements. System Analyst translates them into best possible Detailed Design. Finally, Developer translates design into program.

Players

• Module Owner (MO)

• Business Analyst (BA)

• Systems Analyst (SA)

• Liaison

• CT2 Board - top CT2 decision making committee

• Super user - end user who represents a group of users for specific feature

• Review Group - group of people who must review a feature/change, each particular feature/change has its own review group

Teams per Component

See Mantis fields:

p_BizAnalyst	  
p_Developer	  
p_ModOwner	 
p_QA	  
p_SysAnalyst

COMMUNICATION OPTIONS

  * Media: emails, skype call, mantis, in person, etc
 
   * Pattern: all together, as a sequence, etc