Proceedings IEEE Joint International Conference on Requirements Engineering
DOI: 10.1109/icre.2002.1048516
|View full text |Cite
|
Sign up to set email alerts
|

Relating software requirements and architectures using problem frames

Abstract: Problem frames provide a means of analyzing and decomposing

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

1
76
0

Publication Types

Select...
5
2

Relationship

0
7

Authors

Journals

citations
Cited by 102 publications
(80 citation statements)
references
References 17 publications
1
76
0
Order By: Relevance
“…Research provides us with different system and requirements modelling techniques (e.g. Yu & Mylopoulos 1994, De Landtsheer et al 2003, Hall et al 2002, Rumbaugh et al 1998). However, further research is needed to synchronise them when modelling complex socio-technical systems.…”
Section: Introductionmentioning
confidence: 99%
“…Research provides us with different system and requirements modelling techniques (e.g. Yu & Mylopoulos 1994, De Landtsheer et al 2003, Hall et al 2002, Rumbaugh et al 1998). However, further research is needed to synchronise them when modelling complex socio-technical systems.…”
Section: Introductionmentioning
confidence: 99%
“…It can be used when moving to the design phase (or even in the detailed specification phase) of the software development as advocated in [5,6]. We see the two approaches as complementary: while [11,18] provide a way to incorporate/reuse domain knowledge in the problem description, we focus on proposing a way to move from the problem description to the solution description.…”
Section: Discussionmentioning
confidence: 99%
“…While in [11,18] a related approach is taken to extend problem frames with architectural concepts, so as to introduce more knowledge and information into problem frames, our approach is to propose architectural patterns dedicated to the basic problem frames. It can be used when moving to the design phase (or even in the detailed specification phase) of the software development as advocated in [5,6].…”
Section: Discussionmentioning
confidence: 99%
See 2 more Smart Citations