Is SysML this the holy grail of SE that I have been searching for???
GasGasGas
I'm totally new to SysML (and UML for that matter); I have read about
it (over the last month or so) and have spoken to people about it,
that is it. I work in a paraprofessional capacity in a large
organisation that utilises a document-centric engineering system that
has evolved over many years. We produce aeronautical designs/products
that are usually comprised of mechanical, electrical and software
elements, the design described by Word documents and drawings. I have
always thought that our system of engineering documentation (all
engineering designs captured in Word documents, printed out, written
on some more, signed numerous times etc) was a dinosaur that had well
and truly outlived its usefulness.
SysML looks like it could be the holy grail of Systems Engineering
that could augment/replace our document-centric engineering system
(SysML cannot restrict access, assign privileges to users etc). As I
understand it, SysML allows a proficient user to fully describe a
system with verifiable links back to requirements. There is not a
great deal of information available on SysML on the net at the moment
for the complete newby (I have ordered your book, the first in
Australia so I'm told!), so I am having trouble working out how SysML
might fit into and be used in my organisation.
This may be a silly question but for an organisation to use SysML must
all designers, reviewers etc - everyone that deals in some way with
the design - understand SysML to the n-th degree, or are only a small
number of SysML practitioners required? I'm guessing it's all or
nothing.
How much training (time wise) is required to progress from knowing
nothing of SysML/UML to becoming a proficient practitioner
(paraprofessional or engineer)? Once proficient, is design development
quicker with SysML than in a document-based system? Could proficient
practitioners potentially spend more time coming to terms with the
nuances of the language than actually designing?
How is the analysis of the design described in SysML? In our current
system, if I choose to use a particular component in a design I must
provide written analysis/evidence as to its suitability to a reviewer.
How would this be done in SysML?
What is SysML's target audience? Is it only for use by boffins with
oversized brains (present company excepted of course)? Or is it usable
by the lay-engineer?
So many questions, so little space! :-) Thanks for your time.
Cheers,
Franc
Tim Weilkiens
Franc,
Congratulation! You posted the first message in this group ;-)
> SysML cannot restrict access, assign privileges to users etc
That's correct. It's not part of a modeling language to provide such functionality, but part of the modeling language tool.
> This may be a silly question but for an organisation to use SysML must
> all designers, reviewers etc - everyone that deals in some way with
> the design - understand SysML to the n-th degree, or are only a small
> number of SysML practitioners required? I'm guessing it's all or
> nothing.
Yes, it's all or nothing. It depends on the application of area.
SysML is a language. You can use SysML to sketch the structure and behavior of your system at a whiteboard. You can also use SysML to create a very detailed model that is partly or completely executable to simulate and analyse your system.
As any natural language SysML is a language that is easier to read than to write.
> How much training (time wise) is required to progress from knowing
> nothing of SysML/UML to becoming a proficient practitioner
> (paraprofessional or engineer)?
Compare it with the learning of a foreign natural language. After a 5 day course you are able to use the language. But not perfect and depending on the application of area not proficient. You need practical experience for that.
> Once proficient,
> is design development quicker with SysML than in a document-based
> system?
Yes, if your development environment works well. SysML is only a piece of it.
Others are for example the modeling tool. A tool that doesn't fit into your environment could destroy many advantages of the modeling language.
> Could proficient practitioners
> potentially spend more time coming to terms with the nuances of the
> language than actually designing?
That's a risk of using a modeling language.
> How is the analysis of the design described in SysML? In our current
> system, if I choose to use a particular component in a design I must
> provide written analysis/evidence as to its suitability to a reviewer.
> How would this be done in SysML?
I'm not sure if I understand your question correctly. Could you explain it in other words?
> What is SysML's target audience? Is it only for use by boffins with
> oversized brains (present company excepted of course)? Or is it usable
> by the lay-engineer?
Again a comparison with natural languages:
What is the target audience of English? Is it only for use by Shakespeares? Or is it usable by readers of the yellow press?
It is for both.
> So many questions, so little space! :-) Thanks for your time.
I hope I could answer some of your questions. Please contact me again if you have more.
Greetings,
Tim
-----------------------------------------------------------------
Tim Weilkiens
Head of Systems Engineering
OMG Representative, INCOSE member
oose Innovative Informatik GmbH
Tower Falkenried-Piazza, Straßenbahnring 7, D-20251 Hamburg, Germany HRB 66648 Amtsgericht Hamburg, USt-Id DE191433946 CEO Bernd Schröder-Oestereich, Christian Weiss
Phone: +49 (40) 41 42 50-0, Fax: +49 (40) 41 42 50-50
Internet: www.oose.de, E-Mail: off...@oose.de