Muutke küpsiste eelistusi

E-raamat: SysML for Systems Engineering

3.83/5 (11 hinnangut Goodreads-ist)
,
  • Formaat: PDF+DRM
  • Sari: Computing and Networks
  • Ilmumisaeg: 23-Sep-2011
  • Kirjastus: Institution of Engineering and Technology
  • Keel: eng
  • ISBN-13: 9780863419799
Teised raamatud teemal:
  • Formaat - PDF+DRM
  • Hind: 201,50 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Lisa ostukorvi
  • Lisa soovinimekirja
  • See e-raamat on mõeldud ainult isiklikuks kasutamiseks. E-raamatuid ei saa tagastada.
SysML for Systems EngineeringSuurem pilt
  • Formaat: PDF+DRM
  • Sari: Computing and Networks
  • Ilmumisaeg: 23-Sep-2011
  • Kirjastus: Institution of Engineering and Technology
  • Keel: eng
  • ISBN-13: 9780863419799
Teised raamatud teemal:

DRM piirangud

  • Kopeerimine (copy/paste):

    ei ole lubatud

  • Printimine:

    ei ole lubatud

  • Kasutamine:

    Digitaalõiguste kaitse (DRM)
    Kirjastus on väljastanud selle e-raamatu krüpteeritud kujul, mis tähendab, et selle lugemiseks peate installeerima spetsiaalse tarkvara. Samuti peate looma endale  Adobe ID Rohkem infot siin. E-raamatut saab lugeda 1 kasutaja ning alla laadida kuni 6'de seadmesse (kõik autoriseeritud sama Adobe ID-ga).

    Vajalik tarkvara
    Mobiilsetes seadmetes (telefon või tahvelarvuti) lugemiseks peate installeerima selle tasuta rakenduse: PocketBook Reader (iOS / Android)

    PC või Mac seadmes lugemiseks peate installima Adobe Digital Editionsi (Seeon tasuta rakendus spetsiaalselt e-raamatute lugemiseks. Seda ei tohi segamini ajada Adober Reader'iga, mis tõenäoliselt on juba teie arvutisse installeeritud )

    Seda e-raamatut ei saa lugeda Amazon Kindle's. 

Systems modelling is an essential enabling technique for any systems engineering enterprise. This book provides an introduction to the systems engineering modelling language, the SysML, aimed at systems engineering practitioners at various levels of abilities, ranging from students to experts.

Systems modelling is an essential enabling technique for any systems engineering enterprise. These modelling techniques, in particular the Unified Modelling Language (or UML), have been employed widely in the world of software engineering and very successfully in systems engineering for many years. However, in recent years there has been a perceived need for a tailored version of the UML that meets the needs of today's systems engineering professional.This book provides a pragmatic introduction to the systems engineering modelling language, the SysML, aimed at systems engineering practitioners at any level of ability, ranging from students to experts. The theoretical aspects and syntax of SysML are covered and each concept is explained through a number of example applications. The book also discusses the history of the SysML and shows how it has evolved over a number of years. All aspects of the language are covered and are discussed in an independent and frank manner, based on practical experience of applying the SysML in the real world.
1 Introduction to systems engineering 1
1.1 Introduction
1
1.2 Information sources
1
1.3 Defining systems engineering
2
1.4 The need for systems engineering
4
1.5 The three evils of engineering
5
1.5.1 Complexity
6
1.5.2 Lack of understanding
8
1.5.3 Communication problems
8
1.5.4 The vicious triangle of evil
9
1.6 Systems-engineering concepts
10
1.6.1 Processes
11
1.6.2 Systems
13
1.6.3 The 'context'
15
1.6.4 Life cycles
18
1.6.5 Projects
19
1.7 Modelling
20
1.7.1 Defining modelling
20
1.7.2 The choice of model
21
1.7.3 The level of abstraction
21
1.7.4 Connection to reality
21
1.7.5 Independent views of the same system
22
1.8 SysML – the system modelling language
22
1.9 Using this book
23
1.9.1 Competency
23
1.10 Conclusions
24
1.11 References
24
2 An introduction to SysML 27
2.1 Introduction
27
2.2 What is SysML?
27
2.2.1 SysML's relation to UML
28
2.3 The history of SysML
32
2.3.1 A brief chronology
33
2.4 A comparison of versions
34
2.4.1 The original version
35
2.4.2 The two evaluation versions
36
2.4.3 SysML Merge Team version and the Final Adopted Specification
41
2.5 Potential concerns with SysML
43
2.6 Conclusions
44
2.7 Further reading
44
3 Modelling 47
3.1 Introduction
47
3.2 Structural modelling
47
3.3 Structural modelling using block definition diagrams
49
3.3.1 Modelling blocks and relationships
49
3.3.2 Basic modelling
49
3.3.3 Adding more detail to blocks
52
3.3.4 Adding more detail to relationships
54
3.3.5 A note on instances
59
3.3.6 Other structural diagrams
60
3.3.7 Conclusion
60
3.4 Behavioural modelling
62
3.5 Behavioural modelling using state machine diagrams
64
3.5.1 Introduction
64
3.5.2 Basic modelling
64
3.5.3 Behavioural modelling – a simple example
66
3.5.4 Ensuring consistency
69
3.5.5 Solving the inconsistency
71
3.5.6 Alternative state machine modelling
73
3.5.7 Other behavioural diagrams
75
3.6 Identifying complexity through levels of abstraction
76
3.6.1 Introduction
76
3.6.2 The systems
76
3.6.3 Structural view
76
3.6.4 Behavioural views
77
3.7 Conclusions
81
3.8 Reference
81
4 The SysML diagrams 83
4.1 Introduction
83
4.1.1 Overview
83
4.1.2 Terminology
84
4.2 The structure of SysML diagrams
85
4.2.1 Frames
85
4.3 Stereotypes
87
4.4 The SysML meta-model
88
4.4.1 Diagram ordering
90
4.4.2 The worked example
90
4.5 Block definition diagrams (structural)
90
4.5.1 Overview
90
4.5.2 Diagram elements
91
4.5.3 Example diagrams and modelling — block definition diagrams
96
4.5.4 Using block definition diagrams
105
4.6 Internal block diagrams (structural)
106
4.6.1 Overview
106
4.6.2 Diagram elements
106
4.6.3 Examples and modelling — internal block diagrams
109
4.6.4 Using internal block diagrams
112
4.7 Package diagrams (structural)
112
4.7.1 Overview
112
4.7.2 Diagram elements
113
4.7.3 Examples and modelling — package diagrams
115
4.7.4 Using package diagrams
117
4.8 Parametric diagrams (structural)
117
4.8.1 Overview
117
4.8.2 Diagram elements
118
4.8.3 Examples and modelling — parametric diagrams
119
4.8.4 Using parametric diagrams
122
4.9 Requirement diagrams (structural)
122
4.9.1 Overview
122
4.9.2 Diagram elements
122
4.9.3 Examples and modelling — requirement diagrams
124
4.9.4 Using requirement diagrams
128
4.10 State machine diagrams (behavioural)
129
4.10.1 Overview
129
4.10.2 Diagram elements
129
4.10.3 Examples and modelling — state machine diagrams
132
4.10.4 Using state machine diagrams
137
4.11 Sequence diagrams (behavioural)
137
4.11.1 Overview — sequence diagrams
137
4.11.2 Diagram elements — sequence diagrams
137
4.11.3 Examples and modelling — sequence diagrams
140
4.11.4 Using sequence diagrams
142
4.12 Activity diagrams (behavioural)
143
4.12.1 Overview
143
4.12.2 Diagram elements
144
4.12.3 Examples and modelling
148
4.12.4 Using activity diagrams
153
4.13 Use case diagrams (behavioural)
153
4.13.1 Overview
153
4.13.2 Diagram elements
154
4.13.3 Examples and modelling
157
4.13.4 Using use case diagrams
161
4.14 Summary and conclusions
161
4.14.1 Summary
161
4.14.2 Conclusions
162
4.15 Further discussion
163
4.16 References
164
4.17 Further reading
164
5 Physical systems, interfaces and constraints 165
5.1 Introduction
165
5.2 Connecting parts of the system
165
5.2.1 Flow ports and flow specifications
166
5.2.2 Standard ports and interfaces
168
5.3 Allocations
170
5.4 Parametric constraints
173
5.4.1 Relationships to blocks
173
5.4.2 Types of constraint
176
5.5 Putting it all together — the escapology problem
178
5.5.1 Requirements
179
5.5.2 Definition of the system
180
5.5.3 Definition of the constraints
183
5.5.4 Using the constraints
184
5.6 Conclusions
194
6 Process modelling with SysML 195
6.1 Introduction
195
6.1.1 Modelling processes using SysML
195
6.1.2 The process-modelling meta-model
196
6.1.3 The process meta-model — conceptual view
196
6.1.4 Consistency between views
200
6.1.5 Using the seven-views meta-model
202
6.2 Modelling life cycles
202
6.2.1 Introduction
202
6.2.2 The life cycle
203
6.2.3 The process library
205
6.2.4 Life-cycle models
205
6.2.5 Using life cycles and life-cycle models
210
6.2.6 Summary
210
6.3 Applying the seven views to a standard
210
6.3.1 Introduction
210
6.3.2 Introduction to standards
210
6.3.3 Process-structure view
213
6.3.4 Requirements view
215
6.3.5 Process-content view
217
6.3.6 Information view
217
6.3.7 Using the views
219
6.3.8 Summary
219
6.4 Apply the seven views to a process
219
6.4.1 Introduction
219
6.4.2 The STUMPI life cycle
220
6.4.3 The STUMPI life-cycle model
220
6.4.4 The STUMPI process model
223
6.4.5 Stage iterations
228
6.4.6 Process behaviour
229
6.4.7 Information view
230
6.5 Conclusions
233
6.6 References
233
7 Modelling requirements 235
7.1 Introduction
235
7.2 Requirements engineering basics
236
7.2.1 Introduction
236
7.2.2 The 'requirements stage'
236
7.2.3 Capturing requirements
239
7.2.4 Requirements
241
7.2.5 Stakeholders
246
7.2.6 Summary
249
7.3 Using use case diagrams (usefully)
250
7.4 Context modelling
251
7.4.1 Types of context
251
7.4.2 Practical context modelling
256
7.4.3 Summary
260
7.5 Requirements modelling
260
7.5.1 Introduction
260
7.5.2 Modelling requirements
261
7.5.3 Ensuring consistency
267
7.5.4 Describing use cases
271
7.6 Modelling scenarios
273
7.6.1 Scenarios in the SysML
274
7.6.2 Example scenarios
274
7.6.3 Wrapping up scenarios
277
7.7 Documenting requirements
277
7.7.1 Overview
277
7.7.2 Populating the document
279
7.7.3 Finishing the document
280
7.8 Summary and conclusions
281
7.9 Further discussion
283
7.10 References
284
7.11 Further reading
284
Appendix A Summary of SysML notation 285
A.1 Introduction
285
A.2 Structural diagrams
285
A.3 Behavioural diagrams
300
A.4 Cross-cutting concepts
315
A.5 Relationships between diagrams
321
Appendix B Using SysML concepts in UML 325
B.1 Introduction
325
B.2 Flow ports and flow specifications
325
B.3 Parametric constraints
327
B.4 Activity diagrams
329
B.5 Requirement diagrams
330
Index 331
Dr Jon Holt is the founder director of Brass Bullet Ltd, a systems engineering training and consultancy company. He is a Fellow of both the IET and the BCS and is recognised as a thought leader in the world of systems modelling. He is also the author of several books and is an award-winning public speaker.



Simon Perry is a director of Brass Bullet Ltd. He has over 20 years experience working as a software engineer, systems architect and systems modeller in a wide range of business areas including defence, finance, building construction, nuclear installations, utilities and transport. He is a Member of the IET, the BCS and the IAP.
Lisainfo e-raamatute kohta Lisainfo e-raamatute kohta
Püsilink: https://www.kriso.ee/db/97808634197992e.html
Märksõnad: