65,528 research outputs found
Towards a method for rigorous development of generic requirements patterns
We present work in progress on a method for the engineering, validation and verification of generic requirements using domain engineering and formal methods. The need to develop a generic requirement set for subsequent system instantiation is complicated by the addition of the high levels of verification demanded by safety-critical domains such as avionics. Our chosen application domain is the failure detection and management function for engine control systems: here generic requirements drive a software product line of target systems. A pilot formal specification and design exercise is undertaken on a small (twosensor) system element. This exercise has a number of aims: to support the domain analysis, to gain a view of appropriate design abstractions, for a B novice to gain experience in the B method and tools, and to evaluate the usability and utility of that method.We also present a prototype method for the production and verification of a generic requirement set in our UML-based formal notation, UML-B, and tooling developed in support. The formal verification both of the structural generic requirement set, and of a particular application, is achieved via translation to the formal specification language, B, using our U2B and ProB tools
Exigences dâutilisabilitĂ© pour les outils dâingĂ©nierie des exigences
International audienceRequirement engineering (RE) tools are necessary for several reasons: they allow engineers to manage an increasing amount of information, to maintain traceability between requirements, solution and tests, and to evaluate requirement change impact on the solution and test.\This article proposes an analysis of system engineering practices in the aeronautical industry, with a focus on requirement engineering. From contextual interviews, we have identified scenarios reflecting system engineers's activity related to the editing and management of requirements. The analysis of these scenarios has allowed us to elicit usability requirements for RE tools, more precise than "user-friendly". These usability requirements will feed our future work on RE tool design.Les outils dâingĂ©nierie des exigences sont nĂ©cessaires pour plusieurs raisons : ils permettent de gĂ©rer un nombre croissant dâinformations, de maintenir la traçabilitĂ© entre exigences, solution et tests, dâĂ©valuer lâimpact dâun changement dâexigences sur la solution et les tests. Cet article propose une analyse des pratiques en ingĂ©nierie systĂšme dans lâindustrie aĂ©ronautique, centrĂ©e sur lâingĂ©nierie des exigences. A partir de la rĂ©alisation dâenquĂȘtes contextuelles, nous avons identifiĂ© des scĂ©narios reprĂ©sentatifs de lâactivitĂ© des ingĂ©nieurs systĂšme sur la rĂ©daction et la gestion des exigences. Lâanalyse de ces scĂ©narios nous a permis dâidentifier des exigences en termes dâutilisabilitĂ© des outils, plus prĂ©cises que « user - friendliness », qui alimenteront la conception de nouveaux outils dâingĂ©nierie des exigences
A comparison of two SPLE tools : Pure::Variants and Clafer tools
In software product line engineering (SPLE), parts of developed software is made variable in order to be able to build a whole range of software products at the same time. This is widely known to have a number of potential benefits such as saving costs when the product line is large enough. However, managing variability in software introduces challenges that are not well addressed by tools used in conventional software engineering, and specialized tools are needed.
Research questions: 1) What are the most important requirements for SPLE tools for a small-to-medium sized organisation aiming to experiment with SPLE? 2) How well those requirements are met in two specific SPLE tools, Pure::Variants and Clafer tools? 3) How do the studied tools compare against each other when it comes to their suitability for the chosen context (a digital board game platform)? 4) How common requirements for SPL tools can be generalized to be applicable for both graphical and text-based tools?
A list of requirements is first obtained from literature and then used as a basis for an experiment where support for each requirement is tried out with both tools. Then a part of an example product line is developed with both tools and the experiences reported on. Both tools were found to support the list of requirements quite well, although there were some usability problems and not everything could be tested due to technical issues. Based on developing the example, both tools were found to have their own strengths and weaknesses probably partly resulting from one being GUI-based and one textual.
ACM Computing Classification System (CCS):
(1) CCS â Software and its engineering â Software creation and management â Software development techniques â Reusability â Software product lines
(2) CCS â Software and its engineering â Software notations and tools â Software configuration management and version control system
A Conceptual UX-aware Model of Requirements
User eXperience (UX) is becoming increasingly important for success of
software products. Yet, many companies still face various challenges in their
work with UX. Part of these challenges relate to inadequate knowledge and
awareness of UX and that current UX models are commonly not practical nor well
integrated into existing Software Engineering (SE) models and concepts.
Therefore, we present a conceptual UX-aware model of requirements for software
development practitioners. This layered model shows the interrelation between
UX and functional and quality requirements. The model is developed based on
current models of UX and software quality characteristics. Through the model we
highlight the main differences between various requirement types in particular
essentially subjective and accidentally subjective quality requirements. We
also present the result of an initial validation of the model through
interviews with 12 practitioners and researchers. Our results show that the
model can raise practitioners' knowledge and awareness of UX in particular in
relation to requirement and testing activities. It can also facilitate
UX-related communication among stakeholders with different backgrounds.Comment: 6th International Working Conference on Human-Centred Software
Engineerin
Modeling of system knowledge for efficient agile manufacturing : tool evaluation, selection and implementation scenario in SMEs
In the manufacturing world, knowledge is fundamental in order to achieve effective and efficient real time decision making. In order to make manufacturing system knowledge available to the decision maker it has to be first captured and then modelled. Therefore tools that provide a suitable means for capturing and representation of manufacturing system knowledge are required in several types of industrial sectors and types of companyâs (large, SME). A literature review about best practice for capturing requirements for simulation development and system knowledge modeling has been conducted. The aim of this study was to select the best tool for manufacturing system knowledge modelling in an open-source environment. In order to select this tool, different criteria were selected, based on which several tools were analyzed and rated. An exemplary use case was then developed using the selected tool, Systems Modeling Language (SysML). Therefore, the best practice has been studied, evaluated, selected and then applied to two industrial use cases by the use of a selected opens source tool.peer-reviewe
- âŠ