Software Requirements Specification - EKALAVYA...

Central System for Admission to Universities (CSAU) Version: <1.0>

Software Requirements Specification Date: 2/3/2008

<document identifier>

spiritIIITM, 2008 Page 1

Central System for Admission to Universities (CSAU)

Software Requirements Specification

Version 1.0

Team

spiritIIITM

Team Members

Chandra Prakash

Dhirender Sharma

Rahul Kala

Rahul Khandelwal





Revision History

Date

Version Description Author

2/3/2008 1.0 This was the first major version of SRS. It contain the initial analysis of the system

spiritIIITM





1) Introduction:

1.1) Purpose: The aim of University Admission System is to computerize University admission process

for higher education courses. Its basic objectives are to extend their reach to geographically scattered students, reducing time in activities, centralized data handling and paperless admission with reduced

manpower. Its other factors are cost cutting, operational efficiency, consist view of data and integration

with other institutions. Main challenges are effectively sync internal and external operations in such a manner that job can be finished within time limit and integration with different agencies on an agreed

upon common data format.

1.2) Scope:

University can approach to the geographically scattered students .

Trace all of the University Courses and the seats in each college falls under the University.

Common interface on web accessed by everyone.

Online selling of admission forms along with online submission and online payment.

Central database having all information about candidates, colleges, courses, seats & hostels.

Sending call letters to online users on e-mail, call letter will contain centre for examination based

on preferences given by candidate drawn out from database.

Online examination question paper setting by professors.

Marks details & verifications of filled forms for eligibility checking through online contact with

Universities/Boards.

Online onsite examination along with evaluation of answers given by students & marks allotment.

Preparation of merit list for each category and each course.

Online onsite counseling procedure having various phases ie. I, II,III phases.

College, seat allotment along with hostel allotment based on status of colleges information stored

in database.

On each event all information is stored in central database controlled by authorized persons &

online available for candidates.

1.3) References:

IEEE SRS Format

The J2EE 1.4 Tutorial by Sun Microsystems.

Complete Refrence in Java, Prentice Hall India

IBM DeveloperWorks

Rational Application Developer Tutorial, IBM Publications

http://publib.boulder.ibm.com/

http://www.iitd.ernet.in/jee/

http://www.aieee.nic.in/

http://gate.iitm.ac.in/

http://www.jnu.ac.in/

Kick-start your Java apps, Part 1 & 2: Free software,fast development; Sing Li (IBM Developer Kit)

Wiley Publishiers, Java 2 Enterprise Edition 1.4 Bible Prentice Hall India

Deitel n Deitel, Java How to Program, 4th Edition





1.4) Project Team & Work Role:

S.No. Member Name Work Distribution

1 Chandra Prakash User Interface(UI) design , Web Design & Development, Java

Server Pages (JSP)

2. Dhirender Sharma Xml Technologies ,Java Mail and Application Development

3. Rahul Kala Algorithmic Development ,Architectural Design , Data

Structure and Application Development

4. Rahul Khandelwal Database technologies , survey and analysis* model and user

feedback

* survey and analysis were done by all members

1.5) Technologies used:

Database Server: DB2 (v9.1, IBM)

Web Server: Websphere (IBM)

Application Server: WAS (Websphere Application Server, IBM)

WSAD: Development Tool

IDE: Eclipse, Rational Application Developer

J2EE: Application Architecture (Sun Microsystems)

Language: J2EE, SQLJ

XDoclet

Sun Java Mail APIs

Jbuilder

1.6) Definitions, Acronyms and Abbreviations :

Subject opted: while filling admission form , subject selected by candidates for their respective

course. Candidate will give entrance examination only of these subjects.

Payment transaction: Transaction between candidate account to University account as a

payment of purchasing of form. It can be either through credit card or Demand Draft .

Personal details: Details of candidate such as name, qualification, phone number, address, e-

mail address etc.

Online Onsite Examination: The examination will be conducted on examination centers in

online manner. The Question paper will be downloaded on the day of the exam from the central database on each center prior to the examination. Once the examination over the database

containing the answers will be uploaded back to the central database. This is done so that it can

overcome any internet connection faults.

Counseling Phases: Counseling would be conducted in three phases ie. I ,II,III. Eligible

candidate would go to the next phase only when he didn’t get any college in current phase

counseling .

HTML: Hypertext Markup Language is a markup language used to design static web pages.

EJB: Enterprise Java Beans.





J2EE: Java 2 Enterprise Edition is a programming platform part of the Java Platform for

developing and running distributed multitier architecture Java applications, based largely on

modular software components running on an application server.

DB2: DB2 Database is the database management system that delivers a flexible and cost effective

database platform to build robust on demand business applications.

WAS: Web sphere application server is an application server that runs business applications and

supports the J2EE and web services standards.

WSAD: Web sphere studio application developer is a toolkit which is designed for the creation of

more complex projects, providing fully dynamic web application utilizing EJB’s . This consist of EJB tools , CMP ,data mapping tools & a universal test client that is designed to aid testing of

EJB’s.

HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol between web

browser & a Web Server.

HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer).

TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of communication protocols

used to connect hosts on the Internet. TCP/IP uses several protocols, the two main ones being

TCP and IP.

SMTP: Simple mail transfer protocol ,used to send emails

TC: transfer certificate .The certificate issued by the previous institute/school to the candidates

DD: Demand Draft .One of the mode of the payment during registration and counseling time.

CC: Credit Card .Another mode of the payment during registration and counseling time.

1.7) Time Plan:

As the project scheduling is very important for successful completion of the project. We followed the

Waterfall Software Development model for developing the application. So we have scheduled the

project plan as follows:

S. No. Phase Name Approx.

Days

Actual

Days

Calendar Schedule

1. Analysis 30 28 Jan 5 – Feb 4

2. Design 35 37 Feb 5 – March 10

3. Code 40 Ongoing March 11 - April 20

4. Test 20 To be done April 21 – May 10

5. Deploy / Deployment Script 5 To be done May 11 – May 15

6. Documentation/End-User-

Support

- Ongoing March 1 – May 15

We have developed all Module (names give below) of the project, the development plan for different

modules with different teams is as follow:

S.No. Module Name Features and Front end Team Members

1. University Site Exam details , Online form (*.jsp)

Chandra Prakash ,

Dhirender Sharma

2. Admin Add User, Course, College; Set user

Permission, Login, (*.jsp)

Dhirender Sharma,

Chandra Prakash

3. Candidate Form view, update ,get detailed exam Rahul kala ,





result (*jsp)

Rahul Khandelwal

4. Form Controller\ Main

Counselor

Form update, Add candidate ; XML

interactions ; Allotment of roll no &

exam center; Merit list generation

(*jsp)

Dhirender Sharma ,

Rahul kala

5. Head Exam Controller Question paper assignments to

Professors; Add ,modify & delete

Questions (*.jsp)

Dhirender Sharma ,

Rahul Kala

6. Main Paper Setter Add ,modify & delete Questions ; Regulate Assistant paper setter of

respective subject(*.jsp)

Rahul Khandelwal , Dhirender Sharma

7. Assistant Paper Setter Add ,modify & delete Questions (*.jsp)

Dhirender Sharma ,

Rahul Khandelwal

8. Local Exam Conductor Download question paper and upload

Student Solution through Xml interaction ; Student verification (*.jsp)

Rahul kala ,

Chandra Prakash

9. Examination Module Login ;Take Examination (*.Application)

Rahul kala , Rahul Khandelwal

10. Local Counselor Document verification ; Counseling fee

submission(*.jsp)

Chandra Prakash

11. Counseling Module Login ,choice available; Student

preferences fulfillment ; form 1 and

form2 fulfillment (*Application)

Chandra Prakash ,

Rahul kala

1.8) Intended Audience The software is intended to be used by all universities. It may be used for the end-to-end

solutions to admission. It may also be used for the organizations that conduct entrance

examinations like AIEEE, GATE etc. This software has various modules. Individual modules

may be used for specific purposes. The examination module can be used as a tool for online

exam conductance, paper setting or result declaration by any organization in any field. Being the

first tool of its kind to serve as an integrated tool, the applicability is huge.

2) Overall description It describes the general factors that affect the product and its requirements.

