What ever happened to structured analysis?
Datamation
A hierarchical and functional software process description and its enaction
ICSE '89 Proceedings of the 11th international conference on Software engineering
SPADE: an environment for software process analysis, design, and enactment
Software process modelling and technology
The criticality of modeling formalisms in software design method comparison: experience report
ICSE '97 Proceedings of the 19th international conference on Software engineering
Reinventing methodology: who reads it and why?
Communications of the ACM
Software Engineering: An Engineering Approach
Software Engineering: An Engineering Approach
Software Engineering: A Practitioner's Approach
Software Engineering: A Practitioner's Approach
Diffusing Software-Engineering Methods
IEEE Software
Experience with an Approach to Comparing Software Design Methodologies
IEEE Transactions on Software Engineering
Software Engineering (7th Edition)
Software Engineering (7th Edition)
Proceedings of the special interest group on management information system's 47th annual conference on Computer personnel research
Hi-index | 0.00 |
During the last few decades a number of software development models have been proposed and discussed within the Software Engineering community. Examples of such models are Waterfall, Spiral, V Model, and Prototyping. The introduction of different models and their subsequent adoption by practitioners motivates the need to compare them. Comparisons are defined to i) find the best fit for a particular software development project; ii) improve the models themselves; iii) facilitate dissemination and education on development best practices and iv) find relevant information to define new models. However, existing comparisons are often largely based on the experience of practitioners and the intuitive understandings of the authors. Consequently, they tend to be subjective and inaccurate. The lack of a systematic way of comparing development models reduces understanding of such models and their overall acceptance by practitioners. We propose a systematic way of comparing software development models based on a formal technique originally proposed to compare design methodologies. The use of one well-defined formal technique provides a more consistent and efficient way to compare software development models and could be used to fine-tune the software development process of a software development organization. We present the results of a case study conducted to compare two well known and largely used development models. Results of such comparisons could be used by Information Technology educators to show their students the advantages and disadvantages of each model and instruct them on how and when to apply each model or variations of them.