Internal Guide Presented by

Mrs.B.Deepthi K.Swapna (09D21A0552)

Assistant Prof. K.Priyanka (09D21A0534)
C.S.E V.Navyasree (09D21A0525)

student tracking system 1/48

Abstract
 Student Tracking System software accomplishes
guest logging, resource tracking, time-keeping,
and class roster management all within centralized
tracking system software. Student Tracking System
allows an organization to log, track, analyze,
tutoring centers, classrooms, etc., which requires
visitors to be logged.

student tracking system 2/48

 Introduction
 Outsourcing some activities.

 A Web Application is developed.

 Functionality of server.

student tracking system 3/48

Existing System
 Wide-spread Businesses
 Franchise Model
 Stand-Alone Applications

student tracking system 4/48

Proposed System
 Automation of the Entire Process.
 Easy Access of Information to Management.
 Easy Access of Information to Students.

student tracking system 5/48

Modules involved

Access Management process to allow coaching

center personnel.
Coaching Center Profile and franchise information
setup and maintenance process.
Coaching Center Curriculum and schedules
setup and maintenance process.

student tracking system 6/48

Modules involved
Student enrollment and status
tracking process
Content setup and maintenance
process
Student information retrieval process
Archiving and Backup process

student tracking system 7/48

Project Requirements
 Hardware Requirements.
 Software Requirements.

student tracking system 8/48

Hardware Requirements
Content Description

HDD 20 GB (Min)
40 GB (Recommended)

RAM 1 GB (Min)

student tracking system 9/48

Software Requirements
Content Description

OS Windows XP(SP-3)
Or higher
IDE MS Visual Studio 2010

User Interface ASP .NET, HTML, CSS

Client-Side Scripting Java Script

Programming Language C#

Web Server IIS

Data Base MS SQL Server 2008 R2

student tracking system 10/48

Design

 E-R DIAGRAMS
 DATA FLOW DIAGRAMS
 UML DIAGRAMS

student tracking system 11/48

 ER-DIAGRAM:

They specify the existential entities and also the standard relations through
which the system exists and the cardinalities that are necessary for the system
state to continue.

student tracking system 12/48

 E-R DIAGRAM

MasterCourses
MasterInstitutes CourseId

InstituteId InstituteId

InstituteName CourseName

AddressDetails Contents

ContactDetails CourseFee

status NameOftheStaff

CourseSchedules
ScheduleId
StudentPayments
InstituteId
PaymentId
ScheduleName
StudentId
CourseId
InstituteId
MaxStudents
Amountpaid
ScheduleStartDate
PaidOn
ScheduleEndDate
ReceiptNumber
ClassStartTime

Batchstudents
studentId
MasterBatches
BatchId
BatchId
InstituteId
StudentName
NumberOfStudents
RollNumber
CourseId
StudentFee
Details
ContactNumber
CollegeName

student tracking system 13/48

 DATA FLOW DIAGRAMS
A data flow diagram is graphical tool used to describe and analyze
movement of data through a system.

LEVELS OF DFD:
 LEVEL-0: System Input/Output
 LEVEL-1: Subsystem Level Dataflow Functional
 LEVEL-2: File Level Detail Data Flow.

student tracking system 14/48

LEVEL-0: System Input/Output

student tracking system 15/48

Level-1 Data Flow Diagram for Admin

student tracking system 16/48

Level-1 Data Flow Diagram for Staff

student tracking system 17/48

Level - 2 Data Flow Diagram for Admin

student tracking system 18/48

Level -2 Data Flow Diagram for Staff

student tracking system 19/48

UML DIAGRAMS

 Unified Modeling Language includes a set of graphic

notation techniques to create visual models of object-
oriented software-intensive systems.

student tracking system 20/48

9 Types of UML diagrams:
 Class Diagram
 Object Diagram
 Usecase Diagram
 Interaction Diagrams
 Activity Diagram
 State Chart Diagram
 Component Diagram
 Deployment Diagram

student tracking system 21/48

 UML DIAGRAMS

USECASE DIAGRAM:

It is a behavioral diagram that shows a set of use case actors and

their relationships.

student tracking system 22/48

Use-Case diagram:

fig 1:Usecase Diagram

student tracking system 23/48

Class Diagram
MasterUsers
+UserId MasterInstitutes
MasterLocations
+LocationId
 These diagrams reveal the
+UserTYpe +LocationName
+FirstName
+LastName
+Phone
+Mobile
+Email
1
1..*
+InstituteId
+InstituteName
+AddressDetails
+ContactDetails
+Status 1..*
1
+District
+State
+Status
+view()
static design view
+LoginId +Update()
+View()

 It consists of classes,
+Password
+Update()
+Status
+View()
+Update()

CourseSchedules
+ScheduleId
+InstituteId
StudentPayments
+PaymentId
+StudentId
interfaces and
+ScheduleName +AmountPaid
+CourseId
+MaxStudents
+ScheduleStartDate
+ScheduleEndDate
+ClassStartTime
+PaidOn
+InstituteId
+ReceiptNumber
+Status
collaborations.
+ClassEndTime +view()
+LabStartTime +update()
+LabEndTime
+LabNumber MasterBatches
+Status
+BatchId
+View() +InstituteId
+Update() +NumberOfStudents
MasterCourses +CourseId BatchStudents
+Details
+CourseId +CollegeName +StudentId
+InstituteId +ScheduleId +BatchId
+CourseName +Status +StudentName
+Contents +RollNumber
+CourseFee +View() +StudentFee
+NameOfTheStaff +Update() +ContactNumber
+Status +Email
+Status
+View()
+Update() +View()
+Update()

Fig 2: Class Diagram

student tracking system 24/48

 INTERACTION DIAGRAMS:
Interaction diagrams model the behavior of use cases by
describing the way groups of objects interact to complete the
task.

 SEQUENCE DIAGRAM
 COLLABORATION DIAGRAM

student tracking system 25/48

Sequence Diagrams
Admin Home MasterUsers MasterLocations MasterInstitues
 The sequence diagram
1 : Login()
shows the ordering of the
2 : Validation()

3 : Return()
messages.
 It shows the order of the
4 : Setup() 5 : View/update()

6 : Setup()
7 : View/update()
messages that the admin
8 : Setup()
should perform.
9 : view/update()

10 : logout()

Fig 3.1: Sequence Diagram For Admin

student tracking system 26/48

Sequence Diagrams
Staff Home Master Courses Course Schedules Master Batches Batch Students Student Payments Home

1 : login()

2 : Validation()

3 : Return()

4 : Setup()

5 : View()
6 : Update()

7 : setup()

9 : update()
8 : View()

10 : Setup()

11 : View()
12 : Update()

13 : Setup()

14 : View()
15 : Update()

16 : Setup()

17 : View()
18 : Update()

19 : logout()

Fig 3.2: Sequence Diagram For Staff

student tracking system 27/48
Collaboration Diagrams 12 : Update()

9 : update()
MasterInstitutes 6 : Update()
 It models the objects relating
MasterLocations
10 : Setup() MasterUsers
to their structural behavior.
7 : Setup()

11 : View()
4 : Setup()
 This includes transmission of
8 : View()
Home 5 : View()
message between the
1 : login() 3 : Return()
objects.
2 : Validation()
Admin

13 : logout()

Home

Fig 4.1: Collaboration Diagram For

Admin

student tracking system 28/48

Collaboration Diagrams
12 : Update() 15 : Update() 18 : Update()

Master Batches Batch Students Student Payments

16 : Setup()
6 : Update()
13 : Setup()
10 : Setup()
9 : update() 11 : View() Master Courses
17 : View() 4 : Setup()
Course Schedules 14 : View()

8 : View()
Home 5 : View()
7 : setup()

1 : login() 3 : Return()

2 : Validation()
Staff

19 : logout()

Home

Fig 4.2: Collaboration Diagram For Staff

student tracking system 29/48

STATE CHART DIAGRAM:
 The state-chart diagram explains the life time of an object.
 The state chart diagram of login validation tells the actions that
