Description of a process development methodology

The creation of a development process is a challenging task. The most-widely published process models, such as the Waterfall model, are very generic, and their application and customization to a specific problem domain requires major effort. Additionally, their refinement into fine-grained process steps demands a lot of dedicated work. There is definitely a lack of aid for the customization of processes to specific domains and projects. This article first reviews a generic framework for Requirements Engineering (RE) as well as a domain-specific framework. It then outlines a methodology and tool called (Process Development Assistant) PDA that helps the process engineer develop a process model in an iterative manner. The methodology requires as input from the developer items of major concern, constraints and priorities specific to a certain domain and a particular project. It uses mathematical definitions to generate an initial process model that is then iteratively refined using the feedback of the process designer. The PDA methodology and tool can also be used for more general systems engineering process modeling. Copyright © 2006 John Wiley & Sons, Ltd.

[1]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[2]  W. W. Royce,et al.  Managing the development of large software systems , 1970 .

[3]  Mark C. Paulk,et al.  Capability Maturity Model for Software , 2001 .

[4]  Reidar Conradi,et al.  Techniques for Process Model Evolution in EPOS , 1993, IEEE Trans. Software Eng..

[5]  Judy L. Wynekoop,et al.  System Development Methodologies: Unanswered Questions and the Research-Practice Gap , 1993, ICIS.

[6]  Colette Rolland,et al.  From conceptual modelling to requirements engineering , 2000, Ann. Softw. Eng..

[7]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[8]  Victor R. Basili,et al.  Tailoring the software process to project goals and environments , 1987, ICSE '87.

[9]  Daniela E. Damian,et al.  A Formal Knowledge Level Process Model of Requirements Engineering , 1999, IEA/AIE.

[10]  Doo-Hwan Bae,et al.  Tailoring and verifying software process , 2001, Proceedings Eighth Asia-Pacific Software Engineering Conference.

[11]  B Boehm A spiral model of software development and enhancement , 1986, SOEN.

[12]  Graham King,et al.  Software Engineering Processes: Principles and Applications , 2000 .

[13]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[14]  Ian Sommerville,et al.  Software Engineering, 6. Auflage , 2001 .

[15]  Mark C. Paulk,et al.  Capability Maturity Model for Software, Version 1.1 , 1993 .

[16]  Alan M. Davis,et al.  Software Requirements: Objects, Functions and States , 1993 .

[17]  Watts S. Humphrey The software engineering process: definition and scope , 1988, ISPW '88.

[18]  J. Michael Spivey,et al.  Understanding Z : A specification language and its formal semantics , 1985, Cambridge tracts in theoretical computer science.

[19]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[20]  W. Humphrey,et al.  Software Process Modeling: Principles Of Entity Process Models , 1989, 11th International Conference on Software Engineering.

[21]  Mark P. Ginsberg,et al.  Process Tailoring and the the Software Capability Maturity Model , 1995 .

[22]  Matthias Jarke,et al.  Telos: representing knowledge about information systems , 1990, TOIS.

[23]  Watts S. Humphrey,et al.  Software process development and enactment: concepts and definitions , 1993, [1993] Proceedings of the Second International Conference on the Software Process-Continuous Software Process Improvement.

[24]  Tom Gilb,et al.  Principles of software engineering management , 1988 .

[25]  E. Dubois,et al.  A knowledge representation language for requirements engineering , 1986, Proceedings of the IEEE.

[26]  Steve McConnell,et al.  Rapid Development: Taming Wild Software Schedules , 1996 .

[27]  Klaus Pohl,et al.  The Three Dimensions of Requirements Engineering , 1993, CAiSE.

[28]  Tsutomu Ishida,et al.  Metrics and Models in Software Quality Engineering , 1995 .

[29]  Klaus Pohl,et al.  Process-Centered Requirements Engineering , 1996 .

[30]  Thomas Magedanz,et al.  Intelligent Networks , 1996 .

[31]  Cliff B. Jones,et al.  Systematic software development using VDM , 1986, Prentice Hall International Series in Computer Science.

[32]  Khaled El Emam,et al.  Elements of Software Process Assessment & Improvement , 1999 .

[33]  M. I. Kellner,et al.  Software process modeling: a case study , 1989, [1989] Proceedings of the Twenty-Second Annual Hawaii International Conference on System Sciences. Volume II: Software Track.

[34]  Klaus Pohl,et al.  The three dimensions of requirements engineering: a framework and its applications , 1994, Inf. Syst..

[35]  Mark C. Paulk,et al.  The Capability Maturity Model , 1991 .