Subbu PPT Final

8/13/2019 Subbu PPT Final

1/65

Kid Care Management System(GAGANA)

Final ProjectInternal Review

School of ComputingDepartment ofMaster of Computer ApplicationsName: K.Lakshmi SubbaraoReg.No: 101FD01007MCA III year

Guide: K.Santhi Sri Asso. Prof.


2/65

AbstractThe purpose of the project entitled as KIDCARE M

SYSTEM (GAGANA)is to provide single window solutions Child/Day care Centers for administration and effective of Kid care Institution. It provides an effective platform between management, faculty, parent and child. Tprovides online administrative tools that integrate the care system of an institution. All the functionalities of

centers are integrated into this single application to prodata at once.


3/65

Table of contents1.Introduction2.System Analysis3.Design4.Implementation5.Test Cases6.Conclusion7.Future Enhancement8.Bibiliography


4/65

1.Introduction

GAGANA is a web application which can be acanywhere through internet, it provides great reliabimanagement, students and parents to interact through th

GAGANA we presently have modules to manage amanagement in primary schools of a group of institutapplication we have different access levels, as per the reroutes the access levels related to that particular user. levels are restricted to the particular level of authenticatipermissions are to be given by the admin only.


5/65

1.1 Existing System:

In the existing system, all the data is maintained sepadifferent modules, due to this lot of paperwork is utilized tthe other departments that some modifications have beenparticular record. Every time we must modify all the detaidifferent modules when we have changes made to a recordperson.


6/65

1.2 Proposed System:

Proposed system is a single window solution for all man institution, Interaction between students, parents, teacmanagement made easy, lots of data can be stored & mathe systems, so that it is available for future reference, lotwork and human effort is reduced due to the integration omodules in one platform, there is no need to inform the o

departments about the changes of the record.


7/65

1.3 Feasibility:1.3.1 Technical Feasibility:

GAGANA is Technically feasible, because it was dethe platform independent language PHP, and database Mbe deployed on any platform. This is multi useapplication.

1.3.2 Operational Feasibility:GAGANA is an operationally feasible because it

human effort and lot paper work. The functionalities we project are simply understandable by the user and thealso made easy in this project.


8/65

1.3 Feasibility:1.3.3 Economical Feasibility:

GAGANA is Economically feasible, because it was dethe open sources language PHP, and database MySqdeployed on any platform. The developing cost of the sybe economical because there is no much investmdeveloping tools.


9/65

2.System Analysis2.1 Functional and Non Functional Requirements:2.1.1 Functional Requirements: Admin manages the access levels of all users

All the modules should be grouped together

Admin only can add new modules to the group

In user level there are to be student and parent logins

In management level there has to be chairman, principal and teacher Each and every login must have different access levels as per their le

The user must only have the view permissions only.

In management level there is view and some modify and insert permitaking attendance are provided.

Co


10/65

2.System Analysis2.1.2 Non Functional Requirements:1. Reliability

2. Portability

3. Extensibility

4. Interoperability

5. Maintainability


11/65

2.2 Hardware and Software Requirements:Software Requirements:

Web Presentation : HTML, CSS

Client side Scripting : JavaScript, JQ

Programming Language : PHP

Backend Database : My SQL

Operating System : Platform IndepHardware Requirements:Processor : Pentium IV (later)

RAM : 1 GB

Hard Disk : 80 GB


12/65

2.3Modules2.3.1 Entertainment Module:In this module 2 types of logins.

In Managerial Level Login either chairman or principtype of entertainments and they can upload files relaentertainment (Example: games to play, songs to hear or etc.).

In kid login they can play the games and songs avaientertainment module.


13/65

2.3 Modules2.3.2 Attendance Module:In this module 2 types of logins.

In Managerial login teacher can take attendance, princhairman can view all the details about the attendance.

Chairman can view by Group/Branch/Class/Section/Indiv

Principal can view by Branch/Class/Section/Individual

Teacher can view by Class/Section/Individual

In general login kid can only view his own attendance parent can view their kids attendance by date and betwee


14/65

3.Design


15/65

Control Flow DiagramFailure

Failure Success

Start

LoginLoginFailed

Register

GeneralLogin

ManagerialLogin

AdminLogin

LoginType

GAGANAadmin

General orManagerial

UserType

Principal Chairman

