In Partial Fulfillment of Diploma in Computer Engineering

SEMESTER 5th

Internal Guide:

Nilay Patel

Submitted to
Department of Computer Engineering
R.C Technical Ahmedabad-380061
Month/Year: 2021-2022

Submitted By

No Enrollment Number Name

1 196400307092 Harsh Patel

2 196400307086 Aryan Patel
3 196400307091 Divy Patel
4 196400307079 Sahil Parikh

RCTI(CE) Page |1
STUWI

Student Reward System (STUWI)

No Enrollment Number Name

1 196400307092 Harsh Patel

2 196400307086 Aryan Patel
3 196400307091 Divy Patel
4 196400307079 Sahil Parikh

RCTI(CE) 2|Page
STUWI

Guided By: -Nilay Patel

RCTI(CE) 3|Page
STUWI

R. C. Technical Institute
Sola, Ahmedabad - 60
CERTIFICATE
This is to certify that this work of PROJECT-1 Subject &3350706 Subject Code
of 5thSEM with title:Student Reward System (STUWI)represents the work of the
following students for the partial fulfillment of the Certificate of Diploma in
Computer Engineering at R. C. Technical Institute Sola, Ahmedabad - 60, Gujarat,
during the academic year 2021-2022 and the work is underdevelopment.

No Enrollment Number Name

1 196400307092 Harsh Patel

2 196400307086 Aryan Patel

3 196400307091 Divy Patel
4 196400307079 Sahil Parikh

Submitted to Nilay Patel

Lecturer, Computer Engg. Dept. Head of Computer Dept
RCTI RCTI
RCTI(CE) 4|Page
STUWI

ACKNOWLEDGEMENT

We would like to express our deep feeling of gratitude to the under mentioned officials for their
assistance, guidance and inspiration throughout the project. We are very thankful to our college
“R.C.T.I.”, “Ahmedabad”, for providing best facilities. We are highly grateful to “R.C.T.I” to
give us an opportunity to have experience in working with such an experienced firm. We would
like to express our sincere thanks to who showed trust in us and provide us with such a
challenging project. We would also like to thank our internal project guide for spending her
valuable time for providing us better guidance to achieve our goal. Finally, we want to express
out deep appreciation for the continuous support and encouragement from our faculty members.
Last but not the least, we would also thank all those who have helped us implicitly or explicitly
but whose names have forgotten to mention.

Thanking you.

RCTI(CE) 5|Page
STUWI

Abstract

We are introducing “STUWI”, the django-based webapp which is a free digital reward
system in which every student gets evaluated on academic activities, extra-curriculum
activities and positive behavior.

Our app mainly attracts teachers, administrators and students, which they can use from
any device and earn reward points and quickly track points, for the great things that
students do every day!

Student motivation affects every aspect of Higher education, from attendance, to

academic performance, to extra-curricular activities. Our main aim through this app is to
drive the main audience i.e. students to participate actively in academic as well as extra-
curriculum activities, where they can willingly improve their behavior/performances.
That's why we came up with STUWI for motivating students by providing them digital
reward points which they can earn and redeem different discount and offers on selected
items from selected application .The Student Reward System (STUWI) is webapplication
based system which will use as a platform for interaction and competition between
students of same grade and program. While the main objective of this webapplication is
to connect students of same grade and make them compete.

RCTI(CE) 6|Page
STUWI

