Sie sind auf Seite 1von 65

Kid Care Management System

(GAGANA)
Final Project Internal Review

School of Computing Department of Master of Computer Applications Name: K.Lakshmi Subbarao Reg.No: 101FD01007 MCA III year
Guide: K.Santhi Sri
Asso. Prof.

Abstract
The purpose of the project entitled as KID CARE MANAGEMENT SYSTEM (GAGANA) is to provide single window solutions for complete Child/Day care Centers for administration and effective management of Kid care Institution. It provides an effective platform for interface between management, faculty, parent and child. This software provides online administrative tools that integrate the entire Child care system of an institution. All the functionalities of a Kid care centers are integrated into this single application to provide all the data at once.

Table of contents
1.Introduction 2.System Analysis 3.Design 4.Implementation 5.Test Cases 6.Conclusion 7.Future Enhancement 8.Bibiliography

1.Introduction
GAGANA is a web application which can be accessed from anywhere through internet, it provides great reliability to the management, students and parents to interact through this website. In GAGANA we presently have modules to manage a kid care management in primary schools of a group of institutions. In this application we have different access levels, as per the user login it reroutes the access levels related to that particular user. The access levels are restricted to the particular level of authentication. All these permissions are to be given by the admin only.

1.1 Existing System: In the existing system, all the data is maintained separately for different modules, due to this lot of paperwork is utilized to inform to the other departments that some modifications have been made to particular record. Every time we must modify all the details in different modules when we have changes made to a record of a person.

1.2 Proposed System:

Proposed system is a single window solution for all modules in an institution, Interaction between students, parents, teachers, and management made easy, lots of data can be stored & maintained in the systems, so that it is available for future reference, lots of paper work and human effort is reduced due to the integration of all modules in one platform, there is no need to inform the other departments about the changes of the record.

1.3 Feasibility: 1.3.1 Technical Feasibility: GAGANA is Technically feasible, because it was developed with the platform independent language PHP, and database MySQL. It can be deployed on any platform. This is multi user accessible application.

1.3.2 Operational Feasibility:


GAGANA is an operationally feasible because it reduces the human effort and lot paper work. The functionalities we used in the project are simply understandable by the user and the calculations also made easy in this project.

1.3 Feasibility: 1.3.3 Economical Feasibility: GAGANA is Economically feasible, because it was developed with the open sources language PHP, and database MySql. It can be deployed on any platform. The developing cost of the system is also be economical because there is no much investment for the developing tools.

2.System Analysis
2.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 level

The user must only have the view permissions only.


In management level there is view and some modify and insert permissions like taking attendance are provided.
Cont..

2.System Analysis
2.1.2 Non-Functional Requirements:
1. 2. 3. 4.

Reliability Portability Extensibility Interoperability

5.

Maintainability

2.2 Hardware and Software Requirements: Software Requirements:

Web Presentation
Client side Scripting Programming Language Backend Database Operating System

:
: : : : Pentium IV (later) 1 GB 80 GB

HTML, CSS
JavaScript, JQuery PHP My SQL Platform Independent

Hardware Requirements:
Processor RAM Hard Disk : : :

2.3Modules
2.3.1 Entertainment Module: In this module 2 types of logins. In Managerial Level Login either chairman or principal can add type of entertainments and they can upload files related to the entertainment (Example: games to play, songs to hear or dance and etc.). In kid login they can play the games and songs available in the entertainment module.

2.3 Modules
2.3.2 Attendance Module: In this module 2 types of logins. In Managerial login teacher can take attendance, principal and chairman can view all the details about the attendance. Chairman can view by Group/Branch/Class/Section/Individual 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 and the parent can view their kids attendance by date and between dates.

3.Design

Start

Control Flow Diagram


Failure Success

Login Failed

Failure

Login

Register

General Login

Managerial Login

Admin Login

Principal

Chairman

Manager

Teacher

GAGANA admin

Login Type

General or Managerial

User Type

Admin

Parent

Kid

UML Diagrams
Use Case Diagram

Class Diagram

Sequence Diagrams
Admin:

Sequence Diagrams
Charman:

Sequence Diagrams
Principal:

Sequence Diagrams
Teacher:

