Project Description: 1.1. Current Scenario

1.
Project Description
1.1. Current Scenario

The current scenario is that in order to get any help from the teachers, students
have to take time from the teachers manually, according to the teachers’ suitable
time to get their problems solved. Teachers have to take attendance, maintain
marks manually. And the students are not able to see their marks and also they are
not being able to know their attendance in any subject classes.
1.2. Problem with the existing system

System is to be designed for the faculty as well as the students. The students will
be able to see their sessional examination marks and attendance. The sessional
marks and the attendance will be taken through the CMS.
The faculty this can upload the data and the existing procedure of taking time by
the students experiences the following problems: -
 It is always a time consuming task for both students and teachers.
 Students mainly face problems during the exam time at that time teachers
are not available.
 3.Students as well as the faculty have to go to college for the information
about any new notice.
 Faculty have to take attendance manually and have to maintain many papers
to maintain the overall record of the students.
 Parents or others were not able to see the marks of the student.
 Students are not able to see their marks easily.
 Students were not able to see/know their total attendance in any subject
classes.
 In the manual attendance system, the students will be able to assign proxy
attendance of other students.
1.3. Proposed Solution
COLLEGE MANAGEMENT SYSTEM PROJECT (BCA 6TH SEM) 1

The main purpose of the proposed system is to facilitate the students for getting all
the facilities available under one roof. Some of the proposed solutions for the
existing system problems are: -
 All the system will be online through the system, i.e., all the process will be
computerized.
 For getting rid of the proxy attendance by the students, now the attendance
will be taken by the Subject teacher on the system online(Computerized).
 The attendance will be saved in the database for the long time use.
 Through the storing of the attendance online and doing it computerized, now
the faculty can get the total attendance report automatically by the system if
it is required.
 The sessional marks management and entering will also be done online on
the system that will be stored in the database.
 The Student can view their as well as their attendance in the subject classes
anytime.
 The students as well as the faculty will be able to know any important
notices that will be displayed on the CMS site.

2. Technologies Used
2.1. Hardware Requirements
 For PC (Windows)
 Processor: Pentium 233MHz (Recommended: Pentium

1GHz or greater)
 RAM: 64 MB RAM (Recommended: 128 MB RAM or
Greater)
 Hard disk: 1.5GB of available hard disk space
 Other: Video adapter & monitor with Super VGA (800 X 600)
Or higher resolution display with 256 Colors;
DVD-ROM or CD-ROM drive;
Keyboard and Mouse or compatible pointing Device.
2.2. Software Requirements

 Operating System: Window 2000/XP/Vista
 Web Server: IIS 6.0
 Database Server: Microsoft SQL SERVER 2005
 Development Framework: Microsoft Visual Studio 2008
 Web Browser: Mozilla Firefox 3.0. *
2.2.1. Front-End:

 Asp.Net 4.5 and C# 2.0
ASP.NET is a unified Web development model
that includes the services necessary for you to build enterprise-class Web
applications with a minimum of coding. ASP.NET is part of the .NET Framework,
and when coding ASP.NET applications you have access to classes in the .NET
Framework. You can code your applications in any language compatible with the
common language runtime (CLR), including Microsoft Visual Basic, C#,
Jscript, .NET, and J#. These languages enable you to develop ASP.NET
applications that benefit from the common language runtime, type safety,
inheritance, and so on.
 ASP.NET includes:
• environment A page and controls framework
• The ASP.NET compiler
• Security infrastructure
• State-management facilities
• Application configuration
• Health monitoring and performance features
• Debugging support
• An XML Web services framework
• Extensible hosting environment and application life cycle
• management
• An extensible designer
 ASP.NET:
ASP.NET provides a unified Web development model
that includes the services necessary for you to build enterprise-class Web
applications. ASP.NET is part of the .NET Framework and enables you to take full

advantage of the features of the common language runtime, such as type safety,
inheritance, language interoperability, and versioning. The topics in this section
provide you with conceptual information about how ASP.NET works and
procedural topics that show you how to write code that take advantage of the
power of ASP.NET to create dynamic Web applications.
 Why is ASP.Net 2.0 proffered?

The Microsoft .NET Framework
version 2.0 includes significant enhancements to ASP.NET in virtually all areas.
ASP.NET has been improved to provide out-of-the-box support for the most
common Web application situations. You will find that you can get Web sites and
pages up and running more easily and with less code than ever before. At the same
time, you can add custom features to ASP.NET to accommodate your own
requirements.
 Specific areas in which ASP.NET has been improved are:

 Productivity: You can easily and quickly create ASP.NET Web pages and
applications using new ASP.NET server controls and existing controls with
new features. New areas such as membership, personalization, and themes
provide system-level functionality that would normally require extensive
developer coding. Core development scenarios, particularly data, have been
addressed by new data controls, no-code binding, and smart data-display
controls.
 Flexibility and extensibility: Many ASP.NET features are extensible so
that you can easily incorporate custom features into applications. The
ASP.NET provider model, for example, provides pluggable support for
different data sources.
 Performance: Features such as recompilations, configurable caching, and
SQL cache invalidation allow you to optimize the performance of your Web
applications.
 Security: It is now easier than ever to add authentication and authorization