Table of Contents
1.0 INTRODUCTION....................................................................................................................................7
1.1 Project Summary & Profile................................................................................................................7
1.2 Purpose..............................................................................................................................................7
1.3 Scope & Objectives............................................................................................................................7
1.4 Technologies......................................................................................................................................7
2.0 PROJECT MANAGEMENT...................................................................................................................12
2.1 Project Planning.............................................................................................................................12
2.1.1 Project Development Approach and Planning........................................................................12
2.1.2 Roles and Responsibilities......................................................................................................12
2.2 Project Scheduling........................................................................................................................12
2.3 Risk Management.........................................................................................................................12
3.0 SYSTEM REQUIREMENTS STUDY..........................................................................................................19
3.1 Existing System / Scenario...............................................................................................................19
3.2 Proposed System.............................................................................................................................19
3.1.1 Modules & Features in the New System...................................................................................19
3.1.2 User Characteristics..................................................................................................................19
3.1.3 Hardware & Software Requirements........................................................................................19
3.1.4 Assumptions and Dependencies...............................................................................................19
4.0 SYSTEM ANALYSIS.............................................................................................................................26
4.1 Feasibility Study...............................................................................................................................26
4.2 System Activity Diagram..................................................................................................................26
4.3 Use Case Diagram............................................................................................................................26
4.4 Sequence Diagram...........................................................................................................................26
5.0 SYSTEM DESIGN...................................................................................................................................34
5.1 Database Design / Data Structure Design........................................................................................34
5.1.1 Data Dictionary.........................................................................................................................34
5.1.2 ER Diagram...............................................................................................................................34
5.1.3 Data Flow Diagram...................................................................................................................34
5.2 Input / Output and Interface Design................................................................................................34

RCTI(CE) 7|Page
STUWI

5.2.1 Flow Chart.................................................................................................................................34

1.1Project Summary

In the present times Student constantly needs motivation to keep up in

their studies and to perform well. So, to make it easy they need to be part of
competition in from of motivation. So STUWI focuses on such minor things so
that students can keep up with their friends and they perform extremely well in
their academics. It is difficult task to compete with other students in term of
progress, so this webapplication provides such things.

RCTI(CE) 8|Page
STUWI

1.2PURPOSE

Student motivation affects every aspect of school life, from attendance, to

academic performance, to extra-curricular activities. Promoting the greatest student
motivation possible is extremely important for every teacher in every universities,
especially in today's educational climate, where universities are continuously under
pressure to improve test scores, responsibility, and accountability, punctuality. So
we are building an application which helps students to keep up with their
academics and also helps to improve them, and they can work individually towards
personal reinforces or work together towards group reinforces.

RCTI(CE) 9|Page
STUWI

1.3SCOPE & OBJECTIVES

The scope of Student Reward System is very vast. It includes; efficiency of the
institution, students, securing benefits of the Universities and colleges through practical
measures, clarification of the functions and connection between faculty and students,
coordination of the educational programs, compete with others, good direction, efficient
and systematic execution. It provides close collaboration and sense of sharing
responsibilities, organized purpose and more career oriented.

Any organization plays a vital role in the life of human being. It plays different functions
like; brings efficiency, guide pupil to receive right direction from the right teachers,
enables the pupil to get profit from their learning, bring coordination of the student-
teacher-society. It provides well defined policies and programs, favorable teaching
learning situation, growth and development of students, make use of appropriate
materials, effective development of human qualities, execution of the programs,
arrangement of the activities, efforts for attainment of the objectives etc. 
Every students needs to keep up with their faculty in terms of studies and also in extra
curriculum activities. So this application have the main objective of doing so and helping
students.

RCTI(CE) 10 | P a g e
STUWI

1.4TECHNOLOGIES

This project uses the following technologies, servers.

 Python
 SQLite database
 XML

RCTI(CE) 11 | P a g e
STUWI

2.1PROJECT PLANNING
Project planning is one of the major tasks that are performed during the
development of the project. Using project planning, the task of finding the size of the
project is done and with that total amount of time and cost required for project
development is calculated.

The approach to develop the software system should follow some systematic way
i.e. Software Development Life Cycle. Using the upper level analysis and the
environment of the project, which lifecycle model would fit properly for this project was
judged. After deciding the proper software development lifecycle model, the
development of this project according to the model was done.

2.1.1 Project development Approach and planning

How to choose the right approach for a project is a large topic. The
methodology you choose can depend on many things, including the structure
and location of the project team, the technologies being used on the project,
and the degree to which collaboration is a part of the company’s culture.
Project is done based on the decided development lifecycle model. We decide
the iterative model for our webapplication.

