SCHOLARSHIP MANAGEMENT SYSTEM

Team Members: BM10518,BM10527,BM10545 Class: II-MCA

DERPARTMENT OF COMPUTER APPLICATIONS SACRED HEART COLLEGE THIRUPATTUR

CONTENTS

1. INTRODUCTION 1.1 Purpose 1.2 Scope 1.3 Overall Description 2 .SYSTEM ANALYSIS AND DESIGN 2.1 System Analysis 2.1.1 Existing System 2.1.2 Drawback of Existing System 2.1.3 Need for Proposed System 2.1.4 Modules identification and Description 2.2 System Configuration 2.2.1 H/w Specification 2.2.2 S/w Specification 2.3 System Design 2.3.1 Database Structure 2.3.2 Use case diagram 2.3.3 Class diagram 2.3.4 Activity diagram 2.3.5 State diagram 2.3.6 Sequence diagram 2.3.7 Component diagram

3. TESTING 3.1 Error list and Risk list 3.2 Test Cases 4. SUPPORTING ARTIFACTS 4.1Team Information Sheet 4.2 S/w Project Proposal Statement 4.3 Weekly Status Report 4.4 S/w Task Plan CONCLUSIONS BIBLIOGRAPHIES APPENDIXES A. User Manual B. Data Dictionary C. Programming Coding D. UI Screen Shots E. Sample Reports

1. INTRODUCTION 1.1 Purpose

The main aim of the project is to provide the solution for scholarship management , to manage their student profile, and many details in an effective manner. The system provides the interface for to maintain the student profile ,scholarship applied details and other details.

1.2 Scope
It mainly concentrates on the process of maintaining record of student details. Based on the scholarship management Database the system able to provide Student details.
1.3 Overall Description Product Perspective

The system concentrates on student scholarship activities and some scholarship selection processes. Depending on the student applied the college scholarship management can solve the problems of student which will be helpful for them to concentrate on their students. The objective of the system is to provide easy and friendly access to the users.
Product Features

College admin can able to access information of student details about those are applied. a. Efficient access: The system will display the options for retrieving the information of student and their activities in an efficient way. b. High Availability: The site is available for 24 hours of day. So the user can use the site at any time. The system can be accessed from anywhere and at anytime.

2. SYSTEM ANALYSIS AND DESIGN

2.1 System Analysis 2.1.1 Existing System The student profile, and the whole scholarship details maintained in a desktop application. So, its accessible within the college campus. 2.1.2 Drawback of Existing System

The existing system is accessible within the campus. When the principal or administrator is out of station, they cannot access the student details from where they are. 2.1.3 Need for Proposed System The proposed system overcomes all the drawbacks stated above. When the principal or administrator is out of station, they can retrieve all the information about students from anywhere. 2.1.4 Modules Identification and Description 1. Login Module
In login module, all those who are accessing this system will be provided username and password for security and privacy purposes. So, the system is accessible if only the username and password is correct. Student Access :Username and password will be provided to each student whether they are register for the security and privacy. 2. Home Module In this module, This page have to be displaying general rules for to scholarship holders, 3. Student Profile In student profile, the details of student like personal details, family details and qualification will be present. 4. Goverment Scholarship In this module, if the students are having to apply government scholarship make its to apply with help of the this page. it can be provided to the principal or to the administrator through this module. The reply can also be provided for the scholarship applied for their government scholarship. And applied details will be viewed by admin. The scholarship are: BC ADC

 MBC Farmer Minority 5. Management Scholarship In this module, if the students are having to apply management scholarship make it to apply with help of the this page. it can be provided to the principal or to the administrator through this module. The reply can also be provided for the scholarship applied for their management scholarship. And applied details will be viewed by admin. The scholarship are: CFCA DON 6. Available scholarship The students can make use of this module to view the available scholarship details. The students will be given username and password for security and for privacy. 7. Flash news In this module. The details of current scholarship, Current scholarship Submission details Eligible details

2.2 System Configuration

