THE STAGE INVOLVED IN PROGRAM DEVELOPMENT. THE STAGES INVOLVED IN DEVELOPING PROGRAMS IDENTIFICATION OF PROGRAM

THE STAGE INVOLVED IN PROGRAM DEVELOPMENT.CLICK TO DOWNLOAD

THE STAGES INVOLVED IN DEVELOPING PROGRAMS

IDENTIFICATION OF PROGRAM

The following are the main stages in the development of programs:

1.1            Planning

Estimation how long the assignment will take, deciding what features to implement in what order, setting milestones for completion of various parts of the problem by specific dates before the final deadline. In the unlikely event that you make serious error at the stage, it is probably won’t be identified post-mortem.

This stage tends to be intertwined with the “Analysis and Design” stage. You can’t develop a good estimate of how long the assignment will take until you’ve given some thought to how you’re to solve it. On the other hand, one of the things you need; is to budget time foe it Analysis and Design itself.

THE STAGES INVOLVED IN DEVELOPING PROGRAMS IDENTIFICATION OF PROGRAM.

1.2            Analysis and Design

For most scheme programs, this can be broken down into sub-stages.

v Understand the assignment: that’s to have a clear idea of what the program or function is supposed to do;

v Analyze the data type: here you examine more closely what kind of information the function operate upon, both its input and its output;

v Write contracts ( and perhaps purpose statements) for functions. Decide what kind of information the function needs from the outside world, and what kind of information it returns to the outside world;

v Write examples (with correct answers) to function; write one or more expressions that use this function (in correct scheme syntax, so that if only the function were already defined, you could type them in and get answers), along with the “ right answer” you expect each example to produce to be done on approximately that order. If you later discover that you made wrong decisions about this stuff; it means an error was created at this stage. Errors created at this stage tend to be harder to repair than those created at the implementation stage.

1.3            Coding

Writing code in scheme with java. C++ or some other formal programming languages. Errors created at this stage tend to things matching quotation makes, matching parentheses, misspelling, wrong number of argument etc. it’s possible that you might discover a design error in the process of writing code.

For most scheme programs, the coding stage can be broken down into sub-stages:

v Write a function skeleton: a function definition tells scheme, the name of a new function and how it works. The skeleton of a function definition is a first draft, essentially translating the control into scheme sytax but not specifying how the function does its job.

v Choose and use appropriate function template. The template is the “first Draft” of the function body, comprising all the code you can write based simply on the types of the data involved in the problem.once you’ve done this, you just need to fill a few blanks by actually thinking about the problem to be solved.

v Fill in the function body: replace the parameter-name in the function skeleton with an expression involving the parameter-name and whose vale will produce the correct answer to the function.

1.3.1    Code Review

You’ll probably find a lot of coding errors and possibly a few design errors, at this point. The only way you can create new errors at this point is fixing old errors incorrectly.

1.3.2. compile/Syntax check

          Now is the computer turn to scan for mistakes. Use the “check  syntax” button in  the scheme or the “Compile” button in most java or C++ development environments. Again you’ll probably find a lot of coding errors, and possibly a few design errors, at this only way you can create new errors is by fixing old in correctly.

1.4            Testing and Debugging

If you run your program and it crashes or give wrong answer, you’ve discovered a defect in the “testing “ stage. It was probably created in either the coding or the design stage, we call it coding error. You are in t is stage until the program works correctly ( or you turn it incomplete).

1.5.    Post Mortem

          After you’ve completed the program . review the process of writing it. What kinds of mistake did you make, and how can you avoid them/ or detect them quickly n future project?

In the “planning “ stage , did you allocate enough/or too much time to the various stages and milestones?

Where your initial estimates “ too high, too low or pretty close to reality”

Where did you waste a lot of time?

Where did you use your time well?