College Managment Information System

8/12/2019 College Managment Information System

1/25

1. INTRODUCTION

This project is aimed at developing a College Management Information System (CMIS)that

is of importance to either an educational institution or a college. It is difficult to prepare the

manual work to store the information about the all students, teachers as well as about workers.

This system can be used as a knowledge/information management system for the college. So

this project helps to store those type of information using computerized system.

The title of the project is !"##$%$ &'('%$&$(T I()"*&'TI"( S+ST$&

-!&IS. !&IS is an Intranet based application that aims at providing information to all the

levels of management within an organization. This system can be used as a informationmanagement system for the college.

The frontend will be 0T pages with 1ava Script for client side validation where as

all business logics will be in 1ava reside at middle layer. 'nd these layers will interact with

third layer of database, which will be &Saccess database. The web server will be %lassfish. To

start working on this project environment re2uired is a server having %lassfish as web server,

&Saccess as database and 1ava *untime $nvironment -1*$ as development environment.

The project is divided into 3 scenarios4 each scenario can be developed independently

and knowledge of 1S5 with &Saccess is desirable to e6ecute this project.

2. PROJCT O!R!I"


2/25

This document is the Software *e2uirement Specification -S*S for the !ollege

&anagement Information System project .The purpose of this document is to describe the

functionality, re2uirements and general interface of the !&IS.

2.1. #iterat$re Re%ie&

7henever we implement new system it is developed to remove the shortcomings of an

e6isting system. The computerized has more $dge over the manual system. 's we are

doing a project on !"##$%$ &'('%$&$(T So firstly we will introduce the e6isting

system, the e6isting system is based on manual system, which takes lot of time to get

performance of the test. 7e have developed new system, which is based on computer in which

work is done very easily. It is most reliable 8 time saving system while conducting some

manual work.

2.2. SCOP 'OR D!#OPMNT O' TIS PROJCT

The re2uirement of the user is to9

'ccess/ Search information.

#ogin to the system through the first page of the application

:iew/insert his/her details.

!an get help through the help option to insert/view different features of the system.

The system should give the information of ;epartments.

The system should give the information of #ibrary.

The system should give the information of #abs.

The system should give the information of !ollege $vents.

'n admin login should be present who can read as well as remove any uploads


3/25

2.*. D'INITIONS +,CRON-MS ,//R!I,TIONS

2.0. O!R!I" O' DOCUMNT

This document describes the product and its re2uirements and constraints. It provides a

primarily nontechnical description of the project targeted towards e6ternal audiences. This

section includes information such as data re2uirements, functional re2uirements, and a general


4/25

description of the product and its interaction with users from the perspective of the client.

Section > provides specific technical re2uirements as the team understands them at this time

and is intended for an internal audience. This section includes information such as e6ternal

interface re2uirements, performance re2uirements, and any other technical re2uirements needed

to design the software.

2.. NR,# DSCRIPTION

2..1. User C3ara4teristi4s

