Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering
DOI: 10.1109/isre.1997.566836
|View full text |Cite
|
Sign up to set email alerts
|

Analogical reuse of requirements frameworks

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
32
0
1

Publication Types

Select...
6
2
1

Relationship

0
9

Authors

Journals

citations
Cited by 48 publications
(33 citation statements)
references
References 22 publications
0
32
0
1
Order By: Relevance
“…Because of this difference, techniques like the faceted classification [10] are of no use to help automatic queries since they represent features of the providers rather than the goals it achieves. Techniques such as analogical software reuse [7] share a representation of components that is based on goals achieved by the software, roles, conditions. To this extent their approach is similar to ours, but it requires a complex compilation of a case to match against.…”
Section: Discussionmentioning
confidence: 99%
“…Because of this difference, techniques like the faceted classification [10] are of no use to help automatic queries since they represent features of the providers rather than the goals it achieves. Techniques such as analogical software reuse [7] share a representation of components that is based on goals achieved by the software, roles, conditions. To this extent their approach is similar to ours, but it requires a complex compilation of a case to match against.…”
Section: Discussionmentioning
confidence: 99%
“…To fill this gap, Maiden and his colleagues introduced and experimented at length with creativity techniques adapted to requirements projects in largescale workshops [16]. These techniques included, analogical reasoning, rule-based idea combination and rich storyboarding [17], [18], [16], and were demonstrated to be effective for generating novel requirements for new systems, albeit in multiday workshops with larger numbers of stakeholders.…”
Section: Related Workmentioning
confidence: 99%
“…§ Generar casos de prueba y oráculos desde la especificación [38][39]. § Soportar la reutilización formal de los componentes mediante la especificación correspondiente [40][41]. § Ser la base para la ingeniería inversa y para la evolución del software desde el código [42].…”
Section: Ventajas De La Formalizaciónunclassified