System Development Methodology CSci 446


System Development Methodology

Before embarking on a system development project, the team should decide upon the methodology they will use. In some cases, the methodology is dictated by the organization. In other cases, the group can choose their own methodology (usually within certain guidelines set by the organization). This is what your group will do.

In order to develop the methodology for a project, the group must decide upon at least four things, as follows:
1) process
2) semantics
3) notation
4) techniques/tools

As discussed in class and in chapter one, there are many processes, including the following:
- Waterfall
- Incremental
- Iterative
- Spiral
- Cleanroom
- (..and others..)

This refers to the terminology used between the developers and between the developers and the clients.

There are many notations. However, UML (Unified Modeling Language) is, without a doubt, the most popular one.

There are many of these! Think of each one as a tool in the developer's "toolbox." Just like tools in a carpenter's toolbox, these tools/techniques have different benefits which are there for the choosing. However, there is no reason to choose each one. And any one that you choose can be used in different ways for different purposes. Some of the many examples (in no particular order) follow. Most of these techniques, and other additional ones, can also be found in the Whitten & Bentley Systems Analysis & Design Methods book you used in CSci 342, and in many other analysis and design books you may encounter.