MUFFAKHAM JAH COLLEGE OF

ENGINEERING AND TECHNOLOGY

ESTABLISHED BY

SULTAN UL ULOOM EDUCATIONAL

SOCIETY
(A MINORITY INSTITUTION)
AFFILIATED TO O.U., HYDERABAD.
APPROVED BY A.I.C.T.E AND PERMITTED BY GOVT. OF INDIA
BANJARA HILLS ROAD NO. 3, HYD.
DEPARTMENT OF INFORMATION TECHNOLOGY
OBJECT ORIENTED SYSTEMS DEVELOPMENT PROJECT
E CAMPUS SYSTEM

SUBMITTED BY:
Mubashir Ahmed------------04075046
Zainab Aafia-----------------04075047

CONTENTS
1. ABSTRACT -----------------------------------------------------------------------3
2. DESCRIPTION ------------------------------------------------------------------3
3. USE CASE DIAGRAMS -------------------------------------------------------5
4. USE CASE SPECIFICATION------------------------------------------------9
5. ACTIVITY DIAGRAMS------------------------------------------------------11
6. SEQUENCE DIAGRAMS----------------------------------------------------19
7. COLLABORATION DIAGRAMS------------------------------------------23
8. CLASS DIAGRAMS-----------------------------------------------------------27
9. STATE CHART DIAGRAM-------------------------------------------------28
10. COMPONENT DIAGRAM-------------------------------------------------29
11. DEPLOYMENT DIAGRAM-----------------------------------------------29
12. SOFTWARE REQUIREMENT SPECIFICATION-------------------30

E CAMPUS SYSTEM
ABSTRACT
The E Campus system provides courses for distance education over the internet. This
eliminates the need for traveling to an institute.
The E Campus is a virtual campus of an institute offering various programmes for
individuals and companies. The students can select a course from a list and sign up for it.
The system provides a forum for the students and teachers to interact via lecture threads,
chat and email. The student can also take assessment tests to analyse his progress.
The objective of the project is to develop a system that will allow groups of students and
lecturers to communicate over the internet via chat, email and note-posting systems.
Thus E Campus is an electronic book which allows you to browse guides or lectures
online. It does not require as much time nor cost as creating a homepage. You can look
up information online before requesting it to the company. You can use the website as if
you were actually flipping the pages. The students can only post their doubts and get
information regarding them.

DESCRIPTION
User Requirements
The E Campus system may have 4 types of users:
1) Guest: Any member can use the E Campus system to browse some of the
systems web pages to view information. For security reasons they will not have
access to the student or lecturer pages. If a member of the pubic wishes to do so,
they can register on a course with e Campus via the registration web page.
2) Student: These are users who have registered as students for a particular course.
The Student users of the system will be able to log on to the system via the Log
On web page. Once logged on they can access the chat rooms and use the email
system to send and receive emails. They also have access to view entries, from the
database of posted course notes.
3) Lecturer: These are users who have registered as lecturers. The lecturer is
associated with similar functionality to the students. As well as being able to use
the chat rooms and the email system, they have the additional option of posting
course notes to the database once logged on to the system.

4) System Administrator: These users have access to the entire system and are
responsible for the maintenance of the system.

Functional Requirements
1) Chat Application: Once a student or lecturer logs into the system, he can use the
chat application to chat with his fellow students or lecturers. This way the student
can get his doubts cleared instantly. The user of the chat system logs on to the
system and selects a room that they wish to enter. They may then view the
messages typed by other members of the chat room as they appear on the screen.
They then have the option to log out or to enter text into the room. This can be
done many times before logging out of the room.
2) Email System: A user of the system can take on the roles of both sender and
receiver. The user must first log in to the email system. The sender then can create
an email and send it to the chosen destination. The receiver receives the email and
may delete it or respond to it. Once a response is created the email can be sent.
3) Test Application: This application allows lecturers to post questions and create
test papers, which the students can take and assess their progress in the course.
The student can select their respective course and take the test, which will consist
of multiple choice questions. At the end of the test, the student can view his score.

USE CASE DIAGRAMS

E Campus System

Chat Application

Email Application

Assessment Test Application

USE CASE SPECIFICATION

View Info
1.
2.
3.
4.
5.

Use Case Name: View Info

Summary: This use case allows any user to view info about the courses
Actors: Guest, Student and Lecturer
Preconditions: Nil
Description: When the user accesses the page it displays a list of courses. When
the user selects any course it displays the course details.
6. Postcondition: Nil
7. Alternatives: Nil

Register for Course

