120 likes | 254 Views
This tutorial focuses on the crucial aspect of component representation within software systems, particularly for micro-businesses. It explores the basic concept of how components are represented, from operational methods to measurable outcomes, contributing to essential software qualities. The tutorial covers various representation techniques, including custom miniature and classic component diagrams, aimed at helping developers understand the structure and interactions of software components like sales and inventory systems. Exercises and examples will enhance your learning experience.
E N D
Tutorial 3 –Component Representation RJ Macasaet R&D Dept.
Outline • Basic Concept • Representation
Understand the idea of component representation within the approach Basic Concept
I. Basic Concept • Where is the component represented? NFR Start “speed” Other Process Process Pattern: place to shop Mode: website [done as] Fast Server {measurement: Data Transfer Rate} [applied as] Instantiation: www.shop.com This is where the Component representation must be placed WHY?
I. Basic Concept • An operationalizing method • must be something “measurable” and “observable” • contributes to the “-ilities” of the component • The component “supports” the instantiation (of the pattern)
I. Basic Concept Goals Sub Goals satisfy/satisfice Micro-business Processes Metamodel reference to the components decompose satisfy/satisfice decompose Requirements Functional Requirements Non-Functional Requirements satisfy satisfice Components realize Patterns Specifications Structure
Learn how to represent the software components within the approach Representation
II. Representation • Hence, the basic component representation… Custom Miniature Component Representation – for easy viewing by the developer << contributes >> Instantiation: www.shop.com c1 Fast Server {measurement: Data Transfer Rate} << supports>>
II. Representation Instantiation: www.shop.com Classic Component Diagram – for more detailed viewing Fast Server {measurement: Data Transfer Rate} << component “c1” >> Shop.com online system << supports>> << contributes >> << required interfaces >> sales system, inventory system << provided interfaces >> website for customers << artifact >> shop.exe
II. Representation [applied as] * μb sales pattern Instantiation: www.shop.com realize Fast Server {measurement: Data Transfer Rate} << system >> shop.com online shopping site << supports>> << contributes >> << artifact >> * sales management system Classic Deployment Diagram – showing relationship with the micro-business pattern << artifact >> Inventory mgt system << artifact >> server
II. Representation • Exercise: Illustrate the software components that are used in a retail store software system (sales and inventory system). You may use existing BPMN/SIGs process diagrams.