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 information management system for the college. The front/end 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 &S/access database. The web server will be %lassfish. To start working on this project environment re2uired is a server having %lassfish as web server, &S/access 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 &S/access is desirable to e6ecute this project.

2. PROJ CT O! R!I "

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&
an

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

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 ! #OPM NT O' T(IS PROJ CT)

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

2.*.

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

Software used to view hyperte6t documents. Internet $6plorer and (etscape (avigator are e6amples of browsers. *efers to the user pressing a mouse button to select an object or cause some action the leftmost button. 0yperte6t &arkup #anguage is a specification for graphical layout of a document.

<rowser !lick or !lick

!ommand to occur. "n right/handed mice with more than one button, it usually means to press

0T&#

The specification calls for the document to be stored as te6t containing a series of tags that contain formatting information.

1ava =ser )riendly &S/access

' programming language used to implement source code of our project. ;esigned to be easy to use. Simple, practicable, accommodating, understandable and accessible. &S/access database is a collection of data treated as a unit. The purpose of a database is to store and retrieve related information. 1ava Server 5age -1S5. is a technology for controlling the content or appearance of

1S5

7eb pages through the use of servlet, small programs that are specified in the 7eb page and run on the 7eb server to modify the 7eb page before it is sent to the user who re2uested it.

2.0.

O! R!I " O' DOCUM NT)

This document describes the product and its re2uirements and constraints. It provides a primarily non/technical description of the project targeted towards e6ternal audiences. This section includes information such as data re2uirements, functional re2uirements, and a general

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.1.

2 N R,# D SCRIPTION)

2.1.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.1.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.1.* 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.

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.1.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 <rowser Ser%er) 0ardware 5latform9 5III or above with *'& of @AB or above &< and AC%< or above of 0;. Software 5latform9 ;'T'<'S$/-&S/'!!$SS. 1':' 0T&# 1':'/S!*I5T 7indows/D5

A.3. SP CI'IC R 8UIR M NTS) 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 In6$ts Pro4essing O$t6$ts 'llows administrator to add/remove student/staff records Student/staff/;epartments/#iberary ;etails 'dd/remove student/staff entries in database =pdated records. ,5min Config$ration S4reen

*. S-ST M D SI2N

*.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/C driver, Server, DM#, DD#, Session and ;ata Store are e6plained.

*.2 T,R2 T ,UDI NC )

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) *;<&S and its various component modules. SE# 1ava and 1;<! Interaction ;iagrams !lasses and Interfaces

*.* PR ;R 8UISIT S)

CMS re2uires 1ava JR @.F 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<s. and have to be defined in the !#'SS5'T0 environment variable.

*.0 TOP # ! # INT R,CTION DI,2R,M)

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

Intera4tion Diagram

*.1 ,RC(IT CTUR,# STR,T 2I S)

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. .

,=stra4t %ie& of CMS

*.>..Data flo& 5iagrams)

The whole architectural structure stems from the original flow design. <elow are the #evel C ;ata )low ;iagrams -D'D... The diagrams below more accurately portray the data flow through our system. These diagrams take precedence over the diagrams in the re2uirements document. #e%el ?)

T STIN2
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 software to 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 time in 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 on/going. 's such, the methodology of the test is governed by the chosen software development methodology Software testing methods are traditionally divided into white/ and black/bo6 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 testing and structural testing. tests internal structures or workings of a program, as opposed to the

functionality e6posed to the end/user. In white/bo6 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 to testing nodes in a circuit, e.g. in/circuit testing -I!T.. 7hile white/bo6 testing can be applied at the unit, integration and system levels of the software testing 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 this method 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 any knowledge of internal implementation. The tester is only aware of what the software is supposed to do, not how it does it.HA>I <lack/bo6 testing methods include9 e2uivalence partitioning, boundary value analysis, all/pairs testing, state transition tables, decision table testing, fuzz testing, model/based testing, use case testing, e6ploratory testing and specification/based testing. Specification/based testing aims to test the functionality of software according to the applicable re2uirements. This level of testing usually re2uires thorough test cases to be provided to the tester, who then can simply verify that for a given input, the output value -or behavior., either GisG or Gis notG the same as the e6pected value specified in the test case. Test cases are built around specifications and re2uirements, i.e., what the application is supposed to do. It uses e6ternal descriptions of the software, including specifications, re2uirements, and designs to derive test cases. These tests can be functional or non/functional, though usually functional. Specification/based testing may be necessary to assure correct functionality, but it is insufficient to guard against comple6 or high/risk situations. "ne advantage of the black bo6 techni2ue is that no programming knowledge is re2uired. 7hatever biases the programmers may have had, the tester likely has a different set and may emphasize different areas of functionality. "n the other hand, black/bo6 testing has been said to be Glike a walk in a dark labyrinth without a flashlight., <ecause they do not e6amine the source code, there are situations when a tester writes many test cases to check something that could have been tested by only one test case, or leaves some parts of the program untested. This method of test can be applied to all levels of software testing9 unit, integration, system and acceptance. It typically comprises most if not all testing at higher levels, but can also dominate unit testing as well

SCR

N;S(OTS

CONC#USION)

The project entitled as College Management Information System is 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.

R ' R NC S)
@. Internet 8 7orld 7ide 7eb9 0ow to 5rogram ;eitel, 51 ;eitel. A. 7eb ;evelopment with 1ava Server 5ages <+ ;uane J.)ields and &ark '.Jolb. >. The !omplete *efernce 1avaA 0erbertSchildt. K. !ore Servlets and 1ava Server 5ages <y &arty 0all. F. 'pache 1akarta/Tomcat by 1ames %oodwill. 3. 5ractical 5ostgreSE# by 1ohn 7orsley, 1oshua ;rake