This article Methodology consists of 9 pages and1403 words. In order to have full access to this article, email us at thedocumentco@hotmail.co.uk
Ref No: 937

Methodology

1. Software Development Methodologies

Methodology:Every software goes through a specific set of developmental phases. A software development methodology refers to the specific technique that is followed in order to plan, manage and execute the entire process of development. As such, there are various methodologies including waterfall model, spiral model, incremental model, iterative development, and agile methodology. The development of the online hospital management system will follow agile scrum methodology as it is capable of dealing with the arising complexities (Schwaber, 2004). In addition, agile scrum allows for incorporation of requirement changes as the project progresses.

Waterfall Model:

Waterfall model follows a sequential process for carrying out the developmental activities (Alsmadi and Saeed, 2014).  It is ideal for projects that involve clearly defined requirements and well-known technical specifications. The waterfall model eponymously mimics a ‘waterfall’ where each process activity is followed by another but that which cannot flow backwards (Hentzen, 2002). It begins with problem analysis, subsequently proceeding to establishment of technical requirements, designing of solution, coding, testing, bug fixing, and eventually the implementation of the final product.

Spiral Model:

The spiral model is an iterative, risk-oriented model of software development. Each phase in the iterations is referred to as a spiral. Further, each cycle of the spiral begins with the recognition of the objectives, implementation alternatives, and the limitations associated with the implementation alternatives (Boehm, 1988). Next, the alternatives are assessed and the associated risks are resolved. Prototyping is critical in the spiral model which allows risk to be mitigated and resolved (Landry, 2011). In addition to that, the spiral model conducts risk analysis before each stage (Sabharwal, 2009).

Read More

Incremental Model:

Incremental model takes into account the need for technical requirements to continue being updated. It is an evolutionary process model, which means that it is flexible to changing requirements and can accommodate those changes incrementally adding additional functionalities to the design (Sabharwal, 2009). Each incremental build that is released enhances the functionalities of the previous version allowing the project cost to be minimized. Therefore, every new build adds on to the functionalities contained in the previous one…