Resources
Paper - Use Cases and Architecture
Ivar discusses how use cases are used to drive architecture
If a software project doesn’t get started right, it is not likely to end right. The tendency to rush into construction too soon is starting wrong. To start right means:
- Get the requirements right and get them in shape to drive the development process. That means getting them into the form of use cases.
- Formulate an architecture and make it concrete as an executable baseline that guides construction.
- Get the process iterative and incremental, namely, a series of phases (inception, elaboration, construction, and transition) and iterations within the phases that enable us to attack first things first—but we leave this third step to the next column.
These three steps lie at the heart of good software process. Put this way, you probably agree. Unfortunately, there are still some people, undoubtedly benighted, who contend that the way to develop software is to hire good people, lock them in a room with a tight schedule posted on the wall, and let them do what they do best—write code. Please believe me—it doesn’t work! Good people are always good to have, but they alone are not enough
Filesize - 83 KB