admission system srs

Online admission system

Software Requirements Specification

For

Online Admission System

Prepared by <BSCS-F06-M019>

<BSCS-F07-M07>

<BSCS-F07-M05>

<BSCS-F07-M034>

Dated: <07-03-2011>


Page ii


Overall Description

2.1 Product Perspective

This product gives you the online student admission facility of any dept and inquiry system gives you the merit list of the student. Earlier admission system gives you the solution for a specific dept or institute like earlier school management system (provide NUST, LUMS etc).

But this product gives you the general type of dept admission system which is created by yourself on your requirement and specification. We will provide all the functionalities for a general type of admission system and you can select your specific requirement for your admission system. This product will create all databases required for admission system dynamically on your demand or specification.

We created this product because you can get the general solution for your admission, Earlier each dept or institution demands the admission system for specific institution and when their requirement and specification increased then they contact again the venders and pay for the enhancement as well as it is very difficult to implement the required changes.

The earlier admission system has no proper criteria for admissions but as the time goes, many of the system have been developed but they are not satisfying the requirements of an institution. Earlier admission systems have not any proper way for inquiry of records like BISE etc, they can only fetch the record but they don’t have the functionality of online dynamic merit criteria.

But our admission system will provide all criteria particularly required for an admission. You will provide us all the specifications which you needed for your system and as a result we will provide you the system which will cover all the perspectives according to the criteria mentioned.For example: few institutions include the weighted of NTS test in their admission system but some institutions does not include tests like NTS etc. To handle this situation in future, we are making dynamic criteria which will cover all these circumstances.

Our online admission system is an automated system where all the candidates can easily access the news or alerts related to admission system. Our motive is to provide an ease to all the students to easily get information about their admission. Session wise and class wise student’s information will be maintained. All issues or latest news related to admission system will be maintained here.

Students were given an opportunity to get online up to date information about admissions throughout the year. Students can also easily view that whether they are enrolled in the particular program or not. If they have any query related to admission for that they can get online help or information about their query from management or administrators.

Now, we remove all above constraints to create a general type of admission system.

Page 1


Use case diagram of admission system

Admin

Data bases

student

Include

Include

Include

Close admission Get merit list

Register

Login

Logout

Submit fee

Store data

Register candidate

Access info

Verify candidate

View course detail

Get admission form

View merit list

Provide info

Page 2


The students and administrator are the actors and will use the website and its different features that will be the use cases of the admission system. The detailed description of possible use cases are given below.

Description of all use cases: Close admission Register Login Logout Get merit list Store data Verify candidate Register candidate Get admission form Provide information View course detail View merit list Submit fee

Use case 1: [close admission]

Admin

Goal: To close admissions.

Actor: admin

Pre conditions: close admissions immediately after due date.

Post conditions: Checking of admissions.

Summary: The admin is responsible to close the admissions after the due date and will not accept any admission form after the date has expired.

Close admission

Page 3


Use case 2: [register]

Admin

Goal: To register the student

Actor: admin

Pre conditions: A registration form will fill up by giving information to desired fields.

Post conditions: Checking of account information.

Exp1: Filling up the registration form

Summary: The student will be register by filling up the information fields given in the registration form and will be stored in database.

Use case 3: [login]

Admin

Actor: admin

Pre conditions: Admin will login to update all the information related to admission.

Post conditions: Checking of all information that has been mentioned.

Summary: The admin will login to update the information as well as to check the information and the changes that has been made.

Register

Login

Page 4


Use case 4: [logout]

Admin

Actor: admin


Post conditions: Admin will logout after checking of all information that has been mentioned.

Summary: The admin will logout after making updates and checking the information and the changes that has been made.

Use case: 5 [Get merit list]

Admin

Actor: admin


Post conditions: Checking of all information that has been mentioned.

Summary: The admin will login to update the information as well as to check the information and the changes that has been made.

Logout

Get merit list

Page 5


Use case: 6 [store data]

Admin

Actor: admin

Pre conditions: Admin will get all the information related to admission.

Post conditions: After getting all the data or information, the admin will store it in databases.

Summary: The admin will store the entire data in the data bases

Use case: 7 [Verify candidate]

Admin

Actor: admin

Pre conditions: Admin will analyze the all the data store in the data bases.

Post conditions: After analyzing all the data, the admin will verify the candidate whether he/she is eligible for admission or not.

Summary: The admin will check that whether the candidate is eligible for admission in a particular program or not.

Store data

Verify candidate

Page 6


Use case: 8 [Register candidate]

Admin

Actor: admin

Pre conditions: Admin will check whether the candidate is valid or invalid.

Post conditions: If the candidate is valid, then register the candidate

Summary: Admin after verifying all the candidates will register only those candidates which are eligible.

Software RequirementsSpecification

<Project>

Version 1.0 approved

Prepared by <author>

<Organization>

<Date created>

Software RequirementsSpecification