2.2.1 H/w Specification

CPU Type Co-Processor Hard Disk RAM Memory Operating System Monitor

: AMD64 : Installed. : 7GB : 64 MB : Windows versions : Color monitor

Key Board

: 122 keys

2.2.2 S/w Specification

Front End : J2EE Back End : MYSQL. Design Software : Dreamweaver,

2.3 System Design

2.3.1 Database Structure

Staff Profile
Field name Regno Name Gender Dob Dept Batch mode notify hostel religion community Type Mediumint Int Varchar Varchar Date Varchar Varchar Char(10) Date Varchar Varchar 20 20 10 10 10 25 25 15 5 Size Constraints Unique Primary key Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Description Auto increment Relevant Data Relevant Data Relevant Data Customer option Relevant data Relevant data Relevant data Relevant data Relevant data Relevant data Relevant data Relevant data

scholarshipname Varchar Incomeno Varchar

Navityno communityno farmerregno mother email mobile paddress raddress sslc shsc Sug

Varchar Varchar Date Varchar Varchar Char(10) Date Varchar Varchar Varchar Varchar

20 20 10 10 10 25 25 15 5

Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null

Relevant Data Relevant Data Customer option Relevant data Relevant data Relevant data Relevant data Relevant data Relevant data Relevant data Relevant data

spg yslc yhsc yug ypg pslc phsc pug ppg fname frelationship fage foccupation fincome

Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar

20 20 10 10 10 10 10

Not null Not null Not null Not null Not null Not null Constraints null null null null null null null

Relevant Data Relevant Data Customer option Relevant data Relevant data Relevant data Description Relevant data Relevant data Relevant data Relevant data Relevant data Relevant data Relevant data

Complaints:

2.3.2 Use Case Diagram

Staff profile:

Login

Add Staff

Delete Staff Admin User

View Staff

Logout

Attendance:

Login

Enter Attendance

View Attendance Admin User

Logout

Complaints:

Login

Enter Complaint

View Staff Complaint Staff Reply Complaint User

View Reply

Logout

Leave Letter

Login

Submit Leave form

View Leave form Staff User

Logout

2.3.3 Class Diagram Staff Profile:

Teaching Staff +StaffId : Varchar

+FirstName : char +LastName : char +Dob : Date +Date of Appointment : Date +Department : Varchar +Nature of Appointment : Varchar +Gender : char +Know as : Varchar +Place of birth : char +Destination : Char +Staff type : Char +Session : Char

Add() Delete( varchar id) view()

Non Teaching Staff +StaffId : Varchar

+FirstName : char +LastName : char +Dob : Date +Date of Appointment : Date +Department : Varchar +Nature of Appointment : Varchar +Gender : char +Know as : Varchar +Place of birth : char +Destination : Char +Staff type : Char +Session : Char

Add() Delete( varchar id) view()

Attendance:
Attendance + Date : Date + Status : char + Choose Department : Varchar setattendance() View()

Leave Letter:

ATTENDANCE

#STAFFID:STRING #DATE:DATE #STATUS:STRING #ADD():VOID #VIEW():VOID

Fees Payment:

Fees + Id : Varchar + Register No : Varchar + Student : Char + Class : Varchar + Amount : Float Pay() view( Varchar id)

2.3.4Activity Diagram

2.3.5State Diagram

2.3.5 Sequence Diagram

3. Testing:
3.1 Error List and Risk List (i) Error list/Risk list
S.No

ERROR NAME
Form not displayed properly Validation part- Function name wrongly given Alignment is differ from Dreamweaver and Netbeans

SOLUTION
Tags are checked to correct the form display. Later changed by checking code Problem not yet solved

1. 2. 3.

4. 5.

Database connection problem. Date picker not working properly

Data source name was corrected. Later changed by proper assumption.

Database problem

Field names are corrected.

6.
7.

Validation problem

Changed code .

