Software Reuse

Mobile computing empowers its users to exploit portable computation and context-aware communication, however; a mobile device lacks energy and performance to execute computation and memory intensive tasks. On the contrary, cloud computing exploits the 'pay-per-use' software and hardware services to provide virtually unlimited processing and storage resources. The unification of mobile and cloud computing as Mobile Cloud Computing (MCC) enables mobility and context awareness with computation and storage services to provide systems that are portable, yet resource sufficient. In an architectural context for MCC systems that require context-awareness, mobility and scalability, etc., there is a need to capitalise on reusable solutions – utilising patterns and best practices – to architect and develop mobile cloud software. This research aims to build and exploit a catalogue of patterns that support reusable design knowledge for architecture-based development of the MCC systems. We have discovered some patterns as generic and reusable solutions and demonstrate their usage in the context of mobile cloud systems. The proposed research aims to establish the catalogue as patterns repository – facilitating a continuous discovery and documentation of new patterns overtime that support reusable knowledge and practices to develop MCC systems.

266 Abstract—The estimation accuracy has been focused in various formal estimation models in recent research initiatives. The formal estimation models were developed to measure lines of code and function points in the software projects but most of them failed to improve accuracy in estimation. The concept of reusability in software development in estimating effort using artificial neural network is focused in this paper. Incorporation of reusability metrics in COCOMO II may yield better results. In COCOMO II it is very difficult to find the values of size parameters. A new model called COREAN has been proposed in this paper for better effort estimation accuracy and reliability. The proposed model has focused on two components of COCOMO II. First, instead of using RUSE cost driver, three new reuse cost drivers are introduced. Second, In order to reduce the project cost, three cost drivers such as PEXE, AEXE, LTEX are combined into single cost driver Personnel Experience (PLEX). Final...

Software reusability has considerable effect on software quality. Software quality increases as reuse of software components increases. But software quality cannot be improved unless it can be measured. In this paper we have derived a new approach to measure the software reusability of OO class diagram, an attribute of software quality. We have also empirically studied the approach in OO programming language C++.

The paper focuses on a CBS module of Knowledge-Based Tutoring System for Software Reuse Practices. The paper presents a public CBS using a validated Software Reuse Reference Model (SRRM). A CBS-SRRM allows the software engineer to improve reuse practice by being tutored with selected course material based on the user profile. This material is combined with actual practice based knowledge

Generic programming is an effective methodology for developing reusable software libraries. Many programming languages provide generics and have features for describing interfaces, but none completely support the idioms used in generic programming. To address this need we developed the language G. The central feature of G is the concept, a mechanism for organizing constraints on generics that is inspired by

Abstract: The gap between the demand for complex system software and the supply of this demand has widened. This distance and complexity of software design has led software engineers to find a solution to these two problems as a crisis. Due to this problem, systems have become more complex and creating software for them has become increasingly difficult due to the timely completion of the project and the project budget constraints. Reusing software as a major factor in reducing some problems Due to the software crisis, it has become increasingly important. Traditional approaches to reusing software in dealing with the software crisis are considered ineffective in practice. Over the past few years, a new approach to software reuse has attracted much attention from the industry. This approach is known as the software development product line, and software reuse has become a major achievement within the organization. Has been. Production lines in the manufacturing industry have long been used to reduce costs and increase productivity by exploiting commonalities between products.
However, the product line in practice in the software industry is a relatively new concept. Studies have shown that organizations can use this approach, significant improvements in productivity, market entry time, product quality and satisfaction. Have a customer.

An established approach to cost and risk reduction of space systems is the use of heritage systems. A heritage system is a system which is based on a proven system design. A design is a set of engineering drawings, plans, etc. which are used to manufacture a system [1]. Heritage is the degree to which a system is proven. One example for a system with a high degree of heritage would be a communication satellite where satellites with similar designs have been successfully flown over a dozen times in the same orbit. In the following, an element of a system is called “component”.  Almost all newly developed space systems to some degree rely on preexisting components. Recent examples are NASA’s Space Launch System (SLS), and the Ares V and Area I vehicles for the Constellation program. All these vehicle designs rely on components from the Space Shuttle program, such as the solid rocket boosters and the external tank. However, the use of heritage systems is not as straight forward as one might expect. According to the Governmental Accountability Office (GAO), more than 50% of NASA’s space missions encountered problems linked to heritage components [2]. Heritage components were responsible for some notable catastrophic failures, for example the Ariane 5 Flight 501, where the guidance software was carried over from Ariane 4 [3]. It was a proven piece of software. However, the software was incompatible to the new system architecture in which it operated [3]. Other failures include the Mars Observer mission, where the spacecraft bus was proven for operation in low-Earth orbit (LEO) [4]. According to the failure investigation report, the most probable cause of the failure was a leaking valve. Due to the longer storage duration compared to LEO, the previously reliable valve started to leak. Besides mission failures, the analysis of past space programs shows that the use of heritage technologies can lead to reductions in development cost and risk but can also lead to cost and schedule overruns, if not properly managed [2]. Interviews conducted with engineers from various space companies confirmed that heritage technologies are assessed ad-hoc and no systematic methodology exists. Such a methodology could be beneficial, in particular during the early stages of development, where heritage-related risks can be mitigated easier than later on.

