Both modeling tools are developed as Rational Rose add-in. Teh modeling tool, named OCUM Vectra, is developed to support the OCUM diagram. The modeling tool, named ASREM, is developed to support the CMS diagram. This thesis also presents a scenario descriptive diagram called the Object/Crosscutting/Use Case Maps, including a set of notations for use-case and aspect explanation in the aspects realization process. This thesis presents a new requirements-level diagram called the Crosscutting Stack Model, including a set of notations for modeling the aspects that are extracted by the use-case purification and aspect extraction process. It introduces a new parallel process to the requirements workflow of the unified process. This thesis proposes a requirements model that extends the use-case driven approach. this paradigm at the later development stages. Software requirements, which are the important artifacts in the development process, should be managed using a model for AO to fully support. And this kind of software cannot be solved properly by the object-oriented approach. Thesis (M.Eng.)-Chulalongkorn University, 2002 Due to the fact that aspect-oriented (AO) paradigm can solve the problem of crosscutting concerns in software development. The overall flow of the discussion is in the direction of the evolution of expert systems from numerical programs to highly organized symbolic structures engaged in distinct types of problem-solving and communicating with one another. We will also provide two examples of generic problem-solving types, and show how each type of problem-solving induces an organization of knowledge in the form of a cooperating community of specialists engaged in that problem solving type. V, we will argue that further organizational constructs, such as concepts and types of problem solving, are needed both to construct more powerful expert systems, and to characterize their capabilities. IV, we discuss the several distinct senses and roles that the notion of rules can play and have played in expert systems, and how a failure to keep these separate can cause a great deal of confusion. III is devoted to discussing the increasing need for symbolic content to expert reasoning as the size and demands of the task domain increase i.e., we will analyze why a complete mathematical model of the situation, even if available, will not meet many of the demands placed on expert reasoning. II, we briefly trace the development of the idea of knowledge-based systems in AI. The major line of argument that we will pursue in this paper can be outlined as follows. An evaluation schema is proposed and an evaluation example is demonstrated. Application of the framework to generation of object-interaction designs, represented as sequence diagrams, is illustrated. Generic object-interaction design solutions are represented as Jena rules, which can be instantiated into many domain-specific application contexts. Along with a domain model, requirement artifacts specified in the form of operation contracts are encoded using Web Ontology Language. This paper presents a knowledge-based framework for facilitating object-interaction design, taking into account several commonly occurring design issues, including realization of associations and compositions, handling object creation, and determining appropriate object access paths. An inexperienced system analyst often spends a lot of time and extensive efforts to achieve a good design. Object-interaction design in a software development process is a complex task requiring comprehensive object-oriented design knowledge.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |