Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
1
PERSPECTIVES ON SOFTWARE PRODUCT DEVELOPMENT
iques for estimating how much more engineering are relatively new. The communicati
8 times faster than the worst at coding and debugging an exercise and that the be
ately answerable for choices. Here are two examples of what results from a lack of
slipping schedule. The Army failed, having specified no way to know if the projec
upermarket scanner or the video store rental), is scarcely addressed beyond some
needed to develop applications must be addressed. Project managers need to be awar
emes such as software rejuvenation acknowledge that it is impossible to catch eve
(NATO) conference that set the stage for the early large-scale system development
intenance work. The practice of involving the customer in using prototypes first
ustomized, one-use-only software. Each application program had to know how to physi
rk of managing the files and disk space and allowed several applications to share
ody the first view. This view acts as a driver to help system integrators and prog
view. These scenarios are developed around the functions that are the most import
ptual, functional, and technical operating components to reduce its complexity and
ication servers that have replaced departmental databases benefit from profession
am subfunctions into blocks from program start to end. Branching back to earlier
tures of a particular language direct to some degree the data and logic structure
require the presence of modules that are still in development, dummy programs cal
g no load at all, and by offering the appropriate load in a very short time frame.
ere are tools, techniques, and technology to treat many problems. There are also ar
oblems and stimulate the organization to produce its own recovery plan. In a nont
ude just-in-time training, jump starts with technology experts assigned to the deve
a on which to base an estimate of costs and schedules. The project manager has to
ality checks for customer and designer alike. Useful metrics are availability of t
t all stages of development. The best results come when system designers and huma
t number, communication problems wash out any advantage of extra hands. When the s
er this scheme, instead of a system running for a year, it would run for 1 day, 365
ue pressure from any one of those groups. Standards also define approaches that s