Reuse-oriented Model (Group 1)

Group Members:

• Siti Shahirah Sabran (01DIS17F1024)
• Nur Hidayah Zaini (01DIS17F1006)
• Siti Nurhaliza Ab Aziz (01DIS17F1025)
• Sharmeela A/P P. Gunasegaran (01DIS17F1008)
• Siti Ain Zubaidah Syeikh Ahmad Nasir (01DIS17F1007)
• Noor Fatin Najwa Saharudin (01DIS17F1005)
• Najmy Izwan Norman Wong (01DIS17F1042)
• Muhamad Aiman Marzuki (01DIS17F1048)
• Muhammad Naziruddin Mohd Ahsan (01DIS17F1053)

Reuse-oriented Model

The Reuse Oriented Model or The Reuse Oriented Development (R.O.D) is where they reuse programming or software design in previous project.

The main idea behind this concept is to reuse software to build higher quality software to make it better and answer the needs of demand.

Stages:

1.      Component analysis

Based on the requirements specification, components that implement (some part of) the specification are looked for. In the most of the cases there is no exact match and the components that may be used only provide some of the functionality required.

2.      Requirements modification

During this stage, the requirements are analysed using information about the components that have been discovered. They are then modified to reflect the available components. Where modifications are impossible, the component analysis activity may be re-entered to search for alternative solutions.

3.      System design with reuse

During this phase, the framework of the system is designed or an existing framework is reused. The architects will perform the design by taking into account the components that are reused and they will organize the framework accordingly. New pieces of software may have to be designed if reusable components are not available.

4.      Development and integration

Software that cannot be externally procured is developed, and the components and commercial-off-the-shelf (COTS) systems are integrated to create the new system. System integration, in this model, may be part of the development process rather than a separate activity.

Types of software components that can be used in a reuse-oriented process:

1.      Web services

Developed according to well-known service standards and which will become available for remote invocation.

2.      Collections of objects

Developed as a package to be integrated with a component framework such as .NET or Java EE.

3.      Standalone software systems

Configured for use in a particular environment.

Example:

1. Reuse-oriented model used in game development
   Subway Surfer runs to get coins. Meanwhile, Temple Bear Run runs to get diamonds.
   

Advantages	Disadvantages
Can save time	Can lead to unfortunate compromises
Builds on reliability of existing system	Building with future reuse in mind can slow effort, as we try to build things that are more general
Reduce cost	Not always practical in its pure form because a full performance of reusable components may not be available
Minimize the likelihood of errors or bugs making their way into the final project