Maintenance cost of a software design: A value-based approach

A pair of press tools, such as punches, are mounted on a tool support for axial reciprocation between extended and retracted positions with respect to the support. The tool support may be defined by a press slide, bed or component part of a tooling package mountable thereon and is provided with a hydraulic fluid receiving cylinder for each of the tools. Each tool is interconnected with a piston received in the corresponding cylinder and the cylinders are in flow communication with one another. Accordingly, if one of the tools engages a workpiece before the other during operation of the press, the one tool is displaced in the direction of retraction causing the other tool to be displaced in the direction of extension until both tools engage the workpiece, thus to avoid eccentric loading of the press slide and frame. Both tools have a neutral position with respect to their extended and retracted positions and, upon movement of the press slide away from the work, a biasing arrangement returns the extended one of the tools to its neutral position and the displacement of the corresponding piston causes the retracted tool to be returned to its neutral position.

[1]  Mark Klein,et al.  Quantifying the costs and benefits of architectural decisions , 2001, Proceedings of the 23rd International Conference on Software Engineering. ICSE 2001.

[2]  J. Cleland-Huang,et al.  Financially informed requirements prioritization , 2005, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..

[3]  Giuliano Antoniol,et al.  A Function Point-Like Measure for Object-Oriented Software , 1999, Empirical Software Engineering.

[4]  Jane Cleland-Huang,et al.  A heterogeneous solution for improving the return on investment of requirements traceability , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[5]  Thomas M. Pigoski Practical Software Maintenance: Best Practices for Managing Your Software Investment , 1996 .

[6]  Barry W. Boehm,et al.  How Much Software Quality Investment Is Enough: A Value-Based Approach , 2006, IEEE Software.

[7]  Stefan Biffl,et al.  A case study on value-based requirements tracing , 2005, ESEC/FSE-13.

[8]  Lionel C. Briand,et al.  An assessment and comparison of common software cost estimation modeling techniques , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[9]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[10]  Barry W. Boehm,et al.  Value-Based Software Engineering: Overview and Agenda , 2006, Value-Based Software Engineering.

[11]  Keith H. Bennett,et al.  Software maintenance and evolution: a roadmap , 2000, ICSE '00.

[12]  Stefan Biffl,et al.  A value-based approach for understanding cost-benefit trade-offs during automated software traceability , 2005, TEFSE '05.

[13]  Hema Srikanth,et al.  On the Economics of Requirements-Based Test Case Prioritization , 2005 .

[14]  Javier Garzás,et al.  An ontology for microarchitectural design knowledge , 2005, IEEE Software.

[15]  Ellis Horowitz,et al.  Software Cost Estimation with COCOMO II , 2000 .

[16]  Javier Garzás,et al.  Analyzability and Changeability in Design Patterns , 2002 .