Results 241 to 250 of about 55,186 (301)

An axiomatic system engineering design method based on NSGA-II algorithm applied to complex systems. [PDF]

Sci Rep
Zhang X, Zhang Q, Zhao Q, Zhao S, Zhao Y, Guo Y, Zhao Z, Song L.   +7 more
europepmc   +1 more source

Some of the next articles are maybe not open access.

Related searches:

Requirements Traceability

2010
This chapter presents a research about the Software Requirements Traceability. The main elements of traceability, definitions, problems and prospects are presented. The chapter is organized by topics and its beginning is a review about requirements engineering, its categories (Elicitation, Analysis and Negotiation, Documentation, Validation, and ...
Elias Canhadas Genvigir, Nandamudi Lankalapalli Vijaykumar   +1 more
openaire   +2 more sources

Trust-Based Requirements Traceability

2011 IEEE 19th International Conference on Program Comprehension, 2011
Information retrieval (IR) approaches have proven useful in recovering traceability links between free-text documentation and source code. IR-based traceability recovery approaches produce ranked lists of traceability links between pieces of documentation and source code.
Nasir Ali, Yann-Gaël Gueheneuc, Giuliano Antoniol   +2 more
openaire   +2 more sources

Towards requirements traceability models

Proceedings of the 1995 International Symposium and Workshop on Systems Engineering of Computer Based Systems, 2002
As the current literature or standards do not provide a comprehensive model of Requirements Traceability, the quality and current of traceability information captured in current practice varies widely, with much of the information out-dated and useless.
B. Ramesh, D. Dwiggins, G. DeVries, M. Edwards   +3 more
openaire   +1 more source

Reuse through Requirements Traceability

2008 The Third International Conference on Software Engineering Advances, 2008
The Reuse of code artefacts can make development quicker, cheaper and more robust, but is complex and has many pitfalls: Code artefacts must exist, be available, be found, be understood, be valid and finally be integrated. Many software developers try to ensure that artefacts meet these requirements through a process of making code "reusable." If the ...
Rob Pooley, Craig Warren
openaire   +1 more source