UI Methods and ArchitectureProcess

In commercial practice, there are at least two major motivations for modeling a project's processes.

• Modeling development processes to understand and organize development activities.

  There is often a co-ocurring motive such as geographically dispersed development, large size of project, a need to monitor architectural conformance, or greater system complexity—mixing hardware and software in development or deployment, for example.

• Modeling deployment or engagement process in addition to modeling development process to better coordinate and target development and deployment activities.

  There is usually a co-ocurring motive such as organizational diversity—presence of professional or other integration services in the business model.

This section uses UML notation to model and discuss development processes.

The related topic:

• Modeling business requirements in the course of software specification or delivery of software related professional services.

is covered by the task modeling discussions under UML including Use Case diagrams (available now) and Activity diagrams (coming later this year).

Look for content in this page in 3Q2003.