SA re defined
From UG
(Difference between revisions)
(Created page with 'Category:PM (public) == To == Systems Analysts == Summary == Dev Team expressed concerns to me about what SAs put into wiki spec. To address them we agreed to the following…') |
(→Summary) |
||
| Line 6: | Line 6: | ||
== Summary == | == Summary == | ||
Dev Team expressed concerns to me about what SAs put into wiki spec. To address them we agreed to the following. | Dev Team expressed concerns to me about what SAs put into wiki spec. To address them we agreed to the following. | ||
| + | |||
| + | == Agreements == | ||
* '''Main role of SA''' | * '''Main role of SA''' | ||
| Line 14: | Line 16: | ||
* '''No ZUL''' | * '''No ZUL''' | ||
| - | : No zul code should be created by SA. Reasons: a) time consuming; b) UIs should be created by developers | + | : No zul code should be created by SA. Reasons: |
| + | :: a) time consuming; | ||
| + | :: b) UIs should be created by developers | ||
* '''No mock-up''' | * '''No mock-up''' | ||
: Same reasons as above | : Same reasons as above | ||
| + | |||
| + | * '''UI/functionality prototype''' | ||
| + | : a) Due to changes above UI and functionality can be presented for review AFTER it was coded on Demo server. This is replacing a mechanism of creating/presenting UI mock ups. | ||
| + | : b) in some cases UI mock ups will be used. Examples: in '''Design Ideas''' section; in pdf based proposals to Clients | ||
* '''SA Notes''' | * '''SA Notes''' | ||
| Line 28: | Line 36: | ||
* '''First things first''' | * '''First things first''' | ||
: Explain most important things first... then stop. If you have more time say more. | : Explain most important things first... then stop. If you have more time say more. | ||
| + | |||
| + | * '''Exemplary specs''' | ||
| + | : Create a list of specs that comply to the new standard. See [[#Exemplary specs]] | ||
| + | |||
| + | == Exemplary specs == | ||
| + | |||
| + | * TBD | ||
Revision as of 02:19, 19 November 2010
Contents |
To
Systems Analysts
Summary
Dev Team expressed concerns to me about what SAs put into wiki spec. To address them we agreed to the following.
Agreements
- Main role of SA
- It is in most cases to:
- receive and review Business Requirements from BA,
- point out on missing elements
- help them finalize Business Requirements
- No ZUL
- No zul code should be created by SA. Reasons:
- a) time consuming;
- b) UIs should be created by developers
- No mock-up
- Same reasons as above
- UI/functionality prototype
- a) Due to changes above UI and functionality can be presented for review AFTER it was coded on Demo server. This is replacing a mechanism of creating/presenting UI mock ups.
- b) in some cases UI mock ups will be used. Examples: in Design Ideas section; in pdf based proposals to Clients
- SA Notes
- Section "Detailed Design will be replaced" with "SA Notes"
- Related specs must be linked
- Keep it simple
- First things first
- Explain most important things first... then stop. If you have more time say more.
- Exemplary specs
- Create a list of specs that comply to the new standard. See #Exemplary specs
Exemplary specs
- TBD
