UNIVERSITY WEBSITE

PROBLEM STATEMENT
• A University website should keep information
about its students and academic staff.
• Records for all university members are to
include their id number, surname, given name,
email.
• Students and academic staff each have their
own unique ID number.
 …CONTINUED
• In addition to the attributes mentioned above , the
following assumptions must be followed:
• 1.Students will also have a list of subjects they are
enrolled in.
• 2.Academic employees will have a list of subjects
they teach.
• 3.University is responsible for the admission process
of all the students.
• 4.University website does not contain information
pertaining students other than the information
filled by the students in the admission form itself.
 FRONT PAGE
• The following is the home/front page of the
University website.
• Its features are:
A. Multi-utility drop-down lists.
B. A quick access to all pages from each page in a
given category
C. Images , audio and video files can be embedded
and accessed easily.
UML DIAGRAMS
 UML DIAGRAMS
Object Modeling Technique
+ Object Oriented Software Engineering
=
UML
 …CONTINUED
MAIN OBJECTIVE OF UML :
 TO STANDARDIZE ALL OBJECT-
ORIENTED METHODS WITH GENERAL
SPEAKING NOTATIONS.
 TO REPRESENT USER REQUIREMENTS
PICTORIALLY.
 TYPES OF UML DIAGRAMS
I. USE CASE DIAGRAMS
II. CLASS DIAGRAMS
III. OBJECT DIAGRAMS
IV. STATECHART DIAGRAMS
V. ACTIVITY DIAGRAMS
VI. SEQUENCE DIAGRAMS
VII.COLLABORATION DIAGRAMS
VIII.COMPONENT DIAGRAMS
IX. DEPLOYMENT DIAGRAM
 USE CASE DIAGRAMS
 Purpose :
To present a graphical overview of the
functionality provided by a system in terms of 
actors, their goals (represented as use cases), and
any dependencies between those use cases.
 …CONTINUED
Components :
 Use cases
 Actors
 System boundary boxes (optional)

EXAMPLE
 Use Case Diagram

Input
Marks
Pay Fees

Grade Admin

Print
Student
Schedule
Finance Dept

Teach
Subjects Instructor
Enroll in a Change
Branch Branch

Distribute
fee structure

<<extended>>

Post Office
Academic
Distribute
Brochure Distribute
<<extended>> Information

Add Subject Delete

Subject
<<extended>>

Distribute
Schedules Registrar
 Scenarios
• Each scenario has a sequence of steps.

– Scenario 1 : Student is enrolled for the subject.

• Student chooses the “enroll subject” action.
• Check the student has enrolled in less than 10
subjects.
• Check if the subject is valid.
• Assign the subject to the student.
 Scenarios
• Each scenario has a sequence of steps.

– Scenario 2 : Enrolling fails since the student is

already enrolled in 5 subjects.
• Student chooses the “enroll subject” action.
• Check the student has enrolled in less than 10
subjects.
• Return an error message to the student
 CLASS DIAGRAMS
Purpose :
 Translating the models into 
programming code.
 …CONTINUED
Components:
Boxes which contain three parts --
The upper part holds the name of the class
The middle part contains the attributes of the
class
The bottom part gives the methods or
operations the class can take or undertake
EXAMPLE
University Database: Class Diagram

UDB
uname : String
courses : int
capacity : int

1 1

* *
Member Subject

name : String name : string

age : int stud_enroll: int

0...5 0...3

Teachers Students takes

salary: int id: int 1
course: string course: string

teaches
 OBJECT DIAGRAMS
Purpose :
It focuses on some particular set of 
object instances and attributes, and the links
between the instances
 …CONTINUED
Components :
Same as class diagrams , however the
attributes are assigned values or arguments.

EXAMPLE
 University Database: Object Diagram

MAIN : UDB
uname: "WWE Univ"
courses: 25
capacity: 700

Member 1: Pratik Subject 1 : Neerav Subject 2: Mark

Member 2: Rohin
name: "ABC" name: "OOSE" name: "SPCC"
age: 48 name: "PQR" stud_enroll: 40 stud_enroll: 35
age: 25

teach1: teacher stud1: student