1. Use Case Name: Register for Course.
2. Summary: This use case allows any user to register for a particular course as a
student or a lecturer.
3. Actors: Guest, Student and Lecturer
4. Precondition: Nil
5. Description: When the user visits the registration page the system gives an option
to register as a student or lecturer and then takes the details of the user.
6. Postcondition: The users account is added to the database as student or lecturer.
7. Alternatives: Nil

Log On
1.
2.
3.
4.
5.

Use Case Name: Log On.

Summary: This use case allows a registered user to login to the system
Actors: Student and Lecturer.
Preconditions: The user should have a registered username and password.
Description: The user enters the username and password and the system verifies
the details, if they are found to be valid the user is allowed access to the system.
6. Postconditions: The user is allowed access to the various applications.
7. Alternatives: If the username and password are not valid it displays invalid
details message.

View Course Notes

1.
2.
3.
4.
5.

Use Case Name: View Course Notes.

Summary: This use case allows the user to view course notes.
Actors: Student and Lecturer.
Precondition: The user should be logged in.
Description: When the user accesses the view course notes page it should display
the index and contents and the user will select the desired content he wants to
view.
6. Postcondition: Nil
7. Altenatives: Nil.

Chat

1.
2.
3.
4.
5.

Use Case Name: Chat

Summary: This use case allows the user to chat with fellow users.
Actors: Student and Lecturer.
Precondition: The user should be logged in.
Description: When the user accesses the chat application it displays a list of
rooms, the user selects the particular room views the messages and also types the
messages to be sent. This can be done several times before he logs out.
6. Postcondition: The user appears online to other people using the same chat room
7. Alternatives: If login is invalid, the user is alerted.

Send and Receive Emails

1.
2.
3.
4.
5.

Use Case Name: Send and Receive Mails.

Summary: This use case allows user to send and receive mails.
Actor: Student and Lecturer.
Precondition: The user should be logged in.
Description When the user accesses this application, he is notified of any new
mails received that he has not read. When the user receives a mail, he has the
option to either respond to it or delete it or both. Apart from receiving mails, the
user can also create and send mails.
6. Postcondition: The mail is sent or deleted depending upon the users choice.
7. Alternatives: If the user gives an invalid destination address for the mail to be
sent it displays a message invalid destination address. The user is notified if
login is invalid.

Post Course Notes

1.
2.
3.
4.
5.

Use Case Name : Post Course Notes

Summary: This use case allows the user to post course notes.
Actor: Lecturer
Precondition: The user should be logged in as a lecturer.
Description: When the lecturer wishes to post notes, the system allows him
access to a text editor wherein the lecturer will type his notes and click on post,
which will cause the notes to be saved.
6. Postconditions: The notes are saved and can be viewed by other registered users.
7. Alternatives: If the user is not a lecturer he is alerted.

Log Out
1.
2.
3.
4.
5.

Use Case Name: Log Out

Summary: This use case allows a user to log out of the system.
Actor: Student or Lecturer
Precondition: The user should be logged in
Description: when the user clicks on the logout option the system will log him
out of his account and take him to the log out page where he will be shown a
message indicating that he has been logged out.
6. Post Conditions: The message You have been logged out successfully is
displayed.
7. Alternatives: Nil

ACTIVITY DIAGRAMS

View Info

Register for Course

Log On

View Course Notes

Chat

Send and Receive Emails

Post Course Notes

Log Out

SEQUENCE DIAGRAMS

View Info

Register For Course

Log On

View Course Notes

Chat

Send and Receive Mails

Post Course Notes

Log Out

COLLABORATION DIAGRAMS

View Info

Register For Course

Log On

View Course Notes

Chat

Send and Receive Mails

Post Course Notes

Log Out

CLASS DIAGRAM

STATE CHART DIAGRAM

E CAMPUS SYSTEM

COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM

SOFTWARE REQUIREMENT SPECIFICATION

1. INTRODUCTION
1.1. PURPOSE
The purpose of the project is to develop a system that will allow groups of students and
lecturers to communicate over the internet via chat, email and note-posting systems
In this case study we shall see how E campus has provided the facility of pursuing
courses in various subjects to students worldwide who prefer the flexibility of online
learning. Distance learners include working adults, community college students, working
and retired professionals, stay-at-home parents, military personnel, high school students
and individuals who simply want to take a college course.
E Campus is an electronic book which allows you to browse guides or lectures online.
It does not require as much time nor cost as creating a homepage. You can look up
information online before requesting it to the company. You can use the website as if you
were actually flipping the pages. The students can only post their doubts and get
information regarding them.
1.2 SCOPE
The E Campus is a virtual campus of an institute offering various programmes for
individuals and companies. The students can select a course from a list and sign up for it.
The system provides a forum for the students and teachers to interact via lecture threads,
chat and email. The student can also take assessment tests to analyse his progress
The system does not provide a platform for exchange of files and documents that are not
allowed outside the frames of e-Campus.
1.3 DEFINITIONS, ACRONYMS OR ABBREVIATIONS
RAM: Random Access Memory. The primary memory of a computer.
MB: Mega Bytes.
GB: Giga Bytes.
JVM: Java Virtual Machine.
GUI: Graphical User Interface.
1.4 REFERENCES
IEEE standard 830-1993
http://ieee.com/student /info.html

2.0 OVERALL DESCRIPTION

2.1 PRODUCT PERSPECTIVE
This system requires the Sun Java Virtual Machine (Sun JVM) to be installed on your
computer. Java is used in many web environments to enable online interaction. If you
can't browse your computer to send files (documents, spreadsheets, etc.) or enable html in
emails to change fonts, then you probably need to install and enable Java on your
computer.
2.1.1 SYSTEM INTERFACES
It requires the operating system WINDOWS 98/2000/XP/Vista.
2.1.2 USER INTERFACES
To access your courses on the internet, you need to have an Internet service provider
(ISP), providing either dial-up (phone modem) or broadband (DSL, Cable, T1/LAN)
Internet connection services. To access your online courses, you will need a browser
compatible with the eCampus and it must be configured properly.
2.1.3 HARDWARE INTERFACES REQUIRED FOR THE SYSTEM
Pentium III (or equivalent) running at 400 MHz or higher
Windows 98/NT/2000/XP
128 MB RAM
10 GB Hard drive
56 kbps modem or faster
CD-ROM and/or CD-RW drive
Sound card with speakers and a color display
2.1.4 SOFTWARE INTERFACES
JVM(Java Virtual Machine) to be installed.Plug-ins are software programs that
add functionality to your web browser (e.g., run movies or view animations) or
allow you to view special content (e.g., view PowerPoint or Word files). The
courses may require any or all of the software listed below.
Adobe Reader: It allows you to view, search, and print documents saved as PDFs
(Portable Document Format). [.pdf]
Macromedia flash: The Flash Player allows you to view content, like graphics
and animations, created with Macromedia Flash software. [.swf]

RealPlayer: It allows you to view streaming content, such as audio, video,

animations, and media presentations, created with RealMedia software.
Apple QuickTime: It allows you to view content, such as audio, video,
animations, and panoramas, created with Apple QuickTime software.
Windows Media Player: It allows you to view content, such as audio and video
created using Windows Media software. [.wmp .wma .asf .asx .avi .aif .mpg
.mp3 .wav]

Microsoft PowerPoint Viewer: If the full Microsoft PowerPoint or Office

application is not installed on your computer, you can view and print PowerPoint
slides and presentations with this viewer. [.ppt .pps]
Microsoft Word Viewer: If the full Microsoft Word or Office application is not
installed on your computer, you can view, print, and copy/paste text from Word
documents with this viewer. [.doc]
Microsoft Excel Viewer: If the full Microsoft Excel or Office application is not
installed on your computer, you can view and print Excel spreadsheets with this
viewer. [.xls]

2.1.5 COMMUNICATION INTERFACES

As it is an online course the communication is done only through the internet which also
involves a supported web browser since it is the only way to register into the online
courses.
2.1.6 MEMORY CONSTRAINTS
The minimum memory requirements are 128 MB RAM and 10 GB Hard drive
2.1.7 OPERATIONS
The user can perform several operations on the system. An unregistered user of
the E-Campus can view information on various courses offered in the home page
and also register for any course of his choice by using the Register button,
which will be available on the homepage.

A registered user can login to the system using the login button. This would be an
interactive operation. Other interactive operations of a registered user include
chatting using the chat application embedded into the system and emailing using
the email system.

The login information provided by the user is processed and validated before
logging him in. Also any notes or posts saved by the user will be stored in the
database.

The backup and recovery operations of the database are performed at midnight
every weekend. At this time, users will not be able to use the system. However,
all their information will be safe.
2.1.8 SITE ADAPTATION
New data tables with ample space to store the users information must be installed
and stored on the companies existing database server prior to system activation.

The user of the E-Campus system should have a compatible internet browser such
as Internet Explorer 6 or later or Google Chrome.

2.2 PRODUCT FUNCTIONS

The E-Campus system is designed to provide a platform for the students and the lecturers
to interact with each other. The various functions that the system performs are listed
below.

Registration: Using the registration form available on the websites home page,
the users can register themselves for a particular course. As soon as they are
registered a confirmation email is sent to them. Once the user replies to the email,
his account is added to the database.
Login: The registered users can login to the system by providing a valid user
name and password. The system verifies the username and password for validity.
Chat: The system will contain an embedded chat system that will allow its various
users to interact with each other via text messages. However, these chats will not
be saved on the database.
Email: The system will contain an integrated email application using which the
users can send and receive mails to and from fellow users. These email message
will be saved so that the user can view them at any point in the future. However,
if the user deletes any message, it will be deleted from the server.
Viewing and posting notes: The system allows users to view posts which are
posted by lecturers.

To use any of the systems applications, the user will first have to be logged in to the
system. To log in, the user must be registered on the system.
2.3 USER CHARACTERISTICS
The intended users of the system are required to have basic knowledge of working in a
Windows environment and using the Internet and an Internet Browser. Apart from this,
no technical knowledge as such is required.
Since the potential users of the E-Campus system are students and lecturers, and the
website is to promote an educational atmosphere, the design of the User interface will be
simple, yet aesthetic providing quick access to all features of the system from the Home
Page. Buttons, List and Text Boxes are some of the GUI components that will be used in
the design of the website.
2.4 CONSTRAINTS
A LAN network connects the hardware.
The system should have an internet connection.
The system is developed using HTML and JavaScript.
For security reasons, the information of each user, which includes the users
online profile is not displayed publicly.
2.5 ASSUMPTIONS AND DEPENDENCIES
Windows 98/2000/NT/XP/ Vista is installed on the users system.
A compatible Internet browser is installed on the users system.

The database is updated whenever a new registration is completed.

The time taken for this updation is very little, such that a user who has just
registered can immediately log in to the system.

3.0 SPECIFIC REQUIREMENTS

3.1 EXTERNAL INTERFACE
3.1.1 USER INTERFACES
The system shall be designed using good software engineering practices.
The Home page shall contain information about the E-Campus system in the left
side of the window.
The right side of the page shall provide buttons to login and register.
The registration page shall collect information about the user. This information
will include name, email address, password, confirm password, course, and an
option to register as a student or lecturer.
The login page shall contain text boxes to accept the username and password.
The user page shall contain buttons that will allow the user access to the various
applications. These are chat, email and notes.
Every page shall have a logout link at the top.
3.1.2 HARDWARE INTERFACES
The system shall be designed to run on the following hardware specification.
Pentium III (or equivalent or later) running at 400 MHz or higher.
128 MB RAM.
10 GB Hard drive.
56 kbps modem or faster.
Sound card with speakers and a color display
3.1.3 SOFTWARE INTERFACES
The system shall be designed to run on Windows 98/2000/NT/XP/Vista.
The system shall be compatible with Internet Explorer 6 or later and may be
designed to be compatible with Mozilla Firefox, Google Chrome.
The system shall support Java plug-ins and may support Real Player, Apple
Quicktime, Windows Media Player, Adobe Acrobat Reader, Macromedia Flash
Player, Microsoft Word Viewer, Microsoft Excel Viewer and Microsoft
Powerpoint Viewer.
3.1.4 COMMUNICATION INTERFACE
The system shall be made available on the world wide web, hence the required protocols
shall be used.
For the chat application UDP protocol may be used.
For email the FTP and SMTP may be used.

For connecting the website the HTTP may be used.

3.2 FUNCTIONAL REQUIREMENTS

3.2.1 REGISTRATION PROCESS
3.2.1.1 Introduction
An unregistered user can not avail of the features of the E-Campus System. In order to do
so he should register with the system. For this he shall use the registration link that shall
be provided on the Home Page.
3.2.1.2 Input
The user shall click on Register button to go to the registration page. Here the user
shall enter his details, which include his name, password, confirm password, course, type
of account. After filling up the required information the user will click on Submit
button.
3.2.1.3 Processing
Once the user clicks on Submit, the system shall send an email to the users email
address for validation.
3.2.1.4 Output
After the user confirms the registration by replying to the email, his account is created
and added to the database.
3.2.2 LOGIN
3.2.2.1 Introduction
A registered user can login to the system to use the various features of the system.
3.2.2.2 Input
The user shall click on Login button, which shall be present on the Home Page. This
will take him to the login page. Here the user shall enter his username and password.
3.2.2.3 Processing
Authentication of the username and password.
3.2.2.4 Output
If the users account is found on the database and if his password is correct, the
user is taken to his account.

If the users account is not available in the database he shall be taken to

registration page to register.
If the password is found to be incorrect, a message shall be displayed to the user
asking him to enter the correct password.

3.2.3 CHAT
3.2.3.1 Introduction
The user can use the chat application to chat with other users of the system. He shall do
this by clicking on the chat button that shall be available on his account page.
3.2.3.2 Input
The user shall enter his password and if it is found valid he shall select the room of his
choice.
3.2.3.3 Processing
Authentication of the users password is done.
3.2.3.4 Output
When the users password is valid hes displayed a list of rooms. If the password
is invalid, he is asked to enter a valid password.
When the user selects a particular room, he is taken to that room and shown a list
of other users who are online and using the same room.
3.2.4 EMAIL
3.2.4.1 Introduction
The user can use the email application once he is logged in. He shall use the Email
button provided on his account page.
3.2.4.2 Input
The user shall enter his password to access his email account. Then he will choose
whether he wants to view, compose or delete any message. To compose a message he
will enter the message content in the text editor and also provide a destination address.
3.2.4.3 Processing
Authentication of users password.
Validation of destination address.
3.2.4.4 Output
If the password is valid, the inbox shall be displayed.
If the password is invalid a message Incorrect Password shall be displayed.

If the user clicks Delete Message, the email shall be deleted permanently.
If the user clicks Compose Mail or Reply he shall be displayed a text editor
with appropriate field for Destination Address.
If the destination address is valid, the email shall be sent. If invalid, a message
Invalid Address shall be displayed.

3.2.5 VIEW NOTES

3.2.5.1 Introduction
The user can view notes by clicking on View Notes button from his account page.
3.2.5.2 Input
The user enters his password. Then he selects the notes of his choice.
3.2.5.3 Processing
Authentication of the users password.
3.2.5.4 Output
If the password is valid, the user is displayed a list of notes, from which he shall
select one. The selected notes are displayed to the user.
If the password is invalid, a message Incorrect Password shall be displayed.

3.2.6 POST NOTES

3.2.6.1 Introduction
A lecturer user can post notes for the students using Post Notes button on his account
page.
3.2.6.2 Input
The user enters his password. He enters his notes in a text editor and shall click on
Submit at the bottom of the page when he is finished.
3.2.6.3 Processing
Authentication of users password and verification whether the user is a lecturer.
3.2.6.4 OUTPUT
If the password is valid and the user is a lecturer he is displayed a text editor.
If the password is valid and the user is a student, he is displayed a message Only
Lecturers Allowed to Post Notes.
If the password is invalid, he shall be displayed a message Incorrect Password.

3.3 PERFORMANCE REQUIREMENTS

The system shall be designed keeping in mind that thousands of users can
supported simultaneously. A minimum of 10000 users shall be supported by the
system.
The system shall be capable of handling at least 10GB of data simultaneously,
which may be in the form of texts, videos and audios.
All transactions, including transitions between pages should be completed in a
minimum of one second and a maximum of 6 seconds. However, audio and video
transactions may take 10 to 20 seconds to buffer.
3.4 LOGICAL DATABASE REQUIREMENTS
The database for storing the user accounts shall be a relational database. The
database stores information of customers like, name, account number, designation
etc. Modification to the database is done whenever necessary by the authorized
user. The server which receives the ID from the user verifies for authentication
with the database.
The database that stores notes shall be capable of storing large amounts of text,
audio and video. Modifications to this database is done whenever the need arises.
3.5 DESIGN CONSTRAINTS
The web pages are designed using HTML and JavaScript.
The technical specification document is based on a modified, Finnish version of
ANSI/IEEE 1016-1987
When designing the HTML document type, consideration was given to a certain
simplicity in order to allow many browsers and hopefully editors to be developed
on many platforms.
Lack of nesting: Many text editing systems (Microsoft Word, The NeXT text
object, the Mac text object, etc) handle text in a variety of styles but do not have
any concept of nestable structure in the SGML sense.The constraint here is
therefore that HTML be able to be mapped into a sequence of paragraphs of
styled text, and that if that text is edited that the editor should be able to map the
sequence of styles back onto a sequence of elements in a well-defined way. This
allows some limited trivial nesting (eg LI within UL) but no general nesting, as a
finite and small set of styles is used. In particular, the styles are not parameterized
by the nesting level.
Logical Markup: It is required that HTML be a common language between all
platforms. This implies no device-specific markup, or anything which requires
control over fonts or colors, for example. This is in keeping with the SGML ideal.
Lack of specific semantics: Just as the markup must not be device-specific.
3.6 OTHER REQUIREMENTS
The database of the system shall be regularly backed up.
Users shall be notified of new updates by messages on the Home Page.