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.
The overall goal of this work is to provide problem-oriented support for Pattern-Oriented Analysis and Design (POAD) so that (i) we may construct a better understanding of the relationship of POAD to other software development approaches and (ii) we can extend the reach of problem-orientation to design patterns. This paper extends our previous contributions to show how both high-level and detailed...
Requirements traceability is a challenge for modern software projects where task dependencies and technical expertise are spread across system developers, abstract model representations such as use cases, and a myriad of code artefacts. This paper presents an approach that monitors the navigation trails left by developers when building code artefacts to realise project use cases. These trails are...
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...
Online backup service software provides automated, offsite, secure online data backup and recovery for remote computers. How to satisfy functional requirements and guarantee the fault tolerance of online backup service software is a difficult but crucial problem faced by software designers. In this paper, we investigate to incorporate the fault tolerant techniques in the system design, and propose...
Petri nets and related models have been used for specification, analysis, and synthesis of programs. The paper contains a survey of several literature approaches and an examination of their relationship to Petri net modeling and supervisory control. The discussion is restricted to Petri net models in the class of place/transitions nets and the supervisory control of this class of models.
It is very costly if a software project development has to recover from an error that is due to a mistake made in the construction of the requirements model. Validation of requirements model is thus always an effective means for detecting defects in the requirements model. In this paper, we present an approach to modeling requirements by UML with OCL, and the design of a tool EOC (executable OCL checker),...
The self-adaptation of a software system is a complex process that depends on the system requirements, its operational state and environment, which may change during the system operational lifetime. Hence, the process for coordinating the self-adaptation should also be adaptable to changes that may occur during run-time. As a means for coordinating the self-adaptation process of software systems,...
This work explores how model-driven engineering techniques can support the configuration of systems in domains presenting multiple variability factors. Video surveillance is a good candidate for which we have an extensive experience. Ultimately, we wish to automatically generate a software component assembly from an application specification, using model to model transformations. The challenge is...
Failure of a design to satisfy a system's requirements can result in schedule and cost overruns. When using current approaches, ensuring requirements are satisfied is often delayed until late in the development process during a cycle of testing and debugging. This paper introduces a more rigorous approach to design using Behavior Engineering, which has previously been applied primarily to requirements...
As computers and software applications become ubiquitous the systems we build are increasingly required to run on not just a single piece of hardware, but rather be available for different platforms, different types of hardware and offer different modes of interaction depending on the context of use. Within a formal development process when we consider refinement for interactive systems we therefore...
This paper presents our PABRE method for facilitating requirements elicitation on the basis of requirement patterns with the goal of saving time and reducing errors during this activity. The process presented applies for elicitation in off-the-shelf selection projects driven by call for tenders processes and uses a requirement patterns catalogue. The process selects patterns from the catalogue that...
In this article paper entitled "From Play-In Scenarios to Code: An Achievable Dream",David Harel presented a development schema that makes it possible to go from high-level user-friendly requirements to a full system model, and from there to the final implementation. Even if Harel's schema represents a real contribution to filing the gap between user requirements and final implementations,...
Requirements must be pertinent and aligned to business goals. Frequently, developed requirements meet only immediate concerns and there is dissonance with business goals resulting in wasted opportunities. Comprehensive models exist, whose rigors demand sustained stakeholder engagement and suit process mature environments. Proposed approach supports early alignment of requirements with business goals...
Providing software components with a four level contract specification - syntax, semantics, synchronization, quality of service - is important to their correct (re)use. The mandatory syntactic level is included by all current component models. Academic models also employ one of the others, but use different formalisms to represent it. Through this paper, we propose an integrated approach for handling...
Glossaries in Software Requirements Specifications (SRS) aim at establishing a common ground of definitions. However, ambiguous terms as due to tacit knowledge are seldom captured in glossaries. In addition, even if they are captured, they are seldom read, because potential readers are convinced that they already know how the term is defined. Such misunderstandings introduce high risks in projects...
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.