An iterative model

An iterative life cycle does not attempt to start with a full specification of
requirements. Instead, development begins by specifying and implementing
just part of the software or application.
The key of an iterative software development lifecycle is rigorous validation of
requirements, and verification & testing of each version of the application
against those requirements within each cycle of the model. As the software
evolves through successive cycles, tests must be repeated and extended to
verify each version of the software or application.

RCTI(CE) 12 | P a g e
STUWI

Diagram of an iterative waterfall model: -

Request for change in

Requirements requirements at any stage
Lacking feedback loops
Design for problem

Implementation
Verifying patches Verification
forking updates to next
version
Maintenance

Advantages of iterative model:-

In iterative model, we are building and improving the product step by step. Hence,
we can track the defects at early stages. This avoids the downward flow of the
defects.
In iterative model, we can get the reliable user feedback. When presenting
sketches and blueprints of the product to users for their feedback, we are
effectively asking them to imagine how the product will work.

Disadvantages of Iterative model:-

Each phase of iteration is rigid with no overlaps.
Costly system architecture or design.

RCTI(CE) 13 | P a g e
STUWI

2.1.2 Roles and Responsibilities

Our system was decomposed into different modules and we are responsible persons for
analysis, design and implementation, documentation along with testing. So we have given
different roles to our each and every team members.

ACTIVITIES ROLES AND RESPONSIBILITIES

Requirements Gathering Harsh Patel, Aaryan Patel

Analysis Divy Patel, Sahil Parikh

Design Harsh Patel

Data Dictionary Divy patel, Aryan Patel

Data Modeling Harsh Patel, Aaryan Patel.

Documentation Sahil Parikh, Harsh Patel, Aryan patel, Divy

Patel

RCTI(CE) 14 | P a g e
 STUWI

2.2 PROJECT SCHEDULING

Project scheduling consists of identifying the task needed to complete the project,
determine the dependency among different tasks, plan the starting and ending dates for
various tasks and determine the chain of tasks. The main benefit of scheduling is that we
can use our time efficiently and purposefully.

2.2.1 GANTT CHART

Task July – September - November - January - March - April

name August October December February
W1-2
W3-4
W5-6
W7-8
W1-2
W3-4

W7-8
W1-2
W3-4
W5-6
W7-8
W1-2
W3-4
W5-6
W7-8
W1-2
W3-4
W5-6
W7-8
W5-6

Requiremen
t gathering
Analysis

Design

Coding

Testing

Correction

RCTI(CE) 15 | P a g e
STUWI

2.3 RISK MANAGEMENT

Risk management is the process of measuring or assessing, risk and developing
strategies to manage it. Strategies include transferring the risk to another party,
avoiding the risk, reducing the negative effect of the risk, and accepting some or
all of the consequence of a particular risk. Traditional risk management focuses on
risks that can be managed using traded financial instruments. In ideal risk
management, a prioritization process is followed whereby the greatest loss and
greatest probability of occurrence and lower loss are handled later.

RISK IDENTIFICATION

After establishing the context, the next step in the process of managing risk is to
identify potential risk Risks are about events that when triggered, cause problems.
Hence, risk identification can start with the problem itself.

In this project there can be following risk

The other risk is associated with the application the wrong user is authorized
by mistake then he may do changes that cause the system in dangerous mode.
There can be risk of natural threats.
Unrealistic schedule and budget of our team.
Internal jealousy of team members or programmers due to some reason

RISK ANALYSIS

Risk analysis is the important aspect of the system planning whenever planning
the Application, programmer always should consider the risk of system which he
might face in the Application. Risks are of two type:-

 Proactive Risk.
 Reactive Risk.

RCTI(CE) 16 | P a g e
STUWI

 PROACTIVE RISK:-

Proactive risk management attempts to reduce the tendency of any accident

