2000
DOI: 10.1590/s0104-65002000000200002
|View full text |Cite
|
Sign up to set email alerts
|

Closing the GAP between organizational requirements and object oriented modeling

Abstract: Requirements Engineering has been considered a key activity in any Software

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
4
0
2

Year Published

2007
2007
2021
2021

Publication Types

Select...
4
1
1

Relationship

0
6

Authors

Journals

citations
Cited by 8 publications
(6 citation statements)
references
References 10 publications
0
4
0
2
Order By: Relevance
“…Na literatura, encontramos trabalhos com propostas para integrar modelos de metas (onde são especificados requisitos organizacionais) e modelos orientados a objetos (OO). Em [Castro et al 2000], os autores criaram um conjunto de regras de transformação de modelos i* para modelos OO usando pUML (precise UML) em conjunto com OCL (Object Constraint Language). O conjunto é formado por seis regras gerais de transformação e esta transformação pode ser realizada com o apoio da extensão GOOD (Goals into Object Oriented Development) para a ferramenta Rational Rose.…”
Section: Mapeamento De Modelo I* Para Sistemas Oounclassified
“…Na literatura, encontramos trabalhos com propostas para integrar modelos de metas (onde são especificados requisitos organizacionais) e modelos orientados a objetos (OO). Em [Castro et al 2000], os autores criaram um conjunto de regras de transformação de modelos i* para modelos OO usando pUML (precise UML) em conjunto com OCL (Object Constraint Language). O conjunto é formado por seis regras gerais de transformação e esta transformação pode ser realizada com o apoio da extensão GOOD (Goals into Object Oriented Development) para a ferramenta Rational Rose.…”
Section: Mapeamento De Modelo I* Para Sistemas Oounclassified
“…• The requirements engineering is a key component in the software development process (Castro et al, 2000). However, in Castro et al opinion, the UML is not well prepared to model the initial requirements (early phase).…”
Section: From Business Process Models To Software Modelsmentioning
confidence: 99%
“…For the initial requirements specification, the authors use the i* technique and for the final requirements specification they adopted the pUML (precise UML), which is used in the OCL (Object Constraint Language) for specifying constraints such as invariants and pre-conditions. The i* is a technique that provides a good understanding of the organization relationships in the business domain (Castro et al, 2000). The pUML provides semantics for the UML basic elements, such as relationships, associations and generalizations.…”
Section: From Business Process Models To Software Modelsmentioning
confidence: 99%
See 1 more Smart Citation
“…* A more complete version of the example can be found in [8,91 The need to offer reasonable prices (captured by software goal Good Prices); this objective can be achieved by offering discount on selected items (softgoal Discount Price), or by getting good deals through the purchase of large quantities of popular CDs (softgoal Volume Purchase [Highs]);…”
Section: Requirements Capturementioning
confidence: 99%