to your Web applications.
 Hosting: ASP.NET includes new features that make it easier to manage a
hosting environment and create more opportunities for hosters to add value.
 Completeness: New and existing features work in concert to allow you to
create end-to-end scenarios that address real-world Web development
challenges for sales, one for payroll, one for a document management
application, and so on. Sometimes an application uses only one database;
other applications.
2.2.2. Back-End:
 Microsoft SQL Server:

Microsoft SQL Server is a set of components that
work together to meet the data storage and analysis needs of the largest Web sites
and enterprise data processing systems. Microsoft SQL Server 2010 data is stored
in databases. The data in a database is organized into the logical components
visible to users. A database is also physically implemented as two or more files on
disk.
Each instance of SQL Server has four system databases (Login, Registered and
etc.) and one or more user databases (Grp and Mbr). Some organizations have only
one user database, containing all the data for their organization. Some
organizations have different databases for each group in their organization, and
sometimes a database used by a single application. For example, an organization
could have one database may access several databases.
It is not necessary to run multiple copies of
the SQL Server database engine to allow multiple users to access the databases on
a server. An instance of the SQL Server Standard or Enterprise Edition is capable
of handling thousands of users working in multiple databases at the same time.

3. Feasibility study
Depending on the results of

initial investigation, the survey is expanded to a more detailed feasibility study.
Feasibility study is a test of system proposal according to its work ability, impact
on the organization ability to meet user needs, and effective use of resources. The
three major areas under the feasibility study of project are:
 Technical Feasibility
 Operational Feasibility
 Economic Feasibility
 Social Feasibility
3.1. Technical Feasibility

It is a measure of the practically of a specific technical solution and the availability
of the technical expertise and resources.
3.2. Operational Feasibility

The system will be used if it is developed well then be resistance for users that
undetermined.
3.3. Economical Feasibility

It looks at the financial aspect s of the project; it determines whether the
management has resources and budget to invest in the proposed system and the
estimate time for the cost to be incurred.
3.4. Social Feasibility

The assessment of social feasibility will be done alongside technical feasibility.
Each of the alternative technical solutions that emerge must be evaluated for its
social implication.

4. INTRODUCTION
4.1. Purpose
The main purpose of our project is to maintain the
information about all the courses in “IT Department of Bundelkhand University”.
A user can get the desired information. Students can also get the study material for
the desired courses and can fire queries related to any subjects. Faculties can
upload the study material. Faculties can take the attendance online students can
view their marks easily. And faculty can maintain the records easily.
4.2. Objective and Scope

The objective of “College management System” is to
bring all the courses related activities under one roof and to make easy the process
of finding -up of various study material by the students.
 All the Attendance, Sessional Marks Management, Result, Notices related
procedures will be based on intranet and will be online(Computerized).
 Now faculty can easily take the attendance and can maintain the record of
students.
 Faculty can also retrieve the attendance report on any subject of any
semester that will be processed on the basis of the attendance data stored in
the database.
 Faculty can also enter the sessional marks of the students that will be
directly stored in the database.
 With the help of which the students can get their result retrieved from the
database.
 The students as well as their parents will also be able to retrieve the
student’s attendance report on the basis of the month.
 The students will be able to give feedback related to any subject of the
College/Department.
 The Faculty / Students / Others will also be able to enter complaint on the
basis any subject of the department.
The Scope of this application is limited only to the
mentors and students of IT department; they can login to the system with their

Intranet login ID and Password. The software is designed in such a manner that
anyone who is interested in having knowledge about IT related contents can access
this software. The scope of this project is global of IT users as it is available 24*7
over Intranet in Bundelkhand University.
4.3. Definition, Acronyms and Abbreviations

 Definition: -Software to serve as a discussion forum to provide easy
searching for different students seeking knowledge in IT all at one place.
The following abbreviations and acronyms have been used in this project report:
 ASP.NET: ASP is a web application framework developed and marketed by
Microsoft to allow programmers to build dynamic web services.
 ASP: Active Server Pages.
 SQL: Structured Query Language.
 HTML: Hypertext Markup Language.
 SMTP: Simple Mail Transfer Protocol.
 ODFS: Online Discussion Forum System.
 HTTP: Hypertext Transfer protocol.
 IIS: Internet Information Server
 CMS: College Management System.
4.4. References
This document is prepared in consideration to the following:
 IEEE Recommended Practice for Software Requirement Specification- IEEE
Standard.
 “Software Engineering” by K.K. Agrawal and Yogesh Singh.
 Project Guide: Miss. Varsha Agrawal.
4.5. Overview
The rest of this SRS document describes the various system requirements,
interfaces, features and functionalities in details.

5. Overall Descriptions
The College management system is to be designed for

users to discuss the various subject related problems on their desktop online.
Faculty can take attendance online and can maintain marks online. Students are
able to view their marks easily.
The faculty this can upload the data and the uploaded data is saved in XML/HTML
format. Various features can be used by viewing the project:
5.1. Product Perspective