happening in future by identifying the boundaries of activities, where a
breach of the boundary can lead to an accident.
Proactive risk management combines a mixed method of past, present and
future prediction before finding solutions to avoid risks.

 REACTIVE RISK:-

Reactive risk management attempts to reduce the tendency of the same or

similar accidents which happened in past being repeated in future.
Reactive risk management solely depends on past accidental analysis and
response.

RISK PLANNING

Once risk have been identified and assessed, all techniques to manage the risk fall
one or more of these four major categories:-

 Tolerate(retention)
 Treat(mitigation)
 Terminate(elimination)
 Transfer (buying insurance)

RISK AVOIDANCE

We should do clearly verification process at the login time of the system

We should follow complete approach planning for development.
Every team member should obey each other.

RCTI(CE) 17 | P a g e
STUWI

3.1 EXISTING SYSTEM / SCENARIO

Existing System

 There is no as such application which provides such effective features as STUWI

does.
 There might be some web application, which provides students rewards.

Scenario

 The new system is totally interactive.

 The system should be flexible.
 It provides security and authorization.
 It save time and cost.
 It is user friendly.
 In the new system, students can compete and look up to their academics profile.
 Student can easily view their academics profile so they keep it up.

RCTI(CE) 18 | P a g e
STUWI

3.2 PROPOSED SYSTEM

STUWI is an webapplication which provides an environment where all the process of the
student in the institution is managed. It is done through the help of faulty and admin.

This system helps the student to focus on their studies and their profile. Itincludes
assigning the work by the faculty and accordingly rewards.

This system reduces the cost and workforce required for this job. As the system is online
the students can view other profiles so they feel some competition. This makes the
system more effective.

RCTI(CE) 19 | P a g e
STUWI

3.1.2 User Characteristics

 Admin
 Faculty
 Student

 Admin: Login, Logout, Add Teachers, Add Students, Add Class, Add

Divisions, Add Subjects, Modify/Delete Teachers, Modify/Delete Students,
Modify/Delete Class, Modify/Delete Divisions, Modify/Delete Subjects

 Faculty: Mark Attendance, Upload tasks, uploadexam scheduling, and

providing information regarding other activities.

 Student: view timetable,exam scheduling, tasks, syllabus, attendance, credit

points.

RCTI(CE) 20 | P a g e
STUWI

3.1.3 Hardware & Software Requirements

Hardware requirements
 Minimum core i3 processor
 Minimum 4Gb of RAM
 250Gb free space in Hard Disk storage

Software requirements
 Server: Xampp server
 Database: SQLite
 Documentation: MS Office
 Browser: IE 8.0, Chrome 16.0
 Developing platform: Django

RCTI(CE) 21 | P a g e
STUWI

3.1.4 Assumptions and Dependencies

Assumptions

Once identified, these assumptions and constraints shape a project in specific, but
diverging ways –assumptions bring possibilities, whereas constraints bring limits.

At a minimum, as the project begins, assumptions and constraints must be defined for one
or more of the following elements:

 Key project member’s availability

 Key project member’s performance
 Key project member’s skills
 Budget limitations
 Internal process lead time
 Accuracy of the project schedule dates

Dependencies

A task dependency is a relationship between two tasks in which one task depends on the
finish of another task in order to begin. Dependencies can be created between two or
masks, tasks and tasks group or between two or more task groups.

There are four types of project planning dependencies. They establish the relationships
among the tasks. They are listed in the order most often used.

Finish To Start (FS). The first task must complete before the second task can start.
For example the task “write code module 1” must finish before the task “test code
module 1”can begin.
Finish To Finish (FF). The second task cannot finish before the first task finished.
The task “all code tested” cannot finish before the task “test code module x”
finishes.
Start To Start (SS). The second task doesn’t start until the first task starts. The task
“write training manual” must start before the task “write chapter 1 of training
manual” can start.
Start To Finish (SF). The first task must start before the second task can finish.
The task “assign coder for module 3” must start before the task “all work
assigned” can finish.
RCTI(CE) 22 | P a g e
STUWI

