Object Behavior Analysis nalysis is the study and modeling of a given problem domain, within the context of stated goals and objectives. It focuses on what a system is supposed to do, rather than how it is supposed to do it (which we consider the design aspects). In addition , it must embody the rule of traceability (why), which justifies the existence of a given result by tying it back to the stated goals and objectives. The components of the problem domain can be described as anything that end users of the system, both humans and machines, view as part of the problem context. This may include technical issues, if the users view such issues as part of the problem. • • • • • • • • • • • • • • • • We want the analysis process to be carried out in a predictable and controllable manner. In taking an object-oriented approach to analysis , our goal on completion is that we have a clear understanding of the behaviors exhibited by the system , the objects that exhibit these behaviors, the relationships among the objects, and how the objects interact with one another (the system dynamics). This must all be specified in a clear and well-defined language of object and behavior names, chosen from the problem domain. In addition, any implementation code must be traceable back to the results of the analysis. This means that the vocabulary and structures apparent in the design and implementation must clearly reflect the vocabulary and structures that result from the analysis. Object-oriented analysis endeavors to model a situation in terms of a collection of interacting entities, each of which provides a well-defined set of behaviors and attributes. Most published approaches describe conceptually similar definitions , although they adopt alternate terminologies [2, 3, 10]. There is a high degree of agreement on the desired structure of the end result; we differ in how to get to the end result. Many approaches recommend first searching for the tangible objects , notably seeking the nouns in a requirements specification and any applicable verbs and adjectives. With nouns as the objects, the message interface is determined from the verbs, and the logical properties are derived from the adjectives. Although this basic approach may work for small systems, it is our experience that it simply will not scale up. First, it assumes that a complete, …

Object Behavior Analysis.

A knowledge engineering approach to knowledge management

Fuzzy set theory has been extensively applied to extend various database models and resulted in numerous contributions, mainly with respect to the popular relational model or to some related form of it. To satisfy the need of modeling complex objects with imprecision and uncertainty, recently many researches have been concentrated on fuzzy object-oriented database models. This paper reviews fuzzy database models, in which fuzzy relational and object-oriented databases are discussed.

A Literature Overview of Fuzzy Database Models

Next generation information system applications require powerful and intelligent information management that necessitates an efficient interaction between database and knowledge base technologies. It is also important for these applications to incorporate uncertainty in data objects, in integrity constraints, and/or in application. In this study, we propose an intelligent object-oriented database architecture, FOOD, which permits the flexible modeling and querying of complex data and knowledge including uncertainty with powerful retrieval capability.

IFOOD: an intelligent fuzzy object-oriented database architecture

Purpose – The aim of this paper is to highlight the application of six sigma, software engineering techniques and simulation to software development with a view to improving the software process and product.Design/methodology/approach – This paper attempts to integrate six sigma and simulation to define, analyse, measure and predict various elements of software development (such as cost, schedule, defects) that influence software quality, thereby helping the software personnel take necessary measures early in the development process to improve the software processes and remove defects. Simulation results provide qualitative and quantitative suggestions on the ways to change the software process to achieve six sigma quality. The integration of six sigma and CMM and the role of knowledge management in software organisations have been taken into account.Findings – Most software organisations operate between 2.3 and 3 sigma level. This paper presents a framework for definition, measurement, and analysis of im...

Confluence of six sigma, simulation and software development

https://www.csie.ntu.edu.tw/~jlee/publication/Information%20Sciende%2099.pdf

Modeling imprecise requirements with fuzzy objects

Recently, the coupling of goal-based and user-centered approaches has resulted in a tremendous impact on the research of software engineering However, there is no systematic way in the extant approaches to handling the effects of requirements on the structuring of software architectures As an attempt towards the investigation of the interactions among goals, scenarios, and software architectures, we proposed, in this paper, a goal-driven architecture trade-off analysis method to analyze and construct software architectures in an incremental manner We also identified criteria for architecture evaluation and verification and explored the possible types of realization of software architectures for goals The proposed approach is illustrated using the problem domain of virtual university environment

Modeling software architectures with goals in virtual university environment

Recently, as more and more mobile devices embedded with intelligent software become part of our daily lives, Open Services Gateway initiative (OSGi) has gained increasing attention in the development of services for such devices. However, services residing in OSGi platforms are devised specifically for the platforms' local bundles. Although several works have enhanced OSGi with various communication mechanisms that enable remote service invocations, two crucial issues pertaining to mobile computing remain to be addressed: One is limited resources of mobile devices, and the other is unstable links experienced with mobile devices. To address these two issues, we propose an itinerary-based mobile agent approach with four major features: To implement mobile agents as OSGi bundles to deliver distributed OSGi services with lower resource consumption; to extend WSDL and WS-BPEL to help developers design mobile agent itineraries; to provide an opportunistic service matchmaking mechanism allowing mobile agents to adapt to context changes at runtime; and to devise asynchronous communication mechanism to enable reliable mobile agent transmissions among mobile devices with dynamic IP addresses and intermittent connection to the Internet. Through experimental evaluations, we demonstrate that both network traffic and turnaround time of our approach are better than those of client-server ones.

Itinerary-Based Mobile Agent as a Basis for Distributed OSGi Services

It is widely recognized that requirements engineering is a knowledge-intensive process and cannot be dealt with using only a few general principles Since knowledge plays a crucial role in software development, software engineers have to describe and organize various aspects of knowledge before the program can be written A recent work by Robillard reveals that software development can be further improved by recognizing the relevant knowledge structures In this paper, we propose the use of a task-based conceptual graphs (TBCB) framework as a basis for automating software development By structuring and operationalizing conceptual graphs, TBCG specifications can be transformed into executable programs automatically To construct a conceptual model, task-based specification methodology is used as the mechanism to structure the knowledge captured in conceptual models, whereas conceptual graphs are adopted as the formalism to express task-based specifications and to provide a reasoning capability for the purpose of automation Once task-based graphs have been constructed and verified, a blackboard system will automatically transform TBCG specifications into a software system composed of database schemas, knowledge base, and user interfaces A meeting scheduling system is used as an illustrative example to demonstrate our approach © 2000 John Wiley & Sons, Inc

Task-based conceptual graphs as a basis for automating software development

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 unified 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. © 2010 Wiley Periodicals, Inc.

/pdf/aspect-enhanced-goal-driven-sequence-diagram-56waz28r26.pdf

Kuo-Hsun Hsu

Papers

Modeling imprecise requirements with fuzzy objects

Modeling software architectures with goals in virtual university environment

Itinerary-Based Mobile Agent as a Basis for Distributed OSGi Services

Task-based conceptual graphs as a basis for automating software development

Aspect-enhanced goal-driven sequence diagram