A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2017; you can also visit the original URL.
The file type is application/pdf.
Filters
Tracing all around in reengineering
2002
IEEE Software
Preserved Fulltext
In all-around tracing for reengineering, we trace from the old system implementation to its design and requirements during reverse engineering, and from the modified requirements to the new design and ...
We propose tracing "all around"-from existing code to the legacy system's design to its requirements during reverse engineering, and from the modified requirements to the new design and the new code during ...
Acknowledgments We thank the project members involved in the Trade Bridge reengineering effort for their cooperation. ...
doi:10.1109/ms.2002.1003459
fatcat:c6wqyvt4mzanfhqojhp34s4e2e
Applying standard independent verification and validation (IV&V) techniques within an Agile framework: Is there a compatibility issue?
2017
2017 Annual IEEE International Systems Conference (SysCon)
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2020; you can also visit the original URL.
The file type is application/pdf.
Test Design by Inspecting Traces from Scenarios
Verify Software Implementation by Inspecting Traces to Requirements
Verify Software Interface Design by Inspection Against Interface
Requirements ...
-Trace scenarios to software structure
-Trace the scenarios to test design and environment
UH-CL / VT
24
Test Design Agile Variant
• Identify relevant scenarios
• Map requirements to scenarios ...
doi:10.1109/syscon.2017.7934770
dblp:conf/syscon/ArthurD17
fatcat:ohxegjbojvcppmmxg7nzyksqsy
Traceability in the Co-evolution of Architectural Requirements and Design
[chapter]
2011
Relating Software Requirements and Architectures
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2017; you can also visit the original URL.
The file type is application/pdf.
.), Relating Software Requirements and Architectures, ...
Common phenomena such as this occur every day in software development. Three problematic situations often arise that lead to knowledge communication issues in software design. P. Avgeriou et al. ...
, and NSFC under Grant No.60903034, QuASAK: Quality Assurance in Software architecting process using Architectural Knowledge. ...
doi:10.1007/978-3-642-21001-3_4
fatcat:j3xv4ej4rvhbtp5r3wlmvpcduy
An end-to-end industrial software traceability tool
2007
Proceedings of the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering - ESEC-FSE '07
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2017; you can also visit the original URL.
The file type is application/pdf.
Respect group ownership structure
14
End-To-End Traceability Model
Requirements
Software Dev
Life Cycle
High Level Design
Testing
Requirements
Trace Artifacts
MRQ
UC
FR
TC
Workflow ...
Minimize labor hours in tracing -"Just enough traceability" • Each trace link should provide a benefit • Trace information should aids users in SDLC tasks Software Development Life Cycle (SDLC) What Not ...
doi:10.1145/1287624.1287642
dblp:conf/sigsoft/AsuncionFT07
fatcat:tzr4b3zlk5hkje4x6ldcbtksqy
Trace Queries for Safety Requirements in High Assurance Systems
[chapter]
2012
Lecture Notes in Computer Science
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2017; you can also visit the original URL.
The file type is application/pdf.
In particular we present queries that consider formal artifacts, designed to help demonstrate that: 1) identified hazards are addressed in the safetyrelated requirements, and 2) the safety-related requirements ...
In practice, however, the traceability links provided by software producers are often incomplete, inaccurate, and ine↵ective for demonstrating software safety. ...
"software developers must be able to demonstrate traceability of designs against requirements." ...
doi:10.1007/978-3-642-28714-5_16
fatcat:gz75bj7ayzh25d73y5fgkaon5i
Leveraging Design Decisions in Evolving Systems
2012
Softwaretechnik-Trends
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2017; you can also visit the original URL.
The file type is application/pdf.
The trace model that we developed captures design decisions, the references between them, and their related requirements and software entities. ...
EMFTrace 1 ) do not provide sufficient support for tracing design decisions and their origins (e.g. requirements). ...
doi:10.1007/bf03323468
fatcat:ausqgza7wrhi5f5p6kg7qjjbsa
Tracing the Linkage of Several Unified Modelling Language Diagrams in Software Modelling Based on Best Practices
2018
International Journal of Engineering & Technology
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2019; you can also visit the original URL.
The file type is application/pdf.
And also, how to trace the linkage between those diagrams thus meet all software requirements. ...
To ensure the software and the needs of users requires designing software with a good methodology, which can capture a wide range of user needs properly and accurately. ...
Table 1 and Use Case "Feature Extraction"
Tracing Requirements in Class Diagram Class diagram is main diagram which characterizes object oriented software analysis and design, because class diagram ...
doi:10.14419/ijet.v7i2.29.14255
fatcat:g4qn5hrxavc5bbhms7cn5dhy4m
A software engineering schema for data intensive applications
2018
Proceedings of the ACMSE 2018 Conference on - ACMSE '18
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2020; you can also visit the original URL.
The file type is application/pdf.
The features developed by a software engineer (system specification) for a software system may significantly differ from the features required by a user (user requirements) for their envisioned system. ...
In this paper, a software development framework, called SETh, is presented. ...
This knowledge must be extracted to design and construct a reliable, reusable, and maintainable software system. • Backward Tracking and Tracing: One of the problems in software engineering design and ...
doi:10.1145/3190645.3190675
dblp:conf/ACMse/Suthaharan18a
fatcat:gxvzt6ocrjg6nkzayb45oomce4
Tracing All Around
[chapter]
2000
Lecture Notes in Computer Science
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2017; you can also visit the original URL.
The file type is application/pdf.
Typically, no requirements and design specifications exist and, therefore, also no traceability information. ...
In this paper, we argue for completely tracing all around from code over specifications to code in the course of reverse engineering an existing software system and its subsequent redesign and redevelopment ...
Finally, we acknowledge the cooperation by the project members in the course of this reengineering effort. ...
doi:10.1007/3-540-45140-4_24
fatcat:rfzmaqjdsncptp6ktt5ent63cu
Medical device standards' requirements for traceability during the software development lifecycle and implementation of a traceability assessment model
2013
Computer Standards & Interfaces
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2017; you can also visit the original URL.
The file type is application/pdf.
Risk management has an important role in medical device software development as it is important to ensure that safe software is developed. ...
The paper also summarises the findings obtained when a lightweight assessment method (Med-Trace), that we created, based upon the traceability practices within these standards, was implemented in two SME ...
An example is that IEC 62304 does not require detailed design for software of class A, while FDA expects detailed design of all software.
5 Med-Trace assessments and findings
Development of the Med-Trace ...
doi:10.1016/j.csi.2013.07.012
fatcat:hpujdnizvng7bclwqm6c4vqoou
Traceability Types for Mastering Change in Collaborative Software Quality Management
[chapter]
2016
Lecture Notes in Computer Science
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2018; you can also visit the original URL.
The file type is application/pdf.
Software is constantly evolving and to successfully comprehend and manage this evolutionary change is a challenging task which requires traceability support. ...
In this paper we propose a novel approach to traceability as a cornerstone for successful impact analysis and change management, in the context of collaborative software quality management. ...
Furthermore, in [38] traceability across design artifacts in software project, i.e., from product specification to interface requirements specification, software requirement specification and system ...
doi:10.1007/978-3-319-46508-1_13
fatcat:z5oyxqpjsvcvxkf5xfeazpu6nq
Tailoring Software Traceability to Value-Based Needs
[chapter]
2006
Value-Based Software Engineering
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2011; you can also visit the original URL.
The file type is application/pdf.
Software development generates and maintains a wide range of artifacts, such as documentation, requirements, design models, and test scenarios; all of which add value to the understanding of the software ...
Trace dependencies identify the relationships among these artifacts. They contribute to the better understanding of a software system as they link its distributed knowledge. ...
The following discusses how testing helps in the identification of trace dependencies between: • Requirements/design and code • Requirements and requirements • Requirements and design • Design and design ...
doi:10.1007/3-540-29263-2_14
fatcat:w2hzcwxprbdotdvd3jc2hyer5m
A Runtime Framework for Machine-Augmented Software Design Using Unsupervised Self-Learning
2016
2016 IEEE International Conference on Autonomic Computing (ICAC)
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2016; you can also visit the original URL.
The file type is application/pdf.
In each stage it is designed to interact with human engineers, but maintains a leading role in the design directions taken. 1) Requirement stage: Requirements are viewed as an abstract intent for the system ...
FRAMEWORK Our framework considers the major activities in conventional development: specifying requirements; realising those requirements through implementation; and managing/maintaining the system in ...
doi:10.1109/icac.2016.37
dblp:conf/icac/FilhoP16
fatcat:ac3qjerh5zevhe3wkuilsblwlm
Traceability Establishment and Visualization of Software Artefacts in DevOps Practice: A Survey
2019
International Journal of Advanced Computer Science and Applications
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2019; you can also visit the original URL.
The file type is application/pdf.
This paper explores the trace-link creation and visualization between software artefacts, existing tool support, quality aspects and the applicability in a DevOps environment. ...
Accordingly, we conclude that the software artefact traceability is maturing and applying collaboratively in the software process. ...
ACKNOWLEDGMENT The authors acknowledge the support received from the University of Moratuwa, Sri Lanka in publishing this paper. ...
doi:10.14569/ijacsa.2019.0100711
fatcat:y7pgga4l7zcojaflka6xt3wtlm
Toward Requirements and Design Traceability Using Natural Language Processing
2018
European Journal of Engineering Research and Science
Preserved Fulltext
A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2019; you can also visit the original URL.
The file type is application/pdf.
In our research we built a framework that can be used to generate design diagrams from requirements in semi-automatic way, and make traceability between requirements and design phases, and in contrast. ...
Software requirements written in natural languages (NL), Natural Language Processing (NLP) can be used to process requirements. ...
Renuka and et al [27] designed methodology to design traceability Software Requirements Specification (SRS) and Software Design Document (SDD), SRS Trace Item (SRSTI) is the template that populates data ...
doi:10.24018/ejers.2018.3.7.807
fatcat:pwiqpfayyze45ip442i4cctpdu
« Previous
Showing results 1 — 15 out of 526,725 results