ENTERPRISE MODELLING AND THE TELEOLOGICAL APPROACH TO REQUIREMENTS ENGINEERING

1995 ◽  
Vol 04 (01) ◽  
pp. 45-79 ◽  
Author(s):  
P. LOUCOPOULOS ◽  
E. KAVAKLI

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.

2021 ◽  
Vol 12 (7) ◽  
pp. 339-349
Author(s):  
A. A. Kodubets ◽  
◽  
I. L. Artemieva ◽  

This article contains a systematic literature review of requirements engineering for software systems. The literature published within last 5 years was included into the review. A research question was defined as requirements development process of large scale software system (with thousands of requirements) and an interaction problem during this process (communication, coordination and control). The problem is caused by the fact that large-scale software system requirements process is a cross-disciplinary task and it involves multiple parties — stakeholders, domain experts, and suppliers with own goals and constrains, and thus, the interaction between them seriously slows down the overall requirements development process than writing the requirements specification itself. The research papers were classified by several research directions: Natural Language Processing for Requirements Engineering (NLP4RE), Requirement Prioritization, Requirements Traceability, Quality of Software Requirements, Non-functional Requirements and Requirements Elicitation. Motivation and intensity of each direction was described. Each direction was structured and represented with the key references. A contribution of each research direction into the research question was analyzed and summarized including potential further steps. It was identified that some researchers had met a part of the described problem in different forms during their researches. At the end, other researches were described additionally in a short overview. To approach the research question further potential direction was described.


2014 ◽  
Vol 29 (2) ◽  
pp. 161-182 ◽  
Author(s):  
W. Alec Cram ◽  
M. Kathryn Brohman ◽  
R. Brent Gallupe

ABSTRACT This paper examines the enterprise architecture process from the perspective of information systems controls, which refer to attempts to influence the behavior of employees in order to achieve organizational goals. Although controls have been extensively studied in processes such as systems development, there is little research examining control within the enterprise architecture process, despite its rising importance in today's organizations. This paper examines how enterprise architecture controls are employed in practice and considers the challenges faced in their design and operation. Drawing on empirical data from two in-depth case studies, enterprise architecture controls are classified and analyzed using COBIT 5. Our findings identify a series of specific challenges with enterprise architecture controls. Based on these challenges, we outline recommendations to practitioners in overseeing the enterprise architecture process and develop propositions to help guide future research initiatives to enhance enterprise architecture performance.


Author(s):  
Paul Johannesson

There are several different views of the functional role of information systems. Two of the most important ones are the model view and the communicative action view. According to the model view, the primary purpose of an information system is to provide a model of a Universe of Discourse (UoD), thereby enabling people to obtain information about reality by studying the model. In this respect, an information system works as a passive repository of data that reflects the structure and behaviour of the UoD. In contrast, the communicative action view states that the major role of an information system is to support communication within an organisation by structuring and coordinating the actions performed by the organisation’s agents. The system is seen as a medium through which people can perform social actions, such as stating facts, making promises, and giving orders. In certain cases, the system can itself take on the role of an agent and perform actions on its own initiative. Most representation techniques used in systems development are based on the model view of information systems. For example, Entity-Relationship diagrams or object-oriented class diagrams are used to represent the static and structural aspects of a UoD. Other examples are entity life cycle diagrams and interaction diagrams, which describe the behaviour of objects. Another technique, which also addresses communicative aspects, is the data flow diagram technique by which the information and control flow between agents in an organisation can be represented. These types of techniques have received widespread acceptance and are now important parts of several systems development methodologies. However, the techniques have also been heavily criticised, see for example (Auramäki, 1988) and (Coad, 1990). One line of critique argues that the basic concepts of the techniques are inappropriate for describing the activities of an organisation. When using the techniques, an enterprise is viewed as a collection of physical places or objects, and the work performed is accordingly analysed as physical activities such as sending messages and storing data. This focus on the physical transfer of data results in a computer and technology biased representation of the communication taking place in an organisation. Thus, from a communicative point of view, the very starting point of many modeling techniques are themselves flawed and should be replaced by an approach that focuses on the communicative actions of an enterprise. A promising approach for modelling communication structures is the language/action approach, which is based on theories from linguistics and the philosophy of language. In the language/action approach, business processes are modeled using the notions of speech acts and discourses, which provides a basis for distinguishing between distinct communication phases, such as preparation, negotiation, and acceptance. The purpose of this chapter is to investigate how the language/action approach can be used as a foundation for the information modeling of the communicative aspects in an organisation. This will be carried out by showing how a language/action approach combined with deontic concepts can be used to construct and organise analysis patterns for information modeling. These analysis patterns can be used in information modeling by supporting reuse, validation, and analysis of conceptual schemas. The information model can also be used to suggest how to organise the components that realise the communicative aspects of an information system into a three-tier architecture. The paper is organised as follows. Section 2 briefly discusses related work. Section 3 introduces an information model based on the language/action perspective. Section 4 shows how this model can be used to organise a number of analysis patterns. Section 5 discusses a number of applications of the model for reuse, validation, and systems architecture. Section 6 concludes the paper and gives suggestions for further work. This chapter extends previous work presented in (Johannesson, 1999).


