On building with reusable software: Democratization of information systems automation through software reuse

1996 ◽  
Vol 6 (3) ◽  
pp. 203-216
Author(s):  
Wita Wojtkowski
Author(s):  
George Lepouras ◽  
Anya Soriropoulou ◽  
Dimitrios Theotokis ◽  
Costas Vassilakis

Real-world information, knowledge, and procedures after which information systems are modeled are generally of dynamic nature and subject to changes, due to the emergence of new requirements or revisions to initial specifications. E-government information systems (eGIS) present a higher degree of volatility in their environment, since requirement changes may stem from multiple sources, including legislation changes, organizational reforms, end-user needs, interoperability, and distribution concerns, etc. (Jansen, 2004; Prisma Project, 2002; Scholl, Klischewski, & Moon, 2005. To this end, the design and implementation of eGIS must adhere to paradigms and practices that facilitate the accommodation of changes to the eGIS as they occur in the real world. Object-oriented technologies have been extensively used to encapsulate reusable, tailorable software architectures as a collection of collaborating, extensible object classes; however the inherent conflict between software reuse and tailorability has inhibited the development of frameworks and models that would effectively support all requirements exposed by eGIS (Demeyer, Meijler, Nierstrasz, & Steyaert, 1997). The lack of such frameworks has lead to eGIS that cannot easily be adapted to the new requirements, mainly because only the predetermined specifications are taken into account and design decisions are fixed during the implementation phase (Stamoulis, Theotokis, Martakos, & Gyftodimos, 2003). A key issue to a viable solution eGIS modeling is the provision of the ability to multiple public authorities (PAs) to represent different aspects of the same real-world entity, while maintaining at the same time information consistency. Aspect representation is not only limited to data elements that describe the particular entity, but may extend to behavior alterations, when the entity is examined in different contexts. For example, an entity representing the citizen is expected to assume the behavior of beneficiary, when used in the context of the Ministry of Social Security, and the behavior of taxpayer, when accessed from the Ministry of Finance’s eGIS. Distinct behaviors may rely on different data representations and/or respond differently in requests. In this work we present a role-based modeling and implementation framework, which can be used for building eGIS and we argue that this model promotes the tailorability and maintainability of eGIS.


2013 ◽  
Vol 4 (3) ◽  
pp. 807-812
Author(s):  
Jagmeet Kaur ◽  
Dr. Dheerendra Singh

A great deal of research over the past several years has been devoted to the development of methodologies to create reusable software components and component libraries. But the issue of how to find the contribution of the factor towards the successfulness of the reuse program is still in the naïve stage and very less work is done on the modeling of the success of the reuse. The success and failure factors are the key factors that predict the successful reuse of software. An algorithm has been proposed in which the inputs can be given to K-Means Clustering system in form of tuned values of the Data Factors and the developed model shows the high precision results , which describe the success of software reuse.


Author(s):  
SANJEEV MANCHANDA ◽  
S. B. SINGH ◽  
MAYANK DAVE

The aim of the present research work is to develop an information system development process and a model for the development of new generation information systems. New age information systems are those information systems that are capable of fulfilling the demand of highly dynamic information requirements derived from the competitive environments of business organizations and support controlling the complexity involved in their maintenance and software configuration management. Present research work analyzes the theoretical, financial, technical and practical problems related to the information system development, maintenance and change management to propose an appropriate system development process and a model for the development as well as maintenance of information systems with maximum software reuse. The proposed system development process and model provide inherent support to the business organizations in having total control over information system development, maintenance and software configuration management.


Author(s):  
Chintakindi Srinivas ◽  
Dr.C.V.Guru Rao

Software reuse is the process of creating software systems from existing software rather than building them from scratch. The goal is the use of reusable components as building blocks in new systems with modifications occurring in a controlled way. The reuse of software components is the key to improve productivity and quality levels in software engineering. One of the most promising approaches to reduce costs and improve reliability is component-based development, which aims to allow new applications to be assembled from prefabricated parts rather than coded from scratch. Software reuse involves building software that is reusable by design and building with reusable software. Software reuse includes reusing both the products of previous software projects and the processes deployed to produce them, leading to a wide spectrum of reuse approaches, from the building blocks (reusing products) approach, on one hand to the generative or reusable processor (reusing processes), on the other.


Author(s):  
JUN-JANG JENG ◽  
BETTY H. C. CHENG

Reusing software may greatly increase the productivity of software engineers and improve the quality of developed software. Software component libraries have been suggested as a means for facilitating reuse. A major difficulty in designing software libraries is in the selection of a component representation that will facilitate the classification and the retrieval processes. Using formal specifications to represent software components facilitates the determination of reusable software because they more precisely characterize the functionality of the software, and the well-defined syntax makes processing amenable to automation. This paper presents an approach, based on formal methods, to the classification, organization and retrieval of reusable software components. From a set of formal specifications, a two-tiered hierarchy of software components is constructed. The formal specifications represent software that has been implemented and verified for correctness. The lower-level hierarchy is created by a subsumption test algorithm that determines whether one component is more general than another; this level facilitates the application of automated logical reasoning techniques for a fine-grained, exact determination of reusable candidates. The higher-level hierarchy provides a coarse-grained determination of reusable candidates and is constructed by applying a hierarchical clustering algorithm to the most general components from the lower-level hierarchy. The hierarchical organization of the software component specifications provides a means for storing, browsing, and retrieving reusable components that is amenable to automation. In addition, the formal specifications facilitate the verification process that proves a given software component correctly satisfies the current problem. A prototype browser that provides a graphical framework for the classification and retrieval process is described.


1992 ◽  
Vol 01 (03) ◽  
pp. 351-367
Author(s):  
ROBERT G. REYNOLDS ◽  
ELENA ZANNONI

Biggerstaff and Richter suggest that there are four fundamental subtasks associated with operationalizing the reuse process [1]. They are finding reusable components, understanding these components, modifying these components, and composing components. Each of these sub-problems can be re-expressed as a knowledge acquisition sub-problem relative to producing a new representation for the components that make them more suitable for future reuse. In this paper, we express the first two subtasks for the software reuse activity, as described by Biggerstaff and Richter, as a problem in Machine Learning. From this perspective, the goal of software reuse is to learn to recognize reusable software in terms of code structure, run-time behavior, and functional specification. The Partial Metrics (PM) System supports the acquisition of reusable software at three different levels of granularity: the system level, the procedural level, and the code segment level. Here, we describe how the system extracts procedural knowledge from an example Pascal software system that satisfies a set of structural, behavioral, and functional constraints. These constraints are extracted from a set of positive and negative examples using inductive learning techniques. The constraints are expressed quantitatively in terms of various quality models and metrics. The general characteristics of learned constraints that were extracted from a variety of applications libraries are discussed.


The source code of an application paves way for a quality software product. Quality software in-turn helps in imposing software reuse. In this paper, pieces of similar codes also known as code clones or code duplications are considered as reusable software components. In general code clones are considered harmful in software engineering practice. They are considered to degrade the quality of software. Code clones are detected and removed without further processing. In this paper, a token- based CodeClone reuse method is proposed to detect type1 and type-4 clones. Positive effects of clones are analyzed and beneficial clones are extracted from the cluster of clones detected. The proposed method aids in the art of developing software thereby enforcing the concept of software reuse. The working principle of the proposed method is implemented using open source software as inputs. Beneficial clones are further stored in a database for future use. Clone report is generated as it assists in knowing about the clone details within a software system.


Sign in / Sign up

Export Citation Format

Share Document