Presentation is loading. Please wait.

Presentation is loading. Please wait.

C S E USC CBSP Bridging Requirements and Architecture Models Paul Grünbacher Center for Software Engineering University of Southern California, Los Angeles.

Similar presentations


Presentation on theme: "C S E USC CBSP Bridging Requirements and Architecture Models Paul Grünbacher Center for Software Engineering University of Southern California, Los Angeles."— Presentation transcript:

1 C S E USC CBSP Bridging Requirements and Architecture Models Paul Grünbacher Center for Software Engineering University of Southern California, Los Angeles gruenbac@sunset.usc.edu WESAS Workshop @ UCI, May 8-9, 2000

2 C S E USC WESAS Workshop @ UCI 2 Background Objectives –Improve ties between requirements and architecture models –Integrate EasyWinWin requirements negotiation and SAAGE architecture research Challenges –Requirements and architecture models emerge concurrently in an iterative process –The process involves heterogeneous stakeholders with conflicting objectives and expectations –Natural language leads to imprecision and ambiguities of requirements models –Semantic gap between high-level requirements and elements in a system architecture

3 C S E USC WESAS Workshop @ UCI 3 EasyWinWin Collaborative Requirements Negotiation A set of groupware-supported collaboration techniques (“thinkLets”) enabling stakeholder involvement in the WinWin requirements negotiation process Electronic brainstorming of stakeholder interests Categorization and organization Distributed prioritization Shared definition of terms Shared domain taxonomy Use case analysis

4 C S E USC WESAS Workshop @ UCI 4 A real-world Negotiation Example: COTS Product Release Planning 11 stakeholders created 275 statements  88 win conditions, 108 issues, 150 options Architectural relevance analysis of the 108 issues –20: components and connectors –15: properties of components & connectors (size of client sw, security of connection, …) –13: system-level properties –3: low-level design or implementation –50% of the issues were architecturally relevant

5 C S E USC WESAS Workshop @ UCI 5 CBSP: Component, Bus, System, Property C: describe or involve a Component in an architecture B: describe or imply a connector (Bus) S: describe System-wide features or features pertinent to multiple components and connectors CP: describe or imply component properties BP: describe or imply connector (bus) properties SP: describe or imply system properties pertaining to the entire architecture

6 C S E USC WESAS Workshop @ UCI 6 Cargo Router Example

7 C S E USC WESAS Workshop @ UCI 7 CBSP Voting Tool for Classification

8 C S E USC WESAS Workshop @ UCI 8 CBSP Benefits Lightweight approach Requirements to architecture (synthesis) –Identify and classify WinWin artifacts –Reveal incomplete and puzzling WinWin artifacts –Refine complex WinWin artifacts into CBSP artifacts Architecture to requirements (analysis) –Capture architectural mismatches –Capture architecture trade-off decisions

9 C S E USC WESAS Workshop @ UCI 9 CBSP As a Model Connector


Download ppt "C S E USC CBSP Bridging Requirements and Architecture Models Paul Grünbacher Center for Software Engineering University of Southern California, Los Angeles."

Similar presentations


Ads by Google