Summary - Embedding requirements within the model driven architecture.

Scacchi (2002) proposes that “the death of the traditional system life cycle model may be at hand” (Scacchi 2002). This is due to the arrival of process modelling solutions that are better aligned to the current operating environment of software development. The MDA has evolved as a “consequence” of the UML and is purported to be the last abstraction to human-computer interaction (Génova et al. 2005). In comparison with the alternative approaches discussed in Section 2.3, the MDA appears to offer the most promise as a

framework to complete this human-computer interface whilst remaining broad enough to integrate with other approaches and continuing to be a popular focus in academia. The potential the MDA holds for the business

analyst means that “understanding MDA is going to be crucial for business analysts of the future” (Slack 2008). Therefore, this research gives focus to the MDA as such an interface.

From reviewing available literature, it has been found that the CIM is not central to most MDA implementations. MDA committed companies and products neglect the creation of the CIM and related transformations (Ambler 2007; Kabanda and Adigun 2006; Karow and Gehlert 2006; Phalp et al. 2007), thereby highlighting the insignificance associated with it. “Successful technologies are those that are in harmony with users’ needs” (Shneiderman 2002) and, in consideration, RE and the connection to the MDA appears to be vital for the future of both the MDA and BPM. Process orientation is not the same as building object oriented software systems. “Object orientation is about building and maintaining IT systems; BPM is about building and maintaining business processes, and putting those capabilities in the hands of ordinary business people who get work done through their work processes – not their “objects”” (Bushell 2005). The ideals of the RAD could be beneficial in application to the CIM since a suitable platform for the development of software systems that are tightly linked with the business process is provided. The RAD can be used to describe iterations, concurring role activity and evolving processes, all of which are difficult to describe using software modelling techniques. Although research is limited, it is suggested here that considerable

enhancement to the MDA could be made addressing concerns raised in Section 2.1 with the inclusion of RAD descriptions, allowing for “the opportunity to integrate humanistic and mechanistic processes” (Harrison-Broninski 2005c). Solutions may involve multiple language selection and therefore, some interoperable solution between modelling language and transformation technique is required for applicability to the MDA since “no single language can be adapted to all application domains”(Jouault and Kurtev 2006), supported by Rombach (1988). It is suggested that a solution will be achievable once a specification can be provided that is machine readable, as well as human understandable (Lautenbacher et al. 2007). Since any such method in determining a resultant system should carry the outright support of involved parties, the automation of transformations into design is likely to also be important for consideration.

Ultimately, the MDA lacks a formalised requirements model (Karow and Gehlert 2006) and there is a real danger in confusing business and software artefacts by “building a model of the real-world and then using it as a specification of the software system, producing a system that needlessly matches the structure of the real-world” (Génova et al. 2005), supported by Easterbrook (2003), Nuseibeh and Easterbrook (2000). This is evident in research that goes into extracting design models from CIM definitions, i.e. CIM-to-PIM transformations that do not account for specification and the system boundary. Focus therefore should be given to the MDA framework and how it might be extended to account for these concepts. This can be achieved by investigating the CIM in terms of how appropriate the phase is at delivering user requirements and available solutions in achieving a better integration of requirements within the MDA. It is thought that specification ought to be central to the MDA, and the information delivered in the CIM should be complete in terms of both business and software needs.

Chapter 3 Research Overview

In this chapter an overview of the research process is given and discussion relating to research paradigms is provided before a methodology is selected to define the direction of this research. Specific objectives identified to approach this research are highlighted in Section 3.4. Tasks relating to proposed objectives are then identified in turn and discussed in further detail with respect to the chosen methodology in view of answering the research question identified in Chapter 1.0, relating to aims 1 to 4.

Lubbe (2003) suggests that “an important step any researcher should take is establishing a framework in which to conduct the research” (Lubbe 2003) and, therefore, to achieve the research objectives it is important to first gain an understanding of the foundations of research. Figure 3.1.1 gives an overview of the research process used to realise the knowledge that the objectives seek to attain; the research process is detailed in the subsequent sections of this chapter.

figure 3.1.1,4overview of the research process (Source: adapted from Shelmerdine (2010)).

3.1 Ontology & Epistemology