2.01) Product Perspective:





The web pages (JSP/XHTML) are present to provide the user interface on customer client side.

Communication between customer and server is provided through HTTP/HTTPS protocols.

The Client Software is to provide the user interface on system user client side and for this TCP/IP

protocols are used

On the server side the web server and application server for hosting the application and SMTP

server is used for mail and database server is for storing the information

2.02) Software Interface:

Client on Internet: Web Browser, Operating System (any)

Client on Intranet: Client Software, Web Browser, Operating System (any)

Web Server : WAS, Operating System (any)





Data Base Server : DB2, Operating System (any)

Development End: WSAD (J2EE, Java, Java Bean, Servlets, HTML), DB2, OS (Windows), Web Server.

2.03) Hardware Interface:

Client Side

Processor RAM Disk Space

Internet Explorer

6.0

Pentium II at 500

MHz

64 MB 1 GB

Firefox 1.5 Pentium II at 500

MHz

64 MB 1 GB

Server Side

Processor RAM Disk Space

Web-sphere

application server

V5.0

Pentium III at 1

GHz

512 MB 1GB

DB2 V9.1 Pentium III at 1

GHz

512 MB 1 GB(Excluding

data size)

2.04) Communication Interface:

Client on Internet will be using HTTP/HTTPS protocol.

Client on Intranet will be using TCP/IP protocol.

2.05) Product Function:

Central System for Admission to Universities (CSAU) containing following modules:

Candidate form fulfillment: In this module candidate’s admission form details & payment

details will be stored in database automatically (in case of online form fulfillment & payment)

and manually (in case of form & DD of payment sent by post).

Online onsite entrance examination: In this module, question papers will be downloaded at

examination centre from central database by Local exam controller & stored in local database then examination will be conducted onsite & database containing answers will be uploaded to

central database through XML interface.

Preparation of merit list: Candidates answers are evaluated & marks are allotted .On the basis

of marking, merit list is prepared according to Category and course. Candidates will be able to see merit list on site of university.

Counseling: In this module counseling of selected students will be done on counseling centers. It

will contain three phases, student will be forwarded to next phase only if he is not able to get any





college in current phase. Document verifications is done at counseling center & related

information is stored in central database.

Counseling result & hostel allotment: In this module student will be assigned college on the

basis of his preference & merit. & hostel would be allotted based on information stored in

database. Hostel would be allotted along with the allotment of the college.

2.06) User Characteristics:

Every user should be comfortable of working with computer and net browsing. She/he must have basic knowledge of English too. The administrators of various phases must be aware of basic network

security and must handle the passwords carefully.

2.07) Constraints:

GUI is only in English.

Login and password is used for identification of authorized persons.

Limited to HTTPS/HTTP.

Examination City entered should be perfect.

The static and the dynamic content should be synchronized.

No checks of time line are being implemented.

The course and sub-course and subject id’s in counseling and examination application are present

as static data in the source code rather than the configuration file.

There is no scope of configuration the application to include things like group decision,

progressively negative marking in case of MBA admission.

As we consider the Category system in the system. A SC\ST\OBC PH candidate can only claim

reservation only on PH or general.

The Xml transactions of any examination are done in a go. Separate interaction of any

college\center is not possible.

ALL the colleges need to have a interface / facility for XML transaction.





2.08) Use-Case Model Survey:

USE CASE DIAGRAM





1. Form Controller: Responsible for managing candidate information, managing exam centers

allotment, call letters preparation & delivery, documents verifications through XML transition and prepare merit list.

Fill form details: Form controller can fill form details of candidates in case of form submitted by

post.

Generate Roll No.: Form controller will assign unique roll no. to each candidate by using an

algorithm, which will be used as a identity of candidate for all further processes.

Allocate Exam center: Form controller will allocate exam centre to all candidates on the basis of

his preferences & attach it to call letter.

Candidate communication: All communication to candidates will be handled by form controller

including call letter delivery to candidate’s email and to home by post.

Online Marks Verification: Form controller will contact to previous school or university of

candidate in order to verify marks & documents through XML transition.

Form details management: All form details are managed by form controller. It can also be

updated. He can add/delete/modify/view entries.

Generate merit list: He will evaluate the answer sheet based on an algorithm, generate merit list

& put it on main website for candidates.

2. Candidate: Candidate will fill form, appear for examination on allocated examination centre, go

through counseling procedure & report to the corresponding allotted college.

Form control: Admission form will be filled & submitted by candidate along with payment

details .Candidate can view; update his form details at any time using private code given to him

by acknowledgement letter.

Give Examination: Candidate will appear for entrance examination on examination centre

allotted to him.

Merit List: Candidate can view his rank & eligibility in merit list on main website of University.

Appear for counseling: Eligible candidate will appear for counseling on provided counseling

centre. In counseling he/she will select colleges of his/her choices & submit it.

Report College: Candidate will report to the allotted college on the given date.

Hostel Allotment: The candidate can view the hostel and room number allotted to him

3. Assistant papersetter: Assistant papersetter will add questions, modify questions, delete question &

view questions of the allotted subject and submit to the main paper setter.

Add questions: Assistant papersetter will add questions to the question paper.

Modify questions: Assistant papersetter will modify question in the question paper.

Delete questions: Assistant papersetter will delete questions in the question paper.

View question paper: Assistant papersetter will view question paper.

4. Main papersetter: Main papersetter is having responsibility to finalize the questions for his subject. So Main paper setter will accept, remove, modify questions, and view questions.





Accept questions: Main papersetter will accept questions prepared by subordinates (Assistant

paper setter).

Reject questions: main papersetter could reject questions.

View all questions: Main papersetter can view all prepared questions.

Manage new questions: Main papersetter could add questions from his side as per the need of

scenario.

5. Head exam controller: Head exam controller will supervise question paper setting of all courses. He/she can view questions, modify questions, delete questions.

View questions: Head exam controller could view questions set prepared by all papersetter.

Modify questions: head exam controller have access to modify questions.

Delete questions: Head exam controller could delete questions as per need & finalize question

paper.

6. Local exam conductor: Local exam conductor will be having responsibility of conducting the

examination successfully. She/he will verify candidate’s verification, download question paper and

upload results through XML.

Document verification: Local exam conductor will verify document (admit card) of students

before examination.

Download Question Paper: Local exam conductor will download question papers from central

database prior to examination.

Upload Results: Local exam conductor will upload answers of candidates from local database to

central database.

View merit list: Local exam conductor will get merit list from central database.

7. Local Counselor: Local counselor will be engage in documentation verification, download detail database, upload student preferences and fill counseling payment information.

Document verification: Local counselor will verify document (admit card, counseling letter,

previous mark sheets and other certificates) of students before counseling.

Fill Counseling Payment information: Local Counselor will fill counseling Payment

information.

Download detail databases: Local counselor will download the database of the option form of

the college and branch from central database prior to counseling through XML to overcome any

network or technical fault.

Upload Student preferences: Local counselor will upload preference of candidates from local

counseling center database to central database through XML where seat will be allocated by main counselor.

8. Main Counselor: Main counselor is Form Controller itself. He will be engaged in managing detail database, seat allotment, hostel allotment and communication to college.

Manage detail database: Main counselor will be engaged in managing detail database of student

preferences send from local counseling centers.





Seat allotment: On the basis of candidate seat preferences the main counselor will allocate seats

through an algorithm. This information will be sent to head exam controller to display it online.

Hostel allotment: The main counselor will also allot hostel, according to the college’s room

availability.

College Communication: The main counselor will be engage in communication with college.

The college will provide him the information of the branch, seat and hostel.

9. College: The College will provide the information of the number of the seats, branch and hostel to the University through XML.

College Communication: The College will be engaged in communication with University. The

college will provide the information of the branch, seat and hostel.

Hostel allotment: The main counselor will allot hostel ,according to the colleges rules

2.09) Assumptions and Dependencies:

The various colleges are ready to interact with the code based only based on the xml schema

defined.

The past record of the candidate can be verified online by the respective board by the predefined

xml schema .The contact details of the board is already available.

The detail of Branches, hostels, and information can not be changed once the allotment

process starts.

Administrator is created in the system already.

Roles and tasks are predefined.

