Jaguar Software Development Process
From UG
(Difference between revisions)
(→Requirement Specification Workflow) |
|||
| (7 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| - | [[Category: | + | [[Category:Software Development Processes]] |
| + | == Intro == | ||
| + | * parent mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=1768 | ||
| - | + | == Workflow == | |
| - | == | + | |
[[File:Development process March 26.jpg]] | [[File:Development process March 26.jpg]] | ||
| Line 19: | Line 20: | ||
* [[Systems Analyst]] (SA) | * [[Systems Analyst]] (SA) | ||
| - | * [[ | + | * [[Systems Architect]] |
| - | * | + | * [[Project Manager]] |
| - | * | + | * CT2 [[Liaison]] |
| - | * Review Group - group of people who must review a feature/change, each particular feature/change has its own review group | + | * [[CT2 Board]] - top CT2 decision making committee |
| + | |||
| + | * [[Super user]] or [[Power 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 | ||
| + | |||
| + | === Documentation in Wiki and Mantis === | ||
| + | |||
| + | * see [[Spec_Example]] | ||
== Teams per Component == | == Teams per Component == | ||
| Line 40: | Line 49: | ||
== 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]] | ||
Current revision as of 07:00, 7 June 2010
Contents |
[edit] Intro
- parent mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=1768
[edit] Workflow
[edit] 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.
[edit] Players
- Module Owner (MO)
- Business Analyst (BA)
- Systems Analyst (SA)
- CT2 Liaison
- CT2 Board - top CT2 decision making committee
- Super user or Power 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
[edit] Documentation in Wiki and Mantis
- see Spec_Example
[edit] Teams per Component
See Mantis fields:
p_BizAnalyst p_Developer p_ModOwner p_QA p_SysAnalyst
[edit] COMMUNICATION OPTIONS
- Media: emails, skype call, mantis, in person, etc
- Pattern: all together, as a sequence, etc