Dependencies establish the links, and the types of links, between all the tasks of a project.
Once we have prepared our work breakdown (product backlog), we can establish the
dependencies between to begin to identify the critical path of the project.

RCTI(CE) 23 | P a g e
STUWI

4.1 FEASIBILITY STUDY

Feasibility study is carried out when there is a complex problem or

opportunity. It is considered as the primary investigation which emphasizes
on “Look Before You Loop” approach to any project.

A feasibility study is undertaken to determine the possibility of either

improving the existing system or developing a completely new system.It
helps developers to deliver more effective output.

In feasibility study there three type of study takes place:-

 Technical Feasibility study

 Economic Feasibility study
 Operational Feasibility study

 Technical Feasibility study

In this type of study the current technology in used in an organization

such as the existing software, hardware, and personnel staff to
determine whether it will work for the proposed system or completely
new once is to be used.
The technology that was important in developing a new system such as
development tools, block-end database system were available from
within the organization.
The proposed system is capable of adding, changing, enhancing the
functionality, features etc. the proposed system is capable large storage
of data.
The back-end front-end technology has greater important for providing
an accurate, error-free, frequencies of data to be used.

 Economic Feasibility study

RCTI(CE) 24 | P a g e
STUWI

For proving that system development is economical, the feasibility

study takes place to check the cost of developing a system against the
benefits that it provides. If the costs are less and benefits are than we
can define our system to be economical developed.
User save time in searching for a particular to be purchased by simply
few mouse clicks.
The registration processing is speedier than the registered manually.
The saving of papers as all data are stored computerized.
The record is of free of human error as there is less chance of mistakes.
The above benefits are in terms of saving time, minimize error and
provide efficiency in work done.

 Operational Feasibility study

The operational feasibility is concerned with the operability of the

system after it has been installed. That is some programmer may not like
changes in their routing method of work of has fear that they will lose
their peer group.
The following areas will have the operational feasibility in proposed
project.
The organization has approved this system as their working system.
The user of the System has accepted the proposed system as their new
working system and realized the benefits of it.
The system will work in a proper way after it has been installed and the
installation process is easy to use.

4.2 SYSTEM ACTIVITY DIAGRAM

 Activity diagram is another important diagram in UML to describe aspects of the

system.
 Activity diagram is basically a flowchart to represent the flow from one activity to
another activity.
 The activity can be described as an operation of the system.
 The control flow is draw from one operation to another.

System Activity Diagram of Admission Management System

RCTI(CE) 25 | P a g e
STUWI

Start

Student login

No Yes
Invalid Info If valid Access Info without Administration Rules & Terms

Valid Information Submit

Review Applications by Administration/faculty.

Yes No
Accept Reject
valid?

Permission for Administration Not Permit Message to Student

RCTI(CE) 26 | P a g e
STUWI

4.3 USE CASE DIAGRAM

Use case diagram are valuable for visualizing functional requirement of a

system. That will be translating into the design choice and development priority. They
also help identify any internal or external factor they may influence to the system and
should be taken into the consideration. They provide good level analysis form outside the
system. Use case diagram specify the how the system interacts with actors without
worrying about the detail of how that functionality implemented.

System:-Draw the system’s boundaries using rectangle that contains use case.

System

Use case:-Draw the use case ovals. Label the ovals with verbs that represent the system’s
function.

Use case

Actor:-Actors are users of the system.

RCTI(CE) 27 | P a g e
STUWI

Simple line:-It illustrates relationships between an actor and a use case with a simple line.

Use case diagrams can be used for

 Requirement analysis and high level design.

 Model the context of a system.
 Reverse engineering.
 Forward engineering.

Login

Registration

Add task

Student
Submit task

RCTI(CE) 28 | P a g e

View task

Admin Teacher
 STUWI

4.4 SEQUENCE DIAGRAM

 Sequence diagram are sometimes called event diagram or event scenarios.

 A sequence diagram shows, as parallel vertical lines, different process or objects
