본문 바로가기

Software Engineering

Software Engineering(Software Process and Other Models)

Use case Diagram

-> A use case diagram in part of UML(Unified Modeling Language) set of diatgrams. It shows the important actors and functionality of a system. Actors are represented by stick figures and functions by ovals(타원). Actors are associated with functions they can perform.

 

ex)

 

control flow graph

-> It shows the control structure of code. Each node (circle) represents a block of code that has only one way through the code. That is, there is one entrance at the beginning of the block and one exit at the end. If any statement in the block is executed, then all statements in the block are executed. Arcs between nodes represent possible flows of control. That is, if it is possible that block B is executed, right after block A, then there must be an arc from block A to block B.

 

ex)

 

 

 

The three major types of relationships are (1) inheritance, (2) aggregation(집합), and (3) association(일반 연관).

An inheritance relationship implies that the object at the bottom of the arc is a special case of the object at the top of the arc. For example, the top object might be a vehicle and the bottom object a car, which is a kind of vehicle. This is often called an ‘‘is-a’’ relationship(ex)Car-Lincoln town car/Person-Student).

An aggregation relationship implies that the object at the bottom of the arc is a component of the object at the top of the arc(ex)Library-Library patron/Class-Students).

The final type of relationship is an association, and this arc implies that somehow one of the objects is associated with the other object(ex)Book-Copy/Car-Driver/Patron-Book Loan).

 

'Software Engineering' 카테고리의 다른 글

Software Engineering(Software LifeCycle)  (0) 2024.10.27