You are on page 1of 2

SE Concepts S2 Syllabus

1. Use Case Diagram & Elaborations


Lec#7&8
Tips:
- First you should know the notations
- Identify all actors (users of system)
- Identify all use cases (functions or services provided by user).
- The common use case which is part of one or more use cases must be represented by include
relationship.
- The use cases which are optional i.e. depend on a certain condition are represented by extend
relationship.

Example: [https://www.lucidchart.com/pages/uml-use-case-diagram,
https://www.lucidchart.com/pages/UML-use-case-scenario-examples ]

2. Activity Diagram
Lec#9
Tips:
- First you should know the notations
- Only concurrent (parallel) activities are split by fork and later joined.
- Draw swim lane to show the actors involved in particular actions. Do show start and end of
an activity.
- Identify all actions involved to perform in a activity. Order or sequence of activities is very
important.
Example: [https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-
is-activity-diagram/]
3. Context Diagram & Level 0 DFD
Lec#6 & Lec#10
Tips:
- First you should know the notations and rules.
- To draw context diagram, you need to identify the external entities. Never display the part of
system as an external entity.

Example:

https://www.modernanalyst.com/Careers/InterviewQuestions/tabid/128/ID/1433/What-is-a-
Context-Diagram-and-what-are-the-benefits-of-creating-one.aspx

https://www.lucidchart.com/blog/data-flow-diagram-tutorial

You might also like