From: Simon Hutton (sjh@threesl.com)
Date: Thu Dec 11 2003 - 04:51:19 EST
This is a multi-part message in MIME format.
------=_NextPart_000_0120_01C3BF46.3782A2B0 Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Lionel,
Many thanks for raising this complex and (for the tool vendor community, = emotive) topic, and for the link to the fascinating paper. I would = agree that the process must be the priority, and that tools are there to = support those implementing the process, and, I would suggest, to provide = some coherence and traceability between the data used for these process = activities. In an ideal world we would have one data repository and one = tool interface, ensuring common data and an interface all can use (or, = at least, that's our philosophy with Cradle!). The use of two or more = tools should only be encouraged if one of the selected tools (or, = possibly, mandated or legacy tools and data) do not provide the = necessary coverage or capability. The paper you quote concludes that = "the use of more than one tool can be a good answer to a wide range of = problems not solved by the use of only one tool for all the process = steps". If one tool can solve all the porcess steps, why would 2 be =
preferable, with all the inherent integration problems, usability issues = and data transfers to ensure some concurrency. In the past, I have used = DOORS as a requirements manager, and we managed to integrate with a risk =management tool to give wider coverage within the project management = process, but there was always a need to compromise. I am pleased that = telelogic have finally integrated a modelling tool within DOORS, albeit = limited to UML, but at least they finally acknowledge the significance = of providing functionality to support the whole life cycle rather than = just requirements management.
The need to "deploy a 2 tools based approach" is simply a reflection of = the shortcomings of one of the tools to cover adequately the systems = engineering life cycle. It's a little like rearranging the deck chairs = on the Titanic. The results may be neat and tidy, but the ship still = sinks. But use the deck chairs to build a raft and something useful may = come out of it!=20
Regards,
Simon.
Hello,
Consultants from CS, the major european consulting group, concluded = their presentation in the Convergence2003 (Paris, Dec. 1-3), by :
"For requirements management, the process is the priority. Tools are = only there to support this process as effectively as possible. Today, we = consider that this 2 tools based approach is the most effective one for = large groups, from both technical and cost points of view. It can be = applied to software and hardware designs. It should also be the unique = solution to support the deployment of recent demanding standards as = DO254 for Hardware in Aeronautics, and is a good way to avoid redundancy = in some document-oriented projects.
CS used DOORS and REQTIFY individually in various contexts, and is now = deploying a 2 tools based approach described above. We consider there is = a higher value in a collaboration rather than in the selection of only = one tool after a competition."
This paper will also be presented to the Embedded Real-Time Show (ERTS = 2004) in Toulouse.
As this approach may interest you, we decided to provide you with a = direct access to this analysis :
Read more about the 2-tools-based approach deployed by CS...
Please feel free to contact reqtify@tni-valiosys.com for additional = information, or fill the form to get a demo CD.
Best regards,
Lionel Burgaud
Reqtify Product Manager
TNI-Valiosys
------=_NextPart_000_0120_01C3BF46.3782A2B0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1276" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Lionel,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Many thanks for raising this complex =
and (for the=20
tool vendor community, emotive) topic, and for the link to the =
fascinating=20
paper. I would agree that the process must be the priority, and =
that tools=20
are there to support those implementing the process, and, I would =
suggest, to=20
provide some coherence and traceability between the data used for =
these=20
process activities. In an ideal world we would have one data =
repository=20
and one tool interface, ensuring common data and an interface all can =
use (or,=20
at least, that's our philosophy with Cradle!). The use of two =
or more=20
tools should only be encouraged if one of the selected tools (or,=20
possibly, mandated or legacy tools and data) do not provide the =
necessary=20
coverage or capability. The paper you quote concludes that "the =
use of=20
more than one tool can be<FONT face=3DTimesNewRomanPSMT size=3D2> a good =
answer to a=20
wide range of problems <STRONG>not solved by the use of only one tool =
for all=20
the process steps</STRONG>". If one tool can solve all the porcess =
steps,=20
why would 2 be preferable, with all the inherent integration problems, =
usability=20
issues and data transfers to ensure some concurrency. In =
the=20
past, I have used </FONT>DOORS as a requirements manager, and we =
managed to=20
integrate with a risk management tool to give wider coverage within the =
project=20
management process, but there was always a need to =
compromise. I am=20
pleased that telelogic have finally integrated a modelling tool within =
DOORS,=20
albeit limited to UML, but at least they finally acknowledge the=20
significance of providing functionality to support the whole life cycle =
rather=20
than just requirements management.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The need to "deploy a 2 tools based =
approach" is=20
simply a reflection of the shortcomings of one of the tools =
to cover=20
adequately the systems engineering life cycle. It's a little =
like=20
rearranging the deck chairs on the Titanic. The results may be =
neat and=20
tidy, but the ship still sinks. But use the deck chairs to build a =
raft=20
and something useful may come out of it! </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Simon.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial =
size=3D2>_________________________________<BR>Simon Hutton=20BSc MSc<BR>Principal Consultant<BR>Structured Software Systems = Ltd<BR>Telephone:=20
_________________________________</FONT></DIV>
<DIV><BR></DIV> <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT> </DIV> <DIV></DIV> <DIV><FONT face=3DArial size=3D2><SPAN=20class=3D026280914-06102003>Hello,</SPAN></FONT></DIV> <DIV><FONT face=3DArial size=3D2><SPAN=20 class=3D026280914-06102003></SPAN></FONT> </DIV> <DIV><FONT face=3DArial size=3D2><SPAN = class=3D026280914-06102003>Consultants from=20 CS, the major european consulting group, concluded their = presentation in=20
deployment of recent demanding standards as DO254 for Hardware in =
Aeronautics,=20
and is a<SPAN class=3D026280914-06102003> </SPAN>good way to avoid =
redundancy in=20
some document-oriented projects.</FONT></FONT></EM></DIV>
<DIV><EM><FONT face=3DArial size=3D2></FONT></EM> </DIV>
<DIV></FONT><EM><FONT face=3DArial><FONT size=3D2>CS used<SPAN=20
class=3D026280914-06102003> </SPAN>DOORS</FONT><FONT size=3D1> =
</FONT><FONT=20
size=3D2>and REQTIFY</FONT><FONT size=3D1> </FONT><FONT =
size=3D2>individually in=20
various contexts, and is now deploying a 2 tools based<SPAN=20
class=3D026280914-06102003> </SPAN>approach described above. We =
consider there=20
is a higher value in a collaboration rather than in the selection of =
only<SPAN=20
class=3D026280914-06102003> </SPAN>one tool after a competition.<SPAN=20
class=3D026280914-06102003>"</SPAN></FONT></FONT></EM></DIV>
<DIV><SPAN class=3D026280914-06102003><FONT face=3DArial=20
size=3D2></FONT></SPAN><FONT face=3DTimesNewRomanPSMT><FONT =
face=3DArial=20
size=3D2></FONT></FONT> </DIV>
<DIV><FONT face=3DTimesNewRomanPSMT><SPAN =
class=3D026280914-06102003><FONT=20
face=3DArial size=3D2>This paper will also be presented to the =
Embedded Real-Time=20
Show (ERTS 2004) in Toulouse.</FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DTimesNewRomanPSMT><SPAN =
class=3D026280914-06102003><FONT=20
face=3DArial size=3D2></FONT></SPAN></FONT> </DIV>
<DIV><SPAN class=3D026280914-06102003><FONT face=3DArial size=3D2>As =
this approach=20
may interest you, we decided to provide you <SPAN=20
class=3D266202112-10122003>with </SPAN>a direct access to this =
analysis=20
:</FONT></SPAN></DIV>
<DIV><FONT face=3DTimesNewRomanPSMT><SPAN =
class=3D026280914-06102003><FONT=20
face=3DArial size=3D2></FONT></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D026280914-06102003></SPAN></FONT> </DIV>
<DIV><FONT face=3DTimesNewRomanPSMT><SPAN =
class=3D026280914-06102003><FONT=20
face=3DArial size=3D2><A=20
=
href=3D"http://www.tni-valiosys.com/documents/reqtify/Convergence2003_CSp=
aper.pdf"><STRONG>Read=20
more about the 2-tools-based approach deployed by=20
CS...</STRONG></A></FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D026280914-06102003></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D026280914-06102003></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D026280914-06102003>Please feel free=20
to contact <A=20
href=3D"mailto:reqtify@tni-valiosys.com">reqtify@tni-valiosys.com</A> =
for=20
additional information, or <A=20
=
href=3D"http://www.tni-valiosys.com/?p=3Dhome&s=3Ddownload2&a=3Dr=
3">fill the=20
form to get a demo CD</A>.</SPAN></FONT></DIV>
<DIV><FONT face=3DTimesNewRomanPSMT><SPAN =
class=3D026280914-06102003><FONT=20
face=3DArial size=3D2></FONT></SPAN></FONT> </DIV>
<DIV><FONT face=3DTimesNewRomanPSMT><SPAN =
class=3D026280914-06102003><FONT=20
face=3DArial size=3D2></FONT></SPAN></FONT> </DIV>
<DIV><FONT face=3DTimesNewRomanPSMT><SPAN =
class=3D026280914-06102003><FONT=20
face=3DArial size=3D2>Best regards,</FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DTimesNewRomanPSMT><SPAN =
class=3D026280914-06102003><FONT=20
face=3DArial size=3D2></FONT></SPAN></FONT> </DIV>
<DIV><FONT face=3DTimesNewRomanPSMT><SPAN =
class=3D026280914-06102003><FONT=20
face=3DArial size=3D2>Lionel Burgaud</FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DTimesNewRomanPSMT><SPAN =
class=3D026280914-06102003><FONT=20
face=3DArial size=3D2>Reqtify Product =
Manager</FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DTimesNewRomanPSMT><SPAN =
class=3D026280914-06102003><FONT=20
face=3DArial size=3D2>TNI-Valiosys</FONT></SPAN></FONT><FONT=20
face=3DTimesNewRomanPSMT></DIV></BLOCKQUOTE></FONT></BODY></HTML>
------=_NextPart_000_0120_01C3BF46.3782A2B0--
This archive was generated by hypermail 2.1.6 : Tue Dec 16 2003 - 12:20:51 EST