Student

Result
Management
System

1
A university has decided to engage a software
company for the automation of student result
management system of its UG Programme.The
following documents are required to be
prepared.

(i) Problem Statement

2
Problem Statement
To Develop a system that will
manage

🗸Information about the various Users

4
Level-1 DFD

5
Level-2 DFD of
Login

6
Level-2 DFD of User
account maintenance

7
Level-2 DFD of Student
information management

8
Level-2 DFD of Subject
information management

9
Level-2 DFD of Marks
information management

10
USE CASE DIAGRAM

11
12
13
14
15
USER CASE DIAGRAM

16
17
ER DIAGRAM

18
oooooooooooooooooooooooooo
oooooooooo

19
SOFTWARE REQUIREMENT
SPECIFICATION

20
 1.INTRODUCTION
This document aims at defining overall software
requirement for STUDENT RESULT
MANAGEMENT SYSTEM .Efforts
have been made
accurately. Theto define the requirements
product will exhaustively
having and
features/functionalities
final mentioned be in only
assumptions for any additional functionality/feature
this document should
not be made by any of the parties involved and in
developing/testing/implementing /using this product .

21
1.1 PURPOSE
This specification document describes the
capabilities that will be provided by the
software application STUDENT RESULT
MANAGEMENT SYSTEM .It also states
the various constraints by which the
system will abide.The intended audience
for this document are the development
team, testing team and end users of
the product.

22
1.2 SCOPE
The application will manage the
information about various students
enrolled in this course in different years,
the subjects offered during different
semesters of the course, the marks
obtained by the various students in
various subjects in different semesters.
The application will greatly simplify
and speed up the result preparation
and management process.

23
2. Overall description
The application will have capability to
maintain information about the students
enrolled in the course, the subjects
offered to students during different
semesters , the marks obtained by the
students in different subjects in various
semesters.The software will also
generate summary report regarding
student information, semester wise
marks list and performance reports .

24
2.1 USER INTERFACES
1) Login screen for entering the
username, password, type of
user(Administrator, Data entry operator,
student, teacher)will be provided.
Access will be based upon the ole of
user.
2) A screen showing the marks obtained
by the student in each subject.

25
2.2 Hardware interfaces
1) Intel p4 processor with minimum
2GHz speed.
2) RAM: Minimum 1GB
3) Hard Disk: min 20GB

26
2.3 Software interfaces
1) Visual Studio 2010
2) Service Pack2 for Windows
XP/VISTA
3) DB Server: SQL SERVER 2008
4) OS:Window Vista/XP/7

27
2.4 OPERATIONS
The DBA at client side will be
responsible for manually deleting
old/non required data. Database
backup and recovery will also be
handled by the DBA.
The system will provide a RESET
SYSTEM function that will delete all
existing information from the
database.

28
2.5 Product Functions
Depending upon the user role he/she
will be able to access only the
specific modules of the system.
1) Login facility for enabling only
authorized access to the system
2) User (with role Data Entry operator)
will be able to modify /add/delete
information about different students that
are enrolled for the course in different
years .
29
3) User(with the role of teacher )will
be able to add /modify/delete
information regarding marks obtained
by different students in different
semesters
4) User (with role of administrator) will
be able to reset the system leading to
deletion of all existing information
from the backend database. He will be
able to create/modify/delete existing
user accounts.
30
2.6 User Characteristics
1)Users at University will have to
implement a security policy to
safeguard the marks related information
from being modified by unauthorized
users(by means of gaining access to
backend DB).

31
2.7 ASSUMPTIONS
A N D DEPENDENCIES
1) The number of subjects to be taken
by the student in each semester does
not change .
2) The subject types do not change.
3) The number of semester do not
change

32
 3.1EXTERNAL INTERFACES
3.1.1 User Interfaces
The following screens will be provided:
Login screen:This will be the first screen that will
be displayed. It allows user to access different
screens based upon the user role.Various
fields available on this screen will be
i. User id: alphanumeric of length up to 10char.
ii. Password: alphanumeric of length up to 10char
iii. Role:Will have the following
values: Administrator,Data
entry
Operator,student,teacher 33
2) Subject info Parameter Screen:
This screen will be accessible only to the
Administrator. It will allow the user to
enter the semester number for which the
user wants to access the subject
information.
3) Student info Parameter Screen:
This screen will be accessible only to the
Administrator. It will allow the user to
enter the Batch Year for which the user
wants to access the student information.
34
 4)Student Information Screen:This screen will be
accessible only to the Administrator. It will
allow the user to modify the information
about new/existing student for particular batch
year.
i.Various fields
Student available on
Enrollment No:these screen
of the are:
format
B.E/YYYY where YYYY represents the batch
year
ii. Student Name: only alphabetic letters
iii and length up to 40 chars.
. Batch Year: of the format YYYY

35
5) Marks Entry Parameter Screen:This screen
will be accessible only to the Teacher. It will
allow the user to enter the Batch Year, the
semester number and the subject for which
the user wants to access the marks
information.
6) Marks entry screen: Screen:This screen will
be accessible only to the Teacher. It will allow
the user to add/modify/delete information
about the marks obtained in the selected
subject by different students. It includes Student
enrollment no, student name, internal marks,
external marks, total marks.
36
 3.2 SYSTEM FEATURES
3.2.1 Subject
information maintenance
The system will maintain information about
various subjects being offered during
different semesters of the course.The
following information will be maintained for
each subject: Subject code, Subject type,
Semester.
The system will allow creation , modification ,
deletion of new, existing subjects and also
have the ability to list all the available
subjects for a particular semester.
37
Validity Checks:
1) Only user with the data entry operator
will be able to access the Subject
Information Maintenance module.
2) No two semester will have the same
subject.
3) The subject code will be unique for
each subject .
4) Subject code, Subject name, semester
cannot be blank.
38
 3.3 Marks Information
maintenance
⚫ The system will maintain information about the
marks obtained by various students of different
enrollment year in different semesters.The
following information would be maintained :
Student Enrollment Number, Semester, Subject
code, internal marks, External Marks,Total
marks.
⚫ The system will allow
creation/modification/deletion of marks
information and also have the ability to list all
the available marks information for all students
for a particular subject in the given semester.
39
 Validity check:
i. Only the user with role of teacher will be
authorized to access the Marks
Information maintenance module.
ii. Marks cannot be less than 0.
iii. Total marks will be calculated
as :Internal Marks in that subject +
External Marks in that subject .

40
3.4 User account
information maintenance
⚫A system will maintain information about
various users who will be able to access
the system.The following information
would be a maintained: User name, user
ID, password<Role.
VALIDITY CHECK:
i. Only user with role Administrator will
be authorized to access the User
Accounts Information Maintenance
module.
ii. User Name, UserId, Password, Role
cannot be left blank
41
3.5 Software system Attributes
1) security: the application will be
password protected. Users will have to
enter correct information to access the
application.
2) Maintainability:The application will be
designed in a maintainable manner. It
will be easy to incorporate new req in
individual module.
3) Portability:The application will be
easily portable
42
3.6 Logical DB Requirements
The following information will be placed
in DB:
1) Subject info: Subject Name, Code,
Semester
2) Student Info: Student Enrolment
Number, Student name, enrollment year.
3) Marks info: Student Enrolment ,
Semester, internal marks in each subject,
external marks in each subject
4) User Account Info: UserName, User
Id, password, role
43
44