Compliance to regulatory requirements is a critical concern in information system development projects. Managing this aspect is increasingly challenging while failures impose costly consequence on the organizations world-wide. However, how a legislation may or may not affect information system development projects is often not easily identifiable due to lack of clear understanding and guidelines. This paper presents compliant information system development (CISMET) ontology, exploiting concepts from 21 existing ontologies (regarding regulatory compliance and information system development). The key findings are the six parent classes in the CISMET ontology describing the system development goals, services, process, activities, artifacts, and resources. Also, there are 26 sub classes and 21 class properties that describe various concepts and their relationships in regulatory compliant information system development. The General Data Protection Regulation (GDPR) of the European Union has been instantiated in the proposed framework to indicate how regulatory requirements compliance concepts are mapped to system development projects. Thus, involved stakeholders (information system researchers and system developers) may identify dependencies and actions needed with relation to various rules in the regulation and their link to the system elements through a relevant software application. The latter enables users to easily submit queries towards the backend ontology through a specialized front-end application that can aid in formulating and submitting these queries.

Context: End-user service composition (EUSC) is a service-oriented paradigm that aims to empower end users and allow them to compose their own web applications from reusable service components. User studies have been used to evaluate EUSC tools and processes. Such an approach should benefit software development, because incorporating end users’ feedback into software development should make software more useful and usable. Problem: There is a gap in our understanding of what constitutes a user study and how a good user study should be designed, conducted, and reported. Goal: This article aims to address this gap. Method: The article presents a systematic review of 47 selected user studies for EUSC. Guided by a review framework, the article systematically and consistently assesses the focus, methodology and cohesion of each of these studies. Results: The article concludes that the focus of these studies is clear, but their methodology is incomplete and inadequate, their overall cohesion is poor. The findings lead to the development of a design framework and a set of questions for the design, reporting, and review of good user studies for EUSC. The detailed analysis and the insights obtained from the analysis should be applicable to the design of user studies for service-oriented systems as well and indeed for any user studies related to software artifacts.

This paper reports the work in progress towards the specification of a conceptual architecture of a smart system for supporting the management of disruptions in the manufacturing domain. In particular, it proposes an approach to the description of the system architecture based on a number of interrelated viewpoints following the pertinent ISO 42010 standard. The approach is being developed in the context of the EU-funded H2020 DISRUPT project aiming to deliver a comprehensive data-driven solution for automated vertical and horizontal integration facilitating the transition into smart manufacturing.

Abstract As software complexity grows and clients demand higher quality software, quality requirements can no longer be considered to be of secondary importance. Thus, eliciting, specifying, prioritizing and validating quality requirements is a prerequisite to the development of effective and efficient information systems. Despite the critical importance of quality requirements, there is a considerable gap in the breadth and depth of quality requirements engineering (RE) support in most RE approaches. In practice, it is often the case to have quality requirements considered as an afterthought in the systems development process. While there is a wealth of modelling techniques and tools for functional requirements, there is very limited support for quality requirements in RE. Support for quality requirements is usually ad‐hoc, without clear guidelines on how to capture, specify and manage quality requirements and also without proper usage of standardized terminologies based on established quality models such as the ISO/IEC 9126 quality model. In this paper, we discuss a quality‐driven RE framework and tool that applies knowledge management techniques and quality ontologies to support RE activities. The ontology implements the quality characteristics and metrics prescribed by the ISO/9126 quality model, providing a common vocabulary to address quality concerns/aspects across RE activities. We empirically validate how the framework and tool can be used to effectively support the requirements elicitation and prioritization activities through a case study addressing the development of an intranet portal project at the University of Manchester.

Business process (BP) modelling is considered as an important part of Requirement Engineering in describing the context within which requirements are articulated, specified and analysed. The intertwining of business and information systems imposes considerable stresses on requirements engineers to consider quality factors that need to be present in both business processes and the software that supports these processes. We argue that the quality of BPs has to be taken into account at the requirement engineering stage, where quality requirements are to be defined, along with the corresponding quality factors and the metrics that will be used to evaluate them. We consider that a BP is represented by a model and that quality requirements are to be examined within the BP model. In this work, our goal is to provide a support for evaluating the quality of a BP through the corresponding model. We present a quality framework for BPs and a quality-oriented BP metamodel. This metamodel is enriched with quality-related attributes that will be used to evaluate the quality factors. To demonstrate the utility of the proposed quality framework we will use a BP model relating to the management of spectators at an Olympics venue, we will show the instantiation of our metamodel in this context along with evaluation results for some quality factors.

