Chương 14: Integrating multiple system views

Chia sẻ: Võ Hoàng Nhật Khánh | Ngày: | Loại File: PPT | Số trang:13

Thêm vào BST

Báo xấu

47
lượt xem 2
download

Download Vui lòng tải xuống để xem tài liệu đầy đủ

The domain level: refers to concepts specific to the modeled system (library, loan, block, signal, …).

Chủ đề:

Bình luận(0) Đăng nhập để gửi bình luận!

Lưu

Nội dung Text: Chương 14: Integrating multiple system views

Building System Models for RE Chapter 14 Integrating multiple system views www.wileyeurope .com/college/van lamsweerde Chap.14: Integrating multiple system views © 2009 John Wiley and Sons
Integrating Multiple System Views: outline A metamodel for view integration  – Overall structure of the metamodel – The goal metamodel – The object metamodel – The agent metamodel – The operation metamodel – The behaviour metamodel Interview consistency rules  Grouping related view fragments into packages  www.wileyeurope .com/college/van lamsweerde Chap.14: Integrating multiple system views © 2009 John Wiley and Sons 2
A metamodel for view integration What is metamodel?  – Is a model that defines and interrelates conceptual abstractions in terms of which other models are defined. – Is a conceptual model for the meta level. – Consisting of metalevel concepts, relationships, attributes and constraints. Three different levels of modeling:  – The meta level: refers to domainindependent abstractions. – The domain level: refers to concepts specific to the modeled system (library, loan, block, signal, …). – The instance level: refers to specific instances of domainlevel concepts in the running system. www.wileyeurope .com/college/van lamsweerde Chap.14: Integrating multiple system views © 2009 John Wiley and Sons 3
A metamodel for view integration: example Input Performance Responsibility Link Goal Entity Agent Operation Association meta-concept meta-relationship Responsibility BookCopy Book CopyReturnedOnTime Patron Copy If Borrowed Performs Instance Input concept Borrow Responsibility L.Dupré, info/40/123 CopyReturnedBy Axel Copy Bugs in Writing 11/11/07 Performs Input concept instance Borrow Figure 14.1 – The meta, domain, and instance levels www.wileyeurope .com/college/van lamsweerde Chap.14: Integrating multiple system views © 2009 John Wiley and Sons 4
Overall structure of the metamodel A system model is made up of five views.  The root metaconcept SystemModel aggregates of five metaconcepts corresponding to  those views. Every metaconcept in metamodel is characterized by metaattributes and meta  relationships. Two metaattributes are mandatory for any metaconcept whaterver view it refers to:  Name and Ref SystemModel GoalModel ObjectModel BehaviorModel OperationModel AgentModel Figure 14.2 - Overall metamodel structure www.wileyeurope .com/college/van lamsweerde Chap.14: Integrating multiple system views © 2009 John Wiley and Sons 5
The goal metamodel GoalModel SoftGoal Resolution [FitCriterion] Goal BoundaryCondition ObstructedBy 1..* Achieve Name BehavioralGoal * [Category] Def [Likelihood] [FormalSpec] Divergence [Category] Maintain/Avoid [Criticality] [Priority] [FormalSpec] [Source] 1..* [Stability] Expectation LeafGoal 1 Obstacle OR-Ref Requirement * AND-Ref DomDescript * * Refinement OR-ref AND-ref * [Status] O-Refinement * [Tactic] [Status] [SysRef] Figure 14.3 – The goal metamodel www.wileyeurope .com/college/van lamsweerde Chap.14: Integrating multiple system views © 2009 John Wiley and Sons 6
The object metamodel ObjectModel DomDescript DomInvar Name Concern Def Goal Object DomHyp [FormalSpec] 1..* 1..* Name Def Link DomInit 2..* InstanceOf Role Multiplicity Attribute Range Position ValuesIn Association Agent Entity Event Rigidity Multiplicity Specialization ApplicationSpecific Built-In Aggregation Figure 14.4 – The object metamodel www.wileyeurope .com/college/van lamsweerde Chap.14: Integrating multiple system views © 2009 John Wiley and Sons 7
The agent metamodel AgentModel Dependency dependee dependum * Agent Goal Wish depender Name Monitoring Association Def OR-Ass Ass [Load] LeafGoal 1 1..* Assignment 1 1..* 0..1 Control Attribute [SysRef] stateVar Requirement Expectation EnvironmentAgent SoftwareToBeAgent 1..* 1..* 1 1 Responsibility Responsibility Figure 14.5 – The agent metamodel www.wileyeurope .com/college/van lamsweerde Chap.14: Integrating multiple system views © 2009 John Wiley and Sons 8
The operation metamodel OperationModel InternalEvent Instance Operation Input Association LeafGoal 1..* 1..* Name Def Output Attribute DomPre stateVar Operationalization DomPost [Category] [ReqPre] [ReqTrig] 1..* Performance 1 Agent [ReqPost] Figure 14.6 – The operation metamodel www.wileyeurope .com/college/van lamsweerde Chap.14: Integrating multiple system views © 2009 John Wiley and Sons 9
The behaviour metamodel BehaviorModel Instance Class 1..* 1..* Coverage Coverage 1 Coverage Goal Goal Agent Scenario AgentSM BehaviorOf Episode 0..* History Controlled 1..* Association Variable 1..* StateMachine 1 1 Attribute TimelineSlice 1..* Path 1..* Sequential Parallel State Composition Composition Interaction 11 Input Output 0..1 Guard 1..* 1..* 1..* 1 1 Label * Operation Transition Target InteractionEvent Source 0..1 Event Instance InternalEvent ExternalEvent Figure 14.7 – The behavior metamodel www.wileyeurope .com/college/van lamsweerde Chap.14: Integrating multiple system views © 2009 John Wiley and Sons 10
Interview consistency rules Two views of a system model are said to be structurally consistent if they satisfy a set  of rules constraining their respective elements for compatibility and complementarity. Many structural consistency rules have the following pattern:  – For every item it1 satisfying some property P1(it1) in view V1, there exists a corresponding item it2 in view V2 that satisfies sme property P2(it1, it2) linking it1 and it2. www.wileyeurope .com/college/van lamsweerde Chap.14: Integrating multiple system views © 2009 John Wiley and Sons 11
Some structural consistency rules Structural consistency of the goal and object models  – Every conceptual item referred to in a goal specification in the goal model must appear as an attribute or object in the object model. – Every goal in the goal model must concern at least one object in the object model. – For every object in the object model, there must be at least one goal in the goal model concerning with it. Structural consistency of the goal and behaviour models  – Every scenario in the behaviour model must be covered by at least one goal in the goal model. The other structural consistency rules: ref. textbook(494).  www.wileyeurope .com/college/van lamsweerde Chap.14: Integrating multiple system views © 2009 John Wiley and Sons 12
Grouping related view fragments into packages A package is a container in which model parts are defined and grouped together.  package LibraryModel OperationlModel GoalModel Software Functional Staff GoalModel Performance Development ObjectModel Operations Goals Tasks Goals Goals Goals Agent Legacy Operation Usability Interoperability Behavior Model Components Model Goals Goals Model package containing dependency other packages LibraryModel Catalog BiblioSearch Journal System System Management import dependency BookAcquisition Loan System System Figure 14.8 - Model packaging www.wileyeurope .com/college/van lamsweerde Chap.14: Integrating multiple system views © 2009 John Wiley and Sons 13