You are on page 1of 2

An algorithm has following characteristics:

1. Each and every instruction should be precise and unambiguous i.e. each and
every instruction should be clear and should have only one meaning.
2. Each instruction should be performed in finite time.
3. One or more instructions should not be repeated infinitely. It means that the
algorithm must terminate ultimately.
4. After the instructions are executed, the user should get the required results.
Algorithm
a process or set of rules to be followed in calculations or other problem-solving
operations, especially by a computer.
Pseudocode (pronounced SOO-doh-kohd) is a detailed yet readable description
of what a computer program or algorithm must do, expressed in a formally-styled
natural language rather than in a programming language. Pseudocode is sometimes
used as a detailed step in the process of developing a program. It allows designers
or lead programmers to express the design in great detail and provides
programmers a detailed template for the next step of writing code in a specific
programming language.
Flowcharts are the ideal diagrams for visually representing business processes. For
example, if you need to show the flow of a custom-order process through various
departments within your organization, you can use a flowchart. This paper provides
a visual representation of basic flowchart symbols and their proposed use in
communicating the structure of a well-developed web site, as well as their
correlation in developing on-line instructional projects. A typical flowchart from older
Computer Science textbooks may have the following kinds of symbols:
--BASIC SYMBOLS OF FLOWCHART:
Start and end symbols, represented as lozenges, ovals or rounded rectangles,
usually containing the word "Start" or "End", or another phrase signaling the start or
end of a process, such as "submit enquiry" or "receive product".
Arrows, showing what's called "flow of control" in computer science. An arrow
coming from one symbol and ending at another symbol signifies flow passes to the
symbol the arrow points to.
Processing steps, represented as rectangles. Examples: "Add 1 to X"; "replace
identified part"; "save changes" or similar.
Input/Output, represented as a parallelogram. Examples: Get X from the user;
display X.
Conditional (or decision), represented as a diamond (rhombus). These
typically contain a Yes/No question or True/False test. This symbol is unique in that it
has two arrows coming out of it, usually from the bottom point and right point, one
corresponding to Yes or True, and one corresponding to No or False. The arrows
should always be labeled. More than two arrows can be used, but this is normally a
clear indicator that a complex decision is being taken, in which case it may need to
be broken-down further, or replaced with the "pre-defined process" symbol.
A number of other symbols that have less universal currency, such as:
A Document represented as a rectangle with a wavy base;
A Manual input represented by a rectangle, with the top irregularly sloping up
from left to right. An example would be to signify data-entry from a form;
A Manual operation represented by a trapezoid with the longest parallel side
upmost, to represent an operation or adjustment to process that can only be made
manually.
A Data File represented by a cylinder

(SDLC is also an abbreviation for Synchronous Data Link Control.)


The systems development life cycle (SDLC) is a conceptual model used in project
management that describes the stages involved in an information system
development project, from an initial feasibility study through maintenance of the
completed application.