Authors:
Brian Lings
1
and
Björn Lundell
2
Affiliations:
1
School of Engineering, Computer Science and Matehmatics, University of Exeter, United Kingdom
;
2
University of Skövde, Sweden
Keyword(s):
IS development method, Method use, CASE tools, Automated support for methods, Stakeholder triangle.
Related
Ontology
Subjects/Areas/Topics:
CASE Tools for System Development
;
Enterprise Information Systems
;
Information Engineering Methodologies
;
Information Systems Analysis and Specification
;
Methodologies, Processes and Platforms
;
Model-Driven Software Development
;
Modeling Formalisms, Languages and Notations
;
Requirements Analysis And Management
;
Software Engineering
;
Systems Engineering
Abstract:
Tool support for Information Systems development can be considered from many perspectives, and it is not surprising that different stakeholders perceive such tools very differently. This can contribute on one side to poor selection processes and ineffective deployment of CASE, and on another to inappropriate tool development. In this paper we consider the relationship between CASE tools and Information Systems development methods from three stakeholder perspectives: concept developer, Information Systems developer and product developer. These perspectives, and the tensions between them, are represented within a ‘stakeholder triangle’, which we use to consider how the concept of method-in-action affects and is affected by the concept of method-in-tool. We believe that the triangle helps when interpreting seemingly conflicting views about CASE adoption and development.