Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Suman Mam

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 18

Structured Analysis and Design Technique (SADT) is a 

diagrammatic notation designed
specifically to help people describe and understand systems. It offers building blocks to
represent entities and activities, and a variety of arrows to relate boxes. These boxes and
arrows have an associated informal semantics. SADT can be used as a functional analysis
tool of a given process, using successive levels of details. The SADT method allows to
define user needs for IT developments, which is very used in the industrial Information
Systems, but also to explain and to present an activity’s manufacturing processes,
procedures.

The SADT supplies a specific functional view of any enterprise by describing the
functions and their relationships in a company. These functions fulfill the objectives of a
company, such as sales, order planning, product design, part manufacturing, and human
resource management. The SADT can depict simple functional relationships here and can
reflect data and control flow relationships between different functions.

SSAD TECHNIQUES

Logical Data Modelling – The data requirements of the system being designed are
identified, modelled and documented. This data is separated into entities and
relationships between these entities identified.

Data Flow Modelling – Concerned with how the data moves around the information
system.Examines processes, data stores, external entities and data flows.

Entity Behaviour Modelling – The identifying, modelling and document events with
respect to the entities in the system and the order in which these events take place.
STEPS USED IN SSAD

SSADM is a waterfall view approach whereby there are sequences of events that run in
series and each step leads on from the last. There are five steps in total, and each step can
be broken down further.

1. Feasibility study – To determine whether it is cost effective to go ahead with the


system and whether it is actually possible.

2. Requirements Analysis – Identifying of the requirements and needs of the system


and modelling these needs in terms of the processes carried out.

3. Requirements Specification – The functional and non functional requirements are


identified in detail.

4. Logical System Specification – Technical systems options are created and the logical
design of the system created. This includes the design of update and enquiry processing.

5. Physical Design – The logical system specification and technical system specification
is used to design a physical database and set of program specifications.

For each of the above stages SSAD defines techniques and procedures for recording and
communicating the information. This includes both textual and diagrammatic
representations.
STRUCTURED SYSTEM ANALYSIS AND DESIGN IN
CONTEXT WITH STUDENT RESULT MANAGEMENT
SYSTEM

Student result Management System (SRMS) streamlines data collection, storage &


retrieval and the management of records to improve both operational (calculation, result,
subject marks, examination report and grading) and management tasks (planning,
evaluation and decision-making).

SRMS focuses on storing & processing curriculum data, student data and produce outputs
supporting the operational activities. These outputs include student report cards, subject
descriptions, invoices, schedules and management information.

When information system are designed to provide information needed for effective
decision making by managers,they are called management information systems,Same is
the case of student result management system.

Student result management system is a formal system for providing management with
accurate and timely information of the result which is necessary for decision making.The
student result management system may be defined as a planned and integrated system for
gathering relevant data ,converting it in to right information and supplying the same to
the concerned executives.The main purpose of student result management system is to
provide the right people at the right time.

Student result management system does the following function:


 It collects ,stores,evaluates information systematically and routinely.
 Supports planning and control decision.
 Includes files,hardware,software.software and operations research models.
 It sub serves managerial function.
 It helps in organizing data related to results of a student.

WHAT ARE THE ADVANTAGES OF USING STUDENT


RESULT MANAGEMENT SYSTEM ?
 It facilitates planning
 It minimizes information overload
 It encourages decentralization.
 It brings co-ordination.
 It makes control easier.
 It assembles process,stores,retrives,evaluates and disseminates the information.

BENEFITS OF SSAD IN SRMS:


Timelines: Theoretically, SSADM allows one to plan, manage and control a project well.
These points are essential to deliver the product on time.

Usability: Within SSADM special emphasis is put on the analysis of user needs.
Simultaneously, the systems model is developed and a comprehensive demand analysis is
carried out. Both are tried to see if they are well suited to each other.

Respond to changes in the business environment: As in SSADM documentation of the


project’s progress is taken very seriously, issues like business objectives and business
needs are considered while the project is being developed. This offers the possibility to
tailor the planning of the project to the actual requirements of the business.
Effective use of skills: SSADM does not require very special skills and can easily be
taught to the staff. Normally, common modelling and diagramming tools are used.
Commercial CASE tools are also offered in order to be able to set up SSADM easily.

Better quality: SSADM reduces the error rate of IS by defining a certain quality level in
the beginning and constantly checking the system.

Improvement of productivity: By encouraging on-time delivery, meeting business


requirements, ensuring better quality, using human resources effectively as well as trying
to avoid bureaucracy, SSADM improves the overall productivity of the specific project
and the company.

Cuts costs: SSADM separates the logical and the physical systems design. So the system
does not have to be implemented again with new hard -or software.

DISADVANTAGES OF SSADM

