Software Engineering for Students A Programming Approach

Software Engineering for Students A Programming Approach Software Engineering for Students A Programming Approach

web.firat.edu.tr
from web.firat.edu.tr More from this publisher
21.08.2013 Views

The transition phase Summary 343 This phase means putting the system into use. It involves installing the ATM hardware, the software and communication lines. It means arranging for the ATMs to be serviced, supplied with cash and printer paper. It means installing the server software. Rather than install a whole number of ATMs at once, it makes sense to install just one in some convenient location to act as a beta test. This first iteration, once successfully concluded, is followed by the installation of multiple ATMs. 27.7 ● Discussion The UP is not a single process model. It is a framework from which a project manager can select a process model suitable for a particular project. So the model can be applied to large and small projects, involving a few developers or many. Summary The UP is a process model that primarily aims to: ■ meet user requirements ■ accommodate risks. The process consists of four phases: 1. inception 2. elaboration 3. construction 4. transition. Each phase consists of one or more iterations. Each iteration consists of analysis, design, coding and testing. The purpose of iteration is to accommodate risks. The UP employs a number of techniques: ■ iteration ■ use cases ■ focus on providing executable code ■ establishing a working architecture early on ■ using components ■ establishing an effective team ■ incorporating quality throughout.

344 Chapter 27 ■ The unified process • Exercises 27.1 Assess the UP. 27.2 Compare and contrast the UP with the waterfall model, extreme programming and the spiral model. 27.3 Create an outline plan for developing each of the systems in Appendix A, using the UP. 27.4 Evaluate the UP using the following criteria: ■ capability to accommodate risk ■ capability to meet user requirements ■ capability to respond to changed requirements ■ visibility of the progress of the project. 27.5 Identify the main goals and the main techniques of each of the following process models: ■ waterfall ■ spiral ■ prototyping ■ incremental ■ open source ■ XP ■ UP. Further reading •The following book clearly explains the RUP. It also compares it with waterfall, agile methods and heavyweight approaches: Per Kroll and Philippe Kruchten, The Rational Unified Process Made Easy, Addison-Wesley, 2003. Another straightforward read: Philippe Kruchten, The Rational Unified Process, an Introduction, Addison-Wesley, 3rd edn, 2004.

The transition phase<br />

Summary 343<br />

This phase means putting the system into use. It involves installing the ATM hardware,<br />

the software and communication lines. It means arranging <strong>for</strong> the ATMs to be serviced,<br />

supplied with cash and printer paper. It means installing the server software.<br />

Rather than install a whole number of ATMs at once, it makes sense to install just<br />

one in some convenient location to act as a beta test. This first iteration, once successfully<br />

concluded, is followed by the installation of multiple ATMs.<br />

27.7 ● Discussion<br />

The UP is not a single process model. It is a framework from which a project manager<br />

can select a process model suitable <strong>for</strong> a particular project. So the model can be applied<br />

to large and small projects, involving a few developers or many.<br />

Summary<br />

The UP is a process model that primarily aims to:<br />

■ meet user requirements<br />

■ accommodate risks.<br />

The process consists of four phases:<br />

1. inception<br />

2. elaboration<br />

3. construction<br />

4. transition.<br />

Each phase consists of one or more iterations. Each iteration consists of analysis,<br />

design, coding and testing. The purpose of iteration is to accommodate risks.<br />

The UP employs a number of techniques:<br />

■ iteration<br />

■ use cases<br />

■ focus on providing executable code<br />

■ establishing a working architecture early on<br />

■ using components<br />

■ establishing an effective team<br />

■ incorporating quality throughout.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!