CASE tools increase productivity in the development of software-based systems by performing analysis that cannot be done by humans, and by automating repetitive tasks. The potential of these tools has not been realized due to limited use by small pockets of engineers. The paper describes the results of a survey that explores the perceptions of the engineers that use CASE tools for the development of certified software for commercial air transport avionics. All the engineers cited improvements in software duality, but were split down the middle on the contribution of CASE tools to reduction in project cycle-time. Ease-of-use of the tool the most critical factor in the individual engineers choice to use a CASE tool. Differences between the format and style of documents and code generated by the CASE tool and the corporate format and style standards is the biggest hurdle to integrating CASE tools into corporate development processes.
[1]
David Harel,et al.
Statecharts: A Visual Formalism for Complex Systems
,
1987,
Sci. Comput. Program..
[2]
W. Wayt Gibbs,et al.
Software's Chronic Crisis
,
1994
.
[3]
David Lorge Parnas,et al.
Predicate Logic for Software Engineering
,
1993,
IEEE Trans. Software Eng..
[4]
Lance Sherry,et al.
A formalism for the specification of operationally embedded reactive systems [in aircraft guidance/navigation systems]
,
1995,
Proceedings of 14th Digital Avionics Systems Conference.
[5]
W. J. Kubitz,et al.
Biting the silver bullet: toward a brighter future for system development
,
1992
.
[6]
Lance Sherry,et al.
A Formalism for the Specification of Operationally Embedded Reactive Systems
,
1995
.