• Publications
  • Influence
Design Science Methodology for Information Systems and Software Engineering
  • R. Wieringa
  • Computer Science
  • Springer Berlin Heidelberg
  • 19 November 2014
TLDR
This book provides guidelines for practicing design science in the fields of information systems and software engineering research by providing guidelines on how to effectively structure research goals, how to analyze research problems concerning design goals and knowledge questions,How to validate artifact designs and how to empirically investigate artifacts in context and finally how to present the results of the design cycle as a whole. Expand
Requirements engineering paper classification and evaluation criteria: a proposal and a discussion
TLDR
Members of the steering committee of the IEEE Requirements Engineering (RE) Conference have discussed paper classification and evaluation criteria for RE papers, and are far from a consensus about what classes of paper they should distinguish, and what the criteria are for each of these classes. Expand
Design science as nested problem solving
TLDR
This paper analyzes the mutual nesting of practical problems and knowledge problems, derives some methodological guidelines from this for design science researchers, and gives an example of a design science project following this problem nesting. Expand
Design methods for reactive systems - Yourdon, Statemate, and the UML
TLDR
This book discusses Reactive System Design: Reactive Systems The Environment Stimulus-Response Behavior Software Specifications and Software Specification Methods, which describe Postmodern Structured Analysis (PSA) Statemate and the Unified Modeling Language (UML). Expand
Enterprise architecture: Management tool and blueprint for the organisation
This is an editorial to a special issue of ISF on enterprise architecture.We define the concept of enterprise architecture, notivate its importance, and then introduce the papers in this specialExpand
Agile requirements prioritization in large-scale outsourced system projects: An empirical study
TLDR
This exploratory study sets out to uncover the concepts that practitioners in a large software organization use in the prioritization process and the practices that they deem good, and brings a rich analysis of cases in agile and distributed contexts, from a vendor's perspective. Expand
Technical Action Research as a Validation Method in Information Systems Design Science
TLDR
A way of bridging the gap between idealization and practice by means of action research, called technical action research (TAR), which starts with an artifact, and then tests it under conditions of practice by solving concrete problems with them. Expand
A survey of structured and object-oriented software specification methods and techniques
TLDR
The techniques are classified as techniques for the specification of external interaction and internal decomposition and a plea for simplicity in diagram techniques and for the use of formal semantics to define these techniques is made. Expand
Guest Editors' Introduction: Stakeholders in Requirements Engineering
TLDR
The RE process is reviewed: identifying the stakeholders in a project, determining who and how important they are, prioritizing the identified stakehold roles, and selecting representative individuals or groups from the identified and prioritized stakeholder roles with whom the development team can elicit and validate system requirements. Expand
Six strategies for generalizing software engineering theories
TLDR
This paper argues that for theories to be useful in practice, they should give sufficient understanding of a sufficiently large class of cases, without having to be universal or complete, and provides six strategies for developing theories of the middle range. Expand
...
1
2
3
4
5
...