A critical success factor for information systems is their ability to evolve as their environment changes. There is compelling evidence that the management of change in business policy can have a profound effect on an information system’s ability to evolve effectively and efficiently. For this to be successful, there is a need to represent business rules from the early requirements stage, expressed in user-understandable terms, to downstream system design components and maintain these throughout the lifecycle of the system. Any user-oriented changes could then be traced and if necessary propagated from requirements to design specifications and evaluated by both end-users and developers about their impact on the system. The BROOD approach, discussed in this article, aims to provide seamless traceability between requirements and system designs through the modelling of business rules and the successive transformations, using UML as the modelling framework.

In today's business environment of relentless change, the topic of how one should proceed with understanding the reasons for change and alternative strategic options, has received much attention by researchers and practitioners alike. This paper considers the relation between goal-oriented business process modeling and organizational change and addresses the question "how can we reason about organizational change using a goal-driven approach?" To this end, it describes a systematic way-of-working for modeling organizational change and presents empirical results and observations from applying this approach in a large industrial application in the domain of utility deregulation. The purpose of this paper is twofold. Firstly, to demonstrate and assess the applicability of the proposed methodology on a nontrivial application and secondly to illustrate a number of challenging issues that need to be addressed by goal-driven methodologies in order to effectively support the process of change.

The design and implementation of systems for the support of venue operations for the Olympic games is a complex and multifaceted undertaking. Venue operations are designed to support the efficient functioning of every venue far every day for the duration of the games. We present the challenges faced and experiences gained during two years of requirements engineering projects for this high-profile and multifarious application. We describe the unique nature of the enterprise environment, briefly discuss and critique the approaches traditionally used, present the approach adopted in the venue operations planning of the Athens2004 Olympic games and discuss the issues that influenced the process of requirements elicitation. The purpose is to report on experiences from a particular type of requirements problems (very early, strategic requirements) and to draw lessons that may inform future practice and research.

Rapid technological change has had an impact on the nature of software. This has led to new exigencies and to demands for software engineering paradigms that pay particular atttention to meeting them. We advocate that such demands can be met, at least in large parts, through the adoption of software engineering processes that are founded on a reflective stance. To this end, we turn our attention to the field of Design Rationale. We analyze and characterize Design Rationale approaches and show that despite surface differences between different approaches, they all tend to be variants of a relatively small set of static and dynamic affinities. We use the synthesis of static and dynamic affinities to develop a generic model for reflective design. The model is nonprescriptive and affects minimally the design process. It is context-independent and is intended to be used as a facilitator in participative design, supporting group communication and deliberation. The potential utility of the model is demonstrated through two examples, one from the world of business design and the other from programming language design

A critical factor in successful requirements analysis appears to be the understanding not only of what the system under consideration should do, but also why. To capture the purpose of an information system, one needs a mechanism to describe the behaviour of the organization in which the system will operate. This approach suggests further understanding and modelling of the organizational goals and the way that these goals become operationalised. In software systems development we often make the distinction between the enter prise world and the system world. The former describes the domain about which the proposed software system is to provide some service, while the second is concerned with specifications on what the system does and include descriptions of the systems requirements, conceptual designs and implementations. This paper describes an approach which involves the explicit modelling of organizational objectives, social roles and operations and the synthesis of these different perspectives towards a set of information systems requirements.

Article Free Access Share on Development and evaluation of an application in a deductive environment Authors: Ilias Petrounias Information Systems Group, Department of Computation, UMIST, P.O. Box 88, Manchester M60 1QD Information Systems Group, Department of Computation, UMIST, P.O. Box 88, Manchester M60 1QDView Profile , Pericles Loucopoulos Information Systems Group, Department of Computation, UMIST, P.O. Box 88, Manchester M60 1QD Information Systems Group, Department of Computation, UMIST, P.O. Box 88, Manchester M60 1QDView Profile Authors Info & Claims CIKM '93: Proceedings of the second international conference on Information and knowledge managementDecember 1993 Pages 184–193https://doi.org/10.1145/170088.170126Published:01 December 1993Publication History 1citation218DownloadsMetricsTotal Citations1Total Downloads218Last 12 Months3Last 6 weeks2 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF

The authors demonstrate an approach to software development known as RUBRIC, which recognizes that a particular class of system, namely, business information systems, contain a large element of information processing which is dictated by business needs and that these needs will inevitably change. Consequently, RUBRIC separates data from procedure and business policy from operational procedure, and presents explicit models for all of these. This approach thereby maintains the visibility of those parts of a system which are most volatile and subject to change and thereby reduces system maintenance costs.>