COMPARISON OF SOFTWARE DEVELOPMENT METHODS

Get Complete Project Material File(s) Now! »

Comparison of Software Development Methods

As discussed earlier, software development methods are categorized into two categories, such as Traditional and Agile software development methods. Therefore, this section examined the previous study on comparison with respect to our research focus.

Differences between Agile and Traditional Software Development

Methods

Throughout literature study of traditional and agile (section 2.2 and section 2.3), a clear difference can be made on different key features of software development methods. Underlying principle of tradition methodology is to put the developers on several phases, which are convinced by plan according to customer requirements [47]. But in area of agile methodology, development methods allow the developers to involve the customers in order to improve flexibility in changing requirements. Furthermore, developers of agile being involved to deliver the prototyping or beta version of system, and getting rapid feedback from customer in response to changing requirements.
However, project size is limitation of agile of methodology, it makes more difficult to manage team, if team size more 40 developers, then most preferable approach is to choose the traditional methodology [40].
As reported in [40], there were some drawbacks in traditional approach, such as linearity, inflexibility in changing requirement and high formal processes irrespective with size of project. Bearing this in mind, Beck [37] took these drawbacks and introduced XP that was first agile method. Additionally, comparison study in [40] argued that traditional methods are considered as time wasting including activities like documentations, writing analysis and design documents, when deliverables of project are tightly scheduled with low time efforts. In such case, when time is limited, most desired approach would be agile methodology.
A survey has been conducted on comparison study of software development methods [47]; they suggested that practisers of traditional software development methods have more satisfaction level than practisers of agile software development methods. Moreover, it clearly stated that practisers of
agile software development methods are more satisfied with their method in order to fulfil the customer desires and requirements as compare to processes of traditional methods are not fully recommended in support for customer communication.

READ MARKOV DECISION PROCESSES AND REINFORCEMENT LEARNING IN ROBOTICS

Project Characteristic

With respect to project characteristic, table [30] below identifiedthe key points in order to make choice of software development methodology.

Agile Manifesto with Agile VS Traditional

In report [49], a hot debate was held between agile and traditional practitioners in supporting to discuss agile manifesto in term of traditional practices, and how traditionalists react and reject agile principles. With first agile manifesto value “Individuals and Interaction over Process and Tools”, author strongly motivated on skills programmers and software engineers who required being involved in order to construct highly valuable software. In this particular, tools and processes are considered behind this aspect that traditional practitioners won‟t have much trouble to accept this. Even, SEI [49] has formulated People Maturity Model to support the CMM, and mostly practitioners accept that people matter.
With second agile value “Working Software over Comprehensive Documentations”, again author prefers first option by stating that traditional approach based on document-driven life cycle, and increased number of documents over the years rather than focus should be on end product. Traditionalists likely to measure progress of software by adding extensive documents to management in order to show up development activities, even, they considered this as least activities and avoid the code units. Author argued that RS document and user manual are matter but delivered product is most important concern of agile practitioners. [49]

1 Introduction
1.1 BACKGROUND
1.2 PURPOSE/OBJECTIVES
1.3 LIMITATIONS
1.4 THESIS OUTLINE.
2 Theoretical Background
2.1 METHOD
2.2 TRADITIONAL SOFTWARE DEVELOPMENT METHODS
2.3 AGILE SOFTWARE DEVELOPMENT METHODS
2.4 COMPARISON OF SOFTWARE DEVELOPMENT METHODS
3 Methods
3.1 RESEARCH METHODS
3.2 DATA COLLECTION TECHNIQUES .
3.3 FINDING POPULATION
3.4 EVALUATION METHODS
4 Results and Analysis
4.1 RESULTS
4.2 SURVEY ANALYSIS
5 Conclusion and Discussion