11th IEEE International Enterprise Distributed Object Computing Conference (EDOC 2007) 2007
DOI: 10.1109/edoc.2007.44
|View full text |Cite
|
Sign up to set email alerts
|

Producing a Global Requirement Model from Multiple Requirement Specifications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2008
2008
2022
2022

Publication Types

Select...
4
1
1

Relationship

1
5

Authors

Journals

citations
Cited by 13 publications
(4 citation statements)
references
References 11 publications
(16 reference statements)
0
4
0
Order By: Relevance
“…This corresponds to 4.44% from the total extracted studies. References 10,12,13,18,27–92 are the final articles selected, while the QA scores assigned to each paper is shown in Appendix .…”
Section: Methodsmentioning
confidence: 99%
“…This corresponds to 4.44% from the total extracted studies. References 10,12,13,18,27–92 are the final articles selected, while the QA scores assigned to each paper is shown in Appendix .…”
Section: Methodsmentioning
confidence: 99%
“…Baudry et al [1] introduce a metamodel for requirements and present how they use it on top of a constrained natural language for requirements definition. In [2] they propose a model-driven engineering mechanism to merge different requirement specifications and reveal inconsistencies between them by using their core requirement metamodel. However, their core metamodel is mainly used to produce a global requirements model from a given set of texts.…”
Section: Related Workmentioning
confidence: 99%
“…The formulas in (36) and (37) hold for each model since (allow_lecturer_limit M = has_limit M ) for all models. The satisfaction of R60 excludes the satisfaction of R103 and vice versa.…”
Section: R103mentioning
confidence: 99%
“…On the other hand, our approach covers the static aspects of requirements including non-functional requirements and reasoning on requirements relations. In [37], a model-driven mechanism is proposed to merge different requirement specifications and reveal inconsistencies between them by using a requirements metamodel. The requirements metamodel is mainly used to produce a requirements model from a given requirements document.…”
Section: Requirements Metamodelingmentioning
confidence: 99%