1.input Design

STUDENT PORTAL MCA 2016-19
1.INPUT DESIGN
The input design is the process of converting the user oriented inputs into the computer
based format. The goal of designing input data is make the automation as easy and free from
errors as possible. For providing a good input design for the application, easy data input and
selection features are adopted.
The Student Portal is a web based system that recommends the students to satisfies all
their academic purposes. Any person with basic knowledge to use the computer can make use of
this system.
1.1.Major input screens
The following are the major input screen
 Login
The input screen is used for logging into the system by providing username and
password.
 Add College
This function will help to add colleges.
 Add Course
This function will help to add the courses of colleges.
 Add Subjects
List out all the subjects for a particular course.
 Add Student
Adding of student details for them to acess the site
 Add Teachers
This function would handle the academic criteria’s of students.
SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 1

2.OUTPUT DESIGN
The output design has been done so that the results of processing should be
communicated to the user. Effective output design will improve the clarity and performance of
outputs. Output is the main reason for developing the system and the basis on which they will
evaluate the usefulness of the application.
Output design phase of the system is concerned with the convergence of information to
the end user-friendly manner. The output design should be efficient, intelligible so that system
relationship with the end user is improved and they’re by enhancing the process of decision-
making.
2.1.Major output screens
The following are the major output screens used.
 View colleges
View the set of colleges under Kannur University.
 View courses
View the courses based on the college selected.
 View subjects
View the allotted subjects on each course.
 Views and helps the students academic details.
Students are provided with all academic functionalities.

3.DATABASE DESIGN
The database for “STUDENT PORTAL” has been designed to achieve integrity of the
system. A database is a collection of information and is systematically stored in tables in the
form of rows and columns. The table in the database has unique name that identifies its contents.
The database in turn is further described in detail giving all the fields used with the data types,
constraints available, primary key and foreign key.
Database design is used to manage large bodies of information. For developing an

effective database, we will have to fulfill certain condition such as :
 Control Redundancy
 Ease Of Use
 Data Independence
 Accuracy and Integrity
 Privacy and Security
 Performance
Data types and its description:
Fields in database table have a data type. Some of the data types used in database table
are explained below.
a) Integer
One optional sign character (+ or -) followed by at least one digit (0-9). Leading
and trailing blanks are ignored. No other character is allowed.
b) Varchar
It is used to store alphanumeric characters. In this data type we can set the
maximum number of characters up to 8000 ranges by default SQL server will set the size
to 50 characters large.
c) Date/Time
Date/Time data type is used for representing data or time.
d) Float :Float data type is used for representing floating point values

DATABASE DESIGN
1.Table name :tbl_dept

Description :table with college details
Column name Data type Constraint Description
did Int Primary key Id to identify
departments
dname varchar(25) Not null College name
dno varchar(25) Not null Department number
deptde varchar(20) Not null Department details
2.Table name :admin

Description :Admin with allotted subjects
Id int(255) Primary key Id to identify admin
username varchar(255) Not null Name of user
password varchar(255) Not null Password
3. Table name: course

Description:course entering table for students
crse_id int(255) Primary key Id to identify each
course
did int(255) Foreign key Department Id
crse_no int(255) Not null Course number
crse_name varchar(255) Not null Course name
level varchar(255) Not null Course level
ie.PG,UG

4.Table name :tbl_notification

Description :Notification regarding academic purposes
Noted int(11) Primary key Id to identify each
notifications
crse_id int(11) Foreign key Course Id
did int(11) Foreign key Department id
Topic_id int(11) Foreign key Topic id
title varchar(255) Notification title
content varchar(255) Not null Content of notification
Date Datetime Not null Date and time of
notification
5.Table name :comments
Description :storing uploaded assignments
comment_id int(255) Primary key Id to identify each
comments by student
id int(255) Foreign key Student Id
course_id int(255) Foreign key Course Id
Topic_id int(255) Foreign key Topic Id
content varchar(255) Foreign key Comments about
teacherand course
6.Table name :tbl_uploadmaterial

