“…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.…”
Recently, aspect-oriented approaches have resulted in a tremendous impact on the processing of broadly scoped properties during the development of software systems. However, the weaving mechanism of these crosscutting concerns cannot be easily represented with the extant uniÞed modeling language (UML) notation at the early stage of software development life cycle. As an attempt toward the investigation of how the crosscutting behavior takes place, we proposed, in this work, an aspect-enhanced goal-driven approach to modeling the aspectual behavior in UML state transition diagrams and sequence diagrams with the proposed interaction operators based on the aspectual weaving semantics. By introducing the proposed interaction operations in the UML combined fragment, UML sequence diagrams can be further enhanced to support the modeling of the interactions between aspectual and base behavior in the analysis and design stage of software development. To further exemplify our points, the meeting scheduler system is chosen as a vehicle to illustrate the proposed approach. C
“…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.…”
Recently, aspect-oriented approaches have resulted in a tremendous impact on the processing of broadly scoped properties during the development of software systems. However, the weaving mechanism of these crosscutting concerns cannot be easily represented with the extant uniÞed modeling language (UML) notation at the early stage of software development life cycle. As an attempt toward the investigation of how the crosscutting behavior takes place, we proposed, in this work, an aspect-enhanced goal-driven approach to modeling the aspectual behavior in UML state transition diagrams and sequence diagrams with the proposed interaction operators based on the aspectual weaving semantics. By introducing the proposed interaction operations in the UML combined fragment, UML sequence diagrams can be further enhanced to support the modeling of the interactions between aspectual and base behavior in the analysis and design stage of software development. To further exemplify our points, the meeting scheduler system is chosen as a vehicle to illustrate the proposed approach. C
“…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:…”
In recent years, the influences of design patterns on software quality have attracted increasing attention in the area of software engineering, as design patterns encapsulate valuable knowledge to resolve design problems, and more importantly to improve the design quality. One of the key challenges in object-oriented design is how to apply appropriate design patterns during the system development. In this paper, design pattern is analyzed from different perspectives to see how it can facilitate design activities, handle non-functional requirement, solve design problems and resolve design conflicts. Based on the analysis, various kinds of applicability of design patterns are explored and integrated with a goal-driven approach to guiding developers to construct the object-oriented design model in a systematic manner. There are three benefits to the proposed approach: making it easy to meet requirements, helping resolve design conflicts, and facilitating improvement of the design quality.
“…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.…”
We propose a goal-driven approach to model the service request intention in service-oriented systems. The service request intention can be extracted from the user input and modeled by predefined goal models. We identify this problem as the service request intention extraction. If a service-oriented system has the abilities of user's intention extraction and can make some activities to satisfy the extracted intention, the system can provide a more convenient and efficient service for the user. We start the system construction from the view of goal-driven requirements engineering. The requirements specification is generated by the goal-based requirements analysis in which the functional and nonfunctional requirements will be extended with goal models. A set of computable goal models that represent the user requirements is selected and refined as the basis of system services. The designer can also design related system services based on the requirements specification. Based on the proposed intention extraction approach, the user's vague and imprecise intention will be extracted and mapped to computer understandable and computable goal models for representing the intention. A case-based method is developed to implement the intention extraction process. The intention interpretation knowledge is stored in a case base, and the intention interpretation is based on the process of case retrieval and adaptation. A general architecture for an intention-aware service-oriented system is proposed for demonstrating how to apply the proposed approach. C
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.