Book ChapterDOI
Directions in Software Process Research
H. Dieter Rombach,Martin Verlage +1 more
Reads0
Chats0
TLDR
This paper motivates the need for explicit process models, surveys existing languages to model processes, discusses tools to support model usage, and proposes a research agenda for future software process research.Abstract:
Developing and maintaining software systems involves a variety of highly interrelated activities The discipline of software engineering studies processes of both product engineering and process engineering Product engineering aims at developing software products of high quality at reasonable cost Process engineering in contrast aims at choosing those product engineering processes appropriate for a given set of project goals and characteristics as well as improving the existing knowledge about those processes Explicit models of both types of processes help a software development organization to gain competitive advantage This paper motivates the need for explicit process models, surveys existing languages to model processes, discusses tools to support model usage, and proposes a research agenda for future software process researchread more
Citations
More filters
Posted Content
Out of the Crisis
TL;DR: Deming's theory of management based on the 14 Points for Management is described in Out of the Crisis, originally published in 1982 as mentioned in this paper, where he explains the principles of management transformation and how to apply them.
Journal ArticleDOI
Version models for software configuration management
TL;DR: This article provides an overview and classification of different versioning paradigms and defines and relates fundamental concepts such as revisions, variants, configurations, and changes and focuses on intensional versioning.
Book
An Integrated Approach to Software Engineering
TL;DR: Details the different activities of software development with a case-study approach whereby a project is developed through the course of the book The sequence of chapters is essentially the same as the sequence of activities performed during a typical software project.
Dissertation
Interactive Process Models
TL;DR: The next generation of business process systems will be built to automate routine procedures, with well-understood domains, repetitive processes, clear organisational roles, and an established terminol role.
Journal ArticleDOI
Knowledge-based techniques to increase the flexibility of workflow management
TL;DR: This paper describes how knowledge-based techniques can be used to overcome problems of workflow management in engineering applications using explicit process and product models as a basis for a workflow interpreter, resulting in increased flexibility of project coordination and enactment.
References
More filters
Journal ArticleDOI
Implementing faceted classification for software reuse
TL;DR: The conclusions of the experience are: reuse library technology is available, it is transferable, and it definitely has a positive financial impact on the organization implementing it.
Journal ArticleDOI
Iterative enhancement: A practical technique for software development
TL;DR: The development and quantitative analysis of a production compiler for the language SIMPL-T is used to demonstrate that the application of iterative enhancement to software development is practical and efficient, encourages the generation of an easily modifiable product, and facilities reliability.
Journal ArticleDOI
Prospects for an engineering discipline of software
TL;DR: Five basic steps that the software engineering profession must take to become a true engineering discipline are described, covering the nature of expertise, recognizing different ways to get information, encouraging routine practice, expecting professional specializations, and improving the coupling between science and commercial practice.
Journal ArticleDOI
Software process improvement at Hughes Aircraft
TL;DR: The authors outline the assessment method used, the findings and recommendations from the initial assessment, the actions taken by Hughes, the lessons learned, and the business and product consequences.