salary: 40000 id: 1305
course: course:
"Commerce" "Science"
 STATECHART DIAGRAMS
Purpose :
• To model life time of an active
system.
• To describe different states of an
object during its life time.
 …CONTINUED
 The initial starting point, which is drawn using a
solid circle;
 A transition between states, which is drawn using a
line with an open arrowhead;
 A state, which is drawn using a rectangle with
rounded corners;
 A decision point, which is an open circle;
 One or more termination points, which are drawn
using a circle with a solid circle inside it.
 State Diagram

OPEN
Admission
open

VIEW
Details can
be obtained

PURCHASE
Pay fee for
the forms

SUBMISSION
FILL UP
Submit the
Form filling
form

WAIT
Wait for
results
 ACTIVITY DIAGRAMS
Purpose :
 An activity diagram shows the
overall flow of control.
 …CONTINUED
Components :
• rounded rectangles represent activities;
• diamonds represent decisions;
• bars represent the start (split) or end (join) of
concurrent activities;
• a black circle represents the start (initial state) of
the workflow;
• an encircled black circle represents the end (final
state).
 Activity Diagram for Admission

Fills the Form

Demands Field

Is Approved Not Approved

Confirm Admission

Take Schedule
 DIFFERENCE BETWEEN STATE AND
ACTIVITY DIAGRAMS
STATECHART DIAGRAM ACTIVITY DIAGRAM

State diagram shows the object Activity diagram is a fancy flow

undergoing a process. It gives a chart which shows the flow of
clear picture of the changes in activity of a process.
the object's state in this process.

Example : University System Example : University System

States: Waiting , Viewing , ETC. Activities : Filling the form , Submitting the
form , ETC.
 SEQUENCE DIAGRAM
Purpose :
It shows the messages exchanged
between processes AND the order in which
they occur.
 …CONTINUED
Components :
• Parallel vertical lines (lifelines)
• The arrows represent messages (stimuli)
from an actor or object to other objects.

EXAMPLE
 Sequence Diagram

: Main Screen : Enroll : Security Login : Student

<<UI>> <Controller>> <<UI>> <<UI>>

Wish to enroll <<create>>

1. Student wishes to enroll <<create>>

student name
2. Student inputs name & Number
student num

isEligible (name,student num)

3. System verifies student student

student

: Seminar
<<destroy>> <<UI>>

4. System displays course list <<create>>

selection
5. Student picks a course
QUESTIONS ???
COMMENTS !!!
 COMPONENT DIAGRAM
Purpose :
A component diagram depicts how 
components are wired together to form larger
components and or software systems.
 …CONTINUED
Components :
 Assembly connector 
 Delegation connector 
 Component Diagram

Facilities
Facilities Security
Lect mgmt <<infrastructure>>
<<application>>

Data Access
STUDENT
Student

Persistence
Data Access <<infrastructure>>

Student Admin Subject

<<application>>
Subject

UDB
<<infrastructure>>
Data Access
Schedule
Schedule
 COLLABORATION DIAGRAM
Purpose :
• To describe the message flow in the
system.
• To describe structural organization
of the objects.
 …CONTINUED
Components :
 Boxes to represent states and objects
 Arrows to represent the direction of flow of the
messages

EXAMPLE
 Collaboration Diagram

Administration

Central
Registry

Library
 DEPLOYMENT DIAGRAM
Purpose :
Models the physical deployment of 
artifacts on nodes.
 …CONTINUED
Components :

• The nodes appear as boxes

• The artifacts allocated to each node
appear as rectangles within the boxes.

EXAMPLE
 Deployment Diagram

<<device>>
:ApplicationServer University DB
{OS=Windows xp}
<<device>>
:EJB Container
:Web Server

<<RMI>> :student.ear <<JDBC>>

:course.ear
:scheduke.ear
:stuadmin.war :register.kml

<<deploymentspec>>

courseMgmt.jar

<<message bus>>

<<device>>
:Mainframe

courseMgmt<<legacy>>
 PRESENTED BY
ROHIN SEQUEIRA

MARK FERNANDES

NEERAV RISBOOD

PRATIK NAGAR.