The target audience for CMIS product is the college students/staff -Technical/(on

technical .The users for this system is

'dministrator ? The Super user of the system.

2..2. Pro5$4t Pers6e4ti%e

The product will be a standalone application and may be run on multiple systems within

an Intranet network. The product will re2uire a keyboard, mouse and monitor to interface with

the users. The minimum hardware re2uirements for the product are specified in this document.

2..* O%er%ie& of '$n4tional Re7$irements

The client re2uires the following features9

'ccess/ Search information.

#ogin to the system through the first page of the application

:iew/insert his/her details.

!an get help through the help option to insert/view different features of the system.


5/25

The system should give the information of ;epartments.

The system should give the information of #ibrary.

The system should give the information of #abs.

The system should give the information of !ollege $vents.

Students can give feedback on college/staff/any other student.

'n admin login should be present who can read as well as remove any uploads

2..0 Non f$n4tional re7$irements

Client

0ardware platform9

5III or above with *'& of @AB or above &< and AC%< or above of 0;.

Software 5latform9 1ava $nabled


6/25

A.3. SPCI'IC R8UIRMNTS

2.9.1 :ternal Interfa4e Re7$irements

Simple, 'ttractive, =ser )riendly

Self!ontained, !onsistent, Self$6planatory

*obust.

2.9.2 Detaile5 Des4ri6tion of '$n4tional Re7$irements

,5ministrator Config$ration S4reen

P$r6ose 'llows administrator to add/remove student/staff records

In6$ts Student/staff/;epartments/#iberary ;etails

Pro4essing 'dd/remove student/staff entries in database

O$t6$ts =pdated records.

,5min Config$ration S4reen

*. S-STM DSIN


7/25

*.1 PURPOS

5urpose of College Management Information System (CMIS) ;esign ;ocument is to

describe the design and the architecture of CMIS. The design is e6pressed in sufficient detail so as to

enable all the developers to understand the underlying architecture of CMS. #ogical architecture of

JD/Cdriver, Server, DM#, DD#, Session and ;ata Store are e6plained.

*.2 T,RT ,UDINC

This ;esign document is intended to act as a technical reference tool for developers involved in

the development of College Management System (CMS).

This document assumes that you have sufficient understanding of the following

Con4e6ts

*; Interaction ;iagrams

!lasses and Interfaces

*.* PR;R8UISITS

CMS re2uires 1ava [email protected] or higher. Since CMS is written in 1ava, it can run on any platform

that supports the 1ava runtime environment @.F or higher. The compiled files are contained in 1ava

'rchives -J,R


8/25

*.0 TOP #!# INTR,CTION DI,R,M

#ogical architecture of JD/Cdriver, Server, DM#, DD#, Session and ;ata Store


9/25

Intera4tion Diagram

*. ,RCITCTUR,# STR,TIS

The architectural design of a software project is simply the design of the entire software

system. This includes the hierarchy of the modules and also which modules are present in the

system. ' good architectural design will create a clear and fair balance between cohesion -each

module has only one distinct purpose, coupling -no two modules depend completely on each

other, abstraction -seeing modules in full and not in detail, hierarchy -logical modules stem

from others and partitioning -logically grouping modules together of the software modules.

*.9. #ogi4al !ie& it provides the user with an abstract view of the overall system functionality. .


10/25

,=stra4t %ie& of CMS

*.>..Data flo& 5iagrams

The whole architectural structure stems from the original flow design.


11/25

TSTIN

Software testing is an investigation conducted to provide stakeholders with information about

the 2uality of the product or service under test. Software testing can also provide an objective,

independent view of the softwareto allow the business to appreciate and understand the risks of

software implementation. Test techni2ues include, but are not limited to the process of

e6ecuting a program or application with the intent of finding software bugs-errors or other

defects.

Software testing can be stated as the process of validating and verifying that a computer

program/application/product9

meets the re2uirements that guided its design and development,

works as e6pected,

can be implemented with the same characteristics,

and satisfies the needs of stakeholders.

Software testing, depending on the testing method employed, can be implemented at any timein the software development process. Traditionally most of the test effort occurs after the

re2uirements have been defined and the coding process has been completed, but in the'gile

approaches most of the test effort is ongoing. 's such, the methodology of the test is governedby the chosen software development methodology

Software testing methods are traditionally divided into white and blackbo6 testing. These two

approaches are used to describe the point of view that a test engineer takes when designing test

cases.

"3ite;=o:testing -also known as clear bo6 testing, glass bo6 testing, transparent bo6 testingand structural testing tests internal structures or workings of a program, as opposed to the
http://en.wikipedia.org/wiki/Softwarehttp://en.wikipedia.org/wiki/Software_bughttp://en.wikipedia.org/wiki/Agile_software_developmenthttp://en.wikipedia.org/wiki/Agile_software_developmenthttp://en.wikipedia.org/wiki/Softwarehttp://en.wikipedia.org/wiki/Software_bughttp://en.wikipedia.org/wiki/Agile_software_development


12/25

functionality e6posed to the enduser. In whitebo6 testing an internal perspective of the

system, as well as programming skills, are used to design test cases. The tester chooses inputs

to e6ercise paths through the code and determine the appropriate outputs. This is analogous totesting nodes in a circuit, e.g.incircuit testing-I!T.

7hile whitebo6 testing can be applied at theunit,integration andsystemlevels of the softwaretesting process, it is usually done at the unit level. It can test paths within a unit, paths between

units during integration, and between subsystems during a system?level test. Though thismethod of test design can uncover many errors or problems, it might not detect unimplemented

parts of the specification or missing re2uirements.

/la4@;=o:testing treats the software as a Gblack bo6G, e6amining functionality without anyknowledge of internal implementation. The tester is only aware of what the software is

supposed to do, not how it does it.HA>


13/25

SCRN;SOTS


14/25


15/25


16/25


17/25


18/25


19/25


20/25


21/25


22/25


23/25

CONC#USION


24/25

The project entitled asCollege Management Information Systemis the system that deals with

the issues related to a particular institution.

This project is successfully implemented with all the features mentioned in system re2uirements

specification.

The application provides appropriate information to users according to the chosen service.

The project is designed keeping in view the day to day problems faced by a college.

;eployment of our application will certainly help the college to reduce unnecessary wastage of

time in personally going to each department for some information.

'wareness and right information about any college is essential for both the development of student

as well as faculty. So this serves the right purpose in achieving the desired re2uirements of both the

communities.


25/25

R'RNCS

@. Internet 8 7orld 7ide 7eb9 0ow to 5rogram ;eitel, 51 ;eitel.

A. 7eb ;evelopment with 1ava Server 5ages

College Managment Information System

Documents

Transcript of College Managment Information System