Data sheet


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Data sheet

  1. 1. InfoTech Consulting Requirements and Systems Engineering Profile (RSE™) The RSE UML 2/SysML profile is a comprehensive modeling framework that provides a holistic approach to model based development of any kind of system including EA (Enterprise Architecture), technical and information systems. The Profile provides support for BPM based on Ericsson-Penker UML Business Extensions, component management including systems of systems, variant management of systems and product structures, advanced workflow based change management and automated complexity and size estimation with function points (FP) counted on Use Case and Domain Model specifications. The profile’s logic is defined with a public Meta Model that can be customized to define an organization’s modeling standards. The profile in addition provides more than 50 useful script functions to facilitate customization and development of ergonomic profiles. The profile also extends the Studios SysML profile requirements and block modeling. The profile provides 5 new ARTiSAN Studio Browsers • Organization and Process Specification of business needs and system functional breakdown • Use Case and Domain Model Use case and domain modeling for precise specification of business logic and system requirements including automated FP estimation • Change Management Change Notes, Change Requests and Tasks • Components Components and system of systems management • Blocks Extension Extensions to the default SysML Block browser Organization and Process The organization diagram supports modeling of organization units and organization roles. The organization model units can also be combined with SysML Blocks in a Block Definition Diagram or Internal Block Diagram to build integrated models of organization units, organization roles, organization equipment and HW/SW product components.
  2. 2. Business Process Internal Diagram Manage Vehicle The process diagram is based on the UML 2 Activity Meta Manage Vehicle Model representing a functional breakdown of a system such as an enterprise or a process area. The default configuration includes Processes, Business Activities, Organization Units, Service Vehicle Organization Roles and External Roles. Business goals model Parts Supplier can be built and goals be assigned to processes. With assembly line analysis can a process structure be recursively Owner analyzed and the process dependencies to roles, organization Drive Vehicle units, systems, components etc. be viewed for each process. Ambient Air Processes are stereotyped activities representing the logical Assembly line analysis breakdown of the business in units that typically have a Driver continuous character (e.g. Service Vehicle, Drive Vehicle, InternalCombustionEngine Sales etc.). ElectricalPowerController The process diagram can be regarded as the macro view of a systems process breakdown. The process activities are specified with Activity diagrams, as in the example on page 3, or alternatively with Object Sequence Diagrams (OSD). SysML Requirements Extensions The Requirement View includes usability extensions to the standard Studio SysML profile. The SysML requirement has been extended with a Requirement enumeration Type Tag to support an organization’s different types of requirements e.g. performance, text, constraint etc. For each of the predefined types there is a “virtual folder” (Derived tag) in the Requirement View browser that lists the requirements of the corresponding type. The enumeration list and reporting derived tags can be customized to meet an organization’s standards. In addition, a number of derived tags have been added to view dependency information such as referencing CR, Satisfying Items, linked Rationale notes etc. Double-clicking on a requirements package opens an “instant listing” requirements diagram of the contained requirements. Indented requirements contain sub requirements that can be listed by double-clicking on the indented requirement for simple traverse of requirement trees. Use Case and Domain Model The Use Case and Domain Model View supports advanced use case modeling of functional requirements to enable seamless integration with process models and implementation models. 2 (6)
  3. 3. Use Case modeling is supported with a new Use Case model. Use Cases can be specified with text including RTF references to Register Order model items, Activity Diagrams and OSD diagrams. Sales Clerk Business Process Internal Diagram Sales The model enables a tight integration with other parts of an Sales enterprise model such as a process model where a Use Case {State = New} represents an activity in the context of a supported process. The Order Request organization role is mapped to an Activity Partition in the Use Order confirmation Register Order Case as in the Activity diagram on page 3. In this case is the Sales Clerk playing the role Sales Rep in the organization unit Sales Department. Use Case OSD Drive detail diagram :Driver «Use Case Use» «part» «part» Drive Steering Servo Vehicle ECU A Use Case in a Use Case 1 par diagram then represents a 1.1 Steering Direction {1 mS} Use Case type that can be 1.1.1 Direction used in one or more 1.2 Alert road-user Sound the horn Business Processes. 1.2.1 Sound A Use Case also be 1.3 seq ref Accelerate Extension inserted in an OSD diagram then an OSD 1.4 seq ref Decelerate Extension diagram is used for the 1.5 seq ref Shift Gear Extension Use Case specification. Activity Diagram Order Registration Use Case Register Order A required “use case An actor action i.e. a business action action” i.e. an atomic : Sales Department functional requirement Sales Rep : [Sales Clerk] «Data Store» {State = New} Customer Data : Receive Order Request Customer Order Request Review the received «Central Buffer» : Order Specification Order Request and ... Received Order Data {State = Valid} Order Request Customer Name «Action» Enter Customer name «FP» {Item FP = 3} {OrderSpecification.State <> Valid} {Complexity = LOW} {OrderSpecification.State = Valid} Get Customer Record {State = Invalid} Order Request Customer Record : Customer View Customer record The Use Case Activity diagram also supports function point metrics that are automatically calculated. In the example above is the estimated value 3 FP for the “Get Customer Record” action. This enables a fast and convenient complexity and size calculation without any need for manual FP calculation. For definition of an organization’s information architecture and business logic there is a domain diagram available that also supports automatic calculation of size estimation in function points. A domain object might be a structured composite class containing one or more parts or be a single class. The domain model also includes definition of the items composition, associations and domain object lifecycles. Blocks Extension 3 (6)
  4. 4. The RSE Block extensions add all the ARTiSAN Studio’s System Architecture Diagram items to a SysML Block model (e.g. board, processor, memory in the figure below). The profile also adds a number of other model items to block diagrams such as SW units, Organization Units, Organization Roles, Components etc. enabling enterprise architecture modeling (e.g. the DMDT component in the figure below). However, most organizations will have a number of preferred HW and SW items and so the profile allows additional block stereotypes to be added by updating the stereotype list and the Meta Model. Dispenser Main Microcomputer Dispenser Main Microcomputer Dispenser control Custom I/O Operation of the dispenser is controlled by the Com 1 dispenser (‘main’) microcomputer, this being Height = 100 «satisfy» Com 2 Com6 interfaced to the kiosk controller by an RS422 serial Width = 150 Com 3 comms line. This microcomputer also controls the Com 4 displays, although this is done indirectly via a display Com 5 24V decoder microcomputer. The advantages of using a separate 24 V Connector micro for display handling are threefold: <<Rationale>> Dispenser Main Bus The Dispenser Dispenser Motherboard satisfies ... Dispenser Motherboard Dispenser power down «satisfy» The following data is to be retained by the main «satisfy» micro when the dispenser is powered down. RAM Memory «satisfy» RAM ROM DMDT The RAM memory must be at least 400 Mb DMDT «satisfy» Processor speed 68000 The next release of the SW requires at least a 500 MHz Width = 180 Height = 120 processor The block stereotype has 4 additional derived tags to view the blocks satisfied requirements including all contained block properties. The “Item Satisfied Requirements” and “Item Satisfy Dependencies” list all satisfied requirements for the selected block. The ”All Structure Satisfied Requirements” and “All Structure Satisfy Dependencies” recursively searches the whole structure below the block for satisfied requirements. Components The component modeling support modeling of Systems, Subsystems and Components integrated with software classes and MDA. The Meta model can easily be customized to define the organizations architecture guidelines. 4 (6)
  5. 5. Change Management The Change Management supports Change Request (CR) Change Request State Diagram and Task items. Forward/ A Task can be assigned to one or more CR or a CR can be Alt/ Forward/ assigned to one or more Tasks. Alternatively can also Tasks Specification Rejected be excluded and CR’s be assigned directly to team Forward/Move to CCB members. Alt/ CCB The process flow for managing change through CR’s and Forward/Select Owner Alt/ Task’s is defined with state diagrams allowing the process to Alt/ be tailored to reflect company standards. Assigned Deferred Forward/Select Owner Requirements and other model items can be linked to a CR Forward/ or Task to enable process control of the implementation of Under Work requirements and the Studio model items that is created or Alt/ updated. The linking can be performed from the CR/Task or Forward/ Alt/ Alt/ from a requirement or model item. In Requirements and model items property pages can you also view the status of QA a related CR or Task. CR and Tasks are stereotyped Studio Forward/ ... Change Notes and consequently can also CR and Tasks be enforced if the Studio Change Tracking is turned on. Closed Forward/ This enables a tight integration of change management with model driven development especially with a model centric “MDA” approach where all code is stored in the model and managed within the Studio Repository. Profile Meta Model Use Case Meta Model The profile has a public meta model that defines |Use Case Diagram the modeling standards. All relevant stereotypes have a linked Meta Class in the meta model 1 1 1 with definitions of valid associations, * dependencies, moves, drops etc. for diagrams |Organization Role and browsers. * Communication Path The Meta Model can be customized and * * * extended to support an organization’s modeling |actor |Use Case verify |requirement standards and development process. include extend 5 (6)
  6. 6. About InfoTech Consulting InfoTech is a consulting group specializing in UML/SysML model based development, systems engineering and enterprise architecture modeling. InfoTech is also a reseller and a solutions provider for ARTiSAN’s products for the Nordic market. Contact information InfoTech Consulting AB Box 8156 SE-163 08 Spånga Sweden Tel: +46 8 621 0411 Email: Web: An RSE Tutorial model can be downloaded from The profile requires Studio V7.0f or higher. © 2006 - 2009 InfoTech Consulting AB. RSE™ is a trademark of InfoTech Consulting AB. Artisan and Artisan Studio are trademarks or registered trademarks of ARTiSAN Software Tools Ltd. All other trademarks are the property of their respective holders. 6 (6)