Some of the exercises in this book have many possible solutions. For example, Exercise 4-7 asks you to think of ways to modify the Mr. Bones application. With a little creativity, you could probably come up with hundreds of possible modifications, so your answer probably won’t match mine.
In ambiguous cases like that one, look over the solution to see if it makes sense to you. If it doesn’t, you might want to review the material in the corresponding chapter. (Or you might like to e-mail me and ask, “What on earth were you thinking?”)
You can also start a discussion on the book’s P2P forum about any of these solutions. Sometimes, those kinds of discussions are fascinating.
- The basic tasks that all software engineering projects must handle are:
- Requirements Gathering
- High-Level Design
- Low-Level Design
- The following list gives a one sentence description of each of the tasks listed for Exercise 1.
- Requirements Gathering—Learn the customer’s wants and needs.
- High-Level Design—Describe the major pieces of the application and how they interact.
- Low-Level Design—Provide more detail about how to build the pieces of the application so that the programmers can actually implement them.
- Development—Write code to implement the application.
- Testing—Use the application under different circumstances to try to detect any flaws or bugs.
- Deployment—Roll out the application to the users.
- Maintenance ...