scispace - formally typeset
Open AccessDOI

A systemic paradigm for early IT system requirements based on regulation principles

Gil Regev
TLDR
The Lightswitch approach, described in this thesis, was designed as a tool for IT system designers to create initial requirements taking into account the enterprises needs for stability and change in terms of goals.
Abstract
IT system is a general term for all software based business applications used in enterprises. IT systems support the actions of an enterprise by processing information about the enterprise and its environment and by providing this information to the enterprise and its stakeholders. An enterprise's actions have a direct influence on its ability to succeed in its environment. IT systems, therefore, have a direct influence on the enterprise's long term success. Hence, IT systems are considered to be of strategic importance in most contemporary enterprises. Although enterprises, most of the time, attempt to maintain their identity, forces within them and in their environment push them to change. Enterprise strategy therefore seeks to balance the need to remain the same with the need to change. This balance is maintained by specifying change that the enterprise is capable of sustaining and that the enterprise believes are necessary for its continued success. The design of IT systems should reflect this need for stability and change. The requirements of an IT system are the description of what the IT system will be like and how it will behave. The initial understanding of the requirements is called early requirements. Early requirements define the problems the enterprise is trying to solve and sketch the possible solutions to these problems. An envisioned IT system is often part of these solutions. Enterprise Architecture (EA) and Goal-Directed Requirements Engineering (GDRE) propose methods for defining early requirements by considering the goals of the enterprise and its stakeholders. The concept of goal is used to give structure to the different perspectives on the enterprise defined by its stakeholders and to express the resulting requirements for the IT system. The EA and GDRE literature does not propose a conceptual foundation that gives meaning to the different kinds of goals specified by the EA and GDRE methods as well as how these goals are formed and modified in enterprises. Moreover, EA and GDRE methods are often influenced by Business Process Reengineering (BPR) which is known for specifying radical, often unsustainable change. The resulting early requirements specify goals that could have been changed or that specify too much change for the enterprise. The Lightswitch approach, described in this thesis, was designed as a tool for IT system designers to create initial requirements taking into account the enterprise's needs for stability and change in terms of goals. The Lightswitch approach consists of a conceptualization and a modeling framework. The Lightswitch conceptualization explains the goal-directed behavior of enterprises from the standpoint of the maintenance of success in a changing environment. It is based on General Systems Thinking (GST) and Cybernetics principles. Combined, these theoretical perspectives offer an evolutionary viewpoint describing enterprises as systems that maintain their internal order by regulating their relationships with other systems. GST and Cybernetics offer a set of principles with which to understand this regulation. These principles are used in the Lightswitch conceptualization to explain how enterprises regulate their relationships with their stakeholders in order to remain successful. The Lightswitch conceptualization provides an explanation, in an enterprise context, of the different kinds of goals specified in the EA and GDRE literature. The conceptualization forms the theoretical background of the Lightswitch modeling framework, a goal-directed modeling framework that enables IT system designers to specify early requirements for an IT system based on the enterprise's regulation of its relationships with its stakeholders. The Lightswitch framework complements existing EA and GDRE methods by enabling designers to model both the stability and the changing nature of the relationships of the enterprise with its stakeholders. These models help designers to better understand the enterprise's goals, to propose changes to these goals if deemed necessary, and to specify early requirements for the enterprise's IT systems in the form of high-level goals. This thesis contributes an original conceptualization and method to EA and GDRE. Concretely, the Lightswitch approach consists in reflecting on the conditions that brought the enterprise-under-consideration to be what it is today, to analyze how well it is adapted to its present conditions, and to attempt to foresee some of the challenges it may face in the future. The early requirements for the IT system should reflect these past, present and future perspectives. We present three case studies in which the Lightswitch approach was used to specify the early requirements for an enterprise IT system. Two of the case studies were performed in industrial settings.

read more

Citations
More filters
Proceedings ArticleDOI

Where do goals come from: the underlying principles of goal-oriented requirements engineering

TL;DR: A set of principles are proposed that explain the nature of goal-oriented behavior based on regulation mechanisms as defined in general systems thinking and cybernetics and are used to analyze the existing definitions of these different kinds of goals and to propose more precise definitions.
Journal ArticleDOI

Defining business process flexibility with the help of invariants

TL;DR: Identifying a minimum set of invariants provides a basis for defining flexible processes and support systems and is illustrated with production business process support (BPS) systems.

A Regulation-Based View on Business Process and Supporting System Flexibility

TL;DR: This paper examines organizational flexibility and business processes from the point of view of the regulation of relationships between stakeholders and pro-poses a set of high-level requirements for business process support systems for the maintenance of business process flexibility.
Proceedings ArticleDOI

Defining early IT system requirements with regulation principles: the Lightswitch approach

TL;DR: The Lightswitch approach is presented, an approach for defining early requirements for enterprise IT systems, which can model the way an enterprise regulates its relationships with its environment, identify changing conditions within the enterprise and its environment and propose options for changing this regulation.
Journal ArticleDOI

Modelling the regulative role of business processes with use and misuse cases

TL;DR: A theoretical framework based on the concept of homeostasis, the maintenance of identity in a changing world is proposed, which classifies business processes into three levels (strategic, operational, regulative) and analyse the relationships between these three levels.
References
More filters
Proceedings ArticleDOI

Formal refinement patterns for goal-driven requirements elaboration

TL;DR: An approach to goal refinement and operationalization which is aimed at providing constructive formal support while hiding the underlying mathematics is presented, and the general principle is to reuse generic refinement patterns from a library structured according to strengthening/weakening relationships among patterns.
Book

Software Requirements: Styles and Techniques

TL;DR: This paper presents a meta-analysis of Danish Shipyard requirements and its application in the context of public health and public health administration.
Proceedings ArticleDOI

The use of goals to surface requirements for evolving systems

TL;DR: A summary of a goal-based method (GBRAM) for uncovering hidden issues, goals, and requirements and its application to a commercial system, an Intranet-based electronic commerce application, evaluating the method in the process are presented.
Proceedings ArticleDOI

Goal-directed elaboration of requirements for a meeting scheduler: problems and lessons learnt

TL;DR: The objective of the paper is to assess the strengths and weaknesses of one of these methodologies on a nontrivial benchmark; and to illustrate and discuss a number of challenging issues that need to be addressed for such methodologies to become effective in supporting real, complex requirements engineering tasks.
Journal ArticleDOI

Intent specifications: an approach to building human-centered specifications

TL;DR: This paper examines and proposes an approach to writing software specifications, based on research in systems theory, cognitive psychology and human-machine interaction, to provide specifications that support human problem solving and the tasks that humans must perform in software development and evolution.
Related Papers (5)