Description :storing uploaded study materials

upload_id int(255) Primary key Id to identify each
uploaded items
crse_id int(255) Foreign key Course Id
Topic_id int(255) Foreign key Teachers Id
Topic_name varchar(255) Not null Topic of material
material varchar(255) Not null Uploaded study
material
7. Table name: tb1_course
Description:course entering table for students which provide
certificates
course_id int(255) Primary key Id to identify each
course
course_category int(255) Foreign key Category of course
course_name int(255) Not null Course number
Tid varchar(255) Not null Teacher id
duration varchar(255) Not null Course duration
8.Table name :tbl_addsylabus

Description :Adding syllabus for each courses

sylbid int(11) Primary key Syllabus id
course_id int(11) Foreign key Certificate Course Id
duration int(11) Foreign key duration
sylabus varchar(255) Not null Notification title

9.Table name :teachers

Description :teachers registering details

Tid int(11) Not null Teacher id
name varchar(255) Not null Teacher name
place varchar(255) Not null Place
email varchar(255) Not null Email
qualification varchar(255) Not null Teacher’s
qualifications
experiance varchar(255) Not null Teacher’s experience
certificates
certificate varchar(255) Not null Teacher’s
qualification
certificates
10.Table name :student

Description :student registering details


id int(11) Not null student id
name varchar(255) Not null student name
place varchar(255) Not null Place
email varchar(255) Not null Email
11.Table name :topic

Description :storing topics details

Topic_id int(11) Primary key Topic id
did int(11) Foreign key Department id
crse_id int(11) Foreign key Course id
level varchar(255) Not null Topic level
Topic_no varchar(255) Not null Topic number
Topic_name varchar(255) Not null Topic name

4.DATA FLOW DIAGRAM (DFD)

A Data Flow Diagram (DFD) is a graphical representation of the “flow” of data through
an information system. DFDs can also be used for the visualization of the data processing
(structured design). On a DFD, data items flow from an external data source or an internal data
store to an internal data store or an external data sink, via an internal process.
 Process
A process shows a transformation or manipulation of data
flows within the system. A process transforms
incoming data flow into outgoing data flow.
 External Entity
External entities are outside the system, but they either supply
input data into the system or use system output. External
entities are represented by a rectangle.
 Data Flows
A data flow shows flow of information from source to
destination. A data flow is represented by a line, with
arrowhead showing the direction of flow.
 Data Source
A data store indicates to which database a particular data is

Context Level DFD
Level 0
ADMIN
request response
request E-
request
STUDENT TEACHER
LEARNIN
G
response response

Level 1. 1
ADMIN
Description
1,2.category details
3.family details
4.hotel details

5,6.cuisine details
7,8.course details
9.feedback details
10,11,12.category_id+category_name
13,14.family_id+login_id+name+image+age+gender+address+contact+email+veg+taste
15,16.hotel_id+login_id+name+image+city+area+owner+license+gst
17,18,19.cuisine_id+cuisine_name
20,21,22.course_id+course_name
23.feedback_id+user_id+feedback
Level 1. 2
FAMILY

Description
1,2,3.recipe details
4,5.hotel details

6.category details
7.registration details
8.comment details
9.like action details
10,11,12.recipe_id+name+title+photo+user_id+category_id+cuisine_id+course_id+
skill level+veg+serving+prep time+cook time+ingredients+instructions
13,14.hotel_id+login_id+name+image+city+area+owner+license+gst
15.category_id+category_name
16,17.family_id+login_id+name+image+gender+address+contact+email+veg+taste
18.comment_id+family_id+recipe_id
19. action_id+family_id+recipe_id+action
Level 1.3
HOTEL

Description
1,2.recipe details

3,4.food details
5.category details
6. cuisine details
7.course details
8.hotel registration details
9,10,11.recipe_id+name+title+ photo+ user_id+ category_id+ cuisine_id+ course_id+ skill

