Chapter 18: Software Process and Methodology for Web Applications

Overview

Somebody has hired you to build a web site or a software solution. You’re tasked with determining what the client or owner wants in terms of a site, and you have to get the owner to agree to provide you a certain amount of time and money to produce the web site and make certain that the team performing the work will deliver the same web site that the owner wants. The challenge of such an effort is that often the owner does not know what he or she wants, and often the owner wants it done in less time than is reasonable. The team building the site does not know exactly what the owner wants, nor do they always know how to produce the desired outcome, even when the outcome is known.

Many development managers or technical leads follow a pattern called the Unified Process to help them deliver software solutions. The Unified Process plan is divided into phases that should be performed during any software development cycle. The goal of the process is to reduce the risk of software being delivered that does not meet the needs of the owner and client. The spirit of the process is meant to identify any unknowns, assumptions, or risks, and to measure the effort required to deliver a quality software solution by the most efficient means possible.

Many processes have evolved from the Unified Process, but their implementations may vary somewhat. Companies have built software to help encourage a particular utilization of the Unified Process, too, such as Rational Software, which refers to its version as the Rational Unified Process.




IIS 6(c) The Complete Reference
IIS 6: The Complete Reference
ISBN: 0072224959
EAN: 2147483647
Year: 2005
Pages: 193

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net