Issue/Risk Tracking: 1. Laptop unavailability One of the team member didnt have laptop. 2. Client Letter Cant able to get the letter from the client. 3.2 Test Cases

(ii) TESTING METHODOLOGIES The following are the Testing Methodologies: Unit Testing. Integration Testing.

User Acceptance Testing. Output Testing. Validation Testing.

Unit Testing: Unit testing focuses verification effort on the smallest unit of Software design that is the module. Unit testing exercises specific paths in a modules control structure to ensure complete coverage and maximum error detection. This test focuses on each module individually, ensuring that it functions properly as a unit. Hence, the naming is Unit Testing. Integration Testing Integration testing addresses the issues associated with the dual problems of verification and program construction. After the software has been integrated a set of high order tests are conducted. The main objective in this testing process is to take unit tested modules and builds a program structure that has been dictated by design.

The following are the types of Integration Testing: 1. Top down Integration This method is an incremental approach to the construction of program structure. Modules are integrated by moving downward through the control hierarchy, beginning with the main program module. The module subordinates to the main program module are incorporated into the structure in either a depth first or breathe first manner. 2. Bottom-up Integration This method begins the construction and testing with the modules at the lowest level in the program structure. Since the modules are integrated from the bottom up, processing required for modules subordinate to a given level is always available and the need for stubs

is eliminated. The bottom up integration strategy may be implemented with the following steps: The low-level modules are combined into clusters into clusters that perform a specific Software sub-function. A driver (i.e.) the control program for testing is written to coordinate test case input and output. The cluster is tested. Drivers are removed and clusters are combined moving upward in the program structure User Acceptance Testing: User Acceptance of a system is the key factor for the success of any system. The system under consideration is tested for user acceptance by constantly in touch with the prospective system users at time of developing and making changes wherever required is done in regard to the following point: Input Screen design Output Screen design Menu driven system

Testing for Output: After performing the validation testing, the next step is output testing of the proposed system, since no system could be useful if it does not produce the required output in the specified format. The outputs generated or displayed by the system under consideration are tested by asking the users about the format required by them. Hence the output format is considered in 2 ways one is on screen and another in printed format. Validation Checking: Validation checks are performed on the following fields.

Text Field: The text field can contain only the number of characters lesser than or equal to its size. The text fields are alphanumeric in some tables and alphabetic in other tables. Incorrect entry always flashes, error message.

ID 1 2

Scenario Staff Profile Attendance

Selected option

Condition the required

Expected Result Staff profile added. is is

Insert() update() Enter delete() view() fields submit()

Enter the status i.e., Attendance Present or Absent entered. Enter the complaint. Complaints accepted.

Complaints

Insert() View()

are

Numeric Field: The numeric field can contain only numbers from 1 to 10. An entry of any character flashes an error messages. The individual modules are checked for accuracy and what it has to perform. Each module is subjected to test run along with sample data. The individually tested modules are integrated into a single system. Testing involves executing the real data information is used in the program the existence of any program defect is inferred from the output. The testing should be planned so that all the requirements are individually tested.

4. SOFTWARE ARTIFACTS
4.1Software Task Planning Template

Task S.No 1. 2. 3. 4. 5. Artifacts Project planning Project planning Project planning Project planning Project planning Task Name with date Title identification Selection Module analysis Module selection Form design analysis Study Phase 2 2 3 3 3

Plan Hours

Completion Submission Date 08/12/2010 08/12/2010 08/12/2010 08/12/2010 08/12/2010

Preparation Submissio Submit phase n phase week 1 1 2 2 2 1 1 1 1 1 1st week 1st week 1st week 1st week 1st week

4.2 Software Project Proposal

1. Title: 2. Domain: 3. Tools: Operating System Technology Database CASE College Administration System College Netbeans, dreamweaver, Photoshop, flash Windows family and Linux Java Technology MYSQL Ms Visio

4. Life Cycle Model: 5. Team Role No 1 2 2 Name V.Ganesh S.Rajesh S.Rajesh

Iteration life cycle model(step by step process)

