SYSTEM REQUIREMENT SPECIFICATIONS
Title: Sophomore Strategy
Apportionment and Directorate
Objective:
Ø
This
project is aimed at developing a Student Project Allocation and Management with
Evaluation System, which is a web-based system, which manages the activity of
“Student Project Management” and “Online Testing”.
Ø
This
system will manage the database and maintain a list of all student groups that
have registered on this site, conduct their online test and shortlist those
students who have passed the eligibility criteria as set by the professors.
Existing
System:
Ø
The
Current System is a computerized system which is maintained at individual
databases which maintains in Excel sheets.
Ø
It doesn’t support the online examinations.
In this system there is complete lack of
security to the database as it provides access to every user.
Ø
Here the user cannot easily search the record
from the entire database.
Ø
It
doesn’t provide multiple user accessibility and also has same user privileges.
Limitations in Existing
System
·
Access
single record from the database is very difficult.
·
Database
id maintained at individual levels
·
The
system is not an online system
Proposed System:
Ø
The
Current System is a computerized system which is maintained at individual databases
at centralized database. It support the online examinations.
Ø
In
this system there is security for the database as it provides access to level
of user.
Ø
Here the user can easily search the record
from the entire database.
Ø
It provides multiple user accessibility and
also has same user privileges.
Study of the system:
To provide flexibility to the users,
the interfaces have been developed that are accessible through a browser. The
GUI’S at the top level have been categorized as
- Administrative user interface
- 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. These interfaces
help the administrators 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 end users of the
system in transactions through the existing data and required services. The
operational user interface also helps the ordinary users in managing their own
information in a customized manner as per the included flexibilities.
Feasibility Study:
Feasibility Report:
Preliminary investigation examines
project feasibility, the likelihood the system will be useful to the
organization. The main objective of the feasibility study is to test the
Technical, Operational and Economical feasibility for adding new modules and
debugging old running system. All systems are feasible if they are given
unlimited resources and infinite time. There are aspects in the feasibility
study portion of the preliminary investigation:
- Technical
Feasibility
- Operation
Feasibility
- Economical
Feasibility
Technical
Feasibility:
The technical issue usually raised
during the feasibility stage of the investigation includes the following:
- Does
the necessary technology exist to do what is suggested?
- Do the
proposed equipments have the technical capacity to hold the data required
to use the new system?
- Will
the proposed system provide adequate response to inquiries, regardless of
the number or location of users?
- Can
the system be upgraded if developed?
- Are
there technical guarantees of accuracy, reliability, ease of access and
data security?
Operational
Feasibility:
Proposed projects are
beneficial only if they can be turned out into information systems, which will
meet the organization’s operating requirements. Operational feasibility aspects
of the project are to be taken as an important part of the project
implementation. Some of the important issues raised are to test the operational
feasibility of a project includes the following: -
·
Is
there sufficient support for the management from the users?
·
Will
the system be used and work properly if it is being developed and implemented?
·
Will
there be any resistance from the user that will undermine the possible
application benefits?
This system is targeted to
be in accordance with the above-mentioned issues. Beforehand, the management
issues and user requirements have been taken into consideration. So there is no
question of resistance from the users that can undermine the possible
application benefits.
The well-planned design would ensure
the optimal utilization of the computer resources and would help in the
improvement of performance status.
Economic
Feasibility:
A system can be developed
technically and that will be used if installed must still be a good investment
for the organization. In the economical feasibility, the development cost in
creating the system is evaluated against the ultimate benefit derived from the
new systems. Financial benefits must equal or exceed the costs. The system is
economically feasible. It does not require any additional hardware or
software.
Functional Requirements:
Number of Modules
After careful analysis the system has been identified to have the
following modules:
1 Administrator
2. Student
3. Professor
Administrator
- Can
login to the system through the first page of the application
- Can
create new user account for a professor and assign/change(if existing
user) username and a password
Student
·
A
student if he is a new user registers into the system.
- He
enters details like his name, age, date of birth, college, B.E.
Percentage up to 6 semesters, his knowledge of the latest technologies
and other prior experience details if any…etc.
- He
also enters the name of all his team members and their details
- For
the professor, this student would act as the primary interface between
the student group and the professor
- After
entering successfully all details he is given a student group code which
he shares with his team members.
- Whenever,
a student successfully logs in (after registration) is asked for for his
project code and if successfully entered is taken to a screen (via link)
where he can give an online test
- His/her
details are then stored in the database
- In
such a fashion he all team members give a test and their respective
scores are listed
Professors
·
A
registered professor, who is assigned a user name and a password by the
administrator logs in, should enter at least one project and its description
which he is willing to allocate to the students.
·
He/she
is given an option to sort and shortlist students by various criteria such as
percentage scored in the online test, academic performance, technologies
familiar with, past experience etc. A professor can view all students’
information.
·
He
can see student status, such as whether the student is available or has been
assigned a project by any other professor, and if assigned then by which
professor
·
A
professor after short-listing students clicks a button so that he locks the
student group. i.e. no other professor can assign them any projects now, as
they have already been assigned one by this professor, thus assigning the a
status
·
A
mail is automatically, sent to the student group i.e. all its team members that
they are assigned a project, by this professor
Software:
Technology : Java and J2EE
Web Technologies : Html, JavaScript, CSS
Web Server : Tomcat 5.5
Database
: Oracle 9i
Hardware:
Processor : Pentium
RAM : 1GB
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
achieve 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
Input Types:
It is necessary to determine the
various types of inputs. Inputs can be
categorized as follows:
·
External
inputs, which are prime inputs for the system.
·
Internal
inputs, which are user communications with the system.
·
Operational,
which are computer department’s communications to the system?
·
Interactive,
which are inputs entered during a dialogue.
Input Media:
At this stage choice has to be made
about the input media. To conclude about
the input media consideration has to be given to;
·
Type
of input
·
Flexibility
of format
·
Speed
·
Accuracy
·
Verification
methods
·
Rejection
rates
·
Ease
of correction
·
Storage
and handling requirements
·
Security
·
Easy
to use
·
Portability
Keeping in view the above description
of the input types and input media, it can be said that most of the inputs are
of the form of internal and interactive.
As
Input data is to be the directly keyed
in by the user, the keyboard can be considered to be the most suitable input
device.
Output
Design:
Outputs from computer systems are
required primarily to communicate the results of processing to users. They are
also used to provide a permanent copy of the results for later consultation.
The various types of outputs in general are:
- External
Outputs whose destination is outside the organization.
- Internal
Outputs whose destination is with in organization and they are the User’s
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 the system.
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:
The
outputs were needed to be generated as a hard copy and as well as queries to be
viewed on the screen. Keeping in view
these outputs, the format for the output is taken from the outputs, which are
currently being obtained after manual processing. The standard printer is to be used as output
media for hard copies.