Author(s):  
M. Mahmudul Hasan

Regulations and policies contain a rich source of requirements and failure to address these authoritative requirements in software system development can impose costly penalties for regulatory noncompliance. Despite the advancement of information system research, regulatory requirements compliance remains one of the primary challenges still to be efficiently dealt in system development because of the scarce information, complexity, and understanding of available approaches in requirements engineering process of a system development. This paper reports a systematic literature review of the documented approaches of regulatory requirements compliance, classifies these approaches according to different criteria and provides a qualitative analysis of their operational characteristics. The results of this analysis can serve system developers as the means of deriving appropriate methods and tools for regulatory requirements compliance in the software system development.


10.28945/2805 ◽  
2004 ◽  
Author(s):  
Lukasz Michalec ◽  
David A Banks

This paper explores the relationships between jazz and the development of information systems. Similarities are drawn between music in general and information systems development methodologies and jazz is taken as a specific focus. The idea of music as an information system in its own right is outlined. As systems development methodologies move from formal approaches towards more ad hoc forms, the lessons that can be learned from jazz, such as improvisation and shared meaning, may become increasingly useful.


2008 ◽  
Vol 46 ◽  
pp. 57-66 ◽  
Author(s):  
Ona Barčkutė

Didėjanti konkurencija verčia įmones plėsti informacinių sistemų (IS) taikymo sritis. Taip pat daugėja sistemas naudojančių asmenų, keičiasi technologijos, todėl išskirtinai tampa aktualu sukurti ir įgyvendinti vartotojams priimtiną ir patogią bendravimo su IS formą. Vartotojų nepripažinta sąsaja – viena iš svarbių priežasčių, darančių įtaką, kad IS projektai žlugtų. Todėl geriausias būdas šioms problemoms spręsti yra į sistemos kūrimo darbus kuo plačiau įtraukti vartotojus.Straipsnyje nagrinėjama organizacijos informacinių sistemų plėtra, remiamasi tradiciniu funkciniu požiūriu ir plėtros procesui darančia įtaką komponentų integracija, koncentruojamas dėmesys į vartotoją. Vartotojo vaidmuo sistemos plėtros procese nagrinėjamas atsižvelgiant į IS projektų žlugimo priežastis ir akcentuojant tuos darbų barus, kuriuose eilinio vartotojo patirtis ir nuomonė yra būtina. Kai eiliniai vartotojai ir informacinių sistemų specialistai nebendradarbiauja, sukurtos sistemos neveiksmingos. Straipsnis parengtas remiantis literatūros analize ir darbo autorės atlikto tyrimo rezultatais.Users in information systems development processOna Barčkutė SummaryInformation systems (IS) play an important role in today’s organizations. The usage of everyone IS must increase the efficiency of organization activities. Right systems development helps us achieve this goal. So, the development process for today’s information systems need a framework with integrate viewpoint and system users perspective assigning especial role them. Any useful information system can‘t be developed without systems users and builders properly collaboration.


2021 ◽  
Vol 12 (4) ◽  
pp. 33-39
Author(s):  
Hendro Muftadi ◽  
Rini Malfiany

Abstract PO Sinar Jaya is one of transportation provider companies that still develop and not yet usinginternet technology as services development to customers, the problem is they can’t see theschedule total remainder ticket directly, and company can’t give direct information to thecustomer. Systems development methods used is waterfall, waterfall consists of some stage the flowof activity that walked in one direction from the start to finish system develop project, start fromanalysis, design, code, trial, and supporting stage. According to observation that be held in POSinar Jaya Cibitung obtained complete information about procedure order the ticket during thetime, so can give the solution to information system planning order ticket bus by online. With theinformation ordering ticket bus using online system expected can help ordering ticket bus activitiesand can to increase sale volume, increase the service quality and company’s image.


Author(s):  
M. Gordon Hunter

When is an information system development outcome considered a success and when is it considered a failure? What factors contribute to a conclusion of either success or failure? How does the situation arise to create the environment which contributes to the above conclusions? Generally, an information system is considered a success when it does what it is supposed to and/or the user is satisfied with the system’s performance in support of the information-providing and decision-making responsibilities. Naturally, this area is fraught with the problems inherent in divergent interpretations of “what it is supposed to do,” “satisfaction,” and “systems performance.” Suffice it to say, when the systems developer and user are in positive agreement about these interpretations, the information system development outcome may be considered successful.


Author(s):  
Fadoua Rehioui

The complexity of information systems leads to poor data management and therefore bad decisions. The advantage of using component-based software engineering is to divide an information system into subsystem blocks with less complexity. In fact, a component is intended to provide specific services as management of the combination and communication between the units of the system. This chapter addresses this problem by developing information systems, proposing a component identification approach and the management pattern for data management. In this work, three developed views are taken into account, which include modelization and the design to achieve the purpose of defining and building the components and how they can be assembled. A component is intended to provide specific services, as a combination and communication management between the system units, and the manager component is the important and complementary paradigm pattern and added value for the development of software systems.


Sign in / Sign up

Export Citation Format

Share Document