• The College Management System is an ASP.Net application that resides on
the servers as well as the client machines that has an XP operating system.
The database used to store the data will be SQL server 2005.
• The users can access the application through Intranet connecting clients to
servers.
5.2. Interfaces
The system will have the GUI to interact with the users. The main requirement to
interact with the system would be of course to have an Intranet condition.
5.3. User Interface

The Primary interface via which user will interact with the system is a Web
Browser and for the system is should be Mozilla Firefox3.0. And definitely an
Intranet connection is required. Format of main screen shall be standard and
flexible. The System shall be user friendly designed. Pages shall be connected each
other in consistent way.
5.4. Software Interfaces

 Client

 Operating System: Window 2000/XP/Vista/7/8/10+
 Web Server: Mozilla Firefox 3.0
 Server
 Operating System: Window 2000 sever/ server 2003
 Database Server: Microsoft S Application Framework: Microsoft ASP.Net
2.0
 Development End
 Operating System: Windows 2000/XP/Vista/7/8/9/10+
 Database Server: Microsoft SQL Server 2008
 Development Framework: Microsoft Visual Studio 2010
Visual Studio will be required only for the development of

the application. The final application will be packaged as an independent setup
program that will be delivered to client.
5.5. Hardware Interfaces
 Client
Any machine that has Intranet connection.
For PC (Windows)
1GHz or greater)
 RAM: 64 MB RAM (Recommended: 128 MB RAM+)
 Hard disk: 1.5GB of available hard disk space

 Other: Video adapter & monitor with Super VGA (800 X
600) Or higher resolution displays with 256 Colors,
DVD-ROM or CDROM drive;
Keyboard and Mouse or compatible pointing device.
 Server
 Processor: Pentium III – compatible processor or higher with a
minimum of 600 MHz (Recommended:1GHz or greater)
 RAM: Minimum 512MB or Maximum 4GB (Recommended
1GB)
 Hard Disk: Minimum 8GB of free Hard Disk space.
 Development End
1GB or greater)
 RAM: Minimum 512MB or Maximum 4GB (Recommended:
1GB)
 Hard Disk: Minimum 4GB of available hard disk space
(Recommended :> 20GB)
 Other: Video adapter& monitor with Super VGA (1024X 768)
Or higher resolution displays with 256 colors;
DVD-ROM or CD-ROM drive;
Keyboard and Mouse or compatible pointing device
5.6. Communication Interface

The following protocols will be used in the system:

 HTTP/HTTPS
 SMTP
5.7. Site Adaption Requirements

The terminals at client side will have to support the hardware and software
interfaces specific above.
6. Product Functions
Application will have the following provisions with proper Interfaces:
 First of all, the admin will add the details of the students as well as the
faculty in the database during their admission or the arrival to the
department.
 The faculty as well as the faculty have to register themselves for the use of
CMS.
 To register themselves to the CMS the faculty and student should have their
ID / Roll No that has been provided by the Admin of the Department.
 Users will login by authenticating themselves with their login ID &
passwords.
 All the registered users should be available to the user at any point in the
system.
 Based on the role specified to the users, users will be accessing the
application.
 The user will be verified for that role whether it is authenticated for the
chosen role.
 Three roles are identified for this system,
 Administrator of IT Department
 Faculties of concerned subjects
 Native users i.e. every student can access the system anytime as a
Native user.
 According to the roles system functions have been divided amongst three
modules/components, with each of them specific to the User role. They are
stated as under:
 Module 1:
As an Administrator of a system:
 Should be able to login into the system.
 Should be able to add new faculty to the database of the CMS.
 Should be able to add new student to the database of the CMS.
 Provide Roll No to the student and ID to the Faculties.
 Should be able to retrieve any student / Faculty information or details.
 Should be able to manage the feedbacks send by the students.
 Should be able to manage the complaints that has been done by vari\ous
users.
 Should be able to manage the Notice board of the site of CMS.

 Module 2:
As a faculty:
 Should be able to view student details.
 Should be able to take attendance on the CMS site online that will be
stored in the for further use.
 Should be able to view the attendance report of any student at any
subject.
 Should be able to enter sessional marks of the students that will be stored
in the database.
 Should be able to view the information on notice board.
 Should be able to give complaint on any subject.
Module 3:
All user of the system:
 Should be able to view its Attendance report.
 Should be able to view its attendance report on the basis of month of each
subject.
 Should be able to view its Time Table of the course w.r.t the semester.
 Should be able to view/download its subject syllabus.
 Should be able to view its sessional result.
 Should have at least one role (Native user) for them and should be able to
specify the role for login.
1. Once chosen a role, users should have available to it the access to all the
operations defined for the selected role until the user logout from the
system.
2. Users should be able to logout from the system at any point of time after
selecting the role of login.
CONTEXT LEVEL DIAGRAM

ADD NEW STUDENT REGISTER
ADMIN ADD NEW FACULTY FACULTY
LOGIN
UPLOAD MARKS
VIEW STUD. & FACULTY
DETAILS
MANAGES FEEDBACK UPLOAD ATTENDANCE

& COMPLAINTS
COLLAGE
VIEW ATTENDANCE &
MANAGEMENT MARKS
MANAGES NOTICE BOARD
SYSTEM
REGISTER
LOGIN
PROVIDE ROLL NO, ID
FEEDBACK &
COMPLAINTS VIEW MARKS
VIEW ATTENDANCE
REPORT
STUDENT
6.1. User characteristics:

The user of this system must possess the following characteristics:

1.Must be a permanent student of Bundelkhand University.
2.Educational level: Users should be comfortable with the English language.
3.Technical expertise: Should be comfortable using general purpose applications.
 Constraints:
The following constraints applied to this system:
The system is for the use of Bundelkhand University students only.
To upload or access the information user must possess a valid Intra login ID
and password.
For uploading the files, user needs not to go into the details of the
technology.
6.2. Assumptions and Dependencies

The user must be connected to the intranet to use the system.
The queries and answers submitted by the student &faculties do not change.
The user’s computer must be Windows 95 or later version platforms.
The accuracy of the information of users is the responsibility of all users.
6.3. Specific Requirements

This section contains all the software requirements at a level of detail, sufficient to
enable designers to design a system to satisfy those requirements.
6.4. External Interfaces

The external interface requirements refer to the user
interfaces that have been designed for the user to interact with the system and
perform the required tasks as mentioned in the product functions. The system shall
provide the following interfaces to the user for accessing the system:
The system shall have same interface(s) for all the users entering to the system
until user specifies his/her role-of -login.
Such interfaces are:

 Home: This interface shall provide to user some information about the
system he/she is going to use, as well as shall provide to user an option to
register itself and also for logging to the system for performing other
operation.
 CMS Registration
CMS Student Registration Page: This interface shell provides
students a way to register itself for accessing its modules of CMS.
CMS Faculty Registration Page: This interface shell provides faculty’s
a way to register itself for accessing its modules of CMS.
 CMS Login: This interface shell provides a way to authenticating the
accessing user.
CMS Admin Login Page: This interface shell provides Admin a way to
itself for accessing its CMS modules.
CMS Faculty Login Page: This interface shell provides faculty a way
to authenticate itself for accessing its CMS modules.
CMS Student Login Page: This interface shell provides student a way
to authenticate itself for accessing its CMS modules.
 Specify the Role: This interface shall ask to the user for the role, amongst
his/her assigned role, he/she wants to access the system with.
 Contact US: This interface shell provides contact information about the
department.
 About US: This interface shell provides information about the department.
 Gallery: This interface shell provides the pics related to many events
occurred in the department as well as the pics of the faculties.
 Depending on the role chosen, the user will have different interfaces as
stated below:
 ADMIN: Manages the whole system. This interface shall give way to the
following interfaces:
 Add new Student: This interface shall let the user to add a new
student (i.e. add one) in the system’s database profile.
 Add new Faculty: This interface shall let the user to add a new faculty
(i.e. add one) in the system’s database profile.

 Delete users: This interface shall let the user to delete the account (i.e.
remove one) from the system’s profile.
 Upload Information: This interface shall upload various information
(last year question papers, syllabus, and other information).
 Notice bulletin management: This interface shall let the user know
about what important information is released from the department.
 Gallery Management: This interface will provide to upload photos
related to the campus to the users to the gallery.
 Feedback and Complaint Management: This interface will provide
the admin to know the feedbacks and the complaints given by the
users online on any subject.
 FACULTY: This interface shall give way to the following interfaces:
 Upload Attendance: This interface will help the faculty to take

attendance of its course subject online.
 Upload marks: This interface will help the faculty to maintain
sessional marks of the students.
 Attendance Report: This interface will help the faculty to obtain the
attendance report of any subject based on the month.
 Complaint: This interface will help the faculty to upload complaints
related to any subject of the department/college.
.
 STUDENT: This interface shall give way to the following interfaces:
 Viewing marks: This interface shall provide the details of marks

given to the student.
 Viewing Attendance Report: This interface shall provide the details
of attendance of the class subject.
 Complaint: This interface shall provide the student to give/upload
complaint on the basis of any subject.
 Feedback: This interface shall provide the student to give/upload
feedback on the basis of any subject.
 Time-Table: This interface shall provide the timetable of its class to
which the student belongs.

 Syllabus: This interface shall provide the student to download/view
its syllabus of the subject.
USE CASE DIAGRAMS FOR COLLEGE MANAGEMENT SYSTEM

ARE GIVEN BELOW: -
USE CASE DIAGRAM FOR COLLEGE MANAGEMENT SYSTEM
ADD NEW FACULTY

ADD NEW STUDENT
VIEW STUD., FAC., DETAILS
SIGNUP TO CMS
ADMIN
LOGIN
GALLERY MANAGEMENT
DELETE EXISTING USER
FACULTY
UPLOAD ATTENDANCE
VIEW ATTENDANCE
REPORT
UPLOAD MARKS
VIEW MARKS
STUDENT
MANAGES NB, TT, SYL..
USE CASE DIAGRAM FOR ADMIN

LOGIN

ADD NEW STUDENT
ADD NEW FACULTY
DELETE EXISTING
STUDENT/FACULTY
GALLERY MANAGEMENT
MANAGES TT, SYLLABUS

ADMIN
NOTICE BOARD
MANAGEMENT
COMPLAINT, FEEDBACK
MANAGEMENT
VIEW STUDENT, FACULTY

