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

Evaluating the Effectiveness of a Goal-Oriented Requirements Engineering Method

TL;DR: This work systematically evaluates the KAOS method, and the Objectiver tool, using the major REOs widely accepted as being important attributes of requirements specifications, to answer the need for methods and tools in requirements engineering which are domain specific and can address the main RE objectives.
Book ChapterDOI

Comparing GRL and KAOS using the UEML Approach

TL;DR: The paper analyses and compares the syntax and semantics of GRL and KAOS using the UEML approach, providing a systematic and detailed comparison of the two languages, in part based on the Bunge-Wand-Weber (BWW) model and Bunge’s ontology.
Proceedings ArticleDOI

Visually effective goal models using KAOS

TL;DR: This paper evaluates how the goal modelling language KAOS and its supporting tool, Objectiver, help modellers respect nine visual modelling principles and formulates recommendations for modeller, language designers and tool developers.
Book ChapterDOI

Ontological Analysis of KAOS Using Separation of Reference

TL;DR: A structured approach is applied to describe a well-known goal-oriented language, KAOS, by mapping it onto a philosophically grounded ontology, which provides an intermediate language for comparison, consistency checking, update reflection, view synchronisation and, eventually, model-to-model translation both between goal- oriented languages and between different languages.
References
More filters
Book

Systems Thinking, Systems Practice

TL;DR: The Soft Systems Methodology (SSM) as discussed by the authors is an alternative approach which enables managers of all kinds and at any level to deal with the subtleties and confusions of the situations they face.
Journal ArticleDOI

The Sciences of the Artificial

Book

Extreme Programming Explained: Embrace Change

Kent Beck
TL;DR: You may love XP, or you may hate it, but Extreme Programming Explained will force you to take a fresh look at how you develop software.
Book

Reengineering the corporation: a manifesto for business revolution

TL;DR: In this paper, the authors set aside much of the received wisdom of the last 200 years of industrial management and in its place presented a new set of organizing principles by which managers can rebuild their businesses.

The Tacit Dimension

C. P. Goodman
TL;DR: 'Without symbolism the life of man would be like that of the prisoners in the cave of Plato's simile; it could find no access to the "ideal world" which is opened to him from different sides by religion, art, philosophy, science.
Related Papers (5)