almunimanager srs

7/31/2019 AlmuniManager SRS

1/11

SYSTEM REQUIRMENT SPECIFICATIONS FOR WEB BASED

ALUMNI MANAGER

PURPOSE OF THE SYSTEM

This project is aimed to developing a repository for the alumni of the college, which is of importance to a college

The entire project has been developed keeping in view of the distributed client server computing technology, in

mind. The Alumni Manager is an Internet based application that can be accessed throughout the World. This

system explains about the Alumni (Old students) how exactly the maintenance of the Alumni manager system

works. The system clearly deals with all the information of the Alumni users. Anyone can access the search

Engine to know about any Alumni of that college but cant able to add. Alumni can only update the database when

they are in the college.

PROBLEMS IN THE EXISTING SYSTEM:

It is limited to a single system.

It is less user-friendly.

It is having lots of manual work (Manual system does not mean that you are working with pen and paper,

it also include working on spread sheets and other simple software's).

The present system is very less secure.

It is unable to generate different kinds of report.

It is difficult to maintain Phones.

Manual Interaction of Friends is much difficult.

SOLUTION OF THESE PROBLEMS

The development of the new system contains the following activities, which try to automate the entire process

keeping in view of the database integration approach.

User friendliness is provided in the application with various controls.

The system makes the overall project management much easier and flexible.

It can be accessed over the Internet.

There is no risk of data mismanagement at any level while the project development is under process.

It provides high level of security using different protocols like https etc.


2/11

STUDY OF THE SYSTEM

In the flexibility of the uses the interface has been developed a graphics concept in mind, associated through a

browses interface. The GUIS at the top level have been categorized as

1. Administrative user interface

2. The operational or generic user interface

The administrative user interface concentrates on the consistent information that is practically, part of the

organizational activities and which needs proper authentication for the data collection. The interfaces help the

administrations with all the transactional states like Data insertion, Data deletion and Date updation along with the

extensive data search capabilities.

The operational or generic user interface helps the users upon the system in transactions through the existing dataand required services. The operational user interface also helps the ordinary users in managing their own

information helps the ordinary users in managing their own information in a customized manner as per the

assisted flexibilities.

Number of Modules

The system after careful analysis has been identified to be presented with the following modules:

The modules involved are:

1.Administration

2.Alumni users

3.Search

4.Reports

5.Authentication

Administrator:-

This Module is divided into different sub-modules.

1. State Information

2. City Information

3. University Information

4. College Information

5. Complaints


3/11

In this module the Administrator has the privileges to maintain entire application.

State Information:-

In this module the Admin will add the new State information and also keep track on the state information which is

present in the system.

City Information:-

In this Module the admin will add new Cities of an existing State based on alumni requests or complaints. He can

watch the information of all the Cities in the existing state.

University Information:-

This is the main role of Admin a University will provide different type alumni. So that admin will add set of

University details into the system. He can watch the information of all the Universities in the existing state.

College Information:-

Normally Universities have No of colleges, so that will add these college details into the existing system, and

maintain the college details for provide best alumni for students.

Complaints:-

In this module the Admin can receive all complaints or requests from the students. Based on the complaints or

requests he can manage the State, City, University and Colleges. Admin will take decisions base on these

complaints only.

Alumni Users:-

This module is especially for Old Students

1. Inbox

2. Outbox3. Compose

4. Address Book

5. Personal Mails

6. Complaints

Inbox:-

This module is help the students for check their mails and know from where it comes , when it was comes etc. If

he wants to delete he can delete directly.

Outbox:-

The User can watch the sent items (previously send mails by himself). If he wants to delete he can delete directly.


4/11

Compose:-

By using the module he can send the mails to his friends and create alumni concept, by using their email address

These address are provided by alumni system.

Address Book:-

User can store his Friends details by using this module only. This is very useful to the user to interact with friendsfurther more. Any modifications he want he can do directly in this module.

Personnel Mails:-

User can watch his personnel mails, here he can get subject and where it is comes, whenever he clicks the link

the entire information will displays.

Search:-

Here users can search for his friends for providing alumni. The search is mainly depends on these issues.

1. Friends Name2. Qualification

3. Year Of Passing

A user can search his friends individually or any combination of the above mentioned.

Authentication:-

This module contains all the information about the authenticated user. User without his username and password

cant enter into the login, if he is only the authenticated user then he can enter to his login and he can see the his

details and his document details.

INPUTS & OUTPUTS

The main inputs, outputs and major functions of the system are as follows.

Inputs:

Admin enters his or her user id and password.

Students enter his details along with his or her user id and password.

Student requests for alumni.

Students request the search.

Admin can edit State, City, University, College details etc...

Students send Complaints or Requests


5/11

Outputs:

Admin receives the Complaints or Requests.

Students got their old friends for alumni.

Students watch the status of his complaint.

Displays search result.

SCOPE OF THE PROJECT

This project is aimed at developing a repository for the alumni of the college, which is of importance to a college.

The Alumni Manager is an Internet based application that can be accessed throughout the World. Any one can

access the search Engine to know about any Alumni of that college but cant able to add. Alumni can only update

the database when they are in the college.

SDLC METHODOLOGIES

This Document plays a vital role in the development life cycle (SDLC) as it describes the complete requirement of

the system. It is meant for use by the developers and will be the basic during testing phase. Any changes made to

the requirements in the future will have to go through formal change approval process.

WATER FALL MODEL was being chosen because all requirements were known beforehand and the objective of

our software development is the computerization/automation of an already existing manual working system

Communicated

Requirements

RequirementsSpecification

DesignSpecification

Executable

SoftwareModules

IntegratedSoftwareProduct

DeliveredSoftwareProduct

ChangedRequirements

RequirementsEngineering

Design

Programming

Integration

Delivery

Maintenance

ProductProduct

Input Output

Process


6/11

Fig 2.2: Water Fall Model

The developer is responsible for:

Developing the system, which meets the SRS and solving all the requirements of the system?

Demonstrating the system and installing the system at client's location after the acceptance testing is

successful.

Submitting the required user manual describing the system interfaces to work on it and also the documents

of the system.

Conducting any user training that might be needed for using the system.

Maintaining the system for a period of one year after installation.

INPUT DESIGN

Input design is a part of overall system design. The main objective during the input design is as given below:

To produce a cost-effective method of input.

To achive the highest possible level of accuracy.

To ensure that the input is acceptable and understood by the user.

INPUT STAGES:

The main input stages can be listed as below:

Data recording

Data transcription

Data conversion Data verification

Data control

Data transmission

Data validation

Data correction


7/11


8/11

Users main interface with the computer.

Operational outputs whose use is purely with in the computer department.

Interface outputs, which involve the user in communicating directly with

OUTPUT DEFINITION

The outputs should be defined in terms of the following points:

Type of the output

Content of the output

Format of the output

Location of the output

Frequency of the output

Volume of the output

Sequence of the output

It is not always desirable to print or display data as it is held on a computer. It should be decided as which form of

the output is the most suitable.

For Example

Will decimal points need to be inserted

Should leading zeros be suppressed.

OUTPUT MEDIA:

In the next stage it is to be decided that which medium is the most appropriate for the output. The main

considerations when deciding about the output media are:

The suitability for the device to the particular application.

The need for a hard copy.

The response time required.

The location of the users

The software and hardware available.

Keeping in view the above description the project is to have outputs mainly coming under the category of

internal outputs. The main outputs desired according to the requirement specification are:


9/11


10/11

PERFORMANCE REQUIREMENTS:

Performance is measured in terms of the output provided by the application. Requirement specification plays an importan

part in the analysis of a system. Only when the requirement specifications are properly given, it is possible to design a

system, which will fit into required environment. It rests largely in the part of the users of the existing system to give the

requirement specifications because they are the people who finally use the system. This is because the requirements have

to be known during the initial stages so that the system can be designed according to those requirements. It is very

difficult to change the system once it has been designed and on the other hand designing a system, which does not cater to

the requirements of the user, is of no use.

The requirement specification for any system can be broadly stated as given below:

The system should be able to interface with the existing system

The system should be accurate

The system should be better than the existing system

The existing system is completely dependent on the user to perform all the duties.

FEASIBILITY STUDY

TECHINICAL FEASIBILITY:

Evaluating the technical feasibility is the trickiest part of a feasibility study. This is because, at this point in time,

not too many-detailed design of the system, making it difficult to access issues like performance, costs on (on

account of the kind of technology to be deployed) etc. A number of issues have to be considered while doing a

technical analysis.

Understand the different technologies involved in the proposed system:

Before commencing the project, we have to be very clear about what are the technologies that are to be required

for the development of the new system.

Find out whether the organization currently possesses the required technologies:

Is the required technology available with the organization?


11/11

If so is the capacity sufficient?

For instance Will the current printer be able to handle the new reports and forms required for the new system?

OPERATIONAL FEASIBILITY:

Proposed projects are beneficial only if they can be turned into information systems that will meet the

organizations operating requirements. Simply stated, this test of feasibility asks if the system will work when it is

developed and installed. Are there major barriers to Implementation? Here are questions that will help test the

operational feasibility of a project:

Is there sufficient support for the project from management from users? If the current system is well liked and

used to the extent that persons will not be able to see reasons for change, there may be resistance.

Are the current business methods acceptable to the user? If they are not, Users may welcome a change that

will bring about a more operational and useful systems.

Have the user been involved in the planning and development of the project? Early involvement reduces the

chances of resistance to the system and in General and increases the likelihood of successful project.

Since the proposed system was to help reduce the hardships encountered In the existing manual system, the new

system was considered to be operational feasible.

ECONOMIC FEASIBILITY:

Economic feasibility attempts 2 weigh the costs of developing and implementing a new system, against the

benefits that would accrue from having the new system in place. This feasibility study gives the top management

the economic justification for the new system. A simple economic analysis which gives the actual comparison of

costs and benefits are much more meaningful in this case. In addition, this proves to be a useful point of reference

to compare actual costs as the project progresses. There could be various types of intangible benefits on account of

automation. These could include increased customer satisfaction, improvement in product quality better decision

making timeliness of information, expediting activities, improved accuracy of operations, better documentation

and record keeping, faster retrieval of information, better employee morale.

almunimanager srs

Documents