that live simultaneously and as horizontal arrows, the message exchanged between
them, in the order in which they occur.
 This allows the specification of simple runtime scenarios in a graphical manner.
 A sequence diagram shows objects interaction arranged in time sequence.
 Sequence diagram are typically associated with use case realizations in the logical
view of the system under development.

Student Admin Teacher

Create account
Processes account

Requests Information Checks Student

Information

Provide Information
Checks for Information

Provides admission
decisions
Provides alumni Information if any

View or Update
Manage the profile
user profile
of all students

Admission details
Results

RCTI(CE) 29 | P a g e
STUWI

5. System Design

5.1 Database Design

5.1.1 Data dictionary

What is a data dictionary?

A data dictionary is a collection of description of the data object or items in

a data model for the benefit of programmers and others who need to refer to them.When
developing programs that use the data model, a data dictionary can be consulted to
understand where a data item fits in the structure, what values it may contain, and
basically what the data item means in real-world terms. For example, a bank or group of
banks could model the data objects involved in consumer banking. They could then
provide a data dictionary for a bank's programmers. The data dictionary would describe
each of the data items in its data model for consumer banking (for example, "Account
holder" and ""Available credit").

RCTI(CE) 30 | P a g e
STUWI

5.1.1.1 Table name: Faculty Login Table

NAME TYPE LENGTH/VALUE Constraint Description

Flogin_id Int 5 Primary key Auto Increment
Username VARCHAR 10 NOT NULL Yes
Password VARCHAR 8 NOT NULL -

5.1.1.2 Table Name: Registration Table

Column name Data type Size Constraint Description

First_ name CHAR 10 Not Null -
last_name CHAR 10 Not Null -
Reg_id CHAR 10 Not Null -
Address VARCHAR 30 Not Null -
Mobile_number INTEGER 10 Not Null -
Date of birth DATE - Not Null -
Subject_ name CHAR 10 Not Null -
Email_id INTEGER 4 Not Null -
Gender CHAR 3 Not Null -

5.1.1.3 Table Name: Student register table

Column name Data type Size Constraint Description

Student_id INT 10 Not Null Auto
incremented
First_name VARCHAR 10 Not Null -
last_name VATCHAR 10 Not Null -
Address VARCHAR 30 Not Null -
Mobile_number INTEGER 10 Not Null -
Date of birth DATE - Not Null -
Subject_ name VARCHAR 10 Not Null -
Email_id INTEGER 4 Not Null -
Gender CHAR 3 Not Null -

RCTI(CE) 31 | P a g e
STUWI

5.1.1.4 Table name: Student Login Table

NAME TYPE LENGTH/VALUE Constraint Description

Slogin_id Int 5 Primary key Auto Increment
Username VARCHAR 10 NOT NULL Yes
Password VARCHAR 8 NOT NULL -

5.1.1.5 Table Name: Task Table

NAME TYPE LENGTH/VALUE INDEX Description

Task_Id INTEGER 11 NOT NULL Auto Incremented
Task_Name VARCHAR 1000 NOT NULL -
Subject VARCHAR 10 NOT NULL -
Task_Description VARCHAR 100 NOT NULL -
Task_deadline DATE 50 NOT NULL -
Flogin_id INT 5 NOT NULL Foreign Key

5.1.1.6 Table Name: Credit Point table

NAME TYPE LENGTH/VALUE INDEX Description

Credit_Id INTEGER 11 NOT NULL Auto
Incremented
Credit_point INTEGER 11 NOT NULL -
Task_id INTEGER 6 NOT NULL Foreign Key
Flogin_id INTEGER 6 NOT NULL Foreign Key

5.1.1.7 Table name: Feedback Table

NAME TYPE LENGTH/VALUE INDEX Description

Feedback_id INT 10 NOT NULL Auto Incremented
description VARCHAR 100 NOT NULL -
Slogin_id INT 10 NOT NULL Foreign Key