3) Specific Requirements:

3.1) Use-Case Reports:

i) Form Controller: Responsible for managing candidate information, managing exam centers

allotment ,call letters preparation & delivery and documents verifications.

Form details management: All form details are managed by form controller. It can also be

updated .

Fill form details: Form controller will fill form details of candidates in case of form submitted by

post.

Generate Roll No.: Form controller will assign unique roll no. to each candidate by using an

algorithm, which will be used as a identity of candidate for all further processes.

Allocate Exam center: Form controller will allocate exam centre to all candidates on the basis of

his preferences & attach it to call letter.

Candidate communication: All communication to candidates will be handled by form

controller including call letter delivery to candidate’s email and to home by post.

Online Marks Verification: Form controller will contact to previous school or university of

candidate in order to verify marks & documents.





Form Details Management:

Name of use case: View Details Description: Form controller will View the information filled by the candidate at the registration time.

Preconditions:

Form controller is already logged in.

Normal flow of events:

The form controller will search the Candidate Information. Query will be submitted.

Relevant output will be displayed .

Alternate flow of events: None. Post Condition: None.

Activity diagram of view details:

Name of use case: ADD Details

Description: Form Controller will add the details given by candidate ,in the database(In case of submission by post).

Preconditions:

Form Controller is already logged in.

Information regarding courses, exam centres, subjects for examination are already available.

Normal flow of events: Form controller will select the course chosen by candidate.

Form controller will add the Form details or Payment details(DD details) of candidate.

Query will be submitted. Relevant output (Confirmation) will be displayed.

Alternate flow of events: None.

Post Condition: Confirmation/Error message will be shown to the form controller.





Activity diagram of ADD details:

Name of use case: Modify Details

Description: Form Controller will search the details of candidate & then modify them(if required).

Preconditions:


Candidate’s information has already been inserted.


Form controllers will Search& Select details of candidate.

Form controller will modify the details & log will be created.

Query will be submitted.Relevant output will be displayed.

Alternate flow of events: None.

Post Condition: None.

Activity diagram of Modify details:

\

Name of use case: Delete Details

Description: Form Controller will search the details of candidate & then Delete them(if required).

Preconditions:




Form controller will Search& Select details of candidate. Form controller will Delete the details & log will be created.

Query will be submitted.

Relevant output will be displayed . Alternate flow of events: None.






Activity diagram of Delete details:

Fill form details:

Allocate Exam center:

Generate Roll No.:





Candidate communication:

Description: Form Controller will send acknowledgement of form , Call letter for examination, merit list,

counseling call letter , counseling result all either by email or by post or by both.

Preconditions:


Email id of candidate is valid.

Postal address of candidate is valid.


Form controller will check the mode of form fulfillment & payment of candidate. If candidate has submitted the form & payment online then acknowledgement will be sent by email

only.

In all other cases, acknowledgement will be sent by post & if email id is available then it will be sent

on email also.Alternate flow of events: None.


Activity diagram of Student Communication:





Online Marks Verification: this will be done through XML interaction.

Send Informationof verification

Receive informationfor verification

Online Marks Verification

Activity diagram of Receive information for verification:





ii) Candidate: Candidate will fill form, appear for examination on allocated examination centre, go through counseling procedure & report to the corresponding allotted college.

Form control: Admission form will be filled & submitted by candidate along with payment

details .Candidate can view; update his form details at any time using private code given to him by acknowledgement letter.

Give Examination: Candidate will appear for entrance examination on examination centre

allotted to him.

Merit List: Candidate can view his rank & eligibility in merit list on main website of University.

Appear for counseling: Eligible candidate will appear for counseling on provided counseling

centre. In counseling He/She will select colleges of his/her choices & submit it.

Report college: Candidate will report to the allotted college on the given date.

Form Control Student:





Name of use case: Modify form by candidate

Description: Candidate will be provided a code by which he can login & make changes to his form.

Preconditions:


Candidate knows his secret code


Candidate will enter his form no along with secret code. Candidate will modify details of his form.(If required)

Query will be submitted.

Relevant output will be displayed. Alternate flow of events: None.


Activity diagram of Modify details:

Name of use case: View form by candidate

Description: Candidate will be provided a code by which he/she can login & view his/her form.

Preconditions:


Candidate knows his secret code.






Candidate will enter his form no along with secret code.

Candidate will view details of his form. Query will be submitted.

Relevant output will be displayed.


Activity diagram of view details:

Name of use case: Give Examination

Description: Candidate will be appear for examination at the examination centre & follow procedures of

examination.

Preconditions:

Candidate is having admit card.


Candidate will mark his answer from alternatives. At the time completion , candidate will submit his answers.

Then he can view his score of that examination.


Activity diagram of Give Examination:

Name of use case: Merit List

Description: Candidate will view the merit list on the main website of university.

Preconditions:. Candidate must enter his roll no.


Candidate will enter his course code & roll no.

Candidate will see his rank & marks, eligibility for counseling.

Alternate flow of events: If roll no is invalid, error will be generated.


Activity diagram of Merit List:





Name of use case: Appear for Counseling

Description: Candidate will select colleges according to his preferences.

Preconditions:. Candidate must enter his roll no & must be eligible for counseling.


Candidate will enter his roll no.

Candidate will enter his preferences of colleges on the basis of vacant seats availability.

Candidate will submit his selections & log will be generated.

Alternate flow of events:

If Seat are not available for particular college candidate is selecting, error will be generated.


Activity diagram of Appearing for counseling:

iii) Assistant paper setter: Assistant paper setter of particular subject will add questions, modify

questions, delete question & view questions of his subject and submit to the main paper setter.

Add questions: Assistant paper setter will add questions to the question paper.

Modify questions: Assistant paper setter will modify question in the question paper.

Delete questions: Assistant paper setter will delete questions in the question paper.

View question paper: Assistant paper setter will view question paper to see the structure of

question paper and then final question paper will be uploaded to the database.

Name of use case: Add questions

Description: Assistant paper setter will add question’s option ,description , max marks & min marks.

Preconditions:. Assistant paper setter logged in.


Assistant paper setter will add description of questions.

Assistant paper setter will add options of questions. Assistant paper setter will append max. Marks & negative marks for questions.

Alternate flow of events: None

Post Condition: None

Activity diagram for add questions:





Name of use case: Modify questions

Description: Assistant paper setter will Modify questions(if required).



Assistant paper setter will select the question which is to be modified.

Assistant paper setter will modify the question(if required).

Alternate flow of events: None Post Condition: None

Activity diagram for modify questions:

Name of use case: Delete questions

Description: Assistant paper setter will delete questions(if required). Preconditions:. Assistant paper setter logged in.


Assistant paper setter will select the question which is to be Deleted. Assistant paper setter will delete the question(if required).



Activity diagram for delete questions:

Name of use case: View question paper

Description: Assistant paper setter will select & view question paper.


Normal flow of events: Assistant paper setter will select the question paper.

Assistant paper setter will view all details of question paper.


Activity diagram for view question paper:





iv) Main paper setter: Main paper setter is having responsibility to finalize the questions of paper set by his subordinates .So Main paper setter will accept, remove, modify questions ,view questions and

serialize them .

Accept questions: Main paper setter will accept questions prepared by subordinates (Assistant

paper setter).

Reject questions: main paper setter could reject questions.

View all questions: Main paper setter can view questions prepared.

Serialize questions: Main paper setter will serialize questions keeping timing limitation of

examination & general capability of students.

Manage new questions: Main paper setter will add questions from his side as per the need of

scenario.

Name of use case: Accept questions

Description: Main paper setter will accept question from all questions provided by subordinates.

Preconditions: Main paper setter logged in.

Question paper is already submitted by Assistant paper setter


Main paper setter will select the question.

Main paper setter will mark the question as accepted.


Activity diagram for Accept Questions:

Name of use case: Reject questions

Description: Main paper setter will reject question from all questions provided by subordinates.



Normal flow of events: Main paper setter will select the question.

Main paper setter will mark the question as Rejected.


Activity diagram for Reject Questions:





Name of use case: view questions

Description: Main paper setter can view all questions at any time.




Main paper setter will select the question paper & view it.



Activity diagram for view all questions:

Name of use case: Serialize questions

Description: Main paper setter will arrange & serialize all questions selected by him in order to make final question paper.

Preconditions: Main paper setter logged in. Question paper is already submitted by Assistant paper setter.


Main paper setter will rearrange questions (if required).

Main paper setter will serialize all questions .



Activity diagram for Serialize Questions:





v) Head exam controller: Head exam controller will supervise question paper setting. He will be responsible for setting the final question paper of a particular Course .He/she can view questions ,

modify questions, delete questions and prepare merit list.

View questions: Head exam controller will view questions set prepared by main paper setter.

Modify questions: head exam controller will have access to modify questions .

Delete questions: Head exam controller will delete questions as per need & finalize question

paper.

Generate merit list: Head exam controller will evaluate the answer sheet based on an algorithm,

generate merit list & put it on main website for candidates.

Name of use case: View questions

Description: Head exam controller view the question paper submitted by main paper setter & finalize it.

Preconditions: Head exam controller logged in.

Question paper is already submitted by main paper setter.


Head exam controller will select the question paper. Head exam controller will view questions of question paper.



Activity diagram for View Questions:

Name of use case: Modify questions

Description: Head exam controller will modify the question paper submitted by main paper setter &

finalize it.

Preconditions: Head exam controller logged in.

Question paper is already submitted by main paper setter.

Normal flow of events: Head exam controller will select the question paper.

Head exam controller will modify questions (If required).



Activity diagram for modify questions:





Name of use case: Delete questions

Description: Head exam controller will delete the questions from question paper submitted by main paper setter & finalize it.

Preconditions: Head exam controller logged in. Question paper is already submitted by main paper setter.


Head exam controller will select the question paper.

Head exam controller will delete questions (If required).



Activity diagram for delete questions:

vi) Local exam conductor: Local exam conductor will be having responsibility of conducting the

examination successfully. He/She will verify candidate’s document, download question paper, upload

results.

Student verification: Local exam conductor will verify student by admit card of students before

examination.

Download Question Paper: Local exam conductor will download question papers from central

database prior to examination.

Upload Results: Local exam conductor will upload answers of candidates from local database to

central database.

View merit list: Local exam conductor will get merit list from central database & this list will be

shown publicly.

Name of use case: Student verification

Description: Local exam conductor will verify the documents (admit card ) of candidate before examination starts.

Preconditions: None


Local exam conductor will verify the admit card of candidate & confirm the identity of candidate. In case candidate is not having admit card or identity is not confirmed, candidate will not be allowed





to sit in examination.


Activity Diagram of View Merit List:

vii) Local Counselor: Local counselor will be engage in documentation verification, fulfillment the

information of the mode of payment of counseling fee, download detail database and upload student preferences.

Document verification: Local counselor will verify document (admit card, counseling letter ,

previous mark sheets and other certificates ) of students before counseling .

Mode of payment of the counseling fee: Local counselor will fill the information of the mode of

payment of the counseling fee and a Registration No is assigned through a algo. The mode of

the payment is either DD or Credit Card.

Download detail databases: Local counselor will download the database of the option form of

the college and branch from central database prior to counseling to overcome any network or

technical fault.

Upload Student preferences: Local counselor will upload preference of candidates from local

counseling center database to central database where seat will be allocated by main counselor.

Name of use case: Document verification

Description: Local counselor will verify the all the required documents (admit card, counseling letter ,

previous mark sheets and other certificates) of candidate before counseling start. He will fill

Preconditions: Local Counselor logged in.


Local counselor will verify all the required documents (documents are Counseling call letter, Transfer Certificate, Passing certificate of 10

th standard & 12

th standard or Graduation Post Graduation,

Demand draft for counseling).



Activity Diagram of Document Verification:





Name of use case: mode of payment of the counseling fee

Description:

Local counselor will fill the information of the mode of payment of the counseling fee and a Registration No is assigned through a algo. The mode of the payment would be either through DD or Credit Card.

Preconditions:

Local Counselor logged in.


Local counselor will fill the mode of payment of the counseling fee (Demand draft \Credit card)

.Local counselor on submission of the counseling fee , gives a Registration No, that will be generated

by a algo. .The Registration No would be used further at the time of counseling form login.

Alternate flow of events: None Post Condition: None.





Name of use case: Upload Students Preferences

Description: After the successfully completion of counseling, the Local counselor will upload all students

selection of preferences online through XML interaction. after successful upload of preferences, log will be created.

Preconditions:

Local Counselor logged in. Internet connectivity should be idle at the time of upload.


Local counselor will upload student preferences to the central database.

Alternate flow of events: NonePost Condition: None.

Activity Diagram of Uploading Student Preferences.

viii) Main Counselor: Form controller will act as Main Counselor as well .Main counselor will be

engaging in managing detail database, seat allotment hotel allotment and college communication.

Manage detail database: main counselor will be engaged in managing detail database of student

preferences sent from local counseling centers.

Seat allotment: On the basis of candidate’s preferences ,the main counselor will generate a list of

allocated seats through some algorithm .This information will be sent to head exam controller to display it online.

Hostel allotment: The main counselor will also allot hostel ,according to the colleges rules

College Communication: The main counselor will be involved in communication with college

.The college will provide him the information of the branch, seat and hostel.

Name of use case: Seat Allotment





Description: The main counselor will run some algorithm on his application & generate a list having seats allotted to candidates & store results in database.

Preconditions: Main Counselor logged in.

Normal flow of events: Main Counselor will generate the list of seats allocated to candidates.

Main Counselor will store the list in database. Alternate flow of events: None


Name of use case: Hostel allotment

Description: The main counselor will allocate hostel of particular college assigned to candidate.



Main Counselor will select the hostel & room from database, which fits to the candidate on the basis

of information provided by college. After that Hostel entry is stored in database corresponding details is sent to the candidate.



Name of use case: College Communication

Description: The main counselor will communicate to all colleges falls under university, regarding

college information & candidate information.



Main Counselor will fetch hostel information of college & store it in database through XML.

Main Counselor will send all information of candidates who are allotted that particular college. Alternate flow of events: None


ix) College: The College will provide the information of the number of the seats, branch and hostel to

the University.

College Communication: The College will be engage in communication with University. The

college will provide the information of the branch, seat and hostel through XML.

Hostel allotment: The main counselor will allot hostel, according to the colleges rules.

Name of the use case: College Communication





Description: Some authoritative person of college will provide the information of college to the main counselor through XML & will communicate to the main counselor after counseling has done.

3.2) Supplementary Requirements: Have hours of operation that are 24 x 7 - Because system can be an automated process, so it can stay open for 24 hours a day. If the base is now the entire world, staying open 24 hours a day becomes

critical. System is required to be available 24X7 so UPS support must be on server site for at least 8 hours

in case of power failure. System will remain inaccessible to users at 2:00 to 4:00 am for backup and maintenance purpose.

Make the existing Web site more dynamic in nature - Many early Web implementations consisted

of static HTML pages. This becomes very difficult to manage if the number of pages gets too large. An effective system should be largely dynamic taking advantage of technology that automates this process

rather than relying on manual processes. Application should serve dynamic user based customized web

pages to its clients from server.

Tie the existing Web site into existing enterprise systems – Any existing Web site that relies on the manual duplication of data from another system is one that can be improved. Most of the business

data in the world today exists in enterprise servers that can be connected to the Web servers to make this

process far more effective.Provide good performance and the ability to scale the server – The Web Application Server

should provide good performance and the ability to manage performance with techniques, such as support

for caching, clustering, and load balancing.

Providing session management capability - Web application developers should not spend valuable time worrying about how to maintain sessions within the application. The Web Application Server should

provide these services.

3.3) External Interface Requirements

User Interface: There are various kinds of users in the system. These are the form controller, counsellers,

general users, candidate, form controller etc. All these interact with the system. Software Interface: Software will depend on the security features provided by the operating system

and the language java.

Communication Interface: The system requires an SMTP server and a web connection with direct

connection to the internet. It is assumed that the database connection is established.

Date post:	01-Feb-2018
Category:	Documents
Upload:	hoangkhuong
View:	218 times
Download:	2 times

Software Requirements Specification - EKALAVYA...

Documents