ER Diagrams

• The relation upon the system is structure through a conceptual ER-Diagram,

which not only specifics the existential entities but also the standard relations through
which the system exists and the cardinalities that are necessary for the system state to
continue.
• The entity Relationship Diagram (ERD) depicts the relationship between the data
objects. The ERD is the notation that is used to conduct the date modeling activity the
attributes of each data object noted is the ERD can be described resign a data object
descriptions.
• The set of primary components that are identified by the ERD are
• Data object
• Relationships
• Attributes
• Various types of indicators.

The primary purpose of the ERD is to represent data objects and their relationships

53
54
 UML DIAGRAMS

The use case diagrams describe system functionality as a set of tasks that the system
must carry out and actors who interact with the system to complete the tasks.
Use Case:

Each use case on the diagram represents a single task that the system
needs to carry out. Buy a Product, Add Client, Make Purchase and
Validate Order Information are all examples of use cases. Some use
cases may include or extend a task represented by another use case.
For example, in order to make a purchase, the order information will
need to be validated.

Actor
An actor is anything outside the system that interacts with the system
to complete a task. It could be a user or another system. The actor
"uses" the use case to complete a task. System Administrator, Credit
Authentication System, Accounting System and Web Client are all
examples of actors. Often, it is useful to look at the set of use cases
that an actor has access to -- this defines the actor's overall role in the
system.
Association:
The association is the link that is drawn between and actor and a use case. It indicates
which actors interact with the system to complete the various tasks.

55
Includes:
Use the includes link to show that one use case includes the task described by another
use case. For example, saving a Visual Case project includes saving the diagrams and
saving the project settings. Sometimes the word "Uses" is used instead of "Includes"

Generalization:
The generalization link is an informal way of showing that one use case is similar to
another use case, but with a little bit of extra functionality. One use case inherits the
functionality represented by another use case and adds some additional behavior to it.
Extends:
The extends link is used to show that one use case extends the task described by another
use case. It's very similar to generalization, but is much more formalized.

The use case that is extended is always referred to as the base use case and has one or
more defined extension points. The extension points show exactly where extending use
cases are allowed to add functionality. The extending use case doesn't have to add
functionality at all of the base use case's extension points. The extension link indicates
which extension points are being used.

56
USECASE DIAGRAMS

Usecase diagram for UniversityAdmin

Login

Create Courses
University
Admin
Create Colleges

Reports

Logout

57
Use case name Create courses
Participating actors University administration
Flow of Events Administrator creates courses and update
courses
Entry condition Admin enter into the system with his own
id and pass words
Exit condition Success fully creates course
Quality Requirements Successful course creation

Use case name Create colleges

Participating actors University administration
Flow of Events Administrator creates colleges,update
colleges,delete colleges
Entry condition Admin enter into the system with his own
id and pass words
Exit condition Success fully creates college
Quality Requirements Successful college creation

Use case name Reports

Participating actors University administration
Flow of Events Administrat creates reports of colleges and
courses
Entry condition Admin enter into the system with his own
id and pass words
Exit condition Successview reports
Quality Requirements Generation of Reports

58
Usecase diagram for College Admin:

Login

Create Batches
College Admin

Create Departments

Select University Courses

Create Faculties

Create Students

Reports

Logout

59
Use case name Create batches
Participating actors College administrator
Flow of Events
College admin creates batches , delete or
update batches
Entry condition College admin enter into the system with
his own id and pass words
Exit condition Successful batch creation
Quality Requirements Batch confliction should not occur

Use case name Create departments

Participating actors College administrator
Flow of Events
College admin creates departments
Entry condition College admin enter into with college id
and password
Exit condition Successful department creation
Quality Requirements Department confliction should not occur

Use case name Select university courses

Participating actors College administrator
Flow of Events
College admin should select whatever
courses to be added
Entry condition College admin enter into the system with
his own id and pass words and course id
Exit condition Successful course addition
Quality Requirements Duplication addition should not occur

60
Use case name Create faculties
Participating actors College administrator
Flow of Events
College admin creates faculties
Entry condition College admin enters with his id and
password
Exit condition Successful faculty creation
Quality Requirements Faculty creation

Use case name Create students

Participating actors College administrator
Flow of Events
College admin creates students or delete
student
Entry condition College admin enters with his id and
password
Exit condition Successful student creation
Quality Requirements Student creation

61
Usecase diagram for HOD:

Login

Assign Subjects to Faculties

College HOD

Give Marks

Give Attendance

Reports

Logout

62
Use case name assign subjects to faculties
Participating actors College Hod
Flow of Events Hod assigns subject to faculties
Entry condition Hod enters with his collegename and his
username and password
Exit condition After successful assignment
Quality Requirements Assignment of subjects

Use case name Givemarks

Participating actors College Hod
Flow of Events Hod gives marks to students and modify
them
Entry condition Hod enters with his collegename and his
username and password
Exit condition After successful giving marks
Quality Requirements Proper entering of marks

Use case name Give attendance

Participating actors College Hod
Flow of Events Hod gives attendence to students and
modify them
Entry condition Hod enters with his collegename and his
username and password
Exit condition After successful giving attendance
Quality Requirements Proper entering of attendance

63
Usecase diagram for Faculty:

Login

View Assigned Subjects

College
Faculty
Give Marks

Logout

64
Use case name view assigned subjects
Participating actors College faculty
Flow of Events faculty view assigned subjects
Entry condition Faculty enters with his collegename and
his username and password
Exit condition After viewing assigned subjects
Quality Requirements Faculty will view assigned subjects etc

Use case name Givemarks

Participating actors College faculty
Flow of Events Faculty gives marks to students and
modify them to particular allocated subject
Entry condition Faculty enters with his collegename and
his username and password
Exit condition After successful giving marks
Quality Requirements Proper entering of marks

65
Usecase diagram for student:

Login

View Attendance
College
Student
View Marks

Logout

66