level+ veg+ serving+ prep time+ cook time+ ingredients+instructions
5.UML DIAGRAMS

5.1.USECASE DIAGRAM
Use case diagrams model the functionality of a system using actors and use cases. Use
cases are services or functions provided by the system to its users. A use case diagram depicts
actors, use cases, and the relationships among them. Use case is a software engineering term
that is equivalent to a social scientist's notion of task.
Basic Use Case Diagram Symbols and Notations
 Use Case
Draw use cases using ovals. Label the ovals with verbs that
represent the system's functions.
 Actors
Actors are the users of a system. When one system is
the actor of another system, label the actor system with
the actor stereotype.
 System
Draw your system's boundaries using a rectangle that

contains use cases. Place actors outside the system's boundaries.
 Relationships Illustrate relationships between an actor and a use case

<<include>> with a simple line. For relationships among use cases,
e>> use arrows labeled either "uses" or "extends." A "uses"

<<exclude>>
relationship indicates that one use case is needed by another in
>>
order to perform a task. An "extends"relationship indicates
alternative options under a certain usecase.
Usecase Diagram for Admin

Approve students
Add department details
View department
details
Edit department details
Approve teachers
Approve Study materials
Add Course details
Edit Courses
ADMIN
Add Courses
Delete Courses
Delete Departments

Usecase Diagram for Student
Register
View Profile
Edit Profile
View teachers
profile
View Topics
View Updates
Download study
material
Student Chat with Teachers
View Accomplishments
Demand for Courses
View Departments
Add Comments
View Comments

Usecase Diagram for Teachers
Register
View Profile

5.2.ACTIVITY DIAGRAM
Activity diagrams, which are related to program flow plans (flowcharts), are used to
illustrate activities. In the external view, we use activity diagrams for the description of those
business processes that describe the functionality of the business system.
 Action
The action can possess input and output information The output of one
action can be the input of a subsequent action within an activity. Specific
actions are calling other actions, receiving an event, and
sending signals.
 Edge (Control Flow)
Edges, represented by arrows, connect the individual

components of activity diagrams and illustrate the control
flow of the activity.Within the control flow an incoming arrow starts
a single step of an activity; after the step is completed the flow
continues along the outgoing arrow. A name can be attached to an
edge (close to the arrow).
 Merge Node
Its purpose is the merging of flows. The inputs are not synchronized; if
a flow reaches such a node it precedes at the output without waiting for
the arrival of other flows.

 Fork
For the branching of flows in two or more parallel flows we use a

synchronization bar, which is depicted as a thick horizontal or
vertical line
 Initial Node
The initial node is the starting point of an activity. An activity can have
more than one initial node; in this case several flows start at the
beginning of an activity:
 Activity Final Node
The activity final node indicates that an activity is completed. An

activity diagram can have more than one exit in the form of activity
final nodes

Activity Diagram
Admin
Login
no
Valid
?
yes
Approve Add Add Add study Provide

Teachers Departmen Courses Materials Certificat
ts es
Approve Manage Manage Manage

students Departme Courses. Study
nts Materials

 Student
Login
no
Valid
?
yes
View download
View View teachers study Add
Profile Departmen profile Materials comment
ts s
Manage View Chat Demand

Profile Courses with Study
teachers Materials

Teachers
Login
no
Valid
?
yes
Provide Chat with

View View courses students Provide
Profile Departmen certificate
ts s
Manage Upload
View View
study
Profile Courses comments
material
s

5.3.SEQUENCE DIAGRAM
Sequence diagrams are a type of diagram in the Unified Modeling Language (UML) that
shows interactions over time. Sequence diagrams are the dynamic modeling diagram which
focuses on the interactions occurring within the system. Sequence diagrams specifically focus
on the "lifelines" of an object and how they communicate with other objects to perform a
function before the lifeline ends.
Sequence diagrams are made up of the following elements:
 Object
