Software Development Methodology - Coursework Example

Software Development Methodology Software development methodology or system development methodology is an action framework which includes all the activities involved in the production and development of an information system (Zaulkernan & Faujita, 2008). There are several kinds of software development methodologies, out of which the three which would be compared and used in this paper would be Waterfall Approach, Prototyping Approach and Rapid Application Development (Zaulkernan & Faujita, 2008). These three approaches would be separately be implemented on the project in question and then a conclusion would be drawn from the comparison of all of these approaches which would lead to the methodology that is the most befitting to the project in question. Project The project is the development of an electronic library for a client by the company Top Quality Tech Solutions, which is modifiable. The library needs to have a database of electronic documents which the client can change, copy and return to the library. There are several models which can be used for the development if this software, three methods would be discussed along with their pros and cons and their application would be discussed below. Waterfall Model This kind of model uses a sequential arrangement of the steps of software development. It uses top-down approach, in which the project is started from the base and then built upon (Tsui, 2010). This is the model which is already in use by Top Quality Tech Solutions and has proved to be a successful model for the development of the two projects, thus it would be a natural progression if the model is again used for the current project. The model if used in the development of the software library would have positive results because this is the simplest kind of software development methodology out there; it runs on basic common sense and uses orthodox ways to develop the software which would be beneficial in developing the electronic library as it does not involve very complex programming or development. The steps which are involved in the model are: When this model is applied to the electronic library project, the requirements of the client would be seen, the design of the library and the additional options which the client wants in it are chalked out, a software for the library is developed and then verified and then periodic checks are done to see that the project is working as desired. The advantage of this model would be: It would be simple to execute. The programmers would not need to gain more experience to execute this model. It has been used before in the company. The disadvantages of the model would be: The programmers cannot jump between two phases which means that one phase needs to be finished before the other starts which causes problems if there are bugs in the previous phase. The bugs can only be found and removed at the end. If the customer’s demand changes as it have in the past, the model fails to comply and needs to be started all over again. Can be expensive if the model needs to be redone. The company would not be gaining anything new as this model has already been in use and it has mostly worked except in the case of one project. Software Prototyping This is the kind of development methodology which makes a prototype or an example project in the beginning so that an idea can be achieved as to how the model would look like when completed (Miles & Pilone, 2008). When applied to the electronic library project, this model could be beneficial because it would be able to show the customer what his project would look like in the long run. To start off, a prototype of the electronic library would be developed on which the rest of the project would be based. Advantages of this model would be: The client would be able to look at the prototype and determine if the project is the same as what he wants. Since there are many small requirements of the clients like the viewing of the data from a central repository, consolidation of the data, the checking and checking out of the documents etc, all these requirements can be tested and the best solution out forward. The problems in the design which is being developed can be pointed out early and solved. If the prototype design is not favourable, alternatives can be developed. Lesser money spent on solving problems and adding additional features later on. Disadvantages of the model would be: The client may be too much involved, hindering the project. Developing many prototypes and alternatives might cost money. The project may become too complicated for the two lesser experienced programmers to manage. RAD Rapid Application Development This is a model in which the written coding of the model is done side by side with the practical coding. The code is being written as the project is being developed. This involved two aspects, prototyping and iteration. Iteration means that the project does not go in a specific direction; rather it goes back and forth to make any changes which are needed (Fairely, 2009). While an orthodox model would look like this: RAD would look like this: If RAD is implemented in the project, the project would develop a code while the prototyping starts and code would be written as the project continues. The advantages of this model would be: The project is developed faster. The prototype could be tested and any problems could be solved. The team is small enough to run a project like this. The disadvantages of this model would be: The code is not solid and the many changes could be detrimental. In making rapid software, some bugs might be left unseen. Appropriate Methodology The appropriate methodology for this project would be the software prototyping methodology. This should be used because this fulfils the company’s needs in the following ways: The problems which were faced previously in updating codes would be solved as this methodology is iterative and can go back and forth between the phases. If the customer decides to change his mind, he would be able to do so after seeing the prototype and not the entire project which would save time and energy. The company has a team which is optimum for this methodology as it requires a minimum number of people who can get on together well and make decisions. The testing of the project can also be done on the prototype rather than the original project. Any bugs can be removed and any problems can be solved. The small details which the client wants can be finalized on the prototype. From applying this project, the company gains a more streamlined system and client satisfaction. When the client is involved in the development and his requirements are being met, he would be happier with the results (McConnel, 2004). The company also saves money in the long run as the continuous back and forth because of changes in the requirements or the code can all be done on the prototype. Thus, this is worth the switch because it not only a more effective model of software development but it also helps the company and produces satisfied clients. The work environment would become more active as this project needs a lot of energy and determination, it changes again and again and since prototypes are being developed, the programmers have the opportunity to develop their skills, give innovative ideas and indulge in healthy competition. The phases of development would be affected in the way that the development would not be a one way process, rather it would develop and go in circles, each phase might be changes or improved. The phases would not necessarily develop in a straight line, they will develop in the form of a cycle which improves them, refines them and them tests them. The disadvantages of the methodology would be that: If the customer has too many requirements and wants too many changes, the prototype might need to be changed again and again, this might cost money. The lesser experienced programmers might not be able to cope. The problem of the programmers is not severe because as the company has already done a lot of projects, they can learn and adapt to the new method. Bibliography Fairely, R.E., 2009. Managing and Leading Software Projects, John Wiley & Sons, USA. McConnel, S., 2004. Professional Software Development, Pearson Education, USA. Miles, R. & Pilone, D., 2008. Headfirst Software Development, ORiely Media, USA. Tsui, F., 2010. Managing Systems and IT Projects, Jones and Bartlett Learning, USA. Zaulkernan, I. & Faujita, H., 2008. New Trend in Software Methodologies, Tools and Techniques, IOS Press, Amsterdam, Netherlands. Read More