Iconix Development process

In project development, what kind of development is one of the main issues for project developers to negotiate. In the light of the actual situation of project requirements and development, our team analyzed the following three development processes:

1. RUP: An object-oriented, web-based development process, a framework for process components, methodologies, and technologies. The process structure is clear, the whole development is built on the basis of iteration, the iterative cycle is fixed, the management of requirement and control is clear, and the project risk can be flexibly addressed. However, the development process is expensive.

2. SCRUM: Re-auditing and sequencing requirements in each iteration cycle. Emphasis on communication, emphasis on product re-documentation, development risk control at a lower level. The requirements for project team members are high.

3. Iconix: In between, similar to Rup, Iconix is a use-case driven development process, but less expensive and more compact than RUP. But unlike scrum, it rejects the analysis and design process. Iconix uses a subset of UML to express the entire development process.

Combined with the above analysis, considering our project time only two months, the workload is larger, the use of Iconix process is more suitable.

The following is a detailed introduction to the Iconix development process:

Iconix is based on the idea of extreme programming, which advocates the construction of domain models and user models at the beginning of a project, where the use case model drives the entire dynamic model, while the domain model drives the entire static model. Therefore, the whole system is driven directly or indirectly by use cases. This means that the architecture and design of the software are inferred by analyzing the usage scenarios.

Development process:

1. Domain Modeling

Domain modeling is the foundation of the static part of a UML model. When the domain model is established, the main conceptual objects and the relationships between the systems are first determined.

2. Use case modeling

Design the system from the user's point of view to determine the use case. The basic format for use cases is "noun-verb-noun". Note that when you write a use case, you write using the scene text instead of the functional requirements. Scenario to describe the user's actions and the response the system makes. The text will be placed on the left side of the sequence diagram as a specification of the behavior of the system run phase.

3. Demand review and robustness analysis

Identify the customer, the development team, in the existing use cases, domain models and prototype elements to achieve a basic agreement.

The robustness graph is plotted for robustness analysis, the case text is examined, and the participants, boundary objects, entity objects and controllers are drawn according to the sentence description. Analyze the existing problems, modify the use case text and the static model.

Add some key attributes to the class diagram.

4. Detailed design-timing diagram

Draw a time series diagram and assign the identified functions, methods, and so on to the object.

The drawing steps are:

• Leave the use case text on the left.
• Add entity objects in the robustness graph.
• Joins boundary objects and participants in the robustness graph.
• Assigns a method to a class. Converts a controller in a robustness diagram to a method and a message that performs the desired behavior.

5. Start programming

Based on the above results, the development team is programmed.

Iconix Development process