5
© Telelogic AB
HARMONY-SE / SysML Deskbook(Rev 1.52)
1. INTRODUCTION
1.1 Scope
Meanwhile, many books and articles have been published about SysML,
the standardized language for model-based systems engineering [1].
But in most cases, the question of how to apply it in an integrated
systems and software development process has not been addressed.
This deskbook tries to close the gap. Based on the tool independent
integrated sy
stems / software development process HARMONY it
provides systems engineers with a step-by step guide on using the
SysML in a way that allows a seamless transition to the subsequent
system development.
In this deskbook the chosen tool is the Telelogic systems and software
design tool Rhapsody
®
.
The deskbook is written for the practitioner. Screenshots, notes, and
best practice tips are added to the workflow descriptions. The brief
introductions are minimal rather than narrative
The deskbookdoes not replace the Rhapsody training documentation.
It rather is intended to supplement it. It is assumed, that the reader
is familiar with the SysML and the Rhapsody tool.
1.2 Document Overview
The deskbook is divided into 5 sections:
• Section 1 describes the scope and structure of this book.
• Section 2 introduces the basic concepts of HARMONY-SE. It starts
with an overview of how the systems engineering part of the integrated
systems and software development process HARMONY fits into the
model driven development lifecycle. Then, the task flow and
the
associated work products in the different systems engineering phases
are detailed. With regard to modeling, this section also provides an
overview of SysML artifacts that are considered essential for model-
based systems engineering, followed by an introduction to the
service request driven modeling approach.
• Section 3 describes the project structure that should be followed when
the Rhapso
dy tool is used in a model-based systems engineering
project.
• Section 4 details a case study of the HARMONY-SE workflow using the
Rhapsody tool. The chosen example is a security system. The
workflow starts with the transformation of the requirements into use
case models and ends with the definition of an executable system
architecture model. The workflow includes the usage of Rhap
sody’s
dedicated HARMONY-SE wizards.
• Section 5 addresses the handoff to subsystem development.
A subsystem specification of the security system architecture is ported
into a new Rhapsody project. The completeness of the handoff is
checked through model execution.
Introduction
我的内容管理
收起
我的收益 登录查看自己的收益
我的积分
登录查看自己的积分
我的C币
登录后查看C币余额
我的收藏 
我的下载 
下载帮助 
