Proceedings of the 24th International Conference on Software Engineering - ICSE '02 2002
DOI: 10.1145/581400.581403
|View full text |Cite
|
Sign up to set email alerts
|

Towards large-scale information integration

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Year Published

2003
2003
2015
2015

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 10 publications
(4 citation statements)
references
References 0 publications
0
4
0
Order By: Relevance
“…Complexity. Technical issues such as the sheer number of artefacts to be traced and the complex relationship between artefacts hamper traceability [18,25,26]. Non-functional requirements tracing is particularly complex.…”
Section: Technical Issuesmentioning
confidence: 99%
“…Complexity. Technical issues such as the sheer number of artefacts to be traced and the complex relationship between artefacts hamper traceability [18,25,26]. Non-functional requirements tracing is particularly complex.…”
Section: Technical Issuesmentioning
confidence: 99%
“…This technique is limited to tracing between structured or semi-structured artifacts. Translation techniques meanwhile translate heterogeneous artifacts into a homogeneous format (Anderson et al, 2002). Traceability links can then be automatically generated.…”
Section: Rationale and Related Workmentioning
confidence: 99%
“…The goal of software traceability in software engineering is to discover and manage the relationships that exist between these software artifacts to facilitate the efficient retrieval of relevant information, which is necessary for many software engineering tasks [2,3]. There is a correspondence between this domain and HTN planning; each artifact can be viewed as a primitive/non-primitive task, and relationships between artifacts can be viewed as HTN structures.…”
Section: Introductionmentioning
confidence: 99%