Skip to main content Accessibility help
×
Hostname: page-component-78c5997874-lj6df Total loading time: 0 Render date: 2024-11-19T15:18:59.522Z Has data issue: false hasContentIssue false

EPILOGUE

Published online by Cambridge University Press:  06 July 2010

Ari Jaaksi
Affiliation:
Nokia Telecommunications
Juha-Markus Aalto
Affiliation:
Nokia Telecommunications
Ari Aalto
Affiliation:
Nokia Telecommunications
Kimmo Vättö
Affiliation:
Nokia Telecommunications
Get access

Summary

This book has presented our process model as a collection of phases, notations, models, documents, tips, and rules of thumb. The bigger the development team and the more complicated the system, the more we must place emphasis on how to:

  • Gather and understand requirements.

  • Divide the problem and the system into manageable pieces.

  • Communicate about these pieces.

  • Make these pieces work together to meet the requirements of our customers.

For gathering and understanding, we use use cases, object analysis, and frequent communication with the customers. For successful management, we use concepts such as system products, application products, applications, components, and classes. These entities divide the problems and the systems into manageable pieces. For communication, we use documents, executable software increments, and face-to-face meetings. The Unified Modeling Language (UML) provides the common notation that can illustrate the different views of problems and systems. Finally, we use frequent builds and incremental software development arranged around prioritized use cases to ensure that we create a beneficial software system in time.

We use many activities and tools during software development that are not included in the process framework. These issues are equally important and they are required to make the use of the process model successful.

Typically, we use a lot of group work and brainstorming during software development projects. For example, we may call a meeting to analyze requirements and use cases, to create analysis class diagrams, to construct preliminary user interface sketches, or to give feedback from a user interface prototype. A process model, though, cannot give much to these sessions.

Type
Chapter
Information
Tried and True Object Development
Industry-Proven Approaches with UML
, pp. 295 - 298
Publisher: Cambridge University Press
Print publication year: 1998

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure [email protected] is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×