SSAD
SSAD
SSAD
Warnier-Orr- Diagrams
Warnier- Orr- Diagrams are another tool aimed at producing working and correct
program. The Warnier-Orr diagram reads from left to right and then the top to
down. Whereas a flowchart requires many symbols. Warnier-Orr diagram employ
brackets, circles, parentheses, dots and bars
Nassi-Shneiderman Charts
Nassi- Shneiderman charts offer an alternative to either pseudo code or program
flowcharts. Named after their authors, N-S charts are much more compact than
program flow charts, include pseudo code-like, statements, and feature sequence,
decision and repetition constructs.
3. Discuss the roles of system analysts?
Rules Of System Analysts
System analysis while analyzing the system should:
1. Carry out the analysis of the system at a place where the system is
functioning. This step will ensure that the analyst is accepted as one of those
operating the system.
2. Note down the key personnel in the system besides the head of the
department. The key personnel are those who contribute towards the system
operations.
3. Speed sometime with the operating personnel and observe the system to
understand the finer details of the system.
4. Define the scope of the system and its objective. The scope will cover the
boundaries of the system.
5. Collect all the document which are raised in the system. These documents
carry data from one point to another.
6. Collect separately the outputs. Such as statements reports, momos, etc, made
in the system to throw more light on the information it generates.
7. Make a list of rules, formulae, guidelines, policies, etc, which are used in
running the system.
8. Note down the check points and the controls used in the system to ensure that
the data flow is complete, processing of the data is correct and the analysis is
precise.
9. Study the flow of data in the system in units, summary and aggregates from
document to document from one stage to the other.
10. Make a small note as a base document and seek an appointment with each
head of the department to discuss the system.
11. Examine whether the achievement of the system’s objective is feasible in the
present system. This means, examining whether adequate data exists.
12. If there are problems in the feasibility of implementation then examine
whether the present system can be modified by introduction of documents
controls procedures and system.
System Documentation
System documentation means coordinated effort to communicate the information
of the system in written form. Its purpose is to ensure that the details of the
system are understand by all the persons concerned during the development
process and subsequent operation.
OBJECTIVES OF DOCUMENTATION
1. To narrow down the communication gaps among users, designers,
and management.
2. To provide the necessary information to development training
programmed for operators and users.
3. To create a vehicle of information to provide evidence of progress
in the development process and to monitor the process.
4. To provide a means to determine an advance what will occur and
when.
5. To make a system modifications and implementations easier.
6. To make conversion of a system from one machine to another
machine easier.
CHARACTERISTICS OF A GOOD DOCUMENTATION
1. Availability
2. Objectivity
3. Considerable
4. Easy to maintain when the system gets modified it should be easy
to update the documentation.
5. Completeness.
STRUCTURED SYSTEMS ANALYSIS AND DESIGN SET 2