DETAILS
USE CASE DIAGRAM FOR FACULTY
LOGIN

SIGNUP TO CMS
UPLOAD ATTENDANCE
VIEW ATTENDANCE REPORT
FACULTY
UPLOAD SESSIONAL MARKS
VIEW STUDENT DETAILS
ENTER COMPLAINTS
USE CASE DIAGRAM FOR STUDENT

SIGNUP FOR CMS

LOGIN
VIEW SESSIONAL MARKS
VIEW ATTENDANCE
REPORT
STUDENT VIEW TIME TABLE
VIEW SYLLABUS
ENTER COMPLAINT
ENTER FEEDBACK
6.5.2. Use Case Description
(i). Use case 1:

Name of Use Case: Add new faculty/Student.

Description: For the future authentication of the user that he/she is a member of
the department.
Primary Actor(s): Admin.
Precondition:
 Actor(s) must be logged in.
Normal Flow of Event:
 Enter the details of the new member.
 Submit the details to the system.
Alternate Flow of Event:
 A message appears for submission of data.
Post Condition:
 The faculty will get its Faculty ID.
 The student will get the Roll No.
(ii). Use case 2:

Name of Use Case: Login.
Description: For user authentication.
Primary Actor(s): May be Admin, Student or the Faculty.
Precondition:
 Actor(s) must be registered before logged in.
 Actor(s) must possess login ID & password.
 Enter the login ID & password.
 Get authenticated by the system.
 A message appears for invalid login ID & password.
 Enter the login ID & password again.

Post Condition:
 Only authenticated users will enter & get access to the system on the basis of
their specific role.
(iii). Use Case 3:

Name of Use Case: Registration to CMs.
Description: To register to the CMS to access its modules.
Primary Actor(s): May be Faculty, Student.
Precondition:
 The faculty/ student should be a member of the department.
 The faculty should have their ID Provided by the Admin.
 The student should have their Roll_No provided by the Admin.
 The student /faculty should have their details.
 They should have their pics also.
 The student / faculty should choose / enter the password for login.
 If any duplicity appears then message appears.
 The Actor has to send the details again.
Post Condition:
 A message will be displayed on successful transmission of code.
 Now the faculty will have their Faculty Id and Password to Login to the
CMs.
 Noe the student will have their Roll No and Password to Login to the CMs.
(iv). Use Case 4:
Name of Use Case: Delete an existing user.
Description: To delete an existing member.
Primary Actor(s): Admin.

Precondition:
 Admin is already logged in.
 A list of already registered users appear.
 Select the user name.
 Confirm deletion.
Alternate Flow of Events:
 None
Post Conditions:
 User details will be removed from the data storage.
 A message will be displayed on successful deletion.
(v). Use Case 5:

Name of Use Case: Upload information.
Description: To upload information like Time-Table of any course, syllabus and
event related notices.
Primary Actor(s): IT Admin.
Precondition:
 Admin is already logged in.
Normal Flow of Events:
 Options related to different category are given.
 Select the category for which the information is to be uploaded.
 Browse the file.
 Upload the selected file.
 None
Post Conditions:

 A message will be displayed on successful upload of the information.
(vi). Use Case 6:

Name of Use Case: Upload attendance.
Description: To assign the attendance of the students to the database.
Primary Actor(s): Faculty.
Precondition:
 Faculty is already logged in.
 Choose the Course name.
 Choose the subject name of which attendance to be assigned.
 The students roll number and a checkbox corresponding to all roll numbers
will be displayed.
Post Conditions:
 A message will be displayed on successful upload of the attendance.
(vii). Use Case 7:

Name of Use Case: Retrieve attendance report.
Description: To retrieve the attendance report of the students w.r.t to the data
stored to the database.
Primary Actor(s): Faculty, Students, outsiders (parents also).
Precondition:
 Faculty is already logged in.
 Student is already logged in.
 Others should open the attendance report page.

 Choose the Course name.
 Enter the student’s roll number.
 Choose the subject name of which attendance to be assigned.
 Enter the month in numerical form of which report is needed.
 None.
Post Conditions:
A message will be displayed that will display the total attended classes and total
classes.
(viii). Use Case 8:

Name of Use Case: Upload marks, Retrieve marks.
Description: To assign the sessional marks the students to the database.
To retrieve the sessional marks of the students.
Primary Actor(s): Faculty.
Anyone (Admin, Faculty, Student, Others).
Precondition:
 Faculty is already logged in to enter the marks.
 Result page must be opened.
 Choose the Course name. (To assign marks)
 Choose the semester. (To assign marks)
 Choose the subject name of which marks to be assigned. (To assign marks)
 To retrieve the result one must know the course, roll no, semester.
 The students roll number and a textbox corresponding to all roll numbers
will be displayed.
Post Conditions:

A message will be displayed on successful upload of the marks.
A message will be displayed with the roll no , subject name and the marks of the
student.
(ix). Use Case 9:
Name of Use Case: Complaint, feedback.
Description: To enter complaint related to any subject to the department
To enter the feedback by the student.
Primary Actor(s): Anyone (Admin, Faculty, Student, Others).
Student Only.
Precondition:
 Student is already logged in to enter the feedback.
 Complaint page must be opened.
 Authentication of the student will be held w.r.t its roll number in the case of