Sequence Diagrams
Parent:

Sequence Diagrams
Kid:

Activity Diagram

Entertainment Module Database Tables Design:


Cbc_entertainment
Field Id ent_type_id file_type_id name Data Type int Tinyint Tinyint Varchar Key Primary Foreign Foreign

Cba_entertainment_types
Field Id Name Data Type Tinyint varchar Key Primary Primary

Entertainment Module Tables:


Cbb_file_types
Field Id Name Data Type Tinyint varchar Key Primary Primary

Entertainment Module Database Table Relations:

Attendance Module Database Tables Design :


adb_user_levels
Field Data Type Key

Id
Name User_type_id

Tinyint
Varchar Tinyint

Primary

foreign

Ada_user_types
Field Data Type Key

Id
Name

Tinyint
Varchar

Primary

Attendance Module Tables:


Bfe_staff
Field Id School_branch_id User_id Subject_id Staff_salary Staff_experience Staff_role Blood_group Gender Address Phone_no Data Type Int Smallint int Int Int Int varchar Varchar Varchar Varchar bigint Foreign Key Primary Foreign Foreign Foreign Foreign Foreign

Attendance Module Tables:


Aad_school
Field Id School_id Branch_name Address Attendance_times Data Type Smallint Smallint Varchar Varchar tinyint Foreign Key Primary Foreign

Aab_medium
Field Id Code name Data Type Tinyint Varchar Varchar Key Primary Primary

Attendance Module Tables:


Aah_class
Field Id Board_id Medium_id School_branch_id Code Name Attendance_times Day_periods Study_periods Data Type Smallint Tinyint Tinyint Smallint Varchar Varchar Tinyint Varchar Varchar Foreign Key Primary Foreign Foreign Forign Primary

Attendance Module Tables:


Aai_section
Field Id class_id Code Name Data Type Smallint Smallint Varchar Varchar Key Primary Foreign Primary

Afa_hour
Field Id Name Data Type Tinyint Varchar Key Primary Primary

Attendance Module Tables:


Aam_subjects
Field Data Type Key

Id
class_id Allotment_type_id Subjects_name_id

Smallint
Smallint Tinyint Smallint

Primary
Foreign Foreign foreign

Attendance Module Tables:


Aff_attendance
Field Id Date Sction_id Hour_id Staff_id Subjects_id Absenties Leaves Attendance_times Data Type Int Date Smallint Tinyint Int Int Blob Blob Tinyint Foreign Foreign Foreign Foreign Foreign Key Primary

Attendance Module Database Table Relations :

4. Implementation

5.Test Cases
Test Case Id 1 2 Test Case Entering the wrong user id and password Clicking on submit button without entering any details Expecting Behavior Incorrect Details The page should process, and it should generate prompt message "Please enter Details " Exhibiting Behavior Incorrect Details Resulted message showed. Result Pass Pass

Entering the user details in wrong positions by user in add user option
Go to login screen enter "User Id" and without entering Password tries to click on "OK" button. Access Levels working

Error message will be displayed

Error message is displayed

Pass

The page should process, and it should generate prompt message "Please enter 'Password' " Should work correctly

same as expected result

pass

Working correctly

Pass

6.Conclusion
The KID CARE MANAGEMENT SYSTEM (GAGANA) is web-based application and keeps the data in a centralized way which is available to all the users simultaneously. It is very easy to manage historical data in database. This application software has been computed successfully and was also tested successfully by taking test cases. It is user friendly, and has required options, which can be utilized by the user to perform the desired operations.

7.Future Enhancement
It is not possible to develop a system that makes all the requirements of the user. User requirements keep changing as the system is being used. As the technology emerges, it is possible to upgrade the system and can be adaptable to desired environment. Because it is based on object-oriented design, any further changes can be easily adaptable. Based on the future security issues, security can be improved using emerging technologies.

7.Bibliography

www.php.net www.phpdeveloper.com

www.w3schools.com
www.mysql.com www.smarty.net PHP The Complete Reference by Steven Holzner PHP Manual
By K.Lakshmi Subbarao
III MCA

Thank You.

Any queries.?

Das könnte Ihnen auch gefallen