The Infona portal uses cookies, i.e. strings of text saved by a browser on the user's device. The portal can access those files and use them to remember the user's data, such as their chosen settings (screen view, interface language, etc.), or their login data. By using the Infona portal the user accepts automatic saving and using this information for portal operation purposes. More information on the subject can be found in the Privacy Policy and Terms of Service. By closing this window the user confirms that they have read the information on cookie usage, and they accept the privacy policy and the way cookies are used by the portal. You can change the cookie settings in your browser.
Natural language is currently the basis of the majority of system specifications, even if it has several drawbacks. In particular, natural language is inherently ambiguous. In this article, we propose a way to complete the natural language text of requirements by giving a formal syntax to this text. We introduce and use an example to illustrate our ideas.
Several countries prescribe or advise government departments and organizations to perform a privacy impact assessment (PIA) if these prepare new projects or change existing ones that involve personal information. A PIA shall summarize what personal information is collected, processed, stored, and distributed in the context of the project. But there is only little support for undertaking a PIA and...
Requirements engineering is a most critical activity in the engineering process of complex cyber-physical systems. To avoid the ambiguity of natural or semi-formal languages, to provide tool support for engineering activities all along a system lifecycle (from scoping studies to system operation, maintenance), EDF has developed FORM-L, a formal constraints-based language for the modelling of assumptions,...
In this paper, and in the context of a course of 1st cycle in Informatics, and following the guidelines of the Information Systems courses provided by ACM/AIS, we propose the use of Google tools and Lucidchart modeling tool, aligned with Bloom's taxonomy in our model BML Context Oriented (BML-CO) in a Requirements Engineering course based on Unified Modelling Language (UML) to modeling and specify...
Feature-oriented software requirements specify features in a product line as separate modules. In this paper, we present the Mode-Based Behaviour pattern that provides advice on how to structure the behavioural requirements of an individual feature using state machines. The pattern not only defines the control flow of a feature, but also places constraints on the kinds of behaviour that a feature...
Agent-oriented software products are becoming increasingly complicated, and the competitive market is forcing the producers to reduce time-to-market and increase the quality of the software produced. Therefore, developers have come to realize the need for more reliable and efficient agent-oriented software development processes (methodologies) which address the specific needs of each and every project...
With most of formal methods, an initial formal model can be refined in multiple steps, until the final refinement contains enough details for an implementation. Most of the time, this initial model is built from the description obtained by the requirements analysis. Unfortunately, this transition from the requirements phase to the formal specification phase is one of the most painful steps and is...
In this paper, we present a method to perform the first steps of software evolution, namely evolutionary requirements engineering, where new requirements have to be analyzed in the context of a set of already given requirements. The basic idea is to adjust an existing requirements engineering process so that evolution is supported. In the requirements engineering process we consider, the original...
Function Points (FP) are widely used as a basis to estimate software development cost and efforts. At the requirements level several estimation tools have been developed, but these tools use unified modeling language (UML) diagram. However, not all requirements documents include supplementary UML diagram. This paper describes the development of an automated tool to estimate size of software projects...
This paper presents the application of the use-case modelling approach in deriving software requirements for an ontology-driven requirements analysis tool, namely OntoRAT in the context of the ontology-driven requirements engineering methodology (OntoREM) project and following the spiral model in carrying out the respective requirements engineering process. In particular, this research has demonstrated...
In large-scale collaborative software projects, thousands of requirements with complex interdependencies and different granularity spreading in different levels are elicited, documented, and evolved during the project lifecycle. Non-technical stakeholders involved in requirements engineering activities rarely apply formal techniques; therefore it is infeasible to automatically detect problems in requirements...
Over the last decade, many aspect-oriented (AO) programming and modeling languages have been developed. Pointcut expressions are a key concept of each of these languages as they define the patterns that must be matched for aspects to be applied to the base. To date, most pointcut expressions are constrained to one particular notation - the one for which they were designed - even though a goal of aspect-oriented...
A decision information system (DIS) is a specific component of information system specialized in the support of decision-making by means of online analytical processing tools. Data warehouses (DW), at the core of DIS, integrate and historize collections of data often designed starting from the operational components of the Information Systems (IS). Methods, techniques and tools widely used in the...
Set the date range to filter the displayed results. You can set a starting date, ending date or both. You can enter the dates manually or choose them from the calendar.