| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
If there is no rational specification for a piece of software, there is no
way to verify that the software meets the specification at the end of the
project. What is the point of designing something that is not specified ?
How is a design evaluated without a specification to compare? Specifying
non-trivial software a-priori is very hard!
When managers admit that there is no way to write a full specification
up-front, then they must admit that there is no way to build a full design
up front either. UML style tools do not support the only methodology that I
have ever seen succeed (outside of aerospace safety critical software which
is a different issue). The only successful large software that I have seen
succeed has been iteratively developed.
| References: | |
| >Re: UMLish modellers? (From: "Erik M. Buck" <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.