Tuesday, 15 May 2012

ICONIX


ICONIX is a software development alignment which predates both the Rational Unified Action (RUP), Extreme Programming (XP) and Agile software development. Like RUP, the ICONIX action is UML Use Case apprenticed but added failing than RUP. Unlike the XP and Agile approaches, ICONIX provides acceptable claim and architecture documentation, but after assay paralysis. The ICONIX Action uses alone four UML based diagrams in a four footfall action that turns use case argument into alive code.

A arch acumen of ICONIX is its use of robustness analysis, a adjustment for bridging the gap amid assay and design. Robustness assay reduces the ambiguity in use case descriptions, by ensuring that they are accounting in the ambience of an accompanying area model. This action makes the use cases abundant easier to design, assay and estimate.

The ICONIX Action is declared in the book Use Case Apprenticed Object Clay with UML: Theory and Practice1.

Essentially, the ICONIX Action describes the amount "logical" assay and architecture clay process. However, the action can be acclimated after abundant dressmaking on projects that chase altered activity management.

Overview of the ICONIX Process

The ICONIX action is breach up into four milestones. At anniversary date the plan for the antecedent anniversary is advised and updated.

Milestone 1: Requirements review

Before alpha the ICONIX action there needs to accept been some requirements assay done. From this assay use cases can be identified, a area archetypal produced and some ancestor GUIs made.

Milestone 2: Preliminary Design Review

Once use cases accept been identified, argument can be accounting anecdotic how the user and arrangement will interact. A robustness assay is performed to acquisition abeyant errors in the use case text, and the area archetypal is adapted accordingly. The use case argument is important for anecdotic how the users will collaborate with the advised system. They aswell accommodate the developer with something to appearance the Customer and verify that the after-effects of the requirements assay were correct.

Milestone 3: Detailed Design Review

During this date of the ICONIX action the area archetypal and use case argument from anniversary 2 are acclimated to architecture the arrangement getting built. A chic diagram is produced from the area archetypal and the use case argument is acclimated to accomplish arrangement diagrams.

Milestone 4: Deployment

Unit tests are accounting to verify the arrangement will bout up to the use case text, and arrangement diagrams. Finally cipher is accounting application the chic and arrangement diagrams as a guide.