Chapter 2


1:

Name several tasks that should be performed before a programmer starts writing the first line of code.

A1:

The development team needs to understand the customer requirements and define the features in a product spec. A schedule should be created so team members know what work has been completed and what work remains to be done. The software should be architected and designed, and the test team should start planning their work.

2:

What disadvantage is there to having a formal, locked-down specification?

A2:

There's no flexibility to adjust the software if the customer's needs change or the market moves in a different direction while the software is being developed.

3:

What is the best feature of the big-bang model of software development?

A3:

It's simple. Period.

4:

When using the code-and-fix model, how do you know when the software is ready to release?

A4:

There's no real exit criteria for the code-and-fix process except for when someone, or the schedule, says that it's time to stop.

5:

Why can the waterfall method be difficult to use?

A5:

Just like with salmon, it's difficult to swim upstream. Each step is a discrete, standalone process that follows the one before it. If you get to the end and find that something should have happened further up, it's too late to go back.

6:

Why would a software tester like the spiral model better than the others?

A6:

They're involved very early in the development process and have the opportunity to find problems early, saving the project time and money.



    Software Testing
    Lessons Learned in Software Testing
    ISBN: 0471081124
    EAN: 2147483647
    Year: 2005
    Pages: 233

    flylib.com © 2008-2017.
    If you may any questions please contact us: flylib@qtcs.net