06.AnalysisModeling.key

Size: px

Start display at page:

Download "06.AnalysisModeling.key"

서겸 동
5 years ago
Views:

1 CSE4006 Software Engineering Analysis Modeling Scott Uk-Jin Lee Division of Computer Science, College of Computing Hanyang University ERICA Campus 1 st Semester 2018

2 Overview of Analysis Modeling

3 Requirement Analysis (Operational) (constraints)

4 Requirement Analysis - (user scenarios) - (functional activities)

5 A Bridge 5

6 Elements of Analysis Model 6

7 Rules of Thumb (information domain) - (function and behavior of system) coupling

8 Domain Analysis ( ),, the identification, analysis, and specification of common, reusable capabilities within a specific application domain, in terms of common objects, classes, subassemblies, and frameworks...,,,,, - Donald Firesmith 8

9 Domain Analysis 9

10 Data Modeling (processing) - UML external entities : printer, user, sensor things : reports, displays, signals occurrences or events : interrupt, alarm roles : manger, engineer, salesperson organizational units : division, team places : manufacturing floor structure : employee record 10

11 Data Modeling,, (composite information) (encapsulate) Entity Relationship Diagram (ERD) 11

12 Object-Oriented Concepts (element) : (operation) (instantiation) (inheritance) 12

13 Classes :,, ( ) superclass, 13

14 Methods (Operations, Services) (executable procedure) (data attributes) 14

15 Encapsulation / Hiding (logical procedure) (information hiding) 15

16 Class Hierarchy 16

17 How to Define All Classes 1. (communicate) ~ 6 17

18 Elements of Analysis Model 18

19 Scenario-based Modeling Use-cases are amply an aid to defining what exists outside the system (actors) and what should be performed by the system (use-cases) Use-cases (actors) (use-cases) - Ivar Jacobson 1.? 2.? 3.? 4.? 19

20 Use-Cases (thread of usage) actor (users) use-case actor? actor,,? actor? 20

21 Use-Cases 21

22 Activity Diagram (procedural flow) use-case Business Process modeling Notation (BPMN) [order reject] Receive Order Fill Order [order accepted] Ship Order Close Order Send Invoice Invoice Make Payment Accept Payment 22

23 Swimlane Diagram use-case 23

24 Activity & Swimlane Diagram 24

25 Elements of Analysis Model 25

26 Class-based Modeling : (objects) (operations: methods or services) ( ) : (classes), (objects), (attributes), (operations) CRC collaboration diagrams & packages 26

27 Identifying Analysis Classes (grammatical parse) (analysis class) (attributes) (operations) 27

28 Analysis Classes external entities : other systems, devices. people things : reports, displays, letters, signals occurrences or events : / property transfer, completion of series of robot movement roles : manager, engineer, salesperson organizational units : division, group, team places : (context) manufacturing floor, loading dock structures : sensors, four-wheeled vehicles, computers 28

29 Selecting Classes - Criteria (potential classes) (analysis classes) : 1. retained information 2. needed service 3. multiple attributes 4. common attributes 5. common operations 6. essential requirements potential class ( ) 29

30 Example : Potential SafeHome Classes 30

31 Class Diagram 31

32 CRC Models Class-Responsibility-Collaborator (CRC) (analysis classes) (responsibility) (analysis classes) (collaborators), 32

33 CRC Models CRC 33

34 Class Types in CRC Modeling entity classes (model / business classes) (problem statement) ) FloorPlan, Sensor boundary classes ) interactive screen, printed reports, CameraWindow controller classes - : entity / boundary - entity (communication) 34

35 Responsibilities in CRC Modeling (intelligence) smart vs. dumb (generally) ( ) (information) (behavior) (encapsulation) (localized), 35

36 Collaborators in CRC Modeling 2 : (relationships) 3 : is-part-of has-knowledge-of depends-upon 36

