Contents

1. Abstract 2. About The Project 2.1. Login module 2.2. Admin Module 2.3. User Module 3. Environmental Characteristics 3.1.1. Hardware Specification 3.1.2. Software Specification 4. Goals of Implementation 5. Functional Requirements 6. Non functional Requirements 7. SDLC of Institute Management System 7.1. Requirement Analysis 7.2. Software Design 7.2.1. GUI Design 7.2.2. Database Design 7.3. Coding 7.4. Testing 7.5. Implementation and Maintenance 8. Conclusion 9. Bibliography

Page no.
2 2 2 3 3 3 3 3 4 4 5 6 6 8 8 16 26 93 93 93 94

1. Abstract
Today Institutes are one of the primary sources to provide education around the world. Every institute provides various courses to their students and charge specific amount of fees for each course. A student can register himself with the institute to study a specific course. In this era of globalization the students are more concerned about their education, which in turns attracts the students towards the institutes. Therefore it is becoming a tedious and error prone task for the institutes to keep track of all the students as well as the courses manually. Institutes are looking for an automated system for their daily tasks, which are as follows. Registering new students. Collecting fee and making entry for the same. Viewing and editing the details of the existing students. Searching for a specific student details from a wide range of students.

2. About The Project

Institute Management System is divided into the following module.

2.1. Login Module:The Login Module is important from the security aspect of the Institute Management System. In the project the task of the authenticating the user is implemented using the Login module. Every user must go through this module to access various operational links. The user is authenticated by the entered login name and password. Only after successful verification, a user is allowed to access other operational links of the application.

2.2. Admin Module:The Admin Module is meant for the use of the administrator to add the details of new courses offered by the institute and also view and edit the details of existing courses. The administrator can also create other users for the project with limited access to the project functionalities. Apart from this, an administrator can also view and edit student details that are registered with the
2

institute to learn a specific course. Moreover, the administrator is also allowed to change his existing password.

2.3. User Module:The User Module is intended for the general users who have limited access to the system. This Module enables the user to register new students with the institute and also collect the course fee installments from the students. After registering the student and collecting the fees it also generates an automated pay-in slip with all relevant information on it. Apart from this, the user can also view details of the students and change their own login password to ensure the security of the Institute Management System.

3. Environment characteristics 3.1.1. Hardware Specification:Processor Speed RAM Hard Disk Key Board (104 keys) : Intel Pentium IV : 2.66 GHZ : 1 GB : 80 GB : Standard

3.1.2. Software specification:Operating System : Windows XP /07 Platform Tools Database IDE : .NET 3.5 : WPF, XAML : SQL SERVER 2005 : Visual Studio 2008, SQL Server Management Studio Express Development Kit : SDK

4.

Goals Of Implementation Our goal of implementation is making it adaptive to the other environments
rather that Windows.

To

increase the longetivity of the product by updating it time to time according to the user requirement.

5. Functional requirements
R.1-Administrator Aspect:R.1.1-create user Description-The administrator can create new user by entering the user details such as users name, login ID and Password into the database. Input-Users detail Output-Generate the user R.1.2- view and edit student details Description-The administrator can view and edit student details by entering the registration number. R.1.3- Edit course details Description- The administrator can edit the course details by accessing the database. R.1.4- change password Input-Current Password and new password Output-New Password R.2-User Aspect:R.2.1- View student detail Description-When then user enters student name or Registration number then the will show the student details.
4

R.2.2- student registration Description-It prompts the user to enter the details of a student and store in the database. R.2.3- collect fee Description-When the user enters the fee amount received, then the system stores it in the database. R.2.4-Change Password Input-Current Password and new password Output-New Password

6. Non-functional Requirements 6.1. Maintainability:The system should be capable of adapting new features according to the customer requirement.

6.2. 6.3. 6.4. 6.5. 6.6.

Security:Only registered user, who has authentication to use the system, can be able to access the system. Portability:The software should be easily portable to other machine.

Performance:It should be capable of giving access to the user without Degradation of system performance. Robust:The system should be capable of handling exception as well as memory management efficiently.

7.

SDLC of Institute Management System

A software development follows a life cycle which is termed as Software Development Life Cycle (SDLC). SDLC generally contails the following Requirement analysis

7.1. 7.2. 7.3. 7.4. 7.5.

The Requirement Analysis Phase Software design Coding Testing Implementation and Maintenance

7.1. The Requirement Analysis Phase:The Institute Management System project helps the institute administration to manage the task of student registration, fee collection and maintenance of the student information in the database. The requirements that need to be fulfilled are as follows: Administrator can add, view and edit course details Administrator can view and edit student details Administrator can create and delete other users for the system Other users can register students with the institute Other user can collect fee from the student Other user can view student details but cannot edit them Both administrator and other user can change their passwords

Requirement gathering

Quick design

Prototype development

Refine requirements incorporating customer suggestions

Build Prototype

