StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>At work we use the ICONIX process. It is a subset of AGILE techniques and it is behavioural requirements driven. The ICONIX process aims to be as low-celebration as possible having as little documentation as possible - in order to allow you to easily keep it up-to-date (this is a big difference from other AGILE processes, for example XP practitioners often do not seem to maintain documentation up-to-date after the 1st draft claiming that their code <em>is</em> the documentation). </p> <p>Here's a practical overview of the process:</p> <ol> <li>Quick Draft of Functional Requirements</li> <li>Quick Definition of a Domain Model</li> <li>Model Use Cases on the base of previous steps</li> <li>Optional - Draw a throw-away robustness diagram for each use case, just to understand relations between your classes</li> <li>Draw a Sequence Diagram for each use case</li> <li>Model your test-cases on the use cases</li> <li>Implement </li> <li>Test</li> </ol> <p>At each step you review your work as a whole updating your domain model (it's impossible to get it right first time) and adding comments on your use cases. By the end of step 5) you end up with ready-to-implement classes and logic with just little documentation to maintain if you re-factor or change anything:</p> <ul> <li>Use case diagram</li> <li>Sequence Diagram for each use case</li> <li>Test case diagram (or test plan)</li> </ul> <p>If you need to add a feature, you add a new use case and follow the whole process.</p> <p>Resources:</p> <p><a href="http://iconixprocess.com/" rel="noreferrer">Iconix process website</a></p> <p><a href="http://www.iconixsw.com/" rel="noreferrer">Iconix Software Engineering website</a></p> <p>Books References:</p> <p><a href="http://rads.stackoverflow.com/amzn/click/1590594649" rel="noreferrer">AGILE Development with ICONIX Process</a></p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload