A modest but practical software process modeling technique for software process improvement

2002

One of the main problems with software engineering is due to the difficulties in evaluating and improving our software processes, especially in the light of the fact that reuse depends on a process which supports it. Generally used approaches to the evaluation and improvement of software processes are based on the CMM, for example. In this paper we present a technique to improve software processes through modeling and evaluation. The presented technique is fairly easy to use, provides reasonably good results and requires only a fraction of resources required by CMM appraisals. Copyright © 2002 John Wiley & Sons, Ltd.

Use and Identification of Components in Component-Based Software Development Methods

2000

New software systems are needed ever more but to keep up with this trend software developers must learn to create quality software more efficiently. One approach is to (re-)use components as building blocks of the new software. Recently there has been more interest to create component-based software development methods to support this. In this article we first set out requirements for reuse-based software development and then evaluate three component-based methods, namely Catalysis, OMT++, and Unified Process. As a conclusion we argue that evaluated methods produce prefabricated components and that component-based means that software developers can change better components to existing syste…

Java Integrated Development Environments' Support for Reuse-Oriented Software Development

2002

Component reuse is a promising direction to develop software more efficiently and cost effectively. One part of software development is the actual programming with an integrated development environment (IDE). We studied three Java IDEs and how they support reuse-oriented software development. We derived evaluation criteria from a known reuse model. As a conclusion we suggest that current Java IDEs need to improve their support for the reuse process.

Managing a Software Development Organization with a TQM Approach for Balance in a Period of Rapid Growth

2007

Adding Domain Analysis to Software Development Method

2002

The researchers in the field of software development regard the reuse of components as one possible approach when creating quality software in less time and with fewer people. When components are used and created in the software development, one critical success factor is the use of domain analysis (DA). We report an action case study where the DA technique is first integrated into an existing software development method and then refined based on the experience of using it in a pilot project. The results indicate that our approach produces reusable components across a company-wide domain and eases the use of them in other development projects within domain.

Using Hierarchies to Adapt Domain Analysis to Software Development

2001

Software development strives toward increasing the amount and quality of the software and at the same time decreasing the costs and development time. One approach to achieve these diverse goals is the systematic software reuse (Biggerstaff and Richter, 1987). In the reuse-oriented software development the key success factor is domain analysis (DA) (Arango, 1989; Lam and McDermid, 1997; Prieto-Diaz, 1994). DA is a process through which information used in software development is identified, captured, and organized with the purpose of making it reusable when creating new systems (Prieto-Diaz, 1990). While the traditional development methods (e.g., Jaaksi et al.,1999; Jacobson et al., 1999) fo…

Improving component reuse in software development

2002

This study concerns reuse in the software development process. The focus is in the reuse of components when creating new software. The aim is to improve current software processes to adapt them to the purposes of reuse. The specific research questions are: 1) What are the specific limitations for reuse in the current component-based software development methods? 2) How should reusable components be created and used in software development? 3) How should the components that are created be documented in order to make them reusable in other development projects? The study follows the reflective systems development approach.

Suunnittelumallien käyttö ohjelmistotuotannossa

1998