Evaluating software engineering methods and tools: part 9: quantitative case study methodology
This article is the first of three articles describing how to undertake a quantitative case study based on work done as part of the DESMET project [1], [2]. In the context of methods and tool evaluations, case studies are a means of evaluating methods ...
REFSQ'97 workshop summary
The REFSQ (Requirements Engineering: Foundation for Software Quality) 1997 workshop was held in conjunction with CAiSE'97 in Barcelona, Spain on June 16th and 17th, 1997. It was organised by Eric Dubois, Andreas L. Opdahl and Klaus Pohl. In this ...
A framework for encapsulating card-oriented, interactive, legacy applications
Over the last several years Lockheed Martin has invested IR&D funds to explore lowering the cost of ownership of Command and Control systems for DoD software intensive systems. Two key technologies that address this issue are developing software ...
Making active CASE tools—toward the next generation CASE tools
In CASE field, there is a long-standing topic, i.e. the reason that CASE tools seem to be dearly bought but sparsely used. Based on our practical experience of making and using CASE tools, we point out the reason is that today's CASE tools are actually ...
Overcoming communication obstacles in user-analyst interaction for functional requirements elicitation
The importance of requirement engineering in the software development process has been widely recognised by the scientific community. One of the major error sources that arise in this phase is represented by ineffectual communication between users and ...
Integration of complexity metrics with the use of decision trees
We would like to present the use of the decision tree approach in the integration of various complexity metrics on the example of distinguishing between random and ordinary programs. Following our proposition that randomness indicates meaningless we can ...
Generalization of leaner object-oriented slicing
The Leaner Object-Oriented Slicing technique in [2], albeit effective in providing further code reduction from an object-oriented slice, fails to handle an object-oriented slice with multiple inheritance nets. That is, an object-oriented slice in a tree ...
What's wrong with software engineering research methodology
In a recent conference, there was a panel session on whether Software Engineering is really engineering. The debate was interesting but inconclusive, not because the panelists disagreed on the state of the arts of software engineering, but on the ...
Interacting with Object-Oriented Program Slicing
Object-Oriented Program Slicing was introduced by Law and Maguire [1,2]. On the basis of Object-Oriented Program Slicing, C++ Object-Oriented Program Slicer [C++_OOPS] was developed to assist programmers locate program faults. Technical investigation of ...
Preliminary design use cases: combining use cases and event response lists for reuse and legacy system enhancement
This report describes an approach to combining Use Cases with elements from Event Response Lists to help improve requirements understanding. The format suggested for the combination, called the Preliminary Design Use Cas, proves particularly effective ...
Holistic design of a programming system
The different stages of the prevailing software development model involve the use of software development tools and methods that are usually based on different paradigms. The mismatch between the different levels of this hierarchical process is often a ...
Partnering for reuse
Software Reuse is a business solution to the increasing demand for software over supply. However there remains little investment in software reuse despite the availability of return-on-investment models to show the cost-benefits, organisational models ...
Two-dimensional software development model combining object-oriented method with formal method
Most of current software development models are linear, one-dimensional model. On the basis of the analysis of the current models, this paper provides a two-dimensional software development model that combines object-oriented method with formal method. ...
Integrating the understanding of quality in requirements specification and conceptual modeling
The notion of quality of information system models and other conceptual models is not well understood. However, recent quality frameworks have tried to take a more systematic approach. We have earlier developed a framework for understanding and ...
The UML rules
The Unified Modelling Language (UML), version 1.0, developed in order to standardise different object oriented development practices, offers a general way of representing technical, business and software models through the structure and dynamics of the ...
Software agents and intelligent object fusion
Techniques for modular software design are presented applying software agents. The conceptual designs are domain independent and make use of specific domain aspects applying Multiagent AI. The stages of conceptualization, design and implementation are ...
Viewpoint-centred reuse: bridging the gap between reusability and the needs of the reuser
The "Reuse without Reusers" SyndromeThe problems of low productivity, late delivery and poor software quality are, unfortunately, characteristic of the software industry (Horowitz and Munson 1989). Increasingly, software developers are looking towards ...
A note on state modeling through inheritance
How to achieve the state modeling through inheritance has been considered as an important issue in object-oriented modeling. In this paper, an approach called Focus of Attention is proposed to make the state modeling easier by constructing state ...