SSADM puts special emphasis on the analysis of the system and its documentation. This
causes the danger of over-analysing, which can be very time and cost consuming. Due to
various types of description methods, checks of consistence cannot be carried out.
Especially with large systems, the outline diagram can become very unclear, because all
relevant data flows have to be included.

Student result management system includes al the basic information and academic
information related to the student .it includes the examination details like
subjects,type of exam ,semester,marks,calculations and reports.It includes
relationship between various entities.
PROBLEM IDENTIFICATION

After studying the current student result management system of any institution we found
that in many colleges there are many students, more than 200 students altogether studying
in different semesters. Since the number of students is growing ,and the management has
to handle result records of lots of students .it is facing a little bit problems:

In maintaining the record of lots of students.


In the execution of result.
Many colleges are using information system,but it is totally manual one.
Exchange of data .
It takes a lot of time in current system i.e slow processing.

And hence there is an urgent need of upgrading a systemto that of the computer based
information system , a system which can deal with the problems .
OBJECTIVE
SCOPE DEFINITION AND LIMITATION
PRELIMINARY STUDY OF THE SYSTEM

 Students are enrolled in programs.


 The programs are based on courses.
 Different courses are offered at the start of the semester.
 Students enroll themselves for these courses at the start of semesters.
 Enrolled courses by students and offered courses must not be same.
 The difference is due to the individual situation of every student, because if one
student has not pass a certain course ‘A’ in the previous semester he will not be
able to register for a course ‘B’ offered in this semester as the course ‘A’ is the
prerequisite for course ‘B’.
 After valid registration classes start.
 A Course which is offered is assigned to a teacher also.
 There can be any mid term exams and in this system we have only one mid term.
 All the students are given assignments and quizzes and are awarded marks against
their performance.
 Result of the student is prepared on the basis of assignment marks, sessional and
mid term marks and the final exam.
 GP (Grade point) for students is calculated in each subject.
 Average grade point is calculated on the basis of GPs in individual subjects.
 And the Cumulative GPA is calculated for all the passed semesters.

Once the analysis of the system is done it is important to make a draft of the system using
a standard tool which specifies the component and design of the system. This design is
useful because anyone using the design can work on the existing system and clearly
understand the working without working on the system from the scratch.

Tool used for such graphical design is Data Flow Diagram (DFD) on next page of the
system we have a context diagram of the system which shows integration of different
entities with the result management system, these include Registration
system,examination , controller, student and teacher entities.

Context level diagram


A Context Diagram is the very first DFD that you will make.
A Context diagram has:
– One Process - the name of the process is the name of the system
– No Data Store
– One or more External Entities
– Two or more Data Flows
– A Context Diagram is the simplest DFD of the System.
– In Context level Diagram explode (break up) the Single process in the Context
Diagram into sub-processes.
– This breaking-up results in lower level DFDs.
CONTEXT LEVEL DIAGRAM OF STUDENT
RESULT MANAGEMENT SYSTEM

0.0

EXPLANATION OF THE CONTEXT LEVEL DIAGRAM


 From the diagram we can understand basic functionality of the system and can
find how the data is flowing in the system and how different external entities are
communicating or interacting with the system.
 First of all we have registration system, which provides the data of students to the
systems once the registration process has been completed, this data is now free of
errors in terms of validity of a certain student for a certain course or a semester.
 Second external entity interacting with the system is the teacher, a Teacher is
given a list of students who are enrolled in a class and the registration system has
declared them as valid students for that very course. Then the teacher allows those
students in the class and continues the process of teaching the class, during this
process the teacher takes test of the students and prepares papers for the students
and also prepares quizzes to be submitted by students. All the data of students’
attendance quizzes and assignments alongwith different sessional results is then
submitted by the teacher to the examination system which is responsible for
preparation of results of the students.
 Third interacting entity with the system is the controller’s office it is provided with
the semester overall result, subject results and also the result of each class fir
performance evaluation and many other aspects.
 Fourth entity is student which externally interacts with the system for getting its
result, the result is submitted to the student and may be in one of different forms
such as, transcript and result card etc.
 Fifth entitiy is examination which interacts with the system to provide information
about the performance of the student and helps in calculating the result.

LEVEL 0 –DATA FLOW DIAGRAM


DFDs show the flow of data from external entities into the system, showed how the data
moved from one process to another, as well as its logical storage. 

5.0

You can further detailed it as follows:

8.0
After the process of result submission the result for all the subjects is taken and the GPA
is calculated, once the GPA is calculated the it is used for further calculation of CGPA
and is forwarded to another process which is numbered 7.0 this process will calculate the
CGPA by taking all the results of the current and previous semesters. Further detailed
diagram i.e.—Detailed DFD can be created using the given level 0 DFD and by
expanding all the Processes further.
ENTITY RELATIONSHIP DIAGRAM OF
STUDENT RESULT MANAGEMENT SYSTEM

You might also like