This paper presents a framework and methodology for assessing heritage in the early stages of development.

The methodology allows for identifying heritage with respect to a new application as well as identifying areas where it is missing. Second, possible modifications to the design can be assessed in terms of their impact on the expected development schedule and cost. Lastly, a system design which fits a new application is useless, if it cannot be implemented. Therefore, the ability to assess technological capabilities for implementing a system is also vital for assessing heritage systems. The methodology is applied to a case study which compares the Saturn V with SLS variants.

8th International Conference on Software Engineering (SOFT 2022) will provide an excellent international forum for sharing knowledge and results in theory, methodology and applications of Software Engineering and Applications. The goal of this Conference is to bring together researchers and practitioners from academia and industry to focus on understanding Modern software engineering concepts and establishing new collaborations in these areas.

No seguimento dum artigo anterior acerca da análise de regressão não-linear (simples) utilizando a ferramenta Solver® do Excel® (Esteves, 2010) propõe-se neste artigo a apresentação do R, uma linguagem de programação e um ambiente para computação estatística e gráfica, através da sua aplicação na “descrição” de relações estatísticas (não-lineares) entre variáveis.

Las experiencias de la industria en reusabilidad del software, demuestran que esta no depende específicamente de aspectos tecnológicos sino de aquellos organizativos y de motivación. No obstante las tecnologías pueden ayudar al respecto. Se describe como la orientación a objetos
contribuye en los diferentes niveles de reutilización: bibliotecas de clases, patrones de diseño y
arquitecturas.

Current software cost estimation models, such as the 1981 Constructive Cost Model (COCOMO) for software cost estimation and its 1987 Ada COCOMO update, have been experiencing increasing difficulties in estimating the costs of software developed to new life cycle processes and capabilities. These include non-sequential and rapid-development process models; reuse-driven approaches involving commercial off-the-shelf (COTS) packages, re-engineering, applications composition, and applications generation capabilities; object-oriented approaches supported by distributed middleware; and software process maturity initiatives. This paper summarizes research in deriving a baseline COCOMO 2.0 model tailored to these new forms of software development, including rationale for the model decisions. The major new modeling capabilities of COCOMO 2.0 are a tailorable family of software sizing models, involving Object Points, Function Points, and Source Lines of Code; nonlinear models for software reuse and re-engineering; an exponentdriver approach for modeling relative software diseconomies of scale; and several additions, deletions and updates to previous COCOMO effort-multiplier cost drivers. This model is serving as a framework for an extensive current data collection and analysis effort to further refine and calibrate the model's estimation capabilities.

This study investigated and develops a strategy for software reuse for the Constellation Program. The study team consisted of a group of multidisciplinary experts from across the NASA Centers, with collective expertise spanning the lifecycle of software engineering from research through operations and software obsolescence. The team investigated what software reuse would mean in the context of the Constellation Program, the benefits that might be earned, and the risks to be mitigated.

Reuse is one of the core principles in professional software engineering. Design patterns provide a reusable solution for common design problems. But their implementations are generally not reusable as they are often well tailored to a specific context. We introduce a concept, that facilitates the reuse of their implementations by defining an abstract design pattern definition that can be instantiated with specialized design decisions. This approach is a meta-level Builder constructing design patterns as first-class citizens. It simplifies the application of design patterns by providing a pattern library and still being able to adjust it to the concrete context .

Software maintenance can become monotonous and expensive due to ignorance and misapplication of appropriate design patterns during the early phases of design and development. To have a good and reusable system, designers and developers must be aware of large information set and many quality concerns, eg, design patterns. Systems with correct design pattern may ensure easy maintenance and evolution. However, without assistance, designing and development of software systems following certain design ...

The basic idea behind building Reusable software components is to design interchangeable parts from other industries to the software field of construction. A reuse library or component reuse repository organizes stores and manages reusable components. The biggest advantage of the building reusable software components is that it reduces the time and energy in developing any software. Frameworks provides a standard working system through which user 's main focus is on developing desired modules instead of developing lower level details. By using this facility the software developers can spend more time in developing the requirement of software, rather than preparing the tools of application development. Framework is set of reusable software program that forms the basis for an application. Frameworks help the programmers to build the application quickly .At its best code reuse is accomplished through the sharing of common classes and/or collections of functions, frameworks and procedures. This paper describes how to build the code level reusable components and how to design code level components. Finally providing coding guidelines, standards and best practices used for creating reusable code level components and guidelines and best practices for making configurable and easy to use.