No full-text available
To read the full-text of this research,
you can request a copy directly from the authors.
Demonstration of augmented lifecycle space in heterogeneous environment
ResearchGate has not been able to resolve any citations for this publication.
Traceability is important knowledge for improving the artifacts of software and systems and processes related to them. Even in a single system, various kinds of artifacts exist. Various kinds of processes also exist, and each of them relates to different kinds of artifacts. Traceability over them has thus large diversity. In addition, developers in each process have different types of purposes to improve their artifacts and process. Research results in traceability have to be categorized and analyzed so that such a developer can choose one of them to achieve his/her purposes. In this paper, we report on the results of Systematic Literature Review (SLR) related to software and systems traceability. Our SLR is preliminary one because we only analyzed articles in ACM digital library and IEEE computer society digital library. We found several interesting trends in traceability research. For example, researches related to creating or maintaining traceability are larger than those related to using it or thinking its strategy. Various kinds of traceability purposes are addressed or assumed in many researches, but some researches do not specify purposes. Purposes related to changes and updates are dominant.
The assessment and improvement of the satisfaction of traceability requirements during the development of software in general and of safety-critical software in particular is demanding and costly. The special requirements are reflected in software process related general and industry specific standards and the popular agile approaches as well. It is imminent, for practical and logical reasons, that there is a need for the automation of the assessment of the completeness and consistency of traceability as far as possible. In addition to highlighting experienced weaknesses of current either homogeneous or heterogeneous tool environments intending to support development lifecycle traceability, this paper outlines new solutions and suggests the exploitation of emerging technologies for the automation of traceability assessment and improvement.
The paper presents a knowledge-based approach to requirements engineering process. We propose an ontology as a tool for requirements specification verification and validation. Requirements types are the classes of the ontology. Requirements statements are the instances. A special structure of classes, the Protégé tool 'DL Query', and relations implemented through a set of slots are intended for checking completeness and consistency of requirements specification.
Software traceability is a sought-after, yet often elusive quality in software-intensive systems. Required in safety-critical systems by many certifying bodies, such as the USA Federal Aviation Authority, software traceability is an essential element of the software development process. In practice, traceability is often conducted in an ad-hoc, after-the-fact manner and, therefore, its benefits are not always fully realized. Over the past decade, researchers have focused on specific areas of the traceability problem, developing more sophisticated tooling, promoting strategic planning, applying information retrieval techniques capable of semi-automating the trace creation and maintenance process, developing new trace query languages and visualization techniques that use trace links, and applying traceability in specific domains such as Model Driven Development, product line systems, and agile project environments. In this paper, we build upon a prior body of work to highlight the state-of-the-art in software traceability, and to present compelling areas of research that need to be addressed.
This paper presents the results of an investigation into the nature and extent of variations between project management practices in six industries. The investigation had the practical purpose of supporting a group of pharmaceutical R&D organizations in their search for an optimum project management model. A total of 10 ‘domains’ was identified using qualitative methods and these formed the basis for a programme of 31 in-depth interviews with knowledgeable project management practitioners in 21 organizations drawn from the six industries. Each interview elicited a quantitative assessment of the practices relating to the domain, using pre-determined scales, and qualitative comments on the practices based on the experiences of the interviewee. Differences between companies and industries were found to exist in each domain. The most highly developed project management models (which might be said to equate to measure of project management maturity) were found in the Petrochemical and Defence industries, which on average scored highly on most dimensions. Other industries (Pharmaceutical R&D, Construction, Telecommunications, and Financial Services) displayed some interesting differences in different domains, but did not display the coherence or scores of the two leading industries.
Different advances have been made in the development of software process improvement (SPI) standards and models, e.g. capability maturity model (CMM), more recently CMMI, and ISO's SPICE. However, these advances have not been matched by equal advances in the adoption of these standards and models in software development which has resulted in limited success for many SPI efforts. The current problem with SPI is not a lack of standard or model, but rather a lack of an effective strategy to successfully implement these standards or models. The importance of SPI implementation demands that it be recognised as a complex process in its own right and that organizations should determine their SPI implementation maturity through an organized set of activities. In the literature, much attention has been paid to “what activities to implement” instead of “how to implement” these activities. We believe that identification of only “what” activities to implement is not sufficient and that knowledge of “how” to implement is also required for successful implementation of SPI programmes.We have adopted a CMMI approach and developed a maturity model for SPI implementation in order to guide organizations in assessing and improving their SPI implementation processes. The basis of this model is what we have studied in the SPI literature and an empirical study we have carried out. In the design of this maturity model we have extended the concept of critical success factors (CSFs). We have conducted CSF interviews with 23 Australian practitioners. We have also analysed CSFs and critical barriers using 50 research articles (published experience reports and case studies). This maturity model has three dimensions––maturity stage dimension, CSF dimension and assessment dimension. It provides a very practical structure with which to assess and improve SPI implementation processes.
Space systems are developed using conservative technologies and processes and respecting requirements and restrictions imposed by specific standards, domain policies, and design and optimization constraints. However, the artefacts produced at each lifecycle phase are not perfect. To overcome this, Independent Software Verification and Validation (ISVV) represents a valuable asset to detect issues, but, a proper and efficient issue classification system is necessary to analyze the root causes, identify the development processes to improve, and assess the efficiency of verification activities. The Orthogonal Defect Classification (ODC) is the most commonly used and adopted classification scheme, but was not originally targeted to engineering issues in critical systems. In this paper we present an empirical study where ODC has been used to classify space domain issues and propose an adaptation of the taxonomy for space systems.
This chapter offers a vision for traceability in software and systems engineering and outlines eight challenges that need to be addressed in order to achieve it. One of these challenges is referred to as the grand challenge of traceability because making traceability ubiquitous in software and systems development (traceability challenge eight) demands progress with all seven other challenges. A model of a generic traceability process is used as a framework through which the goals and requirements of each challenge are expressed. For each requirement, the current status of the traceability research and practice is summarised, and areas of promise are highlighted. This systematic analysis is used to articulate eight major research themes for the traceability community, along with a number of underlying research topics and positive adoption practices for industry. This work is a snapshot of an ongoing and collaborative effort between traceability researchers and practitioners within the Center of Excellence for Software Traceability. It is intended to form a structured agenda for traceability research and practice, a basis for classifying research contributions and a means to track progress in the field.
Regulation is a key concern of industries, consumers, citizens, and governments alike. Building on the success of the first edition, Understanding Regulation, Second Edition provides the reader with an introduction to key debates and discussions in the field of regulation from a number of disciplinary perspectives, looking towards law, economics, business, political science, sociology, and social administration.
The book has been extensively revised and updated to take into account the significant developments and events of the past decade. Containing several new chapters, it has been completely restructured into seven parts, covering: the fundamental issues regarding regulation; different types of regulatory strategies; rules and enforcement; quality and evaluation; regulation at different levels of government; network issues; and concluding thoughts.
A description is given of a software-process maturity framework that has been developed to provide the US Department of Defense with a means to characterize the capabilities of software-development organizations. This software-development process-maturity model reasonably represents the actual ways in which software-development organizations improve. It provides a framework for assessing these organizations and identifying the priority areas for immediate improvement. It also helps identify those places where advanced technology can be most valuable in improving the software-development process. The framework can be used by any software organization to assess its own capabilities and identify the most important areas for improvement.< >
Augmented Lifecycle Space for traceability and consistency enhancement”, Invited session paper: “Junior Cybernetics in Applied Sciences
- J Klespitz
- M Bíró
- L Kovacs
Challenges Experienced by Medical Device Software Organizations while following a Plan-driven SDLC
- mchugh
OSLC Resource Shape: A language for defining constraints on Linked Data
- Arthur G Ryman
- Le Hors Arnaud
- Speicher Steve
OSLC Resource Shape: A language for defining constraints on Linked Data
- ryman