47,642 research outputs found
Formalising responsibility modelling for automatic analysis
Modelling the structure of social-technical systems as a basis for informing software system design is a difficult compromise. Formal methods struggle to capture the scale and complexity of the heterogeneous organisations that use technical systems. Conversely, informal approaches lack the rigour needed to inform the software design and
construction process or enable automated analysis.
We revisit the concept of responsibility modelling, which models social technical systems as a collection of actors who discharge their responsibilities, whilst using and producing resources in the process. Responsibility modelling is formalised as a structured approach for socio-technical system requirements specification and modelling, with well-defined semantics and support for automated structure and validity analysis. The
effectiveness of the approach is demonstrated by two case studies of software engineering methodologies
The i* framework for goal-oriented modeling
The final publication is available at Springer via http://dx.doi.org/10.1007/978-3-319-39417-6i* is a widespread framework in the software engineering field that supports goal-oriented modeling of socio-technical systems and organizations. At its heart lies a language offering concepts such as actor, dependency, goal and decomposition. i* models resemble a network of interconnected, autonomous, collaborative and dependable strategic actors. Around this language, several analysis techniques have emerged, e.g. goal satisfaction analysis and metrics computation. In this work, we present a consolidated version of the i* language based on the most
adopted versions of the language. We define the main constructs of the language and we articulate them in the form of a metamodel. Then, we implement this version and a concrete technique, goal satisfaction analys is based on goal propagation, using ADOxx. Throughout the chapter, we used an example based on open source software adoption to illustrate the concepts and test the implementation.Peer ReviewedPostprint (author's final draft
Deriving Information Requirements from Responsibility Models
This paper describes research in understanding the requirements for complex information systems that are constructed from one or more generic COTS systems. We argue that, in these cases, behavioural requirements are largely defined by the underlying system and that the goal of the requirements engineering process is to understand the information requirements of system stakeholders. We discuss this notion of information requirements and propose that an understanding of how a socio-technical system is structured in terms of responsibilities is an effective way of discovering this type of requirement. We introduce the idea of responsibility modelling and show, using an example drawn from the domain of emergency planning, how a responsibility model can be used to derive information requirements for a system that coordinates the multiple agencies dealing with an emergency
On the structure of problem variability: From feature diagrams to problem frames
Requirements for product families are expressed in terms of commonality and variability. This distinction allows early identification of an appropriate software architecture and opportunities for software reuse. Feature diagrams provide intuitive notations and techniques for representing requirements in product line development. In this paper, we observe that feature diagrams tend to obfuscate three important descriptions: requirements, domain properties and specifications. As a result, feature diagrams do not adequately capture the problem structures that underlie variability, and inform the solution structures of their complexity. With its emphasis on separation of the three descriptions, the problem frames approach provides a conceptual framework for a more detailed analysis of variability and its structure. With illustrations from an example, we demonstrate how problem frames analysis of variability can augment feature diagrams
Deferred Action: Theoretical model of process architecture design for emergent business processes
E-Business modelling and ebusiness systems development assumes fixed company resources,
structures, and business processes. Empirical and theoretical evidence suggests that company resources
and structures are emergent rather than fixed. Planning business activity in emergent contexts requires
flexible ebusiness models based on better management theories and models . This paper builds and
proposes a theoretical model of ebusiness systems capable of catering for emergent factors that affect
business processes. Drawing on development of theories of the ‘action and design’class the Theory of
Deferred Action is invoked as the base theory for the theoretical model. A theoretical model of flexible
process architecture is presented by identifying its core components and their relationships, and then
illustrated with exemplar flexible process architectures capable of responding to emergent factors.
Managerial implications of the model are considered and the model’s generic applicability is discussed
Practitioner requirements for integrated Knowledge-Based Engineering in Product Lifecycle Management.
The effective management of knowledge as capital is considered essential to the
success of engineering product/service systems. As Knowledge Management (KM) and
Product Lifecycle Management (PLM) practice gain industrial adoption, the
question of functional overlaps between both the approaches becomes evident.
This article explores the interoperability between PLM and Knowledge-Based
Engineering (KBE) as a strategy for engineering KM. The opinion of key KBE/PLM
practitioners are systematically captured and analysed. A set of ranked business
functionalities to be fulfiled by the KBE/PLM systems integration is elicited.
The article provides insights for the researchers and the practitioners playing
both the user and development roles on the future needs for knowledge systems
based on PLM
Collaborative design : managing task interdependencies and multiple perspectives
This paper focuses on two characteristics of collaborative design with
respect to cooperative work: the importance of work interdependencies linked to
the nature of design problems; and the fundamental function of design
cooperative work arrangement which is the confrontation and combination of
perspectives. These two intrinsic characteristics of the design work stress
specific cooperative processes: coordination processes in order to manage task
interdependencies, establishment of common ground and negotiation mechanisms in
order to manage the integration of multiple perspectives in design
- …