J. Mylopoulos, L. Chung, and E. Yu. From object-oriented to goal-oriented requirements analysis. Communications of the ACM, 42(1):31--37, 1999.  Home/Search   Document Not in Database   Summary   ACM   TOC   Related Articles   Check

....not only because of the system size but also because it is a very well known domain. Actually, we were pleasantly surprised with the considerable number of changes that were introduced due to the use of the framework. 6. Conclusion By using a conceptual modelling point of view, Mylopoulos et al. [23] showed that, although the object oriented approach, in particular the UML standard, significantly advances the state of the practice in requirements modelling , it fails to take into consideration non functional requirements. The article proposes the adoption of a goal oriented method, with ....

Mylopoulos J, Chung L, Yu E. From object-oriented to goaloriented requirements analysis. Commun ACM 1999;42(1):31--37

.... What representational structures are appropriate for systematically recording the results of such actions As pointed out in [6] a goal oriented approach to requirements (such as [3] may work better wrt. non functional requirements than use case driven approaches (such as [11] However, [18] points out that goal oriented analysis and objectoriented analysis complement each other. Thus one can fruitfully employ the goal tree approach to nonfunctional requirements [3] in our work using UML. Speci cally, we propose to combine a use case driven approach as in [11] for the functional ....

J. Mylopoulos, L. Chung, and E. Yu. From object-oriented to goal-oriented requirements analysis. Communications of the ACM, 42(1):31-37, 1999.

....systems. J ur01] gave some initial ideas on how to use UML to develop security critical systems (without actually de ning an extension pro le) For more material on UMLsec see http: www4.in.tum.de umlsec. J ur02d] gives a process for applying UMLsec using goal trees pro ting from work in [MCY99]. Distributed system modeling with UML is considered in [Kob01] FH97] de nes role based access control rights from object oriented use cases. WW01] gives an approach similar to ours but using the notation of the CASE tool AutoFocus. Also relevant is the work towards a formal semantics of UML ....

J. Mylopoulos, L. Chung, and E. Yu. From object-oriented to goal-oriented requirements analysis. Communications of the ACM, 42(1):31-37, 1999.

....least one set of system interaction use cases for each user goal I have identified [Fow97, p. 45] The prominent tendency in software modeling research has been to abstract programming constructs up to requirements level rather than propagate requirements abstractions down to programming level [My199] Requirements engineering research has increasingly recognized the leading role played by goals in the RE process [Yue87, Rob89, Be91, Dar91, My192, Jar93, Zav97b] Such recognition has led to a whole stream of research on goal modeling, goal specification, and goal based reasoning for multiple ....

....TrainSpeed Position NoSuddenStopOfPreceedingTrain The second subgoal above could be assigned to the OnBoardTrainController agent. This alternative would give rise to a fully distributed system. As suggested before, qualitative reasoning techniques in the style of [My199] might be applied to the softgoals identified in Figure 1 to help making choices among alternatives. Deriving agent interfaces Let us now assume that the goal Maintain[SafeCmdMsg] at the bottom of the tree in Annex 1 has been actually assigned to the Speed AccelerationControlSystem agent. The ....

J. Mylopoulos, L. Chung and E. Yu, "From Object-Oriented to Goal-Oriented Requirements Analysis", Communications of the ACM, Vol. 42 No. 1, January 1999, 31-37.

....of another paradigm, even if they were possible, are not usually feasible in practice in view of the time and cost constraints and size of projects nowadays. Mostly, the CMs used are those with which developers are familiar, called for by individual standards or even, as specified by Mylopoulos [74], the models that are in fashion . So, in the era when the structured approach was in vogue, techniques such as DFDs were used for conceptual modelling, whereas, today, with the rise of object oriented programming and design, techniques like object diagrams, interaction diagrams, etc. are ....

J. Mylopoulos, L. Chung, E. Yu, From object-oriented to goal-oriented requirements analysis. Communications of the ACM, vol. 42, no. 1, 1999.

....decisions, runtime architectures, platforms and other characteristics. The subject of domain analysis is modeling common and variant requirements across family members. Implicit variants also arise in traditional analysis of single system requirements. Goal Oriented requirement analysis method [12 ] calls for explicit representation of early decisions related to functional and non functional requirements. These decisions affect each other and without proper analysis model, it is easy to overlook the impact of various decisions on the whole system. From Goal Oriented perspective, at the ....

Mylopoulos, J., Chung, L. and Yu "From Object-Oriented to Goal-Oriented Requirements Analysis", CACM, January 1999/Vol. 42, No. 1, pp.31-37

