0
Technology Reviews

Applications of Software Engineering to Manufacturing Process Planning

[+] Author and Article Information
V. Sundararajan

Department of Mechanical Engineering, University of California, Riverside, CA 92521

Paul K. Wright

Department of Mechanical Engineering, University of California, Berkeley, CA 94720

J. Comput. Inf. Sci. Eng 8(3), 034001 (Aug 21, 2008) (6 pages) doi:10.1115/1.2960488 History: Received May 09, 2007; Revised June 10, 2008; Published August 21, 2008

Agile methods of software development promote the use of flexible architectures that can be rapidly refactored and rebuilt as necessary for the project. In the mechanical engineering domain, software tends to be very complex and requires the integration of several modules that result from the efforts of large numbers of programmers over several years. Such software needs to be extensible, modular, and adaptable so that a variety of algorithms can be quickly tested and deployed. This paper presents an application of the unified process (UP) to the development of a research process planning system called CyberCut. UP is used to (1) analyze and critique early versions of CyberCut and (2) to guide current and future developments of the CyberCut system. CyberCut is an integrated process planning system that converts user designs to instructions for a computer numerical control (CNC) milling machine. The conversion process involves algorithms to perform tasks such as feature extraction, fixture planning, tool selection, and tool-path planning. The UP-driven approach to the development of CyberCut involves two phases. The inception phase outlines a clear but incomplete description of the user needs. The elaboration phase involves iterative design, development, and testing using short cycles. The software makes substantial use of design patterns to promote clean and well-defined separation between and within components to enable independent development and testing. The overall development of the software tool took about two months with five programmers. It was later possible to easily integrate or substitute new algorithms into the system so that programming resources were more productively used to develop new algorithms. The experience with UP shows that methodologies such as UP are important for engineering software development where research goals, technology, algorithms, and implementations show dramatic and frequent changes.

FIGURES IN THIS ARTICLE
<>
Copyright © 2008 by American Society of Mechanical Engineers
Your Session has timed out. Please sign back in to continue.

References

Figures

Grahic Jump Location
Figure 1

Preliminary domain model with classes

Grahic Jump Location
Figure 2

Revised domain level design

Grahic Jump Location
Figure 3

Sequence diagram

Grahic Jump Location
Figure 4

Class diagram for microplanner

Grahic Jump Location
Figure 5

Sequence diagram for microplanner

Grahic Jump Location
Figure 6

Visitor pattern for traversal of feature graph

Tables

Errata

Discussions

Some tools below are only available to our subscribers or users with an online account.

Related Content

Customize your page view by dragging and repositioning the boxes below.

Related Journal Articles
Related eBook Content
Topic Collections

Sorry! You do not have access to this content. For assistance or to subscribe, please contact us:

  • TELEPHONE: 1-800-843-2763 (Toll-free in the USA)
  • EMAIL: asmedigitalcollection@asme.org
Sign In