We use cookies to distinguish you from other users and to provide you with a better experience on our websites. Close this message to accept cookies or find out how to manage your cookie settings.
We use cookies to distinguish you from other users and to provide you with a better experience on our websites. Close this message to accept cookies or find out how to manage your cookie settings.
Published online by Cambridge University Press: 05 June 2012
This chapter introduces the general process model on which the developed case studies were based. It commences with an overview of software development phases and general process models as a preamble to introducing the bridge process model based on which the case studies in the forthcoming chapters were developed.
AN OVERVIEW OF PROCESS MODELS
Several process models were discussed and developed to provide a set of activities that permits the development of software systems from user requirements. Almost all processes follow the development of software through the following phases: analysis, design, and implementation, in addition to system testing.
Analysis is the phase during which user requirements are determined and requirement specifications are documented. User requirements are typically collected in a language that is familiar to the user, where a user in this context could mean a real user, the company, or a vendor that requests the software to be developed to automate certain services. The requirements describe what the system is requested to deliver as automated services. Requirements are documented in a specification language that is understood by the designers and developers and that steps away from the user, creating, more or less, a gap between the language and requirements expressed by the user and language and tools applied by analysts, designers, and implementers. The output of this phase is a requirement specification document.
The design phase follows analysis. During design a system designer relies on system specifications reached during the analysis phase to lay out the design of the system.
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.
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.
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.
