Satish Pradhan Dyansadhana College,Thane

Roll No. :- 53

Department of Information Technology

Certificate

This is to certify that Mr./Miss. : Avadhesh Dindayal Yadav of S. Y.

B. [Link] Technology (Sem-4) class has successfully
completed all the practical work in subject Software Engineering ,
under the guidance of Asst. Prof. Richa (subject in charge) during
Year 2022-23 in partial fulfilment of Information Technology Practical
Examination conducted by University of Mumbai.

Subject in charge Head of the Department

Date
Name – Avdhesh Dindayal Yadav Class – [Link]
Roll No. – 53 Subject – Software

INDEX

Sr. List of Practical Date Sign

No.
1. Study and implementation of class diagrams.
11/01/23

2. Study and implementation of use case diagram.

11/01/23

3. Study and implementation of Entity

Relationship Diagrams. 18/01/23

4. Study and implementation of Sequence

Diagrams. 18/01/23

5 Study and implementation of State Transition

Diagrams. 25/01/23

6. Study and implementation of Data Flow

Diagrams. 01/02/23

7. Study and implementation of Collaboration

Diagrams. 14/02/23

8. Study and implementation of Activity Diagrams.

01/02/23

9. Study and implementation of Component

Diagrams. 08/02/23

10. Study and implementation of Deployment

Diagrams. 14/02/23
Name – Avdhesh Dindayal Yadav. Class – [Link]
Roll No. – 53 Subject – Software

[Link].1 Study and implementation of class diagrams.

➢ A class diagram models are the static structure of the system.

➢ It shows relationships between classes,object,attribute and operation.
➢ Class diagram is a visual representation of class objects in a model system,
categorised by class type each class type is represented as a rectangle with
three compartments for the Class name,Attribute,Operation.

● Syntax:-

Class Name
Attribute
Operation / Return type
● Example:-

Student
Name: String
[Link]: int
Class record()

● Class Diagram Notation :-

1. Classes:-
Classes are represented by rectangle with three compartment
Name,Attribute,Operation.
A rectangle with a double border represents an abstract class.

2. Objects :-
Object are represented as oval that contain class name.

3. Attributes :-
Attributes are listed inside the attribute compartment of a class rectangle.
Name – Avdhesh Dindayal Yadav Class – [Link]
Roll No. – 53 Subject – Software

● Class Diagram Symbols :-

Association

Inheritance

Implementation

Aggregation

Composition

Depending
Name –Avdhesh Dindayal Yadav Class – [Link]
Roll No. – 53 Subject – Software
➔ Class Diagram For ATM System :-
Name –Avdhesh Dindayal Yadav Class – [Link]
Roll No. – 53 Subject – Software
[Link].2 Study and implementation of Use Case Diagrams.

● Use Case Diagram :-

➢ Use case diagram shows a high level overview of the relationship between
use case actor and system.
➢ UML is a modelling tool kit that you can use to build your diagram.
➢ Use cases are represented with a label oval shape.
➢ Stick figure represent actors in the process and actor participation in the
system is model with a line between the actor and the use case.
➢ UML use case diagram are ideal for -
1. Representing the goals of the system - user interact.
2. Defining and organising functional requirement of the system.
3. Specifying the context and requirement of the system.

● Use case diagram component are as follows

1. Actor :-
The users that interact with the system , an actor can be a person, an
organisation or an outside system that interacts with your application or
system.

2. System :-
A specific sequence of action and interaction between actor and the
system

3. Goals :-
The end results of the must use cases.
A successful diagram should describe the activities and variants use to
reach the goal.
Name – Avdhesh Dindayal Yadav Class – [Link]
Roll No. – 53 Subject – Software

➔ Use Case Diagram For ATM System:-

Name –Avdhesh Dindayal Class – [Link]
Yadav Subject – Software
[Link].3 Study and implementation of Entity Relationship
Diagrams.

ER Diagram is used to model the logical view of the system considering the data

● Components of ER Diagram:-

Represent Entity

Represent Attribute

Relationship Among the Entity

Shows Link

● Entity , Entity Type , Entity Set :-

1. An entity mainly an object with a physical existance - A particular person

,car,house or employee or it may be an object with a coceptual existence
like company,job or a university course etc.
2. An entity is an object of entity type and set of all entities is called as entity
type.

3. Example- Entity Set

Entity(E)
Name –Avdhesh Dindayal Class – [Link]
Yadav Subject – Software
● Attributes Of ER Diagram :-

1. Attributes are properties that define the entity type.

Example- rollno,name,DOB,age are attributes of entity type students.
2. Key Attribute -
The attribute which uniquely identify each entity in entity set is called ket
attribute.
Example - rollno
It is represented by an oval with under-line lines.
3. Composite Attribute -
An attribute compose of many other attribute is called as composite
attribute.
Example -

4. Multivalue Attribute –
An Attribute consists of more than one value for an given value.
It is represented by Double Oval.
Example phone-no -

5. Derived Attribute -
An attribute that can be derived from other attribute

It is represented by the Dashed Oval.

Example -
Name –Avdhesh Dindayal Class – [Link]
Yadav Subject – Software
● Relationship type and Relationship Sets :-
1. Relationship Type-
A relationship type represents the association between entity type.
It is represented by Diamond.
Example -
“Enrolled in” is a relationship type that exist between entity type student
and course.

