The Requirements Engineering Reference Model: A Fundamental Impediment to Using Formal Methods in Software Systems Development

2019 ◽  
Author(s):  
Daniel M. Berry
Keyword(s):  
Formal Methods ◽  
Requirements Engineering ◽  
Reference Model ◽  
Systems Development ◽  
Software Systems

ENTERPRISE MODELLING AND THE TELEOLOGICAL APPROACH TO REQUIREMENTS ENGINEERING

1995 ◽  
Vol 04 (01) ◽  
pp. 45-79 ◽  
Author(s):  
P. LOUCOPOULOS ◽  
E. KAVAKLI
Keyword(s):  
Information System ◽  
Information Systems ◽  
Requirements Engineering ◽  
Social Roles ◽  
Critical Factor ◽  
Systems Development ◽  
Software Systems ◽  
Software System ◽  
Organizational Goals ◽  
Systems Requirements

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.

Integrating Requirements Engineering Techniques and Formal Methods

2005 ◽  
pp. 1555-1559 ◽  
Author(s):  
María Virginia Mauco ◽  
Daniel Riesco
Keyword(s):  
Formal Methods ◽  
Requirements Engineering ◽  
Formal Specification ◽  
Specification Language ◽  
Software Systems ◽  
Formal Development ◽  
Secure Software ◽  
Formal Specification Language

Formal methods help to develop more reliable and secure software systems, and they are increasingly being accepted by industry. The RAISE1 Method (George et al., 1995), for example, is intended for use on real developments, not just toy examples. This method includes a large number of techniques and strategies for formal development and proofs, as well as a formal specification language, the RAISE Specification Language (RSL) (George et al., 1992), and a set of tools (George et al., 2001).

Requirements Engineering for Software Systems: A Systematic Literature Review

2021 ◽  
Vol 12 (7) ◽  
pp. 339-349
Author(s):  
A. A. Kodubets ◽  
◽  
I. L. Artemieva ◽  
Keyword(s):  
Literature Review ◽  
Requirements Engineering ◽  
Language Processing ◽  
Systematic Literature Review ◽  
Large Scale ◽  
Development Process ◽  
Research Question ◽  
Software Systems ◽  
Software System ◽  
Requirements Development

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.

Measuring the Progress of a System Development

2014 ◽  
pp. 1415-1439
Author(s):  
Marta (Plaska) Olszewska ◽  
Marina Waldén
Keyword(s):  
Formal Methods ◽  
Design Process ◽  
Formal Specification ◽  
System Development ◽  
Structural Complexity ◽  
Software Systems ◽  
System Construction ◽  
Design Decisions ◽  
And Control

For most of the developers and managers, the structure and the behaviour of software systems represented in a graphical manner is more understandable than a formal specification of a system or than plain code. Our previous work combined the intuitiveness of UML with the development rigour brought by formal methods and created progress diagrams. In progress diagrams, the design decisions within a system refinement chain are assisted by the application of patterns and illustrated in a comprehensible and compact manner. In order to rigorously assess and control the design process, we need to thoroughly monitor it. In this chapter we show how the application of generic refinement patterns is reflected in measurements. We establish measures for the evaluation of the design progress of the system, where the progress diagrams are assessed from the size and structural complexity perspective. Our motivation is to support the system developers and managers in making the design decisions that regard the system construction.

Sign in / Sign up

Export Citation Format

Share Document