Application prototyping: a requirements definition strategy for the 80s
Application prototyping: a requirements definition strategy for the 80s
Designing for usability: key principles and what designers think
Communications of the ACM
Rapid application development
Methodology EngineeringR: a proposal for situation-specific methodology construction
Challenges and strategies for research in systems development
PD and joint application design: a transatlantic comparison
Communications of the ACM - Special issue Participatory Design
Experiences using cooperative interactive storyboard prototyping
Communications of the ACM - Special issue Participatory Design
Inside a software design team: knowledge acquisition, sharing, and integration
Communications of the ACM
Communications of the ACM
Making use: a design representation
Communications of the ACM
Characterizing IS development projects
Proceedings of the IFIP TC8, WG8.1/8.2 working conference on method engineering on Method engineering : principles of method construction and tool support: principles of method construction and tool support
A proposal for context-specific method engineering
Proceedings of the IFIP TC8, WG8.1/8.2 working conference on method engineering on Method engineering : principles of method construction and tool support: principles of method construction and tool support
Diversity in information systems action research methods
European Journal of Information Systems
A set of principles for conducting and evaluating interpretive field studies in information systems
MIS Quarterly - Special issue on intensive research in information systems
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Configurable development processes
Communications of the ACM - Robots: intelligence, versatility, adaptivity
User-Centered Design: An Integrated Approach with Cdrom
User-Centered Design: An Integrated Approach with Cdrom
Prototyping for usability of new technology
International Journal of Human-Computer Studies
Requirements acquisition for rapid applications development
Information and Management
Process Metamodelling and Process Construction: Examples Using the OPEN Process Framework (OPF)
Annals of Software Engineering
Choosing Between Competing Design Ideals in Information Systems Development
Information Systems Frontiers
Selecting a Project's Methodology
IEEE Software
Software development method tailoring at Motorola
Communications of the ACM - Digital rights management
Specifying the Reuse Context of Scenario Method Chunks
CAiSE '98 Proceedings of the 10th International Conference on Advanced Information Systems Engineering
Joint Elicitation of Problems: Important Aspects of Change Analysis
Proceedings of the IFIP WG8.2 Working Group on Information Systems Development: Human, Social, and Organizational Aspects: Human, Organizational, and Social Dimensions of Information Systems Development
Reusing Scenario Based Approaches in Requirement Engineering Methods: CREWS Method Base
DEXA '99 Proceedings of the 10th International Workshop on Database & Expert Systems Applications
Goal-Based Requirements Analysis
ICRE '96 Proceedings of the 2nd International Conference on Requirements Engineering (ICRE '96)
Goal-Oriented Requirements Engineering: A Guided Tour
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Generalizing Generalizability in Information Systems Research
Information Systems Research
Eliciting gaps in requirements change
Requirements Engineering
Situational method engineering: combining assembly-based and roadmap-driven approaches
Requirements Engineering
European Journal of Information Systems - Special issue: Action in language, organisations and information systems
User Needs Analysis and requirements engineering: Theory and practice
Interacting with Computers
Practice-driven approach for creating project-specific software development methods
Information and Software Technology
Requirements change: Fears dictate the must haves; desires the won't haves
Journal of Systems and Software
Information and Software Technology
Comparison of Method Chunks and Method Fragments for Situational Method Engineering
ASWEC '08 Proceedings of the 19th Australian Conference on Software Engineering
Requirements engineering: from craft to discipline
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
Method engineering: towards methods as services
Software Process: Improvement and Practice - Examining Process Design and Change
Situation Vs. Context: Considerations on the Level of Detail in Modelling Method Adaptation
HICSS '10 Proceedings of the 2010 43rd Hawaii International Conference on System Sciences
A tool for IT process construction
Information and Software Technology
Prototyping: the new paradigm for systems development
MIS Quarterly
Hi-index | 0.00 |
Context: Method engineering approaches are often based on the assumption that method users are able to explicitly express their situational method requirements. Similar to systems requirements, method requirements are often vague and hard to explicate. In this paper we address the issue of involving method users early in method configuration. This is done through borrowing ideas from user-centered design and prototyping, and implementing them on the method engineering layer. Objective: We design a computerized tool, MC Sandbox, to capture method requirements through the use of method-user-centered method configuration, hence bridging the gap between systems developers' and method engineers' understanding of and expectations on a situational method. Method: The research method adopted can be characterized as multi-grounded action research. Our implementation of multi-grounded action research follows the traditional 'canonical' action research method, which has cycles of diagnosing, action planning, action taking, evaluating, and specifying learning. The research project comprised three such action research cycles where 10 action cases were performed. Results: MC Sandbox has proven useful in eliciting and negotiating method requirements in a continuously ongoing dialog between the method users and the method engineers during configuration workshops. The results also show that the method engineer role rotated among the systems developers and that they were indeed committed to the negotiated methods during the systems development projects. Conclusion: It is possible for method users to actively participate and construct suitable situational methods if they are provided with appropriate high-level modelling concepts, such as method components, configuration packages and configuration templates. This way, the project members' understanding of the current development practice develops incrementally, both in terms of understanding the needs and available method support. In addition, both method requirements and commitments are made explicit, which are important aspects when working with method configuration from a collaboration point of view.