feedback submission.
 The subject of the complaint as well as the feedback will be asked.
Post Conditions:
A message will be displayed on successful upload of the complaint and feedback.
6.6. Performance Requirements

The system performance is adequate. However, ODFS is working with the user
intranet connection, 70% performance is up to the client side.
6.7. Design Constraints

All documentation of the system shall be prepared related to IEEE standards.
Furthermore, the content shall be compliance with IEEE standard [1, 2, 3].

6.8. System Attributes
There are number of attributes of system that as requirements. t is important that
those required attributes be specified so that their achievement can be objectively
verified. These are also known as non-functional requirements or quality attributes.
6.8.1. Security
User’s Role specific functions shall be performed by the assigned users only. The
application security shall be implemented through Session variables and user’s
roles. User’s navigation between the pages of the application shall be controlled
through proper session maintenance so as to maintain the security of a system.
6.8.2. Maintainability
The application should be designed in a maintainable manner. It should be easy to
incorporate new requirements in the individual modules. The modules of this
system shall be divided based on user’s role so that specified functions for each
user role does not mix up and thus remain easily maintainable.
6.8.3. Portability
The application shall be easily portable on any windows –based system that has IIS
and SQL-server 2008 installed.
6.8.4. Reliability
The system shall operate 90% of time. The number of defect should not exceed 10
per function.
6.8.5. Availability
The availability of the ODFS is upto the intranet connection of the client. User
should have an account to enter the system, if user does not have any account; for
the availability of ODFS user should sign up to the system by clicking the sign up
link from the home page.

Other Requirements
There is no other requirement in this phase. If some extra requirements are wanted
by the customer or acquirer, these are added in this part later.
7. System Architectural Design
7.1. User Interface Issues

Three types of users can use this software. User can be Admin, Faculty or Student
of Bundelkhand University. All the users will have different access and rights
granted by this software.
 ADMINISTRATOR: Manages the whole system. This interface shall give
way to the following interfaces:
 Add Students/Faculty: This interface shall let the user to create a new
account of faculties (i.e. add one) in the system’s profile.
 Delete users: This interface shall let the user to delete the account (i.e.
remove one) from the system’s profile.
 Upload Information: This interface shall upload various information (last
year question papers, syllabus, Notices, Timetables and other information).
 Upload photos: This interface shall upload various photos of the campus to
the gallery.
 FACULTY: This interface shall give way to the following interfaces:
 Upload Attendance: This interface will help the faculty to take

attendance of its course subject online.
 Upload marks: This interface will help the faculty to maintain
sessional marks of the students.
 Attendance Report: This interface will help the faculty to obtain the
attendance report of any subject based on the month.
 Complaint: This interface will help the faculty to upload complaints
related to any subject of the department/college.
 STUDENT: This interface shall give way to the following interfaces:
 Viewing marks: This interface shall provide the details of marks given to the
student.
 Viewing Attendance Report: This interface shall provide the details of
attendance of the class subject.
 Complaint: This interface shall provide the student to give/upload complaint
on the basis of any subject.

 Feedback: This interface shall provide the student to give/upload feedback
on the basis of any subject.
 Time-Table: This interface shall provide the timetable of its class to which
the student belongs.
 Syllabus: This interface shall provide the student to download/view its
syllabus of the subject.
7.2 Data Flow Diagram

DFD Level 0
ADMIN
ADD NEW UPDATE / DELETE

STUDENT / FACULTY OVERALL DATA
COLLEGE SIGN UP
SIGN UP
MANAGEMENT
SYSTEM
ISSUE PASSWORD
ISSUE PASSWORD
UPLOAD MARKS, VIEW MARKS,

ATTENDANCE ATTENDANCE
FACULTY STUDENT
DATA FLOW DIAGRAM (Level 1)

COLLEGE MANAGEMENT SYSTEM
STUDENT
MARKS
INFORMATION
SIGN UP
MEMBERSHIP
DETAILS VIEW MARKS
COLLEGE
MANAGEMENT
VIEW ATTENDANCE
SYSTEM
V MEMBERSHIP DETAILS
ATTENDANCE
SIGNUP
REGISTER
LOGIN FUNCTION
FACULTY
ADMIN
8. DATABASE DESIGN

8.1. Database Description
In this we include, maintain & format Databases and its tables.
The tables corresponding to each of the entity, holding the information about them
are designed.
The tables have the fields, their description, and their data type as well as integrity
constraints.
 ADDING OF FACULTY BY ADMIN AS A MEMBER OF
DEPARTMENT-
 ATTENDANCE TABLE-
 ADDING OF FACULTY BY ADMIN AS A MEMBER OF

DEPARTMENT-

 SEMESTER WISE STUDENT TABLE-
 GALLERY MANAGEMENT TABLE-
 FACULTY REGISTRATION TABLE-

 STUDENT REGISTRATION
 FEEDBACK TABLE-

 COMPAINT TABLE-
 SESSIONAL MARKS TABLE-
9. Detailed Description Of Component

