The platform will undergo maintenance on Sep 14 at about 9:30 AM EST and will be unavailable for approximately 1 hour.
2001
DOI: 10.1016/s0950-5849(00)00144-0
|View full text |Cite
|
Sign up to set email alerts
|

Structuring requirement specifications with goals

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
13
0

Year Published

2005
2005
2010
2010

Publication Types

Select...
5
1
1

Relationship

3
4

Authors

Journals

citations
Cited by 36 publications
(13 citation statements)
references
References 29 publications
0
13
0
Order By: Relevance
“…Consequently, it is important to specify not only how system objects interact to achieve the goal of each base use case, but also how these objects interact to implement the crosscutting concerns of each aspectual use case as well as where the effects take places with respect to the aspectual use case's corresponding base use cases. As a continuation of our previous research, [8][9][10]24 we augment the use case speciÞcation with aspectual property to document the responsibility of an aspectual use case. Through the speciÞcation of aspectual property, aspectual behavior can be modeled within the proposed aspectual sequence diagrams together with three types of aspectual interaction operators to perform on the base use cases.…”
Section: Aspectual Behaviors Modelingmentioning
confidence: 99%
“…Consequently, it is important to specify not only how system objects interact to achieve the goal of each base use case, but also how these objects interact to implement the crosscutting concerns of each aspectual use case as well as where the effects take places with respect to the aspectual use case's corresponding base use cases. As a continuation of our previous research, [8][9][10]24 we augment the use case speciÞcation with aspectual property to document the responsibility of an aspectual use case. Through the speciÞcation of aspectual property, aspectual behavior can be modeled within the proposed aspectual sequence diagrams together with three types of aspectual interaction operators to perform on the base use cases.…”
Section: Aspectual Behaviors Modelingmentioning
confidence: 99%
“…Exploring conflicts is not easy, resolving conflicts is even harder. In [25], we have proposed various conflict resolutions based on the root of conflicts: competing resource, divergent expectation and side effects. Conflicts resulting from competing resource and divergent expectation can be resolved by specializing resource, involving agents or their behavior, or introducing an arbitrator to dispatch the resource.…”
Section: The Role Of Conflict-resolvermentioning
confidence: 99%
“…Based on the analysis, various kinds of applicability of design patterns are explored and integrated with our previous work on the goal-driven use case approach to guiding developers to construct the object-oriented design model systematically [25]. There are three main features in our approach:…”
Section: Introductionmentioning
confidence: 99%
“…Rolland and her colleagues 13 proposed a structure for analyzing the requirements based on a verb and its parameters. Lee et al 14 proposed a systematic approach to handling the interaction among nonfunctional requirements and their impacts on the structuring of requirement specifications. Inspired by the Rolland's and Lee's researches, we proposed a goal model to represent the user's intention.…”
Section: Introductionmentioning
confidence: 99%