This document discusses various techniques for software reuse including application frameworks, software product lines, and COTS product reuse. It defines each technique and compares their benefits and drawbacks. Application frameworks provide reusable structures for common functions but require custom development. Software product lines create families of related applications from shared components. COTS product reuse adapts existing commercial software through configuration or integration, reducing development costs but limiting customization. Overall, the document promotes software reuse as an important approach when feasible to accelerate development and reduce costs.

1. Software reuse
1

2. Hajira Amjad (12282)
Ayesha Nizam (12298)
Sabiha Haider(12280)
Group Members
2

3. ✔Software reuse
✔The reuse landscape
✔Application frameworks
✔Software product lines
✔COTS product reuse
Contents Covered
3

4. ✔understand the benefits and problems
of reusing software
✔understand the concept of an
application framework
✔introduced to software product lines
✔How systems can be developed by
configuring and composing off-the-
shelf application software systems
Objectives : 4

5. What is Software Reuse?
5

6. 6

7. Continued
✔Proposed more than 40 years ago
✔Since 2000 ‘development with reuse’
✔Software as a valuable asset
✔Open source movement huge reusable code base
✔Reuse-based software engineering
I. Application system reuse
II. Component reuse
III. Object and function reuse
IV. Concept reuse (a system model)
7

8. Benefits of reusing software assets:
✔Cost reduction
✔Increased dependability
✔Reduced process risk
✔Effective use of specialists
✔Standards compliance
✔Accelerated development
8

9. Problems of reusing software assets:
✔Component suitable for reuse
✔additional costs in testing (reduction in cost than anticipated)
✔Increased maintenance costs
✔Lack of tool support
✔Creating, maintaining, and using a component library
✔Finding, understanding, and adapting reusable components
9

10. Reuse software assets at organization level:
✔Part of an organization-wide reuse program (most effective)
✔Reuse program => creation of reusable assets, incorporate these assets in new software
✔Reuse an integral part of the Japanese ‘factory’ approach
10

11. The reuse landscape:
✔Techniques to support software reuse
✔Reuse is possible from simple functions to complete applications
11

12. Key factors to consider when planning reuse:
✔Development schedule for software
✔The expected software lifetime
✔The background, skills, and experience of the development team
✔The criticality of the software and its non-functional requirements
✔ The application domain
✔ The platform on which the system will run
12

13. Techniques for Reuse
✔Architectural patterns
✔Design patterns
✔Component-based development
✔Application frameworks
✔Legacy system wrapping
✔Service-oriented systems
✔Software product lines
13

14. Continued
✔COTS product reuse
✔ERP systems
✔Configurable vertical applications
✔Program libraries
✔Model-driven engineering
✔Program generators
✔Aspect-oriented software development
14

15. Application Framework
✔Object-oriented paradigm
-objects are too small
-Reimplement is preferred
✔A generic structure
-Classes, objects and components
-collaborated to provide a reuse
✔Support for generic features
✔Example: user interface framework
15

16. Further Explanation
-interface event handling
-set of widgets to construct display
✔Specific functionality may be added
✔Programming language-specific
✔Framework can incorporate other frameworks
• Classes of Framework
✔ System infrastructure frameworks
-user interfaces, communication, and compilers
16

17. Disadvantages
✔Middleware integration frameworks
-set of standards and association object classes
-support for communication and information exchange
-Examples: Microsoft.NET and enterprise java Beans
✔Enterprise application frameworks
-Specific application domains
-Example: Telecommunication and financial systems
-support development of end user applications
17

18. ✔Web application frameworks
-Recent type , very important
-support for construction of dynamic websites
-model-view-controller pattern
-Security, Dynamic web pages , database support , session management , user interaction
18

19. Software Product Line
✔ A software product line is a collection of multiple software.
✔ SPL is a set of application with a common architecture and shared components
✔ Each application is specialized to reflect different requirements
✔ The core system is designed to be configured
✔ Identification of common functionalities
19

20. Software assets
✔ As we are talking about share assets. So, it is important to know “what are software
assets?”.
✔ There are multiple software assets. Some of these software assets are mentioned here.
✔ Software Requirement
✔ Software design
✔ Software Requirement
✔ Software Prototypes
✔ Software architecture
20

21. Software Product Line Engineering (SPLE)
✔ SPLE is a software engineering paradigm,
✔ which guides organizations toward the development of products
✔ from core assets rather than the development
✔ of products one by one from scratch.
21

22. Key differences
✔Application framework rely on object oriented approach
✔ Application frameworks are focused on providing technical details rather than domain-
specific support
✔ SPL are often control application for equipemant
✔ SPL are made up of a family of related application ,owned by the same organization
22

23. COTS product reuse
✔COTS stands for commercial-off-the-shelf
✔A software system that can be adapted to the needs of different customers without
changing the source code of the system.
✔Has the potential to be reused in different environments and as part of different
applications.
✔COTS products are adapted by using built-in configuration mechanisms.
✔Widely adopted by large companies over the last 15 or so years.
23

24. Benefits of COTS product reuse
✔More rapid deployment of a reliable system may be possible.
✔It is possible to see what functionality is provided by the applications.
✔Some development risks are avoided by using existing software.
✔Technology updates may be simplified.
24

25. Problems of COTS product reuse
✔Requirements usually have to be adapted to reflect the functionality and mode of
operation of the COTS product.
✔The COTS product may be based on assumptions that are practically impossible to
change.
✔Choosing the right COTS system for an enterprise can be a difficult process.
✔The COTS product vendor controls system support and evolution.
25

26. Types of COTS product reuse
✔There are two types of COTS product reuse.
✔COTS-solution systems.
✔COTS-integrated systems.
26

27. Difference between types of COTS product reuse
COTS-solution systems COTS-integrated systems
Single product that provides the
functionality required by a customer
Several heterogeneous system products
are integrated to provide customized
functionality
Based around a generic solution and
standardized processes
Flexible solutions may be developed for
customer processes
Development focus is on system
configuration
Development focus is on system
integration
System vendor is responsible for
maintenance
System owner is responsible for
maintenance
System vendor provides the platform for
the system
System owner provides the platform for
the system
27

28. COTS-solution systems
✔COTS-solution systems are generic application systems.
✔ They may be designed to support a particular business type.
✔For example, a COTS-solution system may be produced for dentists that handles
appointments, dental records, patient recall, etc.
28

29. configuration process
29

30. COTS-integrated systems
✔COTS-integrated systems are applications that include two or more COTS products or,
sometimes, legacy application systems.
✔These systems may be composed by connecting the output of one system to the input of
another or by updating the databases used by the COTS applications.
30

31. Continued
31

32. COTS system integration problems
✔Lack of control over functionality and performance.
✔Problems with COTS system interoperability .
✔No control over system evolution.
✔Support from COTS vendors.
32

33. Conclusion
✔Since 2000 that ‘development with reuse’ has become the norm for new business
systems.
✔An obvious advantage of software reuse is that overall development costs will be
reduced.
✔However, there are costs and problems associated with reuse.
✔ We should consider all aspects of a system carefully and then decide whether to reuse
software or create new one.
33

34. 34

35. Any Questions?
35

36. Thank You
36