Jaguar Software Development Process
From UG
(Difference between revisions)
(→COMMUNICATION OPTIONS) |
|||
| Line 40: | Line 40: | ||
== COMMUNICATION OPTIONS == | == COMMUNICATION OPTIONS == | ||
| - | + | * Media: emails, skype call, mantis, in person, etc | |
| - | + | * Pattern: all together, as a sequence, etc | |
| + | |||
== See Also == | == See Also == | ||
* [[CT2_Development_Process]] | * [[CT2_Development_Process]] | ||
* [[CT2_Development_Process v2]] | * [[CT2_Development_Process v2]] | ||
Revision as of 22:44, 24 May 2010
Contents |
Specifications 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)
- 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
