曝光臺 注意防騙 網曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費者

are not OO languages.
Problem:
While the analysis and OO design and
implementation phases were well specified
and successful in isolation, the transition
from structured analysis into an OO
design and implementation was difficult.
Also, the software tools used to support
the software development process were
becoming dated, requiring the engineers
to use dedicated workstations when the
rest of their work could be done on their
desktop PCs. A better development
process was required – one that would
allow a smooth transition from requirements
analysis into design and that could be
deployed on the desktop PCs.
Solution:
According to Shaun Cullimore, Smiths
Aerospace Software Technology Manager,
the process chosen needed to be capable
of supporting a wide range of software
developments for products in both the
defense and civil marketplaces. The software
in these products would also vary
in size, implementation language and
customer. To minimize risk selecting a
PC-based tool, the selection criteria
required that the vendor be able to provide
training and consultancy support.
Smiths selected Real-time Studio from
ARTiSAN, says Cullimore, because of the
company’s strong focus on real-time
embedded applications, their technical
expertise in the UK, and the price of the
product. The relative maturity of their tool
in a volatile market, together with the
strength of their consulting capability
(engineers with experience of real time
embedded system development), and
emphasis on process, were also key factors
in making ARTiSAN the preferred
partner for Smiths.
Because there was no opportunity to
free staff for extended tool and process
evaluation exercises, Smiths chose to use
Real-time Studio on a “live” project. And,
to minimize risk, Smiths incorporated a
training and consultancy package from
ARTiSAN.
“We needed to adapt ARTiSAN’s ‘outof-
the-box’ lifecycle so we could maintain
a separate ‘requirements view’ and ‘design/
implementation view’ without using two
models for every project,” comments
Cullimore. “Agreement with the customer
of exactly what constitutes the software
requirements baseline is a key milestone
in our programs. A process which distorts
that view through elaboration or pollutes
it with implementation detail, would not
be acceptable to us.We also wanted a
process that was independent of any tool,
though we would obviously be seeking
the best tool to support it.”
A single ARTiSAN model is now used
to accommodate both the requirements
view and the design and implementation
view. “This suits us better than maintaining
two separate models as it is so difficult to
maintain consistency,” says Cullimore. From
these discussions, Smiths has produced a
Code of Practice for OO Analysis and
Design that is used across all new projects.
Smiths uses industry standards whenever
they can, and benefits from ARTiSAN’s
active participation in the Object Management
Group (OMG) who manages UML.
ARTiSAN’s Real-time Studio supports
Unified Modeling Language (UML) but
also provides unique real-time extensions
that go beyond UML.
“Since the beginning, we have actually
implemented the new methodology and
tools on four major real-time projects and
many projects developing supporting test
equipment,” says Cullimore. Smiths continues
to utilize ARTiSAN training and
consultancy as engineers begin to use
the process on new projects. The tool and
process have been employed on projects
ranging from equipment to switch electrical
loads on military aircraft, to helicopter
display systems.
Benefits:
“As a result of adopting our new process
and the ARTiSAN tool, we now find it easier
to move software engineers between
projects. This is a major benefit given the
diversity of our projects,” Cullimore claims.
ARTiSAN continues to develop Real-time
Studio, and following their initial experience
with the tool, Smiths has indicated they
are keen to use some of the newer facilities
that it provides. For example, the
“Package-based Object Repository” of
Real-time Studio, enables a peerless combination
of upstream team collaboration
and downstream development stability.
Teams now have the flexibility to simultaneously
share the centralized project
repository as well as partition it for separate
　
中國航空網 www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：航空資料32(58)