Ontology is the metaphysical study of the nature of the reality in which things exist; that is, the study of being. It is important to understand the very foundation of a topic in order that a “psychological schizophrenia” be avoided (Hampton 2004). “Thinking is the epistemological path to conceptual

comprehension. Knowing is the metaphysical path to apprehension – to the acceptance of a concept as true or valid” (Cobern 1993). The suggestion therefore is to study the foundation of both what exists (the

metaphysical), and that which could exist (the epistemological). From reviewing literature in Chapter 2.0, it is clear that the MDA has been established from the domain of Software Engineering, within which philosophy might be contrary to what is required of the MDA in application to the business domain. Therefore, the study is focussed on accounting for this application. To achieve ontology, an understanding of the relationship between the philosophical nature of knowledge and the reality to which it is exposed is required (Shelmerdine 2010). Epistemology is the philosophical study of the nature of knowledge and the relationship between that knowledge and reality. Therefore, knowledge of the MDA and associated implementations form the foundation of this epistemological journey. The central focus is the application of this knowledge to the reality of the academic and business domain and therefore, a suitable research paradigm is required to investigate this relationship.

3.2 Research Paradigm

There is nothing so practical as a good theory (Gill and Johnson 1997).

Kolb, Rubin et al. (1979) provide a useful research framework in examining the relationship between theory and practice in the form of an experimental learning cycle (see figure 3.2.1).

figure 3.2.1,5experimental learning cycle (Source: adapted from Kolb et al. (1979)).

The left side of the diagram represents the deductive (positivist) research method, the right side the inductive (interpretivist) method. Deductive research is the art of developing theory prior to testing based on observing facts with the objective of making predictions. Inductive research is the polar opposite of that; thereby theory being the product of induction via the observation and reflection on experience. This is in turn demonstrated in the work of Gill and Johnson (1997) which is included in table 3.2.1 where it establishes how quantitative (positivist) methods are related to qualitative (interpretivist) methods.

Positivist Methods Interpretivist Methods

Deduction Induction

Explanation via analysis and covering-laws Explanation of subjective meaning and understanding Generation and use of quantitative data Generation and use of qualitative data

Use of controls to allow testing of hypotheses Research in everyday settings to allow access to, and minimise reactivity among research subjects

Highly structured Minimum structure

Laboratory experiments, quasi-experiments, surveys, action research, ethnography table 3.2.1,2comparison of positivist and interpretivist methods (Source: adapted from Gill and Johnson (1997)).

Braa and Vidgen (1999) provide a framework for integrating research perspectives in information systems research which extends the work of Gill and Johnson (1997) and Kolb et al. (1979) by integrating positivist with interpretivist methods, and adding a further dimension of interventionist (see figure 3.2.2).

figure 3.2.2,6framework for integrating research perspectives (Source: adapted from Braa and Vidgen (1999)).

Interventionism is concerned with gaining “learning and knowledge through making deliberate interventions in order to achieve some desirable change in the organisational setting” (Braa and Vidgen 1999). This forms the basis of action research where “researchers both observe and participate in the phenomena under study”

(Baskerville 1997). Action research started to gain prominence in information systems in the 1990s

(Baskerville 1999) and it is the central motivation in the case that the outcome of this research will enforce a fundamental change within the MDA community via an approach to which the practice of the MDA will be improved, adding intellectual, academic and practical value. In simplistic terms, action research is about