KidParentAdmin


16/65

UML DiagramsUse Case Diagram


17/65

Class Diagram


18/65

Sequence Diagrams

Admin:


19/65

Sequence Diagrams

Charman:


20/65

Sequence Diagrams

Principal:


21/65

Sequence Diagrams

Teacher:


22/65

Sequence Diagrams

Parent:


23/65

Sequence Diagrams

Kid:


24/65

Activity Diagram


25/65

Entertainment Module Database Tables Design:

Cbc_entertainment

Cba_entertainment_types

Field Data Type KeyId int Primary

ent_type_id Tinyint Foreign

file_type_id Tinyint Foreign

name Varchar

Field Data Type KeyId Tinyint Primary

Name varchar Primary


26/65

Entertainment Module Tables:

Cbb_file_types


Name varchar Primary


27/65

Entertainment Module Database Table Relations:


28/65

Attendance Module Database Tables Design :

adb_user_levels

Ada_user_types


Name Varchar

User_type_id Tinyint foreign

Field Data Type KeyId

Tinyint

Primary

Name Varchar


29/65

Attendance Module Tables:

Bfe_staff

Field Data Type KeyId Int Primary

School_branch_id Smallint Foreign

User_id int Foreign

Subject_id Int Foreign

Staff_salary Int Foreign

Staff_experience Int Foreign

Staff_role varchar

Blood_group Varchar

Gender Varchar

Address Varchar

Phone_no bigint Foreign


30/65


Aad_school

Aab_medium

Field Data Type KeyId Smallint Primary

School_id Smallint Foreign

Branch_name Varchar

Address Varchar

Attendance_times tinyint Foreign


Code Varchar Primary

name Varchar


31/65


Aah_class


Board_id Tinyint Foreign

Medium_id Tinyint Foreign

School_branch_id Smallint Forign


Name

Varchar

Attendance_times Tinyint Foreign

Day_periods Varchar

Study_periods Varchar


32/65


Aai_section

Afa_hour


class_id Smallint Foreign


Name Varchar


Name Varchar Primary


33/65


Aam_subjects


class_id Smallint Foreign

Allotment_type_id Tinyint Foreign

Subjects_name_id Smallint foreign


34/65


Aff_attendance

Field Data Type KeyId Int Primary

Date Date

Sction_id Smallint Foreign

Hour_id Tinyint Foreign

Staff_id Int Foreign

Subjects_id

Int

Foreign

Absenties Blob

Leaves Blob

Attendance_times Tinyint Foreign

Attendance Module Database Table Relations :


35/65

Attendance Module Database Table Relations :


36/65

4. Implementation


37/65


38/65


39/65


40/65


41/65


42/65


43/65


44/65


45/65


46/65


47/65


48/65


49/65


50/65


51/65


52/65


53/65


54/65


55/65


56/65


57/65


58/65


59/65

5.Test CasesTest Case Id Test Case Expecting Behavior Exhibiting Behavior


60/65

Test Case Id Test Case Expecting Behavior Exhibiting Behavior1 Entering the wrong user id

and password

Incorrect Details Incorrect Details

2 Clicking on submit button

without entering any details

The page should process,

and it should generate

prompt message "Pleaseenter Details "

Resulted message showed.

3 Entering the user details in

wrong positions by user in add

user option

Error message will be

displayed

Error message is

displayed

4 Go to login screen enter "User

Id" and without entering

Password tries to click on

"OK" button.

The page should process,

and it should generate

prompt message "Please

enter 'Password' "

same as expected result

5 Access Levels working Should work correctly Working correctly

6.Conclusion


61/65

The KID CARE MANAGEMENT SYSTEM GAGANA iapplication and keeps the data in a centralized way which

to all the users simultaneously. It is very easy to manadata in database. This application software has beesuccessfully and was also tested successfully by taking tis user friendly, and has required options, which can be utuser to perform the desired operations.

7.Future Enhancement


62/65

It is not possible to develop a system that marequirements of the user. User requirements keep chan

system is being used. As the technology emerges, it isupgrade the system and can be adaptable to desired Because it is based on object-oriented design, any furtcan be easily adaptable. Based on the future security isscan be improved using emerging technologies.


63/65


64/65

Thank You.

Any queries.?


65/65

Subbu PPT Final

Documents

Transcript of Subbu PPT Final