37 Composite Aggregate Class is-part-of = UML aggregation 37

38 Association & Dependencies UML : (association) (analysis classes) - (multiplicity) (cardinality) (dependency) (analysis classes) client-server client server ( ) 38

39 Multiplicity 39

40 Dependencies (dependency) (stereotype) (stereotype) UML (<< >>) 40

41 Analysis Packages (use-case, analysis class) + (plus) : (analysis class) - (minus) : # (sharp) : 41

42 Reviewing the CRC Model (CRC ) CRC (subset) ( ) use-case scenario ( use-case diagram) use-case, ( ) use-case use-case ( CRC ) 42

43 Elements of Analysis Model 43

44 Flow-oriented Modeling : Data Flow Diagram (DFD) / ( ) 44

45 The Flow Model = 자료원 프로세스 자료도착지 45

46 The Flow Model Notation (process) (external entity) : ( ) ),,, (external entity) : (origin) (sink) ),,, 46

47 The Flow Model Notation (Data Flow) (Data Store) : : 47

48 Data Flow Diagram Example : Bread Factory DFD 48

49 Data Flow Diagram Example : Bread Factory ( : 2) 49

50 Data Flow Diagramming : Guidelines (labeling) DFD context level (level 0) (top-down) (external entity) level 0 (labeling) DFD final level (procedural logic) 50

51 Data Flow Diagramming : Guidelines ) 51

52 Constructing a DFD (operations) (grammatical parse) (external entity) : level 0 DFD 52

53 Constructing a DFD (narrative) (grammatical parse) ( ) & ( ) (balance) level 1 DFD ( 1:5 ) 53

Constructing a DFD Example : SafeHome SafeHome processing narrative The SafeHome security function enables the homeowner to configure the security system when it its installed, monitors all sensors

54 Constructing a DFD Example : SafeHome SafeHome processing narrative The SafeHome security function enables the homeowner to configure the security system when it its installed, monitors all sensors connected to the security system, and interacts with the homeowner through the Internet, a PC, or a control panel. During installation, the SafeHome PC is used to program and configure the system. Each sensor is assigned a number and type, a master password is programmed for arming and disarming the system, and telephone number are input for dialing when a sensor event occurs. 54

55 Constructing a DFD Example : SafeHome [level 1] SafeHome (refinement) 55

56 Constructing a DFD Example : SafeHome [level 2] Monitor sensors (refinement) 56

57 Flow Modeling Notes (process) (one thing) DFD (external entity) level 0 (flow model) 3 ~ 7 data dictionary 57

58 Flow Model Components Data Flow Diagram Data Dictionary Process Specification (Mini-Spec) 58

59 Data Dictionary (data item) = = composed of { } repetition ( ) optional + and [ / ] or address = house no. + (street / area) + city + state course ID = course no. + name + level + grades 59

60 Process Specification (PSPEC) level (flow model) 60

61 Elements of Analysis Model 61

62 Behavioral Modeling (behavioral model) (events) (stimuli) : use-cases (interaction sequence) use-case (state diagram) - 62

63 What are Events? Event = a type of observable occurrence (interaction) (instances) synchronous object operation invocation (call event) asynchronous signal reception (signal event) creation and destruction of instances occurrence of time instants (time event) interval expiry calendar/clock time change in value of some entity (change event) 63

64 Behavioral Modeling (states) (characterization) : (behavior) (behavior) (transition) : (action) state / sequence 64

65 State Diagram (active state) 65

66 State Diagram Example SafeHome control panel class 66

67 Sequence Diagram 67

68 Sequence Diagram Example SafeHome 68

소프트웨어개발방법론

소프트웨어개발방법론 사용사례 (Use Case) Objectives 2 소개? (story) vs. 3 UC 와 UP 산출물과의관계 Sample UP Artifact Relationships Domain Model Business Modeling date... Sale 1 1..* Sales... LineItem... quantity Use-Case Model objects,