......
Analysis:
What's the problem? What does the user want? What does the user need? What can the user afford? What kind of reliability do we need?
Design:
How do we solve the problem? What should be the overall structure of the system? Which parts does it consist of ? How do those parts communicate with each other? How does the system communicate with its users?
Programming:
Express the solution to the problem (the design) in code. Write the code in a way that meets all constraints (time, space, money, reliability, and so on). Make sure that the code is correct and maintainable.
Testing:
Make sure the system works correctly under all circumstances required by systematically trying it out.
.........
7/26/2015
A problem is a programme.
What would be a good program to look at?
 A program that
*) Illustrates design and programming techniques
*) Gives us a chance to explore the kinds of decisions that a programmer must make and the considerations that go into such decisions.
*) Doesn't require too many new programming language constructs
*) Is complicated enough to require thought about its design
*) Allows for many variations in its solution
*) Solves an easily understood problem
*) Solves a problem that's worth solving
*) Has a solution that is small enough to completely present and completely comprehend.
(TBD)