Meta Software Engineering for Information System Development Projects

Today’s software systems demand increasing tremendously for sophisticated software engineering processes. However, there are a multitude of different development and each have various advantages and disadvantages, some of which relate to the problem domain or the development context. Computer software development processes have to pass from many faces to complete the development. There are many ways to solve a single problem in software development. Sometimes, in Structural engineering, developer is not able to decide which process will suit to that particular problem or we can say that selecting a good process is a big issue in Structural Process Software engineering. The problem of selecting a good candidate method is a big issue in structural process engineering. The solution of such kind of problem can be found in the work to be done, and the task to be performed by the Operational process rather than process structure. This paper introduces the notion of process operationality and proposes ‘process architecture’ to represent this operationality. Thus, Structural Process Engineering (SPE) becomes Operational Process Engineering (OPE). Operationally close process architecture is selected, adapted, enhanced, and restricted as needed. The task of construction handles the putting together of process features and structuring the new process.

[1]  Sarah Theiss.  60 Minute Software Strategies For Accelerating The Information Systems Delivery Process , 2016 .

[2]  Michael Heym,et al.  Computer-aided methodology engineering , 1993, Inf. Softw. Technol..

[3]  Henk Sol,et al.  Information Systems Methodologies: A Framework for Understanding , 1988 .

[4]  René Börner,et al.  Applying Situational Method Engineering to the Development of Service Identification Methods , 2010, AMCIS.

[5]  Marvin V. Zelkowitz,et al.  SEL's Software Process Improvement Program , 1995, IEEE Softw..

[6]  Sjaak Brinkkemper,et al.  Situational Method Engineering for Information System Projects , 1994 .

[7]  Iris Reinhartz-Berger,et al.  Semi-Automatic Composition of Situational Methods , 2011, J. Database Manag..

[8]  John Parkinson.  60 minute software: strategies for accelerating the information systems delivery process , 1996 .

[9]  W. W. Royce,et al.  Managing the development of large software systems: concepts and techniques , 1987, ICSE '87.

[10]  M. Saeki,et al.  Comparison of four method engineering languages , 1996 .

[11]  Sjaak Brinkkemper,et al.  Method engineering: engineering of information systems development methods and tools , 1996, Inf. Softw. Technol..

[12]  Sanjiv Purba,et al.  How to manage a successful software project , 1995 .

[13]  A. F. Harmsen,et al.  Situational Method Engineering , 1997 .

[14]  Sergio Bandinelli,et al.  Modeling and Improving an Industrial Software Process , 1995, IEEE Trans. Software Eng..

[15]  Vessey Iris,et al.  APPLICATIONS-BASED METHODOLOGIES Development by Application Domain , 1994 .

[16]  Sjaak Brinkkemper,et al.  Assembly Techniques for Method Engineering , 1998, CAiSE.

[17]  Colette Rolland,et al.  Towards a Generic Model for Situational Method Engineering , 2003, CAiSE.

[18]  Tobias Bucher,et al.  Situational Method Engineering - On the Differentiation of "Context" and "Project Type" , 2007 .

[19]  Sanjiv Purba,et al.  How to manage a successful software project : methodologies, techniques, tools , 1995 .