Map
Index
Random
Help
Topics
th

Topic: software lifecycle

topics > computer science > programming > Group: software engineering



Group:
program design
Group:
requirement specification
Group:
software maintenance
Group:
testing

Topic:
incremental development
Topic:
management of large software projects
Topic:
programming environment
Topic:
software management

Summary

The software life cycle is usually defined as: requirements specification, design, implementation, testing, and maintenance. Notice that this life cycle is linear without room for experimental systems. Maintenance occurs at the end; it is separate and probably inferior to the rest of programming. Yet studies show that maintenance is most significant in terms of cost and duration. The Thesa life cycle for an incremental addition is: idea, implementation, testing/modification, certified specification. (cbb 5/80)
Subtopic: waterfall model up

Quote: always build a preliminary program before delivering to a customer; study timing, storage, and critical design/operation areas [»roycWW8_1970]
Quote: program large systems by systems requirements, software requirements, program analysis, design, coding, and testing [»roycWW8_1970]
Quote: management of software requires a lot of documentation; need a 1500 page software specifications vs. a 30 page hardware specification [»roycWW8_1970]
Quote: testing is the most expensive phase of software development [»roycWW8_1970]
Quote: testing has the greatest risk in cost and schedule; testing occurs last when backup alternatives are least available

Subtopic: involve the customer up

Quote: software design is subject to wide interpretation; involve the customer in a formal way before final delivery [»roycWW8_1970]

Subtopic: examples up

Quote: DOD's software life cycle: concept formulation and requirements specification, software development, operations and maintenance [»wegnP12_1976]

Subtopic: sync/stabilize up

Quote: synchronize and stabilize -- evolve designs interactively with frequent synchronization and periodic stabilization [»cusuMA10_1999]

Subtopic: implementation phase up

Quote: literate programming is currently ill-suited for software developers; limited to implementation phase, high overhead, awkward [»cordD6_1991]

Subtopic: life cycle is historical up

Quote: software life cycle occurred because of severe limitations in available design and implementation tools

Subtopic: life cycle is wrong up

Quote: the software life cycle is like forcing supermarket customers to specify their shopping list at the door [»mccrDD4_1982]
Quote: with the software life cycle, changes occur reluctantly and in large packets [»mccrDD4_1982]
Quote: the software life cycle rigidifies thinking and reduces a system's responsive to change [»mccrDD4_1982]


Related Topics up

Group: program design   (13 topics, 454 quotes)
Group: requirement specification   (11 topics, 307 quotes)
Group: software maintenance   (14 topics, 368 quotes)
Group: testing   (18 topics, 557 quotes)

Topic: incremental development (74 items)
Topic: management of large software projects (63 items)
Topic: programming environment (46 items)
Topic: software management
(28 items)


Updated barberCB 1/06
Copyright © 2002-2008 by C. Bradford Barber. All rights reserved.
Thesa is a trademark of C. Bradford Barber.