Reusable software component life cycle

In order to decrease the time and effort of the software development process and increase the quality of the software product significantly, software engineering required new technologies. Nowadays, most software engineering design is based on reuse of existing system or components. Also, it is become a main development approach for business and commercial systems. The concept of reusability is widely used in order to reduce cost, effort, and time of software development. Reusability also increases the productivity, maintainability, portability, and reliability of the software products. That is the reusable software components are evaluated several times in other systems before. The problems faced by software engineers is not lack of reuse, but lack of widespread, systematic reuse. They know how to do it, but they do it informally. Therefore, strong attention must be given to this concept. This study aims to propose a systematic framework considers the reusability through software life cycle from two sides, build-for-reuse and build-by-reuse. Furthermore, the repository of reusable software components is considered, and the evaluation criteria from both sides are proposed. Finally, an empirical validation is conducted by apply the developed framework on a case study

ON THE NEED FOR TOOLS TO SUPPORT SEARCH IN SOFTWARE REUSE: A Perspective Paper Presented to Seer Technologies, Inc.

Software reuse in the presence of a repository and object-based CASE tool is likely to be "biased." Prior research (Banker, Kauffman and Zweig, 1991) showed that a developer will be: most likely to reuse her own objects; somewhat less likely to reuse objects developed by her project team members; and, even less likely to reuse objects stored in the repository, but developed elsewhere in the corporation. This paper characterizes this problem in terms of three familiarity biases: personal bias, project bias and time bias. In the presence of these biases it is appropriate to deploy tools that support the search for software reuse, so that they may be overcome. However, the tools that are chosen or created for this purpose must adequately treat the technical and cognitive fundamentals for individual developers, and recognize the organizational and economic perspectives of a firm that wishes to maximize the business value of its software development activities.Information Systems Working Papers Serie

SUPPORTING SEARCH FOR REUSABLE SOFTWARE OBJECTS

Software reuse in the presence of a repository and object-based CASE tool is likely to be "biased" Prior research has shown that a developer will be: (1) most likely to reuse her own objects; (2) somewhat less likely to reuse objects developed by her project team members; and, (3) even less likely to reuse objects stored in the repository, but developed elsewhere in the corporation. These biases can result in sub-optimal levels of software reuse. In the presence of such biases it is appropriate to deploy tools that support the search for software reuse, so that developers find it easier to reuse software objects authored by developers other than themselves or project team members. However; the tools that are chosen or created for this purpose must adequately treat the technical and cognitive fundamentals of the problem for individual developers, and recognize the organizational and economic perspectives of a firm that wishes to maximize the business value of its software development activities. In this paper we present a two-stage descriptive model that represents the search process for reusable software objects. We evaluate appropriate technologies, propose a technical solution to the problem of searching for reusable objects, and demonstrate its feasibility via a prototype implementation. The technical tool combines an automated classifier and a hypertext system. We describe an architecture to automatically create hypertext networks based on the classification schema. We illustrate our architecture using a classification of software objects obtained through structured interviews with software developers.Information Systems Working Papers Serie

THE BUSINESS CASE FOR AUTOMATING SOFTWARE METRICS IN OBJECT-ORIENTED COMPUTER AIDED SOFTWARE ENGINEERING ENVIRONMENTS

This paper makes the business case for automating the collection of software metrics for gauging development performance in integrated computer aided software engineering (CASE) environments that are characterized by an object-oriented development methodology and a centralized repository. The automation of function point analysis is discussed in the context of such an integrated CASE environment (ICE). We also discuss new metrics that describe three different dimensions of code reuse -- leverage, value and classification -- and examine the p,ossibility of utilizing objects as means to estimate software development labor and measure productivity. We argue that the automated collection of these software metrics opens up new avenues for refining the management of software development projects and controlling stra-egic costs.Information Systems Working Papers Serie

Requirements and Tools for Variability Management

Explicit and software-supported Business Process Management has become the core infrastructure of any medium and large organization that has a need to be efficient and effective. The number of processes of a single organization can be very high, furthermore, they might be very similar, be in need of momentary change, or evolve frequently. If the ad-hoc adaptation and customization of processes is currently the dominant way, it clearly is not the best. In fact, providing tools for supporting the explicit management of variation in processes (due to customization or evolution needs) has a profound impact on the overall life-cycle of processes in organizations. Additionally, with the increasing adoption of Service-Oriented Architectures, the infrastructure to support automatic reconfiguration and adaptation of business process is solid. In this paper, after defining variability in business process management, we consider the requirements for explicit variation handling for (service based) business process systems. eGovernment serves as an illustrative example of reuse. In this case study, all local municipalities need to implement the same general legal process while adapting it to the local business practices and IT infrastructure needs. Finally, an evaluation of existing tools for explicit variability management is provided with respect to the requirements identified.

A Study on Reuse-based Requirements Engineering by Utilizing Knowledge Pattern

Software development has become an essential part of many industries over the past decade. The use of software has become an essential element for the organization to support its operation and business. Some software has certain features in common, which allow its requirements to be used repetitively in the requirement engineering phase. This paper presents a study on knowledge patterns for reuse-based requirements engineering. Reuse-based requirements engineering is saving the effort to conduct the process and, at the same time maintaining the standard since reused requirements come with its properties as well.  Software development is an iterative process itself and so does the knowledge it holds in every iteration. When analysts perform many iterations of elicitation processes, it is often the case that a significant amount of requirements is recurring and similar software system will likely benefit from them. This research adopted a literature review method to investigate and to present current studies on knowledge pattern for the purpose of reuse. Knowledge reuse by utilizing knowledge pattern is becoming a significant method in software requirements engineering as it safes the effort of developing requirements from scratch. The study found that a specific pattern is required to develop good requirements specification. A proposed prototype to deploy reuse-based requirements engineering is also presented and evaluated. Experts’ judgment method is used for evaluation by adapting the Technology Acceptance Model (TAM). The results showed that reusing knowledge pattern expedites the requirements elicitation process and improves the requirements quality.

Transformation From Business Process Models To Process Ontology: A Case Study

Business process modeling is utilized by organizations for defining and reengineering their business processes. On the other hand, ontologies are developed to strengthen shared understanding between people, organizations and software systems and ease reuse. From knowledge management point of view, both are efficient tools for creating knowledge. A tool supported transformation from process models to ontology could enhance the benefits gained from both and increase development efficiency and consistency. This study aims to demonstrate such an automated transformation on a real case. Within the study, a case study is performed to enable this transformation manually from business process models defined with eEPC language to a process ontology and an algorithm is designed and implemented for automated transformation

An Exploratory Case Study of the Benefits of Business Rules Management Systems

Business rules engines and business rule management systems (BRMS) are gaining popularity especially in large, complex, and real-time business environments. In essence, the business rules approach represents a new paradigm for compartmentalizing the formalization of business policies and rules as a separate component from application code. Given that this phenomenon has not yet been empirically investigated from a research perspective, we report on an exploratory case study undertaken to better understand the impacts of the business rules approach on activities throughout the software development lifecycle at a large Fortune 500 corporation. Our study integrates theoretical notions from the literature on knowledge reuse and systems theory with four constructs – centralization, standardization, externalization and structuration – to categorize the benefits arising from BRMS. Our results suggest that the application of the business rules approach has the potential to facilitate information systems development activities at all stages of the software development lifecycle