9.1. New Student Membership Module
Description of Component
This module allows the new student to become the member of the Department
/College.
Interface Description
Inputs: - Student’s all details.
Outputs: -Roll number of Student.
Processing Details
Admin is responsible for membership of new student to the department. The admin
should be logged in. The Add student form should be displayed and be filled
properly with the correct student details. At the end of the membership successful
the admin will provide roll number to the student will be used for registration later.
9.2. New Faculty Membership Module
This module allows the new faculty to become the member of the Department
/College.
Inputs: - Faculty’s all details.
Outputs: - Faculty ID of Faculty.
Processing Details
Admin is responsible for membership of new faculty to the department. The admin
should be logged in. The Add faculty form should be displayed and be filled

properly with the correct faculty details. At the end of the membership successful
the admin will provide ID to the faculty will be used for registration later.
9.3. Registration Module
This module allows the new user to become the member of the site.
Inputs: -All user details, the roll no of the student, the Id for the faculty.
Outputs: -The Successful User register submission page.
Processing Details
Display the form containing fields of user details to be filled by user in order to get
registered.
Check whether the information submitted is proper or not and all fields are
properly filled or not user id is unique or not.
9.4. Login Module
Description of component
In order to make the system safe from unauthorized access it is protected with user
name and password, so that only valid and legitimate users can access the system.
Inputs: - Faculty ID and Password for the Faculty Login.
Roll Number and Password for the Student Login.
Outputs: - The CMS Homepage will open up.

Processing Details:-Display the different login screen for Faculty and Student.
Faculty will use its Id and password to login, and student will use its Roll number
and password.
Mark all the fields as compulsory.
Check whether r the user name is valid or not, if yes check whether password
matches or not. Open the main form after clicking Login button after validation
checking.
9.5. NOTICES
Description of components
This module is used to view, add and delete notices according to user
authorization.
ADD NOTICE
Description
Admin and staff member can add the notices.
Input:-Notice topic, Notice detail, date of issue, date of expiry, concerned person
and category.
Output:-New notices
Processing Detail: Admin and faculty members can click on add notices
option to add any new notice.
VIEW NOTICES
Description
Admin, faculty and student member and student can view the notice.
Input: - Click the notice button

Output: - View notices
Processing Details
Admin, Faculty and students members can click on notice subject to view any
existing notice.
DELETE NOTICES
Description
Admin can delete the notices.
Input: - Notice ID
Output:-Notice is deleted.
Processing Details
Admin can click on notice subject to open the notice and then use delete option to
delete any existing notice.
9.6. Update module

Description of component
This module is used to update the database by Admin.
Input: - Account details, event details.
Output: - Update the database and display a message for updated successfully.
Processing Details First admin enters the desired information which is to
be modified and then submission of changes is done.
9.7. Feedback

This module is used to give the feedback about the faculty as well as other
subjects.
Input: - Feedback given.
Output: - Redirect on user home page.
Processing Details
Click on feedback button and after this write the feedback on feedback form.
9.8. Complaint
This module is used to give the Complaint about the faculty as well as other
subjects.
Input: - Complaint given.
Output: - Redirect on user home page.
Processing Details
Click on Complaint button and after this write the complaint on complaint form.
9.9. Attendance
This module is used to take the attendance of any subject of any course online on
the intranet with the CMS. Only the faculty can perform this module after he is
logged in.
Input: - Checking on the present students corresponding checkbox.
Output: - Redirect on the submission successful page.

Processing Details
The faculty should login firstly. Then the faculty should click on the Attendance
Management system option and then should click on the “Enter Attendance
“option. Now the faculty have to choose course, subject and semester of which he
has to take the attendance. After it the table will be visible with the roll number of
the students of the class and the checkbox corresponding to it.
9.10. Sessional Marks

This module is used to enter the sessional marks of any subject of any course
online on the intranet with the CMS to store it in the database. Only the faculty can
perform this module after he is logged in.
Input: - Entering the marks of the students in the textbox corresponding to the roll
number of the student.
Output: - Redirect on the submission successful page.
Processing Details
The faculty should login firstly. Then the faculty should click on the Sessional
Marks Management system option. Now the faculty have to choose course, subject
and semester of which he has to enter the sessional marks. After it the table will be
visible with the roll number of the students of the class and the textbox
corresponding to it.
E-R DIAGRAM OF COLLEGE

MANAGEMENT SYSTEM
CODE
DEPARTMENT
1
OFFER BY
NAME 1
MANAGES
ID
1
NAME
ADMIN
PHOTO
ID
1
REGISTER
NAME
N N ROLL NO
NAME
F.NAME
FACULTY
STUDENT F.NAME
DOB N ADD
EMAIL N
ADD
PHN PHONE
DOB
SPECILISATION TEACH
CODE N
N GENERALISATION
NAME COURSE
10.User Interface Design

o HOMEPAGE
o ADMINISTRATOR’S LOGIN PAGE
o ADMINISTRATOR’S HOMEPAGE AFTER LOGIN

o ADDING OF FACULTY / STUDENT AS MEMBER BY ADMIN

o FACULTY AND STUDENTS CMS REGISTERATION PAGE
o VIEW STUDENT DETAILS BY ADMIN

