没有合适的资源?快使用搜索试试~ 我知道了~
温馨提示
试读
142页
IBM 首席系统方法论工程师Hans-Peter Hoffmann博士著作。 Systems Engineering Best Practices with Rational Solution for Systems and Software Engineering Deskbook Release 4.1. 中文名为“基于模型的系统工程最佳实践” 是基于模型的系统工程和软件工程的实践指南。 是Rhapsody的实践指南。 对应的软件是Rhapsody 7.5。
资源推荐
资源详情
资源评论
Foreword
The file "Deskbook Rel311.pdf" is the latest version of the Rational Harmony for Systems Engineering Deskbook Release 3.1 (“Deskbook”), released
May 28, 2010.
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 Deskbook is not intended to replace training for the IBM Rational Rhapsody component of the IBM Rational
Workbench for Systems and Sofware Enigineering; it is intended to supplement it. It is assumed that the reader is familiar with UML/SysML and the
IBM Rational Rhapsody component of the IBM Rational Workbench for Systems and Software Engineering.
Permission to use, copy, and distribute, this Deskbook, is granted; provided, however, that the use, copy, and distribution of the Deskbook is made in
whole and not in part.
THIS DESKBOOK IS PROVIDED "AS IS." IBM MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT
NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
IBM WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE
DESKBOOK OR THE PERFORMANCE OR IMPLEMENTATION OF THE CONTENTS OF THE DESKBOOK..
The directory "Deskbook Rel.3.1 Requirements and Models" contains the requirements specification for the Security System example and snapshots
of the models generated with Rhapsody.
Copyright IBM Corporation 2006, 2010
IBM Corporation
Software Group
Route 100
Somers, NY 10589
U.S.A.
Licensed Materials - Property of IBM Corporation
U.S. Government Users Restricted Rights: Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo and other IBM products and services are trademarks of the International
Business Machines Corporation, in the United States, other countries or both.
Other company, product, or service names may be trademarks or service marks of others.
The Rational Software home page on the Internet can be found at ibm.com/software/rational
The IBM home page on the Internet can be found at ibm.com
February 2011
Systems Engineering Best Practices with the Rational
Solution for Systems and Software Engineering
Deskbook Release 3.1.2
Model-Based Systems Engineering with Rational Rhapsody and
Rational Harmony for Systems Engineering
Hans-Peter Hoffmann, Ph.D.
Chief Systems Methodologist
hoffmape@us.ibm.com
© 2011 IBM Corporation
IBM Software Group
The file "Deskbook Rel312.pdf" is the latest version of the “Systems Engineering Best Practices with the Rational Solution for Systems and Software
Engineering Deskbook Release 3.1.2” (“Deskbook”), released February 21, 2010.
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 Deskbook is not intended to replace IBM Rational Rhapsody training; it is intended to supplement it. It is
assumed that the reader is familiar with UML/SysML and the IBM Rational Rhapsody tool.
Permission to use, copy, and distribute, this Deskbook, is granted; provided, however, that the use, copy, and distribution of the Deskbook is made in
whole and not in part.
THIS DESKBOOK IS PROVIDED "AS IS." IBM MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT
NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
IBM WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE
DESKBOOK OR THE PERFORMANCE OR IMPLEMENTATION OF THE CONTENTS OF THE DESKBOOK..
The directory "Deskbook Rel.3.1.2 Requirements and Models" contains the requirements specification for the Security System example and
snapshots of the models generated with Rhapsody.
Copyright IBM Corporation 2006, 2011
IBM Corporation
Software Group
Route 100
Somers, NY 10589
U.S.A.
Licensed Materials - Property of IBM Corporation
U.S. Government Users Restricted Rights: Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo and other IBM products and services are trademarks of the International
Business Machines Corporation, in the United States, other countries or both.
Other company, product, or service names may be trademarks or service marks of others.
The Rational Software home page on the Internet can be found at ibm.com/software/rational
The IBM home page on the Internet can be found at ibm.com
© Copyright IBM Corporation 2006, 2010. All Rights Reserved
.
Foreword
The Author - by J. Rick White
Foreword to the Deskbook Release 3.0
Here it is – the long awaited next iteration. I completely restructured
the Deskbook, focusing more on the methododical part of Harmony for
Systems Engineering and its support in Rhapsody by means of the
Rhapsody SE-Toolkit. This release also extends the previous scope.
It now addresses Requirements Elaboration and Traceability as well
as Architectural Analysis through Trade Studies.
I want to thank two colleagues who deserve special mentions with
regard to their contributions to this release: Andy Lapping and Dr.
Graham Bleakley. Andy - the “Wizard Guru” – is the author of the
Rhapsody-SE-Toolkit. Whenever I came up with an idea, how the SE
workflow could be automated, the next day I got the wizard-based
solution. Graham is the specialist for Architectural Analysis. The
chapter on how to perform a trade study is based on his input. Here
again, Andy automated it by respective wizards.
Any feed-back for the next iteration (release) is appreciated.
Andover, 06-01-09
Foreword to the Deskbook Release 2.0
The systems engineering process is iterative. There is no reason why
this should not be applicable also to this Deskbook. Meanwhile,
numerous companies started to apply the Harmony for Systems
Engineering process using the Deskbook as a general guideline.
This revision takes into consideration the feed-back that I got from “the
field”. Especially with regard to the use case analysis, I realized that
the approach needed to consider the needs of projects with a large
numbers of use cases. Nothing changed with regard to the workflow.
What changed, is the project structure. The new project structure
supports team collaboration. Each use case now may be elaborated
separately and then – iteratively - merged to a common system model.
The outlined process (Harmony for Systems Engineering) is tool
independent.
Andover, 10-12-06
ii | Systems Engineering Best Practices Deskbook © Copyright IBM Corporation 2006, 2011. All Rights Reserved
.
Table of Contents
Table of Contents
1 INTRODUCTION 1
1.1 Scope.................................................................................................................................................................................................................... 1
1.2 Document Overview ............................................................................................................................................................................................. 1
2 FUNDAMENTALS OF HARMONY FOR SYSTEMS ENGINEERING...............................................................................................................................2
2.1 Rational Integrated Systems / Embedded Software Development Process Harmony ........................................................................................ 2
2.2 Model-based Systems Engineering Process........................................................................................................................................................ 4
2.2.1 Requirements Analysis.................................................................................................................................................................................. 5
2.2.2 System Functional Analysis .......................................................................................................................................................................... 6
2.2.3 Design Synthesis......................................................................................................................................................................................... 10
2.2.3.1 Architectural Analysis (Trade Study).................................................................................................................................................... 11
2.2.3.2 Architectural Design ............................................................................................................................................................................. 14
2.2.3.3 Detailed Architectural Design............................................................................................................................................................... 16
2.2.4 Systems Engineering Hand-Off................................................................................................................................................................... 18
2.3 Essential SysML Artifacts of Model-based Systems Engineering...................................................................................................................... 19
2.3.1 Requirements Diagram ............................................................................................................................................................................... 20
2.3.2 Structure Diagrams...................................................................................................................................................................................... 20
2.3.2.1 Block Definition Diagram...................................................................................................................................................................... 20
2.3.2.2 Internal Block Diagram......................................................................................................................................................................... 20
2.3.2.3 Parametric Diagram ............................................................................................................................................................................. 22
2.3.3 Behavior Diagrams...................................................................................................................................................................................... 22
2.3.3.1 Use Case Diagram............................................................................................................................................................................... 23
2.3.3.2 Activity Diagram ................................................................................................................................................................................... 23
2.3.3.3 Sequence Diagram .............................................................................................................................................................................. 24
2.3.3.4 Statechart Diagram .............................................................................................................................................................................. 24
2.3.4 Artifact Relationships at the Requirements Analysis / System Functional Analysis Level.......................................................................... 25
2.4 Service Request-Driven Modeling Approach ..................................................................................................................................................... 26
3 RHAPSODY PROJECT STRUCTURE............................................................................................................................................................................27
3.1 Project Structure Overview................................................................................................................................................................................. 27
3.2 Requirements Analysis Package........................................................................................................................................................................ 28
3.3 Functional Analysis Package.............................................................................................................................................................................. 29
3.4 Design Synthesis Package................................................................................................................................................................................. 30
© Copyright IBM Corporation 2006, 2011. All Rights Reserved. Systems Engineering Best Practices Deskbook | iii
Table of Contents
3.4.1 Architectural Analysis Package ................................................................................................................................................................... 30
3.4.2 Architectural Design Package ..................................................................................................................................................................... 31
3.5 System-Level Definitions .................................................................................................................................................................................... 32
4 CASE STUDY: SECURITY SYSTEM ............................................................................................................................................................................. 33
4.1 Getting Started.................................................................................................................................................................................................... 33
4.2 Requirements Analysis ....................................................................................................................................................................................... 34
4.2.1 Import of Stakeholder Requirements........................................................................................................................................................... 35
4.2.2 Generation of System Requirements .......................................................................................................................................................... 36
4.2.3 Linking System Requirements to Stakeholder Requirements..................................................................................................................... 38
4.2.4 Definition of System-Level Use Cases ........................................................................................................................................................ 40
4.2.5 Linking Requirements to Use Cases ........................................................................................................................................................... 41
4.3 System Functional Analysis................................................................................................................................................................................ 43
4.3.1 Uc1ControlEntry .......................................................................................................................................................................................... 44
4.3.1.1 Project Structure of the Uc1 Model ...................................................................................................................................................... 44
4.3.1.2 Definition of Uc1 Functional Flow......................................................................................................................................................... 45
4.3.1.3 Definition of Uc1 Scenarios.................................................................................................................................................................. 46
4.3.1.4 Definition of Ports and Interfaces ......................................................................................................................................................... 50
4.3.1.5 Definition of State-based Behavior....................................................................................................................................................... 51
4.3.1.6 Uc1 Model Verification ......................................................................................................................................................................... 53
4.3.1.7 Linking Uc1 Block Properties to Requirements................................................................................................................................... 55
4.3.2 Uc2ControlExit............................................................................................................................................................................................. 58
4.3.2.1 Project Structure of the Uc2 Model ...................................................................................................................................................... 58
4.3.2.2 Definition of Uc2 Functional Flow......................................................................................................................................................... 58
4.3.2.3 Definition of Uc2 Scenarios.................................................................................................................................................................. 59
4.3.2.4 Definition of Ports and Interfaces ......................................................................................................................................................... 60
4.3.2.5 Definition of State-based Behavior....................................................................................................................................................... 60
4.3.2.6 Uc2 Model Verification ......................................................................................................................................................................... 61
4.3.2.7 Linking Uc2 Block Properties to Requirements................................................................................................................................... 61
4.3.3 Merging Use Case Blocks ........................................................................................................................................................................... 62
4.4 Design Synthesis ................................................................................................................................................................................................ 63
4.4.1 Architectural Analysis (Trade-Off Analysis)................................................................................................................................................. 63
4.4.1.1 Definition of Key System Functions ..................................................................................................................................................... 64
4.4.1.2 Definition of Candidate Solutions ......................................................................................................................................................... 65
4.4.1.3 Definition of Assessment Criteria ......................................................................................................................................................... 66
4.4.1.4 Assigning Weights to Assessment Criteria .......................................................................................................................................... 67
4.4.1.5 Definition of a Utility Curve for each Criterion ...................................................................................................................................... 68
4.4.1.6 Assigning Measures of Effectiveness (MoE) to each Solution............................................................................................................. 69
4.4.1.7 Determination of Solution ..................................................................................................................................................................... 70
4.4.2 Architectural Design .................................................................................................................................................................................... 72
剩余141页未读,继续阅读
资源评论
IsaacCanton
- 粉丝: 1
- 资源: 6
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功