1、像rup，iconix是用例驱动的但是比rup更轻量级。 iconix 仅仅使用四种diagram(用例图、健壮性图、时序图、类图)就可以把用例文本转成代码。
2、值得注意的健壮性分析图并不是uml标准的一部分。健壮性分析图架起了分析和设计的桥梁。是可以参看：http://www.agilemodeling.com/artifacts/robustnessDiagram.htm
Overview of the ICONIX Process
The ICONIX process is split up into four milestones. At each stage the work for the previous milestone is reviewed and updated.
Milestone 1: Requirements review
Before beginning the ICONIX process there needs to have been some requirements analysis done. From this analysis use cases can be identified, a domain model produced and some prototype GUIs made.
在需求审核阶段，产生了use case text,use case， domain model ,prototype guis 等。
Milestone 2: Preliminary Design Review
Once use cases have been identified, text can be written describing how the user and system will interact. A robustness analysis is performed to find potential errors in the use case text, and the domain model is updated accordingly. The use case text is important for identifying how the users will interact with the intended system. They also provide the developer with something to show the Customer and verify that the results of the requirements analysis were correct.
画出健壮性分析图，更新第一阶段的内容。
Milestone 3: Detailed Design Review
During this stage of the ICONIX process the domain model and use case text from milestone 2 are used to design the system being built. A class diagram is produced from the domain model and the use case text is used to make sequence diagrams.
画出顺序图和类图。
Milestone 4: Deployment
Unit tests are written to verify the system will match up to the use case text, and sequence diagrams. Finally code is written using the class and sequence diagrams as a guide.
ICONIX过程总览--ICONIX过程的特点
ICONIX过程是一种以最少步骤实现从用例到代码的OOAD[object-oriented analysis and design]方法学，开覆盖了软件过程中所有关键的环节。
ICONIX过程使用了一个最小的UML核心子集实现用例驱劢的OO设计。（传说中的20%）
本方法将健壮性分析[robustness analysis]作为从需求到设计的重要过渡步骤，这是其它软件过程方法中几乎没有或忽视的。
ICONIX过程的最主要特点是有健壮性分析的过程，它是连接需求和设计的桥梁。健壮性分析可以完善用例分析描述，使其更加清晰，
ICONIX主要分为四个阶段: 需求分析阶段、初步设计阶段、详细设计阶段、部署阶段。
ICONIX过程总览--ICONIX过程值得掌插的理由
1.只使用4个UML图（用例图、健壮性图、时序图、类图）完成所有工作；
2.在不同阶段便于迭代和跟踪；
3.形成清晰、完善的用例，使需求满足用户，使设计正确指导开发人员；
4.在敏捷开发中同样适用；
5.经过上百真实项目的验证；