o FACULTY AND STUDENT’S LOGIN PAGE
o ENTERING ATTENDANCE

o RETRIEVING ATTENDANCE REPORT

o MARKS SUBMISSION
o RETRIEVING SESSIONAL MARKS

o FEEDBACK SUBMISSION PAGE
o COMPLAINT SUBMISSION PAGE

11.Testing Issues
Software testing can be stated as the process of validating ad verifying that a

software program/ application/ product:
Meets the requirements that guided its design and development;
Works as expected; and can be implemented with the same characteristics.
Testing is the process of making sure that the program performs the intended tasks.
 Unit Testing: Each component or part of the system is tested individually.
 Module Testing: A collection of dependent components such as an object

class, procedures and functions are tested in this testing.
 Integration Testing: In this, many units tested modules are combined into
sub systems, which are then tested.
 System Testing: Entire system software is tested. It is a testing of the

system against its initial objectives.

12.REFERENCES
1.ASP.NET Unleashed, Second Edition by Stephen Walther

2.Programming Microsoft.NET Applications: Advanced topics by Glenn Johnson
3.ADO.NET in a Nutshell by Bill Hamilton, Matthew MacDonald
4.Project Guide – Miss.Varsha Agrawal Mam.
A) stackoverflow.com

13.CONCLUSION
The application works satisfactory. Using it the users can perform the listed
function appropriately. The result of the application is pleasing.
The website gives accurate and desired results in various ways. Overall the
performance of the application is near to perfection. It works according to user’s
demand.

Project Description: 1.1. Current Scenario

Uploaded by

Copyright:

Available Formats

Project Description: 1.1. Current Scenario

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project Description: 1.1. Current Scenario

Uploaded by

Copyright:

Available Formats

1.

1.1. Current Scenario

1.2. Problem with the existing system

1.3. Proposed Solution

COLLEGE MANAGEMENT SYSTEM PROJECT (BCA 6TH SEM) 1

COLLEGE MANAGEMENT SYSTEM PROJECT (BCA 6TH SEM) 2

2.1. Hardware Requirements

 Processor: Pentium 233MHz (Recommended: Pentium

2.2. Software Requirements

COLLEGE MANAGEMENT SYSTEM PROJECT (BCA 6TH SEM) 3

COLLEGE MANAGEMENT SYSTEM PROJECT (BCA 6TH SEM) 4

 Why is ASP.Net 2.0 proffered?

 Specific areas in which ASP.NET has been improved are:

 Microsoft SQL Server:

COLLEGE MANAGEMENT SYSTEM PROJECT (BCA 6TH SEM) 6

Depending on the results of

3.1. Technical Feasibility

3.2. Operational Feasibility

3.3. Economical Feasibility

3.4. Social Feasibility

COLLEGE MANAGEMENT SYSTEM PROJECT (BCA 6TH SEM) 7

4.2. Objective and Scope

COLLEGE MANAGEMENT SYSTEM PROJECT (BCA 6TH SEM) 8

4.3. Definition, Acronyms and Abbreviations

COLLEGE MANAGEMENT SYSTEM PROJECT (BCA 6TH SEM) 9

The College management system is to be designed for

5.1. Product Perspective

5.3. User Interface

5.4. Software Interfaces

COLLEGE MANAGEMENT SYSTEM PROJECT (BCA 6TH SEM) 10

Visual Studio will be required only for the development of

5.5. Hardware Interfaces

COLLEGE MANAGEMENT SYSTEM PROJECT (BCA 6TH SEM) 11

5.6. Communication Interface

COLLEGE MANAGEMENT SYSTEM PROJECT (BCA 6TH SEM) 12

5.7. Site Adaption Requirements

COLLEGE MANAGEMENT SYSTEM PROJECT (BCA 6TH SEM) 14

CONTEXT LEVEL DIAGRAM

COLLEGE MANAGEMENT SYSTEM PROJECT (BCA 6TH SEM) 15

MANAGES FEEDBACK UPLOAD ATTENDANCE

6.1. User characteristics:

COLLEGE MANAGEMENT SYSTEM PROJECT (BCA 6TH SEM) 16

6.2. Assumptions and Dependencies

6.3. Specific Requirements

6.4. External Interfaces

COLLEGE MANAGEMENT SYSTEM PROJECT (BCA 6TH SEM) 17

COLLEGE MANAGEMENT SYSTEM PROJECT (BCA 6TH SEM) 18

 FACULTY: This interface shall give way to the following interfaces:

 Upload Attendance: This interface will help the faculty to take

 Viewing marks: This interface shall provide the details of marks

COLLEGE MANAGEMENT SYSTEM PROJECT (BCA 6TH SEM) 19

USE CASE DIAGRAMS FOR COLLEGE MANAGEMENT SYSTEM

USE CASE DIAGRAM FOR COLLEGE MANAGEMENT SYSTEM

ADD NEW FACULTY

COLLEGE MANAGEMENT SYSTEM PROJECT (BCA 6TH SEM) 20

VIEW STUD., FAC., DETAILS

DELETE EXISTING USER

MANAGES NB, TT, SYL..

USE CASE DIAGRAM FOR ADMIN