By Topic

Using object oriented analysis and design in a non-object oriented environment experience report

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
K. Williams ; Rockwell Software Inc., Highland Heights, OH, USA

The paper is an experience report about using James Rumbaugh's Object Modeling Technique (OMT) in Allen-Bradley's 6200 Series Programming Software for Programmable Controllers (6200). It explores three stages of subsystem development: analysis, design, and implementation. For each stage, a brief description of the Object Modeling Technique is given. Also included are solutions to obstacles that were overcome while working on the project. Metrics were kept during the development and independent test of the two object oriented subsystems that were introduced into 6200. These metrics compare the object oriented (OO) subsystems to structured analysis/structured design (SA/SD) subsystems of roughly the same complexity and in the same area of the product as the object oriented subsystem. The metrics presented are: number of function points, length of time spent in each development stage, number of lines of code and number of functions for the subsystem, number of defects found by an independent test group (categorized by development stage), and length of time required to fix the defects

Published in:

Software Maintenance, 1995. Proceedings., International Conference on

Date of Conference:

17-20 Oct 1995