Citation Context

...nt need for experimentation aimed at validating the effectiveness of all software engineering abstraction techniques and methods including object-oriented techniques. This paper and a companion paper =-=[30]-=- are derived from the first author’s Ph.D. thesis [29], which describes an attempt to fulfill the need identified by Hatton, Kaindl, and Kramer with respect to one particular OOA method, the Use Case ...

Citation Context

...dology with the Symbiosis tool support, to derive a syntactically and semantically correct and complete design model that fully conforms to textual requirements. Keywords. Requirements, Natural Language, Fact Oriented Modeling, Model Driven Engineering, Object Model and Co-evolution. 1 Introduction Requirements are typically written in natural language and therefore ambiguity is unavoidable. Transitioning from textual and ambiguous requirements to design (e.g., represented as a design model) is usually done manually by domain experts based on their tacit knowledge. Automated approaches (e.g., [11, 13, 14]) have been proposed in the literature to ease this process; however to obtain a correct and complete design model, most of these approaches rely on the manual refinement of an automatically generated design model from requirements. The manual refinement of the generated model requires additional effort from users having knowledge on modeling notations of the design model, and needs a round trip solution to ensure the synchronization of the design model and the requirements after the refinement is performed. These challenges hinder the practical application of these approaches. In this paper, ...

Citation Context

...laims it is. Here, traditional OOA is a scenario-based OOA, such as that described by Larman [17]. In response to these difficulties, we introduced in a second work, hereinafter called the UCUM paper =-=[27]-=-, an OOA method called the Use Case Unification Method (UCUM). In UCUM, a functional model, in the form of a statechart [11], of the entire domain of a computer-based system (CBS) is built from its us...

Citation Context

... claims it is. Here, traditional OOA is a scenariobased OOA, such as that described by Larman [5]. In response to these difficulties, we introduced in a second work, hereinafter called the UCUM paper =-=[6]-=-, an OOA method called the Use Case Unification Method (UCUM). In UCUM, a functional model, in the form of a statechart [7], of the entire domain of a computer-based system (CBS) is built from its use...

Citation Context

...eptual analysis. Note that we consider OOD completely distinct from OOA and self-sufficient, and none of the conclusions of this paper apply to OOD. 9 7 Related Work and Counter Indications The paper =-=[27]-=- describes related work by Glinz; Whittle and Schumann; and Harel, Kugler, and Pnueli [11, 29, 14] whose qualitative conclusions generally agree with those of our work. The present results showing the...