This box shape represents a class, or object, in UML.They
demonstrate how an object will behave in the context of the
system.
 Activation boxes
Represents the time an object needs to complete a task.
When an object is busy executing a process or waiting
for a reply message, use a thin gray rectangle placed vertically
on lifeline.
 Actors
Represented by a stick figure, actors are entities that are both

interactive with and external to the system.
 Lifeline Represents the passage of time as it extends downward.

This dashed vertical line shows the sequential events that
occur to an object during the charted process. Lifelines may
begin with a labeled rectangle shape or an actor symbol.
 Message
Represented by a solid line with a solid arrow head.
Synchronous message This symbol is used when a sender must wait for a response

to a message before it continues. The diagram should show

both the call and the reply.
Represented by a solid line with a lined arrowhead.

Asynchronous message Asynchronous messages don't require a response before the
sender continues. Only the call should be included in
the diagram.
Represented by a dashed line with a lined arrowhead, these Reply

message messages are replies to calls.

Sequence Diagram

6.ENTITY RELATIONSHIP DIAGRAM (ER)

Entity relationship diagram is used in modern database software engineering to illustrate
logical structure of database. It is a relational schema database modeling method used to model a
system and approach. This approach commonly used in database design. The diagram created
using this method is called E-R diagram.
The E-R diagram depicts the various relationships among entities considering each object
as entity. Entity is represented as diamond shape and relationship is represented as rectangle. It
depicts the relationship between data objects. The E-R diagram is the relation that is used to
conduct the data modeling activity.
Basic ER Diagram Symbols and Notations
 Entity
Entity is the thing which we want to store information
An entity represents an objects defined within the information
system about which you want to store information.
 Relationship
A relationship is named connection or association between
entities used to relate two or more entities with some common
attributes of meaningful interaction between the object.
 Attributes
Attributes are the properties of the entities and relationship.
Descriptor of the entity. Attributes are elementary pieces of
information attached to an entity.
 Key Attributes
The Key attribute is used to denote the property that uniquely
identifies an entity (the Entity Key), and which is mapped to
the Primary Key field in a database.

ER Diagram

1.input Design

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

1.input Design

Caricato da

Copyright:

Formati disponibili

STUDENT PORTAL MCA 2016-19

1.1.Major input screens

The following are the major input screen

SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 1

2.1.Major output screens

The following are the major output screens used.

View the set of colleges under Kannur University.

View the courses based on the college selected.

View the allotted subjects on each course.

 Views and helps the students academic details.

Students are provided with all academic functionalities.

SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 2

Database design is used to manage large bodies of information. For developing an

Data types and its description:

SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 3

1.Table name :tbl_dept

2.Table name :admin

3. Table name: course

SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 4

4.Table name :tbl_notification

6.Table name :tbl_uploadmaterial

SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 5

Description :storing uploaded study materials

8.Table name :tbl_addsylabus

Column name Data type Constraint Description

SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 6

9.Table name :teachers

Column name Data type Constraint Description

10.Table name :student

SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 7

Column name Data type Constraint Description

11.Table name :topic

Column name Data type Constraint Description

SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 8

4.DATA FLOW DIAGRAM (DFD)

SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 9

Context Level DFD

SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 10

SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 11

SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 12

SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 13

9.like action details

SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 14

SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 15

8.hotel registration details

9,10,11.recipe_id+name+title+ photo+ user_id+ category_id+ cuisine_id+ course_id+ skill

SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 16

Basic Use Case Diagram Symbols and Notations

Draw your system's boundaries using a rectangle that

 Relationships Illustrate relationships between an actor and a use case

e>> use arrows labeled either "uses" or "extends." A "uses"

Usecase Diagram for Admin

SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 17

Add department details

Edit department details

Approve Study materials

Add Course details

SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 18

Usecase Diagram for Student

Student Chat with Teachers

Demand for Courses

SCHOOL OF INFORMATION SCIENCE AND TECHNOLOGY 19

Usecase Diagram for Teachers