Rational Unified Process (RUP)

The unified process is framework for object oriented models. This model is also called as Rational Unified Process Model (RUP). It is proposed by Ivar Jacobson Grady Bootch and James Rumbaugh. This model is iterative and incremental by nature. Let us discuss various phases of unified process.

There are 5 phases of unified process model and those are-

1.   Inception – In this phase there are two major activities that are conducted – Communication and Planning. By having customer communication business requirements can be identified. Then a rough architecture of the system is proposed. Using this rough architecture it then becomes easy to make a plan for the project. Use cases are created which elaborates the user scenario. Using use cases the sequence of actions can be identified. Thus use cases help to identify the scope of the project which ultimately proves to be the basis for the plan.

2.   Elaboration – Elaboration can be done using two activities – Planning and Modelling. In this phase the use cases are redefined. And architectural representation is created using five models such as use-case model, analysis model, design model, implementation model and deployment model. Thus executable baseline gets created. Then a plan is created carefully to check whether scope, risks and delivery dates are reasonable.

3.   Construction – The main activity in this phase is to make the use cases operational.  Source code is developed which implements all desired functionalities.

4.   Transition – In the transition phase Beta testing is conducted when software is delivered to the end user. User feedback report is used to remove defects from the created system. Finally software team prepares user manuals, installation guides and troubleshooting procedures.

5.   Production – In this phase mainly the maintenance activities are conducted in order to support the user in operational environment.

Inception Phase	Elaboration Phase	Construction Phase	Transition Phase
·         Initial use case model ·         Initial risk assessment ·         Project plan	·         Use case model ·         Requirements analysis model ·         Architecture model ·         Preliminary design model ·         Risk list ·         Iterative project plan ·         Preliminary user manual	·         Design model ·         Software components ·         Test plan ·         Test cases ·         User manual ·         Installation manual	·         Delivered software increments ·         Beta test report ·         User feedback report

 

Read more

Component Assembly Model

1.   Component based assembly model uses object oriented technologies. In object oriented technologies, the emphasis is on creation of classes. Classes are the entities which encapsulates data and algorithms.

2.   In component based architecture, classes (i.e. components required to build application) can be used as reusable components.

3.   Software development can be done using iterative approach.

4.   In CBD model, multiple classes can be used. These classes are basically the prepared components.

5.   The model works in following manner –

                I.      First identify all the required candidate components, i.e. classes with the help of application data and algorithms.

               II.      If these candidate components are used in previous software projects then they must be present in the library.

              III.      Such pre existing components can be extracted from the library and used for further development.

              IV.      But if the required component is not present in the library then build or create the component as per requirement.

               V.      Place this newly created component in the library. This makes one iteration of the system.

              VI.      Repeat step I to V for creating n iterations, where n denoted the number of iterations required to develop complete application.

Advantages of Component Assembly Model 

1.   This model emphasizes on reusability of software components. This reusability of component reduces the development cycle time by 70% and project cost by 84%. 

Read more