Role Planner and Designer Team Leader,Tester,Ddesigner Ttester,Designer

Functions Planning of over all projects. Managing team activities, designing modules. Managing team activities, designing modules.

(Possible Roles are Team Leader, Planer, Designer, Developer, Tester, and Deployer) 6. Team Goals i. ii. To prepare a effective dynamic web page Prepare a page with on time.

7. Team Meeting Schedule Type of meeting Weekly Status Review Meet Planning Meet Review Meet Assessment Meet (Current status of the project) Date and Time Every 5th day order(3.45 p.m) Daily (3.45 p.m) Monthly once Monthly twice

8. Problem Statement The problem of Affects The impact of which is A successful solution would College Administration system. Staff Profile, Attendance, Complaints, Fees Payment, Leave Letter. College Administration. Reduce human manual work and time.

9. Scope Managing College through online. Admin has rights to view all details of the page. 10. 11. 12. Project Staff Incharge: Prof.Rajiv Other Resource persons Reference (Previous project document, Books, Websites and etc)

1. Previous project 2. Other team members 3. Getting information through net.

4.3 Weekly Status Report

Name Rajesh.S Staff Incharge Raji Module Title Staff Profile Week Hrs Spent 8 Week Status Report No1

Date From19-12-2011 Date To 27-01-2011

Weekly Data Planned Actual

Total hours spent up to this week on technology preparation: 7 Total hours spent up to this week towards system (project) preparation: 6 Total: Completed Week 2 Hours 10

Remaining Week 9 & Hours 167

Development task completed

1. Database design and staff profile form designed.

1.

Issue/Risk Tracking
Status Not clear Not clear Not clear 1. Confusion in validation 2. Confusion in staff profile form 3. Not clear in sever validation form

Issue/Risk Name

4.3 Weekly Status Report

Name V.Ganesh Staff Incharge Raji Module Title Attendance Week Hrs Spent 8 Week Status Report No 4

Date From 5-1-2011 Date To 11-01-2011

Weekly Data Planned Actual

Total hours spent up to this week on technology preparation: 7 Total hours spent up to this week towards system (project) preparation: 6 Total: Completed Week 10 Remaining Week 9 & Hours 167 Hours 10

Development task completed

2. Database design and Attendance form designed.

2.

Issue/Risk Tracking
Status Clear 4. Confusion in Database

Issue/Risk Name

4.3Weekly Status Report

Name Rajesh Staff Incharge Raji Module Title Home Page Week Hrs Spent 15 Week Status Report No 3

Date From 5-1-2011 Date To 12-1-2011

Weekly Data Planned Actual

Total hours spent up to this week on technology preparation: 7 Total hours spent up to this week towards system (project) preparation: 6 Total: Completed Week 4 Hours 10

Remaining Week 8 & Hours 166

Development task completed 1.Database Normalization

3.

Issue/Risk Tracking
Status

Issue/Risk Name 1. No Laptop

Conclusion:
This College Administration System will be helpful for colleges to maintain their day-today activities.

Bibliographies:
www.java2s.com

www.roseindia.com

Appendixes:
a) User Manual
Staffs Page: 1. It is the home page of the College Administration System. 2. The users have to login to access the system. 3. When the staff logs in, he will be having the functionality of leave letter and complaints where the staffs can post their leave letter and can make complaints respectively. Admin Page: 1. It is the page meant only for the admin. 2. The admin has to login to access the system. 3. When the admin logs in, he or she will be having the functionality of adding, viewing, updating and deleting the staff profile, adding, viewing the attendance details, viewing the leave letter and adding the fees payment details.

b) Data Dictionary
PART-1 EXPANSION OF THE WORDS: NAME Reg.No Staff ID Email User ID Register Number Staff Identification Electronic Mail User Identification DESCRIPTION

PART-2 DESCRIPTION OF THE WORDS:

Admin - To maintain the records and the details staffs. Staff - Who post the leave letter and complaints. Type To mention the category of the user