Original Title: Towards a method for designing methods

Towards a method for designing methods

Type:
  • Master Thesis Business Information Systems
Status:
offered
Tutor:
Bei Interesse melden Sie sich unter: sekretariat.umo (at) uni-due.de

Abstract

In practice and academia a wide variety of methods for different classes of typical business informatics problems exists, developed by consultancy agencies, standardization bodies, software companies, universities, and public-private partnerships. Such methods include agile software development methods (Qumer, 2008), or methods for enterprise architecture design and management (Winter et al, 2010). The wide variety of methods is not surprising, as in addressing a particular problem (e.g., developing a new piece of software) the adoption of an appropriate method allows one to, roughly speaking, capitalize on codified experiences with similar problems encountered in the past. Thus, one does not have to start from scratch.  Yet, to be effective the method often needs to be adapted to the context of use (Henderson-Sellers et al (2011)). Here, a major challenge is that there is no uniform view of what are the constituents of a method. For one, whereas agile software development methods are characterized by adherence to a set of principles (from the agile manifesto (Fowler et al, 2001)), enterprise architecture methods typically aim at offering a set of different perspectives (sometimes also called layers, or dimensions (cf. Winter et al, 2006)), with concepts that are relevant for describing each perspective. This hints at what actually characterizes a method in practice can be quite diverse, in terms of adhering to a common way of thinking, providing a process,  a process and a modeling language, or all of the above complemented with heuristics and guidelines. In the end, this lack of a uniform method conception inhibits the systematic adaptation of methods to a given enterprise’s context of use.

The aim of this master’s thesis is to construct a method for constructing methods - i.e., a meta-method. This meta-method shall at the very least consist of a meta-model which describes the core elements of a method and a process, and corresponding guidelines, for instantiating the method, so that the meta-method at hand can be used to create or adapt a method to the situation at hand. To showcase the meta-methods fitness for use, you use it for the construction of a method for a domain/context of choice.

Einstiegsliteratur

Strecker, Stefan, David Heise, and Ulrich Frank. "RiskM: A multi-perspective modeling method for IT risk assessment." Information Systems Frontiers 13.4 (2011): 595-611.

Henderson-Sellers, Brian, and Jolita Ralyté. "Situational method engineering: state-of-the-art review." Journal of Universal Computer Science (2010).

Qumer, Asif, and Brian Henderson-Sellers. "An evaluation of the degree of agility in six agile methods and its applicability for method engineering." Information and software technology 50.4 (2008): 280-295.

Winter, Katharina, et al. "Investigating the State-of-the-Art in Enterprise Architecture Management Methods in literature and Practice." MCIS (2010).

Winter, Robert, and Ronny Fischer. "Essential layers, artifacts, and dependencies of enterprise architecture." Enterprise Distributed Object Computing Conference Workshops, 2006. EDOCW'06. 10th IEEE International. IEEE, 2006.

Fowler, Martin, and Jim Highsmith. "The agile manifesto." Software Development 9.8 (2001): 28-35.