<Project>

Version 1.0 approved

Prepared by <author>

<Organization>

<Date created>Use case: 9 [Get admission form]

Student

Actor: student

Pre conditions: student will access the website.

Post conditions: after accessing the website he/she will get the admission form.

Summary: Student can easily get the admission form.

Register candidate

Get admission form

Page 7


Use case: 10 [Provide information]

Student

Actor: student

Pre conditions: student will put on the necessary information on admission form.

Post conditions: after putting the necessary information, the student must check whether the information is correct or not.

Summary: It is compulsory for a student to put the necessary information required for an admission.

Use case: 11 [View course details]

Student

Actor: student

Pre conditions: student will view the course detail in which he/she will get admission.

Post conditions: After viewing the course details, the student will able to choose the program easily.

Summary: student will view the details of the course and then make decision that in which course he/she is able to go.

Provide information

View course details

Page 8


Use case: 12 [View merit list]

Student

Actor: student

Pre conditions: he/she can view the merit list displayed.

Post conditions:

Summary: student can view the merit list which has been displayed and stored in the data bases.

Use case: 13 [Submit fee]

Student

Actor: student

Pre conditions: if student name is in the merit list then he /she will submit the fee.

Post conditions:

Summary: student will check the name in the merit list and if his/her name is in the list then he will submit the fee for that particular program.

Actors Details:

Students

Students have a facility to get online admission form Provide the information that is required for an admission

View merit list

Submit fee

Page 9


View the course details in order to decide in which course he/she should take admission.

View the merit list, if he/she got admission then he/she should submit the fee.

Admins

Close all admission after the due date. Get merit list from the data bases and store the data in the data bases again. Access the required information needed for the admissions. Login to verify the candidate. If the candidate is valid the register the candidate and logout.

2.2 Product Function

Student registration. Download admission forms from website. Provide course details. Provide you the information that is needed for an admission. Check admission updates. Set enquiries. News alert. Feed back and suggestions.

2.3 User Classes and Characteristics

Students

Login and get admission form. Submit the form along with all the required documents within due date. View if he/she is enrolled in particular program. If not then set enquiry to solve the problem.

Administrators

Register the students. Login and receive admission forms. Check all the forms whether completed or not. If there is any query related to any form then inform the relevant student to complete

the form. . Provide solutions of the different enquiries.

2.4 User Documentation

In the project we add the user manual tutorials, site map. Contact us, tool tips, and online help for the student. If the student does not know how to use this web site he/she can get help from tutorials, user manuals and online help options. Student can also call and send mail to administration for help related to any query.

By using the site map facility the student can move any page related to its requirement.

Page 10


By providing above mentioned facilities the student can use this web application.

2.5 Assumptions and Dependencies

Project Assumptions

These are basically details or scope you have assumed ahead of the Project Management Requirements and Business Requirements Specification being documented.Our web site must be open in fire fox and Google chrome. It basically covers 10 assumptions in web development that might be costing you money. The article was written with business and ecommerce websites in mind, but most points can be applied to blogs as well. The 10 assumptions are:

1. Student will know how to find your website2. Student know what you sell3. Everything will go as planned4. Student know where to click5. Student know how to get home6. Student know where they are7. Student know how to buy8. Student will volunteer loads of personal information9. Student will contact customer service if they have a question or problem10. Student will come back

The key take away from the article is: never assume. In other words, you should not design your website based on assumptions. Just because you behave in a certain way, it does not imply that other people will do so, too. This is an interesting topic and we will be covering it soon in a more in-depth post. Stay tuned!

So what is a website? What are the assumptions we make about them?

A website is square; it lives in the browser; it appears on a screen; it looks cool; you can see it, hear it,

bookmark it or add it to your favorites; you can buy things on it; it is flat, scrolls up, down, left and

right; you interact with it; it has buttons; it has a logo; it has a menu for navigation; it has a footer, a

contact page, an about page, a home page; it can have video; it has music and sound; it is on the

internet; it is made of code; it is on Google and Yahoo; it informs, it connects, it sends, it receives; it

has an address; it is an interface; it loads, you click on it, search on it, and you visit it.

.

Project Dependencies

When a project consumes executable code generated by another project, the project that generates

the code is referred to as a project dependency of the project that consumes the code. Whenever a

Page 11


project dependency has not been built or has been modified since the most recent build, that project is

built first, to generate and update the code to be consumed.

These are basically deliverables from other Projects and Programs which your project needs in order

to launch. Often these get overlooked which is why it is vital that you research these thoroughly and

then list them here so there is no confusion going forward.

Our project component is not completely depend on other project component .we enhanced and

modify the component that are used in the project .Some feature we borrow from other project like

forum, chat etc. it is possible that the deliverable of the project are matched with other project

component but it’s not mean that we used that component in our project. We give the functionality in

which some functionality is same with other deliverables but with core competency.

Page 12

admission system srs

Documents