RCTI(CE) 32 | P a g e
STUWI

5.1.2 ER Diagram

What is ER diagram?

An Entity Relationship (ER) Diagram is a type of flowchart that illustrates how

“entities” such as people, objects or concepts relate to each other within a system.
ER Diagrams are most often used to design or debug relational databases in the
fields of software engineering, business information systems, education and
research. Also known as ERDs or ER Models, they use a defined set of symbols
such as rectangles, diamonds, ovals and connecting lines to depict the
interconnectedness of entities, relationships and their attributes. They mirror
grammatical structure, with entities as nouns and relationships as verbs.

ER diagrams are related to data structure diagrams (DSDs), which focus on the
relationships of elements within entities instead of relationships between entities
themselves. ER diagrams also are often used in conjunction with data flow
diagrams (DFDs), which map out the flow of information for processes or
systems.ER diagrams are used to model and design relational databases, in terms
of logic and business rules (in a logical data model) and in terms of the specific
technology to be implemented (in a physical data model.)

In software engineering, an ER diagram is often an initial step in determining

requirements for an information systems project. It’s also later used to model a
particular database or databases. A relational database has an equivalent relational
table and can potentially be expressed that way as needed. ER diagrams are used
to analyze existing databases to find and resolve problems in logic or deployment.

The diagrams are used to design or analyze relational databases used in business
processes. Any business process that uses fielded data involving entities, actions
and interplay can potentially benefit from a relational database. It can streamline
processes, uncover information more easily and improve results. ER diagrams help
in analyzing databases used in business process re-engineering and in modeling a
new database setup.

Databases are today’s method of storing relational information for educational

purposes and later retrieval, so ER Diagrams can be valuable in planning those
data structures. Since so much research focuses on structured data, ER diagrams
can play a key role in setting up useful databases to analyze the data.

RCTI(CE) 33 | P a g e
STUWI

RCTI(CE) 34 | P a g e
STUWI

5.1.3 Data flow diagram

What is data flow diagram?

A data-flow diagram (DFD) is a way of representing a flow of a data of a process or a

system (usually an information system). The DFD also provides information about the
outputs and inputs of each entity and the process itself. A data-flow diagram has no
control flow, there are no decision rules and no loops. Specific operations based on the
data can be represented by flowchart.

There are several notations for displaying data-flow diagrams. The notation presented
above was described in 1979 by TOM DEMARCO as part of Structured Analysis.

For each data flow, at least one of the endpoints (source and / or destination) must exist in
a process. The refined representation of a process can be done in another data-flow
diagram, which subdivides this process into sub-processes.

The data-flow diagram is part of the structured-analysis modeling tools. When using
UML, the activity diagram typically takes over the role of the data-flow diagram. A
special form of data-flow plan is a site-oriented data-flow plan.
This project has following Data flow diagrams:

RCTI(CE) 35 | P a g e
STUWI

5.1.3.1 0-Level DFD:

RCTI(CE) 36 | P a g e
STUWI

5.1.3.2 1-Level DFD (Student):

RCTI(CE) 37 | P a g e
STUWI

5.1.3.2 1-Level DFD (Teacher):

RCTI(CE) 38 | P a g e
STUWI

5.1.3.2 1-Level DFD (Admin):

RCTI(CE) 39 | P a g e
STUWI

5.2 Flow Chart

A flowchart is a formalized graphic representation of a logic sequence, work or

manufacturing process, organization chart, or similar formalized structure. The purpose
of a flow chart is to provide people with a common language or reference point when
dealing with a project or process.

Flowcharts use simple geometric symbols and arrows to define relationships. In

programming, for instance, the beginning or end of a program is represented by an oval.
A process is represented by a rectangle, a decision is represented by a diamond and an
I/O process is represented by a parallelogram. The Internet is represented by a cloud. 

RCTI(CE) 40 | P a g e
STUWI

RCTI(CE) 41 | P a g e