The Experts below are selected from a list of 149838 Experts worldwide ranked by ideXlab platform
Jos J. M. Trienekens - One of the best experts on this subject based on the ideXlab platform.
-
Quality specification and metrication, results from a case-study in a mission-critical Software Domain
Software Quality Journal, 2010Co-Authors: Jos J. M. Trienekens, Robbert J. G. Kusters, Dennis C. BrusselAbstract:Software quality is of increasing importance in mission-critical embedded\nSoftware systems. Due to the fast growing complexity and accompanying\nrisks of failures of these systems, Software quality needs to be\naddressed explicitly by Software developers, preferably with a systematic\nmethod for an optimal implementation of Software qualities, such\nas reliability, time-behavior and usability. At the Centre of Automation\nof Mission-critical Systems ({CAMS)} of the Dutch Royal Navy, a new\napproach has been defined for Software developers to improve the\nway that they deal with Software quality in the process of mission-critical\nsystems engineering. The stepwise approach is based on both an international\nquality standard for Software product quality, i.e. {ISO9126}, and\non Multi-Criteria Decision Making techniques, i.e. analytical hierarchy\nprocess ({AHP).} The stepwise approach has been validated in a case\nstudy. In particular, the tailoring of the {ISO9126} standard toward\nthe specific {CAMS} development situation, and the applicability\nof {AHP} techniques, from the perspective of Software developers,\nhas been investigated. The case study is carried out in a representative\nSoftware development project, i.e. the Software for combat management\nsystems ({CMS)} of warships. Results of the case study show that\nSoftware developers can explicitly deal with quality on the basis\nof both the {ISO9126} standard and the {AHP} techniques, respectively\nregarding the specification, prioritization and metrication of Software\nproduct quality.
-
PROFES - No Improvement without Learning: Prerequisites for Learning the Relations between Process and Product Quality in Practice
Product Focused Software Process Improvement, 2000Co-Authors: Rini Van Solingen, Egon Berghout, Rj Rob Kusters, Jos J. M. TrienekensAbstract:Generic relationships between process and product quality are rarely available, because such relationships are highly depending on context factors; the impact of a certain process on product quality is often largely influenced by the characteristics of the specific organisation, processes, business Domain, people, timing factors, etc. This does not mean we should stop investigating those relationships, but that we have to look at these context factors and learn these relationships within such a specific context. Creating an organisational structure, in which effective learning is established, is, therefore, a major challenge for organisations in the Software Domain.
Dines Bjørner - One of the best experts on this subject based on the ideXlab platform.
-
Domains as a prerequisite for requirements and Software Domain perspectives & facets, requirements aspects and Software views
Lecture Notes in Computer Science, 1998Co-Authors: Dines BjørnerAbstract:We take Software [systems] engineering to consist of three major phases: Domain engineering, requirements engineering and Software [systems] design engineering. We outline these and emphasise Domain perspectives andfacets, requirements aspects and Software architecture and program organisation views. This paper is the direct result of a US Office of Army Research October 12-14, 1997 workshop on Requirements Targeting Software and Systems Engineering held at Bernried am Staarnberger See, Bavaria, Germany. In consonance with the aims & objectives of that workshop we conclude some subsections with a set of meta-requirements (i.e. requirements to Software engineering, its research, education and practice). The paper is discursive and informal: we identify a number of methodological principles, techniques and tools. Not all such (hence discursive) and not all necessarily formalisable (hence informal). Wrt. the latter: one cannot formalise the principles that are needed in a systematic, well-guided process of selecting and applying techniques and tools in the analysis and synthesis of specifications - whether of Domain, requirements or Software. Instead we are left to conjecture the usefulness of certain such principles, techniques and tools. Sometimes such conjectures are refuted when better principles, techniques and tools are proposed. Some sociological issues of 'formal methods' are summarised (in section 4.5). Since this paper will appear in a workshop proceedings with a number of other papers from that workshop, the paper will not repeat the relevant points made by other workshop participants and supposedly published in their contributions. I refer, amongst several, to contributions made at the workshop by Carl Gunther, Anthony Finkelstein, Michael Jackson, Tom Maibaum and others. On issues of requirements, I have, in particular, benefited much from [83, 82, 111]. The handy book [82] is simply a pearl: delightful and thought provoking!
-
Requirements Targeting Software and Systems Engineering - Domains as a Prerequisite for Requirements and Software Domain Perspectives & Facets, Requirements Aspects and Software Views
Requirements Targeting Software and Systems Engineering, 1998Co-Authors: Dines BjørnerAbstract:We take Software [systems] engineering to consist of three major phases: Domain engineering, requirements engineering and Software [systems] design engineering. We outline these and emphasise Domain perspectives and facets, requirements aspects and Software architecture and program organisation views.
Iman Keivanloo - One of the best experts on this subject based on the ideXlab platform.
-
Context-awareness in the Software Domain-A semantic web enabled modeling approach
Journal of Systems and Software, 2016Co-Authors: Mostafa Erfani, Juergen Rilling, Mohammadnaser Zandi, Iman KeivanlooAbstract:Ontological context model that can be instantiated for the Software Domain.Context that supports information sharing and reuse among tools within the Software Domain.Application examples for the use of the context model in the Software Domain.Evaluation of the model to illustrate the applicability for mentor assignment. Recent years have witnessed rapid advances in the use of contextual information in ubiquitous and ambient computing. Such information improves situated cognition and awareness as well as stakeholders' usage experience. While Domains such as Web 3.0 - the next generation of the web - have made context-awareness a main requirement of their solution space, the Software engineering Domain still lacks the same rate of adoption. In our research, we introduce an ontology based context-aware meta-model that takes advantage of Semantic Web technologies to capture and formalize context information. Providing such formal context representation allows us to make context information an integrated and reusable part of the Software engineering Domain. We present several case studies related to the Software evolution Domain to illustrate the benefit of sharing and reusing context for various Software engineering tasks, such as mentor recommendation, code search, and result ranking.
-
COMPSAC Workshops - Towards an Ontology-Based Context-Aware Meta-model for the Software Domain
2014 IEEE 38th International Computer Software and Applications Conference Workshops, 2014Co-Authors: Mostafa Erfani, Juergen Rilling, Iman KeivanlooAbstract:Over the last decade, contextual modeling has gained on importance due to the wide spread introduction of ubiquitous and mobile computing. Common to these systems is that they integrate contextual information to improve situated cognition and awareness as well as stakeholders' usage experience with these systems. While Domains such as the next generation of the Web - Web 3.0, which shares many commonalities with the Software Domain, have made context-awareness as part of their solution space, the Software Domain still lacks the same rate of adoption. In our research, we introduce an ontology based context- aware meta-model that takes advantage of Semantic Web technologies to capture and formalize different context abstraction levels. We also discuss the applicability of our context modeling approach for various Software applications, including code search and result ranking.
Insup Lee - One of the best experts on this subject based on the ideXlab platform.
-
automated test coverage measurement for reactor protection system Software implemented in function block diagram
Departmental Papers (CIS), 2012Co-Authors: Eunkyoung Jee, Sungdeok Cha, Suin Kim, Insup LeeAbstract:We present FBDTestMeasurer, an automated test coverage measurement tool for function block diagram (FBD) programs which are increasingly used in implementing safety critical systems such as nuclear reactor protection systems. We have defined new structural test coverage criteria for FBD programs in which dataflow-centric characteristics of FBD programs were well reflected. Given an FBD program and a set of test cases, FBDTestMeasurer produces test coverage score and uncovered test requirements with respect to the selected coverage criteria. Visual representation of uncovered data paths enables testers to easily identify which parts of the program need to be tested further. We found many aspects of the FBD logic that were not tested sufficiently when conducting a case study using test cases prepared by Domain experts for reactor protection system Software. Domain experts found this technique and tool highly intuitive and useful to measure the adequacy of FBD testing and generate additional test cases.
-
SAFECOMP - Automated test coverage measurement for reactor protection system Software implemented in function block diagram
Lecture Notes in Computer Science, 2010Co-Authors: Eunkyoung Jee, Sungdeok Cha, Suin Kim, Insup LeeAbstract:We present FBDTestMeasurer, an automated test coverage measurement tool for function block diagram (FBD) programs which are increasingly used in implementing safety critical systems such as nuclear reactor protection systems. We have defined new structural test coverage criteria for FBD programs in which dataflow-centric characteristics of FBD programs were well reflected. Given an FBD program and a set of test cases, FBDTestMeasurer produces test coverage score and uncovered test requirements with respect to the selected coverage criteria. Visual representation of uncovered data paths enables testers to easily identify which parts of the program need to be tested further. We found many aspects of the FBD logic that were not tested sufficiently when conducting a case study using test cases prepared by Domain experts for reactor protection system Software. Domain experts found this technique and tool highly intuitive and useful to measure the adequacy of FBD testing and generate additional test cases.
Jorge Sousa Pinto - One of the best experts on this subject based on the ideXlab platform.
-
Formal Verification With Frama-C: A Case Study in the Space Software Domain
IEEE Transactions on Reliability, 2016Co-Authors: Rovedy Aparecida Busquim E Silva, Nanci Naomi Arai, Luciana Akemi Burgareli, José Maria Parente De Oliveira, Jorge Sousa PintoAbstract:With the increasing importance of Software in the aerospace field, as evidenced by its growing size and complexity, a rigorous and reliable Software verification and validation process must be applied to ensure conformance with the strict requirements of this Software. Although important, traditional validation activities such as testing and simulation can only provide a partial verification of behavior in critical real-time Software systems, and thus, formal verification is an alternative to complement these activities. Two useful formal Software verification approaches are deductive verification and abstract interpretation, which analyze programs statically to identify defects. This paper explores abstract interpretation and deductive verification by employing Frama-C’s value analysis and Jessie plug-ins to verify embedded aerospace control Software. The results indicate that both approaches can be employed in a Software verification process to make Software more reliable.