Customer evaluation of Prototype

Acceptance by Customer Design

Iterative development Test

Implement

Maintain

(Prototype model)
7

7.2. The Software Design Phase

The software design phase of any software project recommends the way of implementing the requirements specified by the user.

7.2.1.

Graphical User Interface Design

Database Design
LoginTable:Column
AdminName(PK)

Data type
varchar(15)

Allow null values

No

Description
Unique login name for the Administrator that is Administrator by default
Password for the Administrator that is admin by default

AdminPassword

varchar(15)

No

UsersInfo:Column
UserName LoginName (PK)

Data type
varchar(40) varchar(40)

Allow null values

No No

Description
Name of the user other than Administrator Unique login name for the user other than Administrator Password for the user other than Administrator

UserPassword

varchar(20)

No

Coursesinfo:Column
CourseName(PK) CourseDuration CourseFee FirstInstallment SecondInstallment

Data type
varchar(30) varchar(50) bigint bigint bigint

Allow null values

No No No No No

Description
Unique course name offered by the institute Duration of the course in years + months format Total fees of the course First installment of the course fee Second installment of the course fee

StudentRegistration:Column
RegistrationNumber (PK) StudentName StudentAddress ContactNumber DateOfBirth Qualification CourseEnrolled CourseDuration CourseFee FirstInstallment FirstInstallmentStat us SecondInstallment SecondInstallmentSt atus BalanceFee

Data type
varchar(100) varchar(100) varchar(1000) bigint varchar(25) varchar(20) varchar(30) varchar(50) bigint bigint varchar(15) bigint varchar(15) bigint

Allow null values

No No No No No No No No No No

Description
Unique Registration number for each student Name of the student Address of the student Mobile number of the student Date of birth of the student Highest qualification of the student Course that student want to study. Name of the course stored in CourseInfo table Duration of the enrolled course from the CourseInfo table Total fee of the course First Installment of the course Status of first installment(Paid or Unpaid) Second Installment of the course Status of second installment(Paid or Unpaid) Fee amount to be paid

yes
No

yes yes

10

ER Diagram

Name Type 1 Has

Institute
1 Address

M Provide M Course Fee M Teaches Name COURSE Second Installment Course Duration Course Name M First Installment

M EXPERTS

Register Expert Id Experience Student Name Qualification Address Contact Number Student Registration Number Address Qualification 1 Date of Birth

STUDENT
Contact Number

11

DFD Level 0

Admin/user

0 IMS

Task Performed

DFD Level 1
User Name and Password Admin/user 0.1 Login Task Performed

LoginTable

DFD Level 2
Admin Admin User Detail 0.2.1 Create User

UsersInfo

12

User Name Admin

0.2.2 View user Detail

Report

UsersInfo

Student Reg.No. Admin

0.2.3 View Student Detail Report

StudentRegistration

Course Details Admin 0.2.4 Add NewCourse

CoursesInfo

0.2.5 Update Course Details 13

Current Password Admin 0.2.6 Change Password New password

LoginTable

Fee Collection User 0.2.7 Collect fee 0.2.8 Student Registration Report

StudentRegistration

StudentRegistration

14

State Chart Diagram

Check Login Id and Password

Authentication Rejected Unsuccessful

Authentication Accepted Successful

User Administrator Task to Perform

Add User

View and edit student details

Edit Course details

Change Pass word

15

Activity Diagram
User
Login Collect fee

Account Section/User

Registration

Student details

Report

Allot ID

View Student details

Generate Report

Register Course

First Installment

Second Installment

Log Out

16

Class Diagram

17

Use Case Diagram

Authentication

<<include>>

Login

Admin

Change Password

User

Log out

Create user

New Student registration <<extend>> <<extend>> View Student details <<extend>>

View user details

View and edit Student details

Collect fee

<<extend>> Update Course details 18 Pay slip

7.3. The Coding Phase:For developing the Institute Management System you have to use Microsoft Visual Studio 2008 for designing the interface, making validation on the designed interfaces and creating connection to the database. You need to use Microsoft SQL Server 2005 as database server.

7.4. The Testing Phase:The testing of the project ensures that the written code and the connections created in the project functions properly. We need to check data is properly stored in the database and is retrieved and updated whenever required.

7.5. The Implementation and Maintenance Phase:This is the last stage of SDLC. The Institute Management System project can be implemented in the real world environment after we complete all the phases of SDLC. The maintenance of the project refers to updating the project as per the required changes in the implemented system. While running the project in the real world environment, several loopholes and areas of improvement may be discovered. The user can also suggest changes and report the problem faced in the system based on which the project is updated to meet the users requirement.

8. Conclusion
With the completion of our project we conclude that it has achieved its purpose and is up to our satisfaction. It will enable an organization to manage its tedious and error prone daily task in a simpler, easier and better way. We wish that using the automated system instead of manual system will be beneficial in the fruitful operation of the organization.
19

9. Bibliography

20