Shivanshu K. Singh
ABSTRACT
This paper aims at modeling a system that has to perform maintenance, by employing a Corrective Action and come up with a stable pattern, which can form a part of such a system, focusing at applying corrective action in a holistic way, rather than tying it on only one application specific context, which might cause potential impedance mismatch between process and workflows at a later stage. This ensures high reusability, ensuring that a design once created can be used to model any application, in any domain, thus making the task of designing more efficient, and the modeled system, largely domain independent. The goal of this paper is to design a Stable Pattern for Corrective Action and to model the system on the basis on an Enduring Business Theme (EBT). Here, the ultimate goal or the EBT is Maintenance and AnyCorrective action is what acts as a workhorse to achieve the goal of maintenance. In this paper, we have first designed a model, which defines the relationship of the Enduring Business Theme to Business Objects. We have then gone ahead with modeling an application scenario, which portrays the reusability of the developed stable pattern. A comparison of the Traditional Models and the Stable Model has also been included to describe how the latter overcomes to drawbacks of the former. Different models, such as, use cases, CRC cards, class diagrams and sequence diagrams have been used to give a better insight into the pattern and possible applications of it.
- "Corrective Action", n.d. {Online}. Available: Onelook.com http://onelook.com/?w=corrective+action&ls=a {Accessed May 26, 2010}.Google Scholar
- M. E. Fayad, and A. Altman, "Thinking objectively: an introduction to software stability", Communications of the ACM, vol. 44, no. 9, pp. 95, Sep. 2001. Google ScholarDigital Library
- H. Hamza, A. Mahdy, M. E. Fayad and M. Cline, "Extracting Domain-Specific and Domain-Neutral Patterns Using Software Stability Concepts", Lecture Notes in Computer Science, vol. 2817. Berlin / Heidelberg: Springer, 2003, pp. 191--201.Google Scholar
- "Correction", n.d. {Online}. Available: MSN Encarta, http://encarta.msn.com/encnet/features/dictionary/DictionaryResults.aspx?refid=1861600494 {Accessed May 26, 2010}.Google Scholar
- "Correction", n.d. {Online}. Available: YourDictionary.com: http://www.yourdictionary.com/correction {Accessed May 26, 2010}.Google Scholar
- M. E. Fayad, H. A. Sánchez and H. S. Hamza. A Pattern Language for CRC Cards. Proceedings of Pattern Language of Programs' 2004 (PLOP'04), Monticello-Illinois, USA, Sept. 2004.Google Scholar
- M. E. Fayad, Haitham Hamza, and Huáscar A. Sánchez "A Pattern for an Effective Class Responsibility Collaborator (CRC) Cards". Proceedings of the 2003 IEEE International Conference on Information Reuse and Integration (IRI'03), Las Vegas, Nevada, pp. 584--587, October 2003.Google Scholar
- "Addressing Conduct & Performance Issues", Administrative Guide Memo 22.15, Stanford University, September 1, 2010 {Online}, Available: http://adminguide.stanford.edu/22_15.pdf {Accessed Oct 15, 2010}.Google Scholar
Index Terms
- The AnyCorrectiveAction stable design pattern
Recommendations
A Controlled Experiment in Maintenance Comparing Design Patterns to Simpler Solutions
Software design patterns package proven solutions to recurring design problems in a form that simplifies reuse. We are seeking empirical evidence whether using design patterns is beneficial. In particular, one may prefer using a design pattern even if ...
A controlled experiment for assessing the contribution of design pattern documentation on software maintenance
ESEM '10: Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and MeasurementIn this paper we present the preliminary results of a controlled experiment to assess the contribution provided by the design patterns on the maintenance of source code. In particular, the study aimed at assessing the effort and the efficiency to ...
Assessing conformance of pattern-based design in UML
ACM-SE 46: Proceedings of the 46th Annual Southeast Regional Conference on XXA design pattern is a generic solution to a recurring problem in a given design context [1]. The use of design patterns has many known benefits to the design process. However, since it is the task of a human to instantiate patterns within designs, it is ...
Comments