“learning by doing” (O'brien 2001). However, such fundamental change is unlikely to occur in the short term.

There is scarce availability of accurate facts; quantitative data is limited and a sufficient test arena to produce worthy output from deduction is unavailable. However, knowledge is available in the form of existing and potential MDA experiences and, therefore, an inductive methodology can be followed in order that theory might result from the study of such experiences. It was thought that considerable opportunity existed in that the MDA definition and technical representation in the software development domain could be compared and contrasted upon to discover the theoretical reasoning which is cause for concern in the application of MDA to business users in defining requirements and specification. Further to this, soft cases could be used to verify the application of this research and therefore, an interpretivist approach to research is to be followed. To achieve this, a suitable methodology is required and the next section of this chapter is directed at identifying and discussing the relative merits of several interpretivist methodologies to identify those offering the most potential in application to the subject matter.

3.3 Research Methodology

3.3.1 Phenomenology

Phenomenology is a philosophical method used in qualitative research to examine the experience of an individual in terms of phenomena; the presumption being that the subject has no preconception of the subject matter (Husserl 2001). “The purpose of the phenomenological approach is to illuminate the specific, to identify phenomena through how they are perceived by the actors in a situation” (Lester 1999). This method is usually formed of directed interviews with small groups of individuals with a view to gaining an overall appreciation for the individual experience and the dynamics within the group. However, Phenomenology does not permit “priori” coding in analysing central themes, requiring time to be expended on individual cases (King 2006) which could make this methodology difficult to employ in consideration of available resources.

3.3.2 Ethnography

Ethnography is an anthropological method that can be used to study groups of people and the interactivity between them, and to some degree overlaps with phenomenology (Lester 1999). There are four characteristics presented in the Manifesto for Ethnography that distinguish ethnography from other qualitative

methodologies. They are: “The recognition of the role of theory as a precursor, medium, and outcome of ethnographic study and writing… The centrality of “culture”… A critical focus in research and

writing…[and] An interest in cultural policy and cultural politics” (Willis and Trondman 2002). Typically, observations involve groups of individuals over an extended period of time with focus on cultural aspects and since there is no opportunity to observe a group of individuals involved within the MDA environment, this method is rejected as impractical in consideration of the scope of the research.

3.3.3 Grounded Theory

Grounded Theory was first described in 1967 in Glaser and Strauss (1967) as a sociological method whereby the behaviour of groups of people is systematically observed and the collected data is codified in order that theory is derived from such observation to explain phenomena. An example of how grounded theory can be utilised in information systems research is given in Shannak (2009). Focus groups could be used whereby a concept tool is produced to accommodate any enhancement to the MDA framework and be used to further verify results. However, as previously noted, this is impractical since there is no availability of a sufficient test environment from which individuals could be observed to gain results that would be useful in providing insight with relation to the research question.

3.3.4 Template Analysis

Template Analysis is a method described in King (2006) and is concerned with the codification and thematic analysis of data that can be used where there is the assumption that “there are always multiple interpretations to be made of any phenomenon” (King 2006). Codes (numbered data labels) represent themes that are derived from the analysis of text. Often organised hierarchically to describe relationships between themes, the emphasis of Template Analysis is on “flexible and pragmatic” coding (King 2006). Template Analysis differs from other methodologies such as Grounded Theory - which is typically realist and prescriptive, and

Phenomenology - which requires greater attention be placed on the individual (King 2006). Since this research is directed at resolving a problem between individuals, it could be appropriate to combine this technique with others, especially in consideration of resolving student feedback regarding the application of extending the MDA.

3.3.5 Surveying

Qualitative survey methods became popular in the 1980s (Marsland et al. 1998) and can be employed to broaden the scale of the target population with relation to research. It could be suggested that much failure is derived from models being presented to high-level managerial stakeholders, rather than lower tier technical representatives or system users. The project is based on an understanding of the stakeholder definition and how software developers can adapt to the paradigms of business. Qualitative surveys could be directed at a mixed sample of business users with the target sample population including members of the business community from both technical and non-technical backgrounds. As per recommendations (Deveaux et al.

2005), a randomised sample would be selected; this selection would then be stratified to increase the representation of the population (Saunders et al. 2003). A methodological framework for combining quantitative and qualitative survey methods is presented in Marsland et al. (1998), however, the extent to which results of qualitative and/or quantitative survey techniques could be useful in consideration of the available knowledge were deemed negligible because of the limitation of scope with regards to a sufficient test arena.

3.3.6 Interviewing

“Throughout the social sciences including language-based studies, interviews are widely used as data collection instruments” (Ikeda 2007). Processes could be modelled in different formats and presented to stakeholders or general users for analysis and data capture. Upon presentation, interviews could take place in a directed format with opportunity for the interviewee to make clear their opinions, along with their responses to pre-defined questions. Techniques relating to how to overcome issues of data quality, specifically in consideration of interviewer and interviewee bias are demonstrated in Saunders et al. (2003). However, as with previous methods described which employ the use of the interview as a research method, such as phenomenology and ethnography, a suitable environment to utilise the interview research method on a useful scale is unavailable.

3.3.7 Case Study

The case study method can be used to address the research question directly via one or more case studies relating to the subject matter and is used in information systems research for “exploratory investigations, both prospectively and retrospectively, that attempt to understand and explain phenomenon or construct theory”

(Perry et al. 2004). Cases can be described as hard, soft or action cases (Braa and Vidgen 1999). The case study approach can be used to gather “data with which to develop grounded theory” (Lubbe 2003) and can allow for multiple avenues of data collection with the central notion being to identify themes particular to the case in hand, or across multiple cases. However, it is argued that gathering multiple evidence is not

necessarily able to prove (or disprove) a theorem (Yin 1994). In consideration of the construction of case studies, focus can be given to areas of the research context; exploratory questions; validation; ethical issues;

data gathering and analysis; publishing; and reviewing (case replication) (Perry et al. 2004). “As a research strategy the case study research method is a technique for answering who, why and how questions” (Lubbe 2003). This is emphasised by Yin who writes that “case studies are the preferred method when (a) “how” or

“why” questions are being posed, (b) the investigator has little control over events, and (c) the focus is on contemporary phenomenon within a real-life context” (Yin 2008), which is particularly suited to the type of qualitative knowledge available with regards to this research. The objective here is to understand the

relationship between the business and software use of the MDA; to understand who the users of the MDA are, why it is being used and how. Since the problem is set in a real-life context, i.e. that of the MDA and involved organisations, little control over events is available. A good example of case study research in information systems is given in Card et al. (1986) where six characteristics of good design are studied (Card et al. 1986) against programming modules.

3.4 Knowledge

The problem highlighted in Chapter 2.0 from the analysis of the current state of the art seems to be about gaining an understanding of, and bridging the gap between, various stakeholders and software developers in the context of the MDA. Once a software system is presented to a user (as a prototype), a significant understanding of the system and an idea of the available potential is gained (Kavis 2008), enabling

development. Therefore, by illustrating the underlying strategies and goals in a manner to which they can be understood (such as a model), clear requirements might succinctly follow.

Several objectives are identified in this section directed at achieving the aims outlined in Section 1.2, within the context of the research question. The described problem is multi-faceted and therefore, the selection of research methodology reflects these objectives to best accommodate each. It is thought that, whilst any single research methodology might give invaluable insight to the academic and commercial application of the area under consideration, the results obtained would be difficult to verify without a degree of conjecture.

Therefore, from reviewing available research methods in the previous section, a mixed inductive approach, involving specifically a combination of theoretical, case and thematic analysis, is considered to be of benefit to this investigation and is outlined in the subsequent section of this chapter. The approach considers propositions to be directly verifiable by comparing and contrasting results obtained via multiple methodologies, allowing for findings to be triangulated in a complementary manner (Brannen 2005).

3.4.1 MDA Evaluation

The literature review, included in Chapter 2.0, was an ongoing process throughout the duration of this project, with a view to keeping up to date with current research and ensuring that developments within the context of this research are adequately addressed. “Requirements understanding problems inevitably lead to poor customer-supplier relationships, unnecessary re-works, and overruns in costs and/or time” (Elliott and Raynor-Smith 2000). Chapter 2.0 reveals that the MDA appears to neglect a RE perspective (Ambler 2007;

Kabanda and Adigun 2006; Karow and Gehlert 2006; Phalp et al. 2007), and is therefore failing to sufficiently bridge between business stakeholders and the software developers. This forms the basis of this research and the point from which the first two objectives are defined for investigation in achieving aim 1.

Aim 1: To examine the definition of the CIM within the MDA and consider the appropriation of it as an interface with the business user for defining requirements in MDA notations.

In Chapter 4.0, a complete and thorough analysis of the MDA will be conducted in the context of user requirements for assessing the adequacy of the CIM in catering for requirements and specification. The first objective is related to the proposition that RE and BPM are somewhat disconnected from the MDA and will

In document Embedding requirements within the model driven architecture. (Page 61-200)