should be performed by a user.
 The user should enter the details in the form, and then either he can
submit the form or reset the form.

student tracking system 30/48

State chart diagram

Fig 5: State Chart Diagram

student tracking system 31/48

ACTIVITY DIAGRAM:

 Activity diagram shows the flow of events or activities within our

system.

 It represents the business and operational workflows of the system.

student tracking system 32/48

Activity Diagram

Fig 6: Activity Diagram for User

student tracking system 33/48

 COMPONENT DIAGRAM:

 Component diagrams are used to model physical aspects of a system.

 Component diagram is used to visualize the organization and
relationships among components in a system.
 They are also used to make executing systems.

student tracking system 34/48

Component Diagram
<<artifact>> <<artifact>> <<artifact>> <<artifact>>
setuplocations setupinstitutes setup courses setup schedules

<<artifact>>
setupbatches

<<artifact>>
setupUsers <<artifact>>
ADMIN STAFF setup payments

<<artifact>>
setup students
<<artifact>>
View&update usres <<artifact>>
view&update courses
<<artifact>>
view&update batches

<<artifact>> <<artifact>>
view&update locations view&update institutes
<<artifact>> <<artifact>>
view&update schedules view&update students

<<artifact>>
view&update payments

Fig 7: Component Diagram

student tracking system 35/48

 DEPLOYMENT DIAGRAM:

 Shows the run time processing nodes and the components

that live on them.
 Deployment diagrams address the static deployment view
of the architecture.

student tracking system 36/48

Deployment Diagram

Fig 8: Deployment Diagram

student tracking system 37/48

Screen Shots
Home Page :

Fig 9.0: Screenshot for Home Page

student tracking system 38/48

Admin

Fig 9.1: Screenshot for Admin Page

student tracking system 39/48

Registration Page :

Fig 9.2: Screenshot for Registration Page

student tracking system 40/48

Contact Us Page :

Fig 9.3: Screenshot for Contact Us Page

student tracking system 41/48

Login Page :

Fig 9.4: Screenshot for Home Page

student tracking system 42/48
 TEST CASES
Home Page :

Test case1:Checking for proper alignment Priority (H,L): High

and navigation of hyperlinks
Test Objective: To check whether the alignment is correct or not and by clicking on
menu or hyperlink it must navigate to appropriate page.
Test Description :The alignment is checked and [menu] or [hyperlink] is also checked.
Requirements Verified: Yes
Test Environment : SQL Server
Test Setup/Pre-conditions: Receiver should be in connection accept state
Actions Expected
The pages are verified for redirection and Logged successfully
alignment.
Pass: Yes Condition Pass: Yes Fail: No
Problems/Issues: NIL
Output: Successfully Executed

student tracking system 43/48

Login Page :
Test case1: Validating the Admin/Staff Priority (H,L): High
login

Test Objective: To check whether the Admin/Staff has logged into the application

Test Description: The Admin/Staff enters the login data that will be verified against the
valid data in the database
Requirements Verified: Yes
Test Environment : SQL Server
Test Setup/Pre-conditions: Receiver should be in connection accept state
Actions Expected
The Admin/Staff will enter the data Logged successfully

Pass: Yes Condition Pass: Yes Fail: No

Problems/Issues: NIL
Output: Successfully Executed

student tracking system 44/48

Conclusion
 It will be a medium for the educational societies for proper
management of student’s information along with the staff ’s
information in an organized way.

 Easy flow of information between the different staff and student’s.

 The loss or misleading of information on trivial problems can be

reduced.

student tracking system 45/48

References
 FOR .NET INSTALLATION
www.support.mircosoft.com
 FOR DEPLOYMENT AND PACKING ON SERVER
www.developer.com
www.15seconds.com
 FOR SQL
www.msdn.microsoft.com
 FOR ASP.NET
www.msdn.microsoft.com/net/quickstart/aspplus/default.com
www.asp.net
www.fmexpense.com/quickstart/aspplus/default.com

student tracking system 46/48

Any queries??

student tracking system 47/48

Thank you

student tracking system 48/48