Patterns of Situational Method Engineering

  • Mohsen Asadi
  • Raman Ramsin

Summary

Situational Method Engineering (SME) addresses the need for custom-built software development methodologies that are tailored to fit specific project situations. A process pattern is a description of a recurring development process fragment that can be used as a generic model or a building block for engineering development processes. Software development process patterns are extensively used in SME, mainly as process components assembled to form bespoke methodologies; however, the SME field itself has not been scrutinized as to the methodology development process fragments frequently encountered. Situational method engineering knowledge captured in the form of SME process patterns is not only useful for building and improving SME processes, but can also facilitate knowledge transfer among method engineers. We propose a set of SME process patterns obtained through studying existing method engineering approaches. The set of patterns is organized into a generic pattern-based framework for SME. The framework can be used for developing SME processes according to the specific requirements of method engineering projects; the resulting SME processes can then be enacted to yield custom-built, project-specific methodologies.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Ramsin, R., Paige, R.F.: Process-Centered Review of Object-Oriented Software Development Methodologies. ACM Computing Surveys 40(1), 1–89 (2008)CrossRefGoogle Scholar
  2. 2.
    Ralyté, J., Deneckére, R., Rolland, C.: Towards a generic model for situational method engineering. In: Eder, J., Missikoff, M. (eds.) CAiSE 2003. LNCS, vol. 2681, pp. 95–110. Springer, Heidelberg (2003)CrossRefGoogle Scholar
  3. 3.
    Ramsin, R.: The Engineering of an Object-Oriented Software Engineering Methodology. Ph.D. Thesis, University of York, York, UK (2006), http://www.cs.york.ac.uk/ftpdir/reports/YCST-2006-12.pdf
  4. 4.
    Ralyte, J., Rolland, C., Ayed, M.B.: An Approach for Evolution Driven Method Engineering. In: Krogstie, J., Halpin, T., Siau, K. (eds.) Information Modeling Methods and Methodologies. Idea Group Inc, USA (2003)Google Scholar
  5. 5.
    Karlsson, F., Gerfalk, P.J.: Method configuration: adapting to situational characteristics while creating reusable assets. Information and Software Technology 46(9), 619–633 (2004)CrossRefGoogle Scholar
  6. 6.
    Ralyte, J., Rolland, C.: An assembly process model for method engineering. In: Dittrich, K.R., Geppert, A., Norrie, M.C. (eds.) CAiSE 2001. LNCS, vol. 2068, pp. 267–283. Springer, Heidelberg (2001)CrossRefGoogle Scholar
  7. 7.
    Paige, R.F., Brook, P.J.: Formal Agile Method Engineering. In: Romijn, J.M.T., Smith, G.P., van de Pol, J. (eds.) IFM 2005. LNCS, vol. 3771, pp. 109–128. Springer, Heidelberg (2005)CrossRefGoogle Scholar
  8. 8.
    Ambler., S.W.: Process Patterns: Building Large-Scale Systems Using Object Technology. Cambridge University Press, Cambridge (1998)Google Scholar
  9. 9.
    Gnatz, M., Marschall, F., Popp, G., Rausch, A., Schwerin, W.: Modular Process Patterns supporting an Evolutionary Software Development Process. In: Bomarius, F., Komi-Sirviö, S. (eds.) PROFES 2001. LNCS, vol. 2188, p. 326. Springer, Heidelberg (2001)CrossRefGoogle Scholar
  10. 10.
    Tasharofi, S., Ramsin, R.: Process Patterns for Agile Methodologies. In: Advanced Programming Environments. IFIP, vol. 244. Springer, Heidelberg (2007)CrossRefGoogle Scholar
  11. 11.
    Prakash, N., Bhatia., M.S.P.: Generic models for engineering methods of diverse domains. In: Pidduck, A.B., Mylopoulos, J., Woo, C.C., Ozsu, M.T. (eds.) CAiSE 2002. LNCS, vol. 2348, pp. 612–625. Springer, Heidelberg (2002)CrossRefGoogle Scholar
  12. 12.
    Brinkkemper, S.: Formalisation of information systems modeling. Ph.D. thesis, University of Nijmegen. Thesis Publishers, Amsterdam (1990)Google Scholar
  13. 13.
    Osterweil., L.J.: Software processes are software too. In: 9th international Conference on Software Engineering, pp. 2–13. IEEE Computer Society Press, Los Alamitos (1987)Google Scholar
  14. 14.
    Coulin, C., Zowghi, D., Sahraoui, A.-E.-K.: A Lightweight Workshop- Centric Situational Approach for the Early Stages of Requirements Elicitation in Software Systems Developme. In: Proceedings of the International Workshop on Situational Requirements Engineering Processes (SREP 2005), France (2005)Google Scholar
  15. 15.
    Ralyte, J.: Requirements definition for the situational method engineering. In: Proceedings of the IFIP WG8.1 working conference on engineering information systems in the internet context (EISIC 2002), pp. 127–152 (2002)Google Scholar
  16. 16.
    Zhu, L., Staples, M.: Situational Method Quality. In: IFIP WG8.1 Working Conference on Situational Method Engineering: Fundamentals and Experiences (ME 2007) LNCS, vol. 244, pp. 193–206. Springer, Heidelberg (2007)CrossRefGoogle Scholar
  17. 17.
    Esfahani, N.: Introducing a set of process patterns for real-time software, MSc Thesis (in Persian), Department of Computer Engineering, Sharif University of Technology, Tehran, Iran (2008)Google Scholar
  18. 18.
    Cuccuru, A., De Simone, R., Saunier, T., Siegel, G., Sorel, Y.: P2I: An Innovative MDA Methodology for Embedded Real-Time System. In: Proceedings of the 8th Euromicro Conference on Digital System Design, pp. 26–33 (2005)Google Scholar
  19. 19.
    Firesmith, D., Henderson-Sellers, B.: The OPEN Process Framework: An Introduction. Addison-Wesley, Reading (2001)Google Scholar
  20. 20.
    Object Management Group, Systems and Software Process Engineering Metamodel v2.0 (SPEM), OMG (2007)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2009

Authors and Affiliations

  • Mohsen Asadi
    • 1
  • Raman Ramsin
    • 1
  1. 1.Department of Computer EngineeringSharif University of TechnologyTehranIran

Personalised recommendations