2. Relationship Sets-
A set of relationships of some type is known as relationship set.

● Weak Entity :-
1. There exists some entity type in any entity set for which key attribute can
be define this is called weak entity.
2. It is represented by a double rectangle and its relationship is also denoted
by a double diamond.
3. Example -
Name –Avdhesh Dindayal Class – [Link]
Yadav Subject – Software
➔ ER Diagram For Hospital Database Management System :-
Name –Avdhesh Dindayal Class – [Link]
Yadav Subject – Software
[Link].4 Study and implementation of Sequence Diagrams.

1. Sequence diagrams are a popular dynamic modelling solution.

2. Dynamic modelling focuses on the interaction occurring within the system.
3. Sequence diagrams specifically focus on the “lifelines” of an object and how they
communicate with other objects to perform a function before the lifeline ends.

➔ Sequence Diagram For Online Shopping.

Name –Avdhesh Dindayal Class – [Link]
Yadav Subject – Software
[Link]. 5 Study and implementation of State Transition
Diagrams.
1. State transition diagrams describe all of the states that an object can have,the
events under which an object changes state,the conditions that must be fulfilled
before the transition will occur ,and the activities undertaken during the life of an
object.
2. State-transition diagrams are very useful for describing the behaviour of
individual object over the full set of use cases that affect those objects.
3. State-transition diagrams are not useful for describing the collaboration objects
that cause the transitions.

● State-Transition Diagram Notation:

1. State :-
A condition during the life of an object in which it satisfies some condition,
perform some action or wait for some event.
2. Event :-
An occurrence that may trigger a state transition. Event types include an
Explicit signal from outside the system,an invocation from inside the system, The
passage of a designated period of time,or a designated condition becoming true.
3. Guard :-
A boolean expression which,if true,enables an event to cause a transition.
4. Transition :-
The change of state within an object.
5. Action :-
One or more actions taken by an object in response to a state change.

● State-Transition Diagram Component :

Start Symbol

End Symbol

Activity
Name – Avdhesh Dindayal Yadav Class – [Link]
Roll No. – 53 Subject – Software

➔ State Transition Diagram for ATM machine.

Name – Avdhesh Dindayal Yadav Class – [Link]
Roll No. – 53 Subject – Software
[Link]. 6 Study and implementation of Data Flow Diagrams.
1. Data flow diagram is a traditional visual representation of information flow within a
system.
2. It is also called as Data Flow Graph Or Bubble Chart.

● About Data Flow Diagram

1. All names should be unique.

2. Arrows in data flow diagram represent flowing date A data flow diagram does not
involve any order of event.
3. Suppress logical decisions.
4. Do not become bogged down with details differ error condition an error handling
until the end of the analysis.

 Standard symbol for data flow diagram are derived from the
electric circuit diagram analysis and are as follow :

Data Flow

Process

Source Of Sink

Data Store
Name – Avdhesh Dindayal Yadav Class – [Link]
Roll No. – 53 Subject – Software

➔ Data Flow Diagram For ATM System

Name – Avdhesh Dindayal Yadav. Class – [Link]
Roll No. – 53 Subject – Software

[Link]. 7 Study and implementation of Collabration Diagrams.

1. Collaboration diagrams are used to show how objects interact to perform the
behaviour of a particular use case, or a part of a use case.
2. Along with sequence diagrams, collaborations are used by designers to define
and clarify the roles of the objects that perform a particular flow of events of a use
case.
3. They are the primary source of information used to determining class
responsibilities and interfaces.
4. Unlike a sequence diagram, a collaboration diagram shows the relationships
among the objects.

➔ Collaboration Diagram For ATM System.

Name – Avdhesh Dindayal Yadav. Class – [Link]
Roll No. – 53 Subject – Software

[Link].8 Study and implementation of Activity Diagrams.

1. An activity diagram is a behaviour diagram i.e. it depicts the behaviour of a

system.
2. It is very similar to flowchart.

● Activity Diagram Notation :-

1. Initial State.

2. Activity.

3. Action Flow/Control Flow.

4. Final State.
Name – Avdhesh Dindayal Yadav. Class – [Link]
Roll No. – 53 Subject – Software
➔ Activity Diagram For an order management system.
Name – Avdhesh Dindayal Yadav. Class – [Link]
Roll No. – 53 Subject – Software
[Link].9 Study and implementation of Component Diagrams.

1. Component diagrams are different in terms of nature and behaviour.

2. Component diagrams are used to model the physical aspect of a system.
3. Component diagrams are used to visualize the organization and relationships
among components in a system.
4. These diagrams are also used to make executable systems.

➔ Component Diagram For ATM System.

Name – Avdhesh Dindayal Yadav. Class – [Link]
Roll No. – 53 Subject – Software

[Link].10 Study and implementation of Deployment Diagrams.

1. Deployment diagrams also help to model the physical aspect of an Object-

Oriented software system.
2. It models the run-time configuration in a static view and visualizes the distribution
of components in an application.
3. A deployment diagram can cover a wide variety within a single model.

➔ Deployment diagram For ATM System.