....Ontario, N2L 3G1, CANADA Tel. 519) 888 4567 x5388 dsvetinovic, migod uwaterloo.ca ABSTRACT Several recent achievements in software architecture and requirements engineering are based on the study and use of quality attributes; these include goal driven requirements engineering processes [1, 14], Architecture Tradeoff Analysis Method (ATAM) 7] and Attribute Based Architectural Styles [13] This paper presents an initial study of the evolution of the systems in terms of quality attributes. The purpose of the study is to put the knowledge about evolution in the form directly usable by ....

....and use of quality attributes has made many contributions to software engineering practice. The goal oriented requirement engineering processes have helped capture a wider range of requirements then previously possible, improve the requirements traceability, and facilitate the process in general [14]. The Attribute Based Architecture Styles (ABAS) have allowed qualitative reasoning about the use of a particular architectural style [13] Architecture Tradeoff Analysis (ATA) method relies upon the use of quality attributes to analyze and express the architectural tradeoffs [7] The quality ....

J. Mylopoulos, L. Cheung, and E. Yu. From Object-Oriented to Goal-Oriented Requirements Analysis. Communications of ACM, Vol. 42, No. 1, (January

.... requirements analysis method in [3, 4] Lee and Xue have developed a goal driven use case analysis method [50] Mylopoulos and his colleagues analyse requirements from the point of view of satisficing softgoals, for which there is no clear cut criterion as to whether they have been satisfied [57]. They also refer to the work of Herbert Simon when selecting the purpose of satisficing, as I have done in this thesis. Van Lamsweerde and Letier have developed a very interesting conceptual model (see for example [82] which combines goals, assumptions, agents, objects and operations, and uses ....

Mylopoulos, J., Chung, L., and Yu, E. From object-oriented to goal-oriented requirements analysis. Communications of the ACM 42, 1 (Jan. 1999), 31--37.

....and formalized are programming concepts most often, data and operations. It is time to raise the level of abstraction and conceptual richness found in informal requirements documents such as, e.g. goals and their refinements, agents and their responsibilities, alternatives, and so forth [Fea87, Fic92, Dar93, Myl98, Myl99]. Isolation. With a few exceptions mentioned before, formal specification techniques are isolated from other software products and processes both vertically and horizontally. Vertical isolation: specification techniques generally pay no attention to what upstream products in the software ....

J. Mylopoulos, L. Chung and E. Yu, "From Object-Oriented to Goal-Oriented Requirements Analysis", Communications of the ACM, Vol. 42 No. 1, January 1999, 31-37.

....between those phases) they now tend towards a standard set of notations [Rum99] with built in extension mechanisms, which hopefully will in the end have a precise semantics. However, the concepts and structuring mechanisms supported essentially emerged by abstraction from the programming field [Myl99] the same way as structured analysis came out by abstraction from structured programming techniques. In particular, the why concerns in the early stages of requirements engineering practice [Hic74, Ros77b, Mun81, Ber91] are not addressed. The aim of this section is to illustrate the benefits of ....

....The second subgoal above could be assigned to the OnBoardTrainController agent. This alternative would give rise to a fully distributed system. To help making choices among alternatives, qualitative reasoning techniques might be applied to the softgoals identified in Figure 1 [Myl99]. Deriving agent interfaces Let us now assume that the goal Maintain[SafeCmdMsg] at the bottom of the tree in Annex 1 has been actually assigned to the Speed AccelerationControlSystem agent. The interfaces of this agent in terms of monitored and controlled variables can be derived from the ....

J. Mylopoulos, L. Chung and E. Yu, "From Object-Oriented to Goal-Oriented Requirements Analysis", Communications of the ACM, Vol. 42 No. 1, January 1999, 31-37.

No context found.

J. Mylopoulos, L. Chung, and E. Yu. From object-oriented to goal-oriented requirements analysis. Communications of the ACM, 42(1):31--37, Jan. 1999.

....builds on these earlier work with a focus on dealing with NFRs. Our work adopts the distinctions between NFR and FR goals, but incorporates FR goals to establish alternative functional elaborations, and for relating operationalizing softgoals to them during design, as initially outlined in [27]. Our work therefore falls within the area of goaloriented requirement engineering [28,29] where goals are used to identify, analyze and refine requirements and serve as selection criteria for solution specifications. Our approach also relates to the area of requirements traceability support ....

Mylopoulos J. Chung L. Yu E. From object-oriented to goal-oriented requirements analysis. Communications of the ACM 1999;42(1): 31-37.

....are met, then the higher goal will be sufficiently met. Or means the higher goal will be sufficiently met if any of its subgoals are met. During system analysis and design, softgoals such as profitability and safety are systematically refined until they can be operationalized and implemented [6]. Unlike functional goals, nonfunctional qualities represented as softgoals frequently interact or interfere with each other, so the graph of contributions is usually not a strict tree structure [4] 3. STUDY OF TRUST IN SMART CARD BASED SYSTEM We now use i to model some aspects of trust in the ....

J. Mylopoulos, L. Chung, and E. Yu, From Object-Oriented to Goal-Oriented Requirements Analysis, Communications of the ACM, 42(1): 31-37, January 1999.

....e.g. visualization, animation, simulation, verification, support for reasoning (e.g. qualitative, quantitative, case based, etc. and basic management facilities (maintaining design history, traceability, navigation, query, retrieval, version and change management, etc. The NFR framework [MCY99] [CNYM 00] for example, treats non functional requirements such as performance, reliability, usability, etc. as goals applied to various aspects of a system. These are to be incrementally elaborated and refined until specific techniques for addressing them are identified. Each potential solution ....

J. Mylopoulos, L. Chung, and E. Yu. From Object-Oriented to Goal-Oriented Requirements Analysis. Communications of the ACM, 42(1): 31-37, January 1999.

....modeling, beginning with Feather (1987) and continuing with recent proposals, such as Dardenne (1993) and Chung (1993) Software nonfunctional requirements, such as software usability, security, reliability, user friendlines, performance, etc. can be modeled using softgoals (Chung, 1993; Mylopoulos, Chung Yu, 1999). Softgoals are goals whose criteria for satisfaction are not crisply defined a priori. The softgoal concept extends intentional ontologies for capturing design rationale (Potts Bruns, 1988) Making available intentional information such as pro and con arguments and resulting decisions can be ....

....management, and not just to process data or information. Many advances contribute to taking information systems beyond mere data into the realm of knowledge. These include: cooperative query processing (Chu et al. 1996; Jurisica, 1999) similarity based retrieval and browsing (Jurisica, Glasgow Mylopoulos, 1999), data mining and knowledge discovery (Jurisica et al. 1998) text understanding (Hahn, Romacker Schulz, 1999; Riloff, 1996) data translation services (Gruber, 1993) and knowledge sharing (Orthner, Scherrer Dahlen, 1994) to name a few. However, the key to providing useful support for ....

Mylopoulos, J., Chung, L. & Yu, E. (1999). From Object-Oriented to Goal-Oriented Requirements Analysis. Communications of the ACM, 42(1): 31-37.

No context found.

J. Mylopoulos, L. Chung, and E. Yu. From object-oriented to goal-oriented requirements analysis. Communications of the ACM, 42(1):31--37, 1999.

No context found.

J. Mylopoulos, L. Cheung, and E. Yu. From object-oriented to goal-oriented requirements analysis. Communications of ACM, Vol. 42, No. 1, 1999.

No context found.

J. Mylopoulos, L. Chung, and E. Yu. From object-oriented to goal-oriented requirements analysis. Communications of the ACM, 42(1):31--37, January 1999.

No context found.

J. Mylopoulos, L. Chung, and E. Yu. From object-oriented to goal-oriented requirements analysis. Communications of the ACM, pages 31--37, Jnauary 1999.

No context found.

J. Mylopoulos, L. Chung, E. Yu, From object-oriented to goal-oriented requirements analysis, Commun. ACM 42 (1) (1999) 31--37.

No context found.

J. Mylopoulos, L. Chung, & E. Yu, "From Object-Oriented to Goal-Oriented Requirements Analysis," Communication of the ACM, vol. 42, pp. 31--37, 1999.

No context found.

J. Mylopoulos, L. Chung, and E. Yu. From object-oriented to goal-oriented requirements analysis. Communications of the ACM, 42(1):31--37, January 1999.

No context found.

J. Mylopoulos, L. Cheung, and E. Yu. From object-oriented to goal-oriented requirements analysis. Communications of ACM, Vol. 42, No. 1, 1999.

No context found.

J. Mylopoulos, L. Chung & E. Yu, From Object-Oriented to Goal-Oriented Requirements Analysis,Communication of the ACM, vol. 42, pp. 31-37, 1999

No context found.

J. Mylopoulos, L. Chung, and E. Yu, "From ObjectOriented to Goal-Oriented Requirements Analysis," Comm. ACM, vol. 42, no. 1, Jan. 1999, pp. 31-37.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC