Software Process Models - Essay Example

Software Process Models Number The CIO Glasgow Bank Limited Alotaibi, Faris K. 21st September 2012Subject: Software DevelopmentSpiral methodology in software development In June this year, Television Network Company embarked on the spiral methodology for developing the accounting software “X,” and awarded the world’s leading manufacturer of personal computers, Hewlett Packard (HP) the contract to go ahead with its production. HP specializes in the development and production of computing products such as networking hardware, and data storage devices.

It also designs applications and provides service delivery. HP’s major product lines encompass personal computing hardware and software; servers for small businesses and for industries as well as associated memory devices, networking hardware, software and a broad range imaging products. The products are usually distributed through physical outlets in the market as well as through the Internet. Additionally, electronic outlets, product-line retailers, software partners and big technology retailers also serve consumers with the company’s goods.

The company also boasts effective consultancy services relative to its products. The spiral methodology blends the design of prototyping with the structured, refined qualities of the waterfall methodology (Kan, 2003). The development of the spiral model is premised upon a refinement of the application on a bit-by-bit basis as the spiral grows. The methodology also clearly encompasses risk management measures within software engineering. The approach recognizes major risks at various stages of implementation such as the practical and supervisory aspects, and explores ways in which the risks can be reduced.

These measures keep the software engineering work better and more controlled. The spiral methodology is premised on continuous polishing of the main products in order to ensure that the product meets the market standards including the system and design of the application as well as the code developed for use (Geambaşu, Jianu, Jianu, & Gavrilă, 2011). Notably, at each stage around the spiral, the software is an improvement of a prior product. The spiral model shares most development phases with the waterfall model, with the main differences involving planning, evaluation of risks, and the development of models and simulations.

Software developed through this methodology solves the problem of haphazard production of documents, which otherwise would not reflect the important details at a given stage in the engineering process. Like the application they describe, the documents are representative of the all the key stages of development (Kan, 2003). The concept is to guarantee a continuous flow of products manufactured and accessible for a review by consumers. The methodology presents a more precise estimate of production costs and timeline as this can be done as the work continues.

The discovery of priorities can also be achieved early enough. Additionally, the spiral model often eases flexibility, which is a common aspect of software engineering. Software developers who prefer flexibility instead of a long design process can make significant contributions to the start and development of a project earlier enough. Although the methodology is largely effective, there are a number of pitfalls that might come up. The model is highly costly, thus may be inappropriate for a smaller budget.

The methodology is very complicated, especially for programs with a definite software requirements specification (SRS) (Kan, 2003). Additionally, high expertise is required in order to successfully assess and review each project throughout all the stages. The expertise would also come in handy through the much needed meticulous observation of all the vital rules and protocols. Owing to various customizations that customers may prefer, the use of a single model in other projects, in future, is tricky (Geambaşu et al, 2011).

The model is also not suitable for use in high risk projects; besides, the heavy documentation would prove difficult to keep. Recommendations: Spiral methodology is highly efficient for projects where more flexibility is needed. In such a case, development stages can be approved by the project supervisor; this depends on the convolution of the project. Owing to the complex nature of project monitoring, more so on constant basis, high expertise in needed to make the work easier and more effective.

Project managers can make any changes they deem fit with relative ease, especially in the current environment of technological revolution. This flexibility results in the development of a stronger product that is responsive to customer needs. Spiral methodology is highly effective in software development, as the current technologies are driven by constant changes.Copy to:Name:Name: ReferencesGeambaşu, C.V., Jianu, I., Jianu, I., & Gavrilă, A. (2011). Influence factors for the choice of a software development methodology.

Accounting & Management Information Systems, 10(4), 479-494.Kan, S.H. (2003). Metrics and Models in Software Quality. New York: Addison-Wesley Professional.