Kiyoshi Itoh

既に他のシステムで作成した分析情報を再利用する方法として,「要求・設計」情報である業務フローのダイアグラム情報を再利用し,業務フロー分析の作業を効率化する方法を提案する.業務フローを表すダイアグラムとしてはペトリネット図を用いる.似ている業務で情報システムを作成するとき,すでに似たものが開発されている場合,情報システムの「要求・設計」の情報を再び使う可能性が高いので,この「要求・設計」情報の再利用が効果的である可能性が高い.このため,業務フローのダイアグラムで再利用の単位となる「経路」を定義し,自動的に抽出する.これにより抽出した経路を組み合わせて,業務フロー分析の作業が効率化できるような情報の再利用方法を検討する.

STD (State Transition Diagram) is used to analyze the system from "state" and "transition" perspective. But, the existent STD can't describe concepts such as states of two or more personnel, synchronization between personnel and time advance which are necessary to model the collaborative systems. This paper proposes Timed STDs with the three concepts, and models the collaborative systems with this diagram. And the authors developed the simulator to show an animation of transition and synchronization and to analyze the performance parameters such as utilization.

The development of Ontology for Domains and Inter-Domains is considered from the viewpoint of Component and Task. Therefore, the recycling method of described Ontology and the description method of reusable Ontology are examined. The Ontology of Trust of Work is described as an example of the described Ontology. Task Ontology is described along the case grammar and the commitment network. Component Ontology is extracted from Task Ontology, and the relation of the component is described. This description method and the recycling method were implemented with Excel VBA.

当研究では,複数プロジェクトに関わる作業者の割り付けを支援するシステムを提案する.プロジェクトスケジュールを管理する際,複数のプロジェクトが同一の作業者を同時期に求めて競合が発生するケースがある.これによりプロジェクト期間の冗長化を招き,納期遅れ等の障害が見込まれる.従来はその解決のために作業者数や納期の変更で対応してきたが,この方法では大幅なコスト増加を招いてしまう.そこで当研究では,作業者数と納期を変更せずにこの競合状態を解消するリスケジュール法として「タスク分割」を用いる.タスクを分割することで作業者の割り付け案の幅を広げ,競合状態が解消されたリスケジュール案をシステムが提供する.

待ち行列モデルにおけるオントロジを作成した.モデリングには待ち行列モデルをベースにしているものが多くある.しかし,モデリングによっては,待ち行列とは異なった用語や概念が多く存在し,待ち行列の知識があっても,待ち行列とどう対応しているかわからないことがある.たとえばクライアントサーバシステムにおけるペトリネットでは,トランジションは待ち行列におけるサーバファシリティ(窓口)と似たような概念を待っている.そこで,待ち行列をオントロジ化することで概念を与え,一つの例題として,ペトリネットモデルのオントロジを待ち行列オントロジに挿入し,待ち行列との関係を推論できるような仕組みをOWLエディタで実現した.

In this study, we propose the system for the allocation of personnel to multiple projects. Execution of multiple projects often requires the same personnel at the same time interval. This can create conflicts, leading to unexpected delays in the completion of the projects. So far, project manager solves such problems by changing parameters such as the number of workers and the deadline. But it needs more cost. Therefore, the system uses the "task fragmentation" method to solve such problems without changing those parameters. This method gives the project manager greater flexibility in allocating the personnel needed for multiple projects. With this method, multiple projects can be run on a desirable schedule and completed before the deadlines.

In this paper, we discuss about the development of a queuing net work ontology. Waitingline analysis is used in performance evaluation of a variety of systems. The ontology seeks to establish relationships among the different performance metrics that are used in different systems. Further, we analyze a class of Petri nets called server-client Petri nets that can model collaborative systems, and build an additional server-client Petri net sub-ontology. The sub-ontology can be integrated in the main queuing ontology by means of an efficient reasoner.

The authors translated diagrams for System analysis and design to Prolog formed description, and developed the method for Reuse diagrams. As a method to search reusable diagrams, the authors developed the search method with diagram's structure. The search method is not only adaptable to identical type of diagrams but different type of diagrams. The authors developed conversion method for different type of diagrams.

In collaborative Engineering, two or more developers collaborates in analysis and design, and produce various kinds of documents such as diagrams. There are some ways of describing diagrams: The one is that one diagram is described by two or more developer. The other is that each developer describes a part of one diagram then the diagrams are made into one diagram and modified. This paper proposes an environment for supporting developers in distributed place to share and describe diagrams.

The domain expert's heuristics are used in the performance design of collaborative systems which are modeled by client-server timed Petri nets. The entire Petri net model is decomposed into basic primitive structures. The performance design rules that make up the expert system are categorized according to the primitive structure type. The rules are classified as: Diagnostic Rules, Primitive Structure Rules, Upstream Search Rules, Downstream Propagation Rules and Advisory Rules. In tuning the system operation, the expert system follows the policy of local improvement, while keeping the global propagation of adverse effects of tuning to a minimum.

This paper proposes a courseware to support learning systems analysis. Courseware contains tools for supporting analysis and tutorials. Courseware provides an environment for a series of systems analysis. Learning analysis is performed with Petri net, STD, DFD and IDEF0 according to a process of analysis prepared for education of software engineering. Courseware has diagram editors and navigation tool that supports reusing common elements between diagrams. According to instructions of the courseware, learners can analyze systems.

In study of solid geometry, it is essential to look at a solid geometry from many viewpoints and the cross-sectional view of solid geometry. In a class, solid geometry is drawn on text and teacher draws a solid geometry in two-dimensional drawing on blackboard. However, the solid geometry cannot be seen from other viewpoints, and this is one of the reasons to cause difficulty of learning solid geometry. This system asks a learner about solid geometry with questions such as "the shape seen from a certain side including three basic figure", "the solid which is symmetric with respect to a point", and "recognition of position between two or more figures when arranged at an arbitrary position". This system has some functions such as "making of solid used for each question" and "automatic generation of question".

The authors propose a diagrams reuse environment to make System Analysis easy. First, various domains are analyzed with the viewpoint of Generic Tasks which across two or more domains. Then, thesaurus is organized by classifying the vocabulary used in Generic Tasks based on Case Grammar. A user can search for diagrams' information per tasks by using a set of vocabulary. Then, diagrams are described by combining them.

In education of software engineering, it is important to teach analysis processes rather than notations of diagrammatic representations. The analysis processes include viewpoints of the target system, the way of using various diagrams and the combination of diagrams suitable for the target system. In this paper, the authors propose an analysis process using four kinds of diagrammatic representations such as Petri Net, State Transition Diagram, Data Flow Diagram and IDEFO. The analysis process is used in the class for systems analysis. Members of the class describe the diagrams by using the analysis process.

STD(State Transition Diagram) is used to analyze the system from "state" and "transition" perspective. But, the existent STD can't describe concepts such as states of two or more personnel, synchronization between personnel and time advance which are necessary to model the collaborative systems. This paper proposes Timed STDs with the three concepts, and models the collaborative systems with this diagram.

In systems analysis, it is important to analyze and describe the target system from the viewpoint of collaboration task. This paper uses use case diagram at the beginning of the analysis of collaboration task. The authors propose a method to describe use case diagram from the viewpoint of collaboration task. In the method, use case diagram is described for each material or information in the system. A use case expresses a state of material or information. By focusing on lifecycle of each material and information, use cases can be identified easily. Since the use case is described for representing collaboration task, the components described in the use case diagram can be used to next phase in the analysis. The authors developed the editor for describing use case diagram for collaboration task. The editor implements navigator which supports to describe Petri Net and MCM by using components in the use case diagram.

The domain expert's heuristics in the performance improvement of collaborative systems are systematized as qualitative rules. An expert system built by using the qualitative rules, diagnoses the bottlenecks in system operation and suggests improvement in the operation. However, bottlenecks cannot be completely resolved owing to the constraints imposed on system resources. Our strategy is to resolve local bottlenecks, while keeping in check the global state of the system. No local bottleneck may be improved at the cost of incurring fresh bottlenecks elsewhere in the network. Performance improvement task is guided by a set of forward propagation and backward propagation rules; in particular, the changes to be made in the upstream of the network so as to resolve a given bottleneck are guided by the backward propagation rules. The effect on the downstream of the network due to the resolution of the network is given by the forward propagation rules.

In this paper we propose a composite-server model and make use of the knowledge of the intrinsic composition of its service providing units (personnel or equipment) to derive Qualitative knowledge-based rules for its performance evaluation. The composite server model that takes into account the composite nature of service has wider scope in its applications and can be used to represent a variety of system classes. We use this novel concept in the performance design and improvement of collaborative engineering systems. System modeling is done by Multi-Context Map (MCM) technique. MCM is a descriptive model that expresses the collaborative activity performed through the exchange of token, material and information; bottlenecks primarily arise due to the non-uniformity in the flow of token, material and information. Another source of bottlenecks in collaborative engineering systems is the lack or surplus of service-providing units, known as "Perspectives" in the MCM terminology. Bottlenecks due to inappropriate Perspective allocation are resolved by the Qualitative Reasoning approach. We have found this method successful in the performance design, evaluation and improvement of a practical collaborative engineering system presented at the end of this paper.

本稿では,システム化の対象業務を協調業務の観点から捉え,分析するプロセスの提案を行う.この協調業務の分析プロセスでは,対象業務の中でサービスを受ける主体と,サービスを提供する作業主体を捉え,作業主体ごとの作業の流れを記述し,作業主体間でのものや情報のやりとりを分析・記述する.本稿では,協調業務の記述にペトリネットを用いる.著者らは,ペトリネットに協調業務の分析向きに規律を導入した.このペトリネットの記述により,サービスを受ける主体と,サービスを提供する主体の観点からのペトリネットの記述が行える.このペトリネットによる分析・記述を支援するためのEditor, Visualizer, Simulatorを開発した.

In order to build a cross organizational business process model, views and responsibilities of each person or organization involved should be specified. Deliverables, control flows, and Plan-Do-Check structure in the process should also be specified. This paper presents a method of cross organizational business process modeling, which allows us to clarify the roles and responsibilities in the process, using Petri Net and Usecase diagram.

複数部門が関わるビジネスプロセスをモデル化する場合,関与する組織や人のもつそれぞれの観点や責任範囲を明確にする必要ある.また,業務の遂行によって得られる成果物や指示系統,計画,実行,および評価の流れがモデルに表現されることが望ましい.本論文では,ペトリネットとユースケースを利用して,ロールとレスポンシビリティを明確に規定した,ビジネスプロセスモデルの作成方法を提案する.

Process for systems analysis is clarified using two or more types of diagram representations in order to increase the efficiency in systems analysis. It adopts use case diagram. Petri net, IDEF0 diagram as changing systems views and semi-automatic diagram transformations. The entrance examination management system is analyzed as an example.

In study of solid geometry, it is essential to look at a solid geometry from many viewpoints and the cross-sectional view of solid geometry. In a class, teacher draws a solid geometry in two-dimensional drawing on blackboard. The solid geometry can not be seen from other viewpoints. It is difficult to learn solid geometry by using blackboard. In this paper, we propose a tool for supporting the understanding of solid geometry. This tool, Asks a learner about solid geometry with questions such as "the cross-sectional view of solid geometry cut by plane", "the shape seen from a certain side", "the solid which is symmetric with respect to a point". This tool has some functions such as "Rotating a solid in the arbitrary direction only by mouse operation", "Cutting a solid by an arbitrary plane", "Making a solid of revolution formed by an arbitrary curve round an arbitrary axis", "Making a projection of an object on an arbitrary plane".

This paper discusses the design and implementation of a novel system performance improvement Expert System (ES) with a Qualitative inference engine. The motive for using Qualitative Reasoning is to overcome the computational complexity posed by the triple-input-triple-output contexts interactions in the Multi-Context Map (MCM) queuing network which models the system. The ES analyses the GPSS simulation data of system performance, consults the MCM knowledge base of the system, and with its inference engine driven by qualitative rules draws the parameter-tuning plan to resolve bottlenecks. The ES has been successfully applied in improving a typical benchmarking system in Collaboration Engineering.

This paper discusses the design and implementation of a novel system performance improvement Expert System (ES) with a Qualitative inference engine. The motive for using Qualitative Reasoning is to overcome the computational complexity posed by the triple-input-triple-output contexts interactions in the Multi-Context Map (MCM) queuing network which models the system. The ES analyses the GPSS simulation data of system performance, consults the MCM knowledge base of the system, and with its inference engine driven by qualitative rules draws the parameter-tuning plan to resolve bottlenecks. The ES has been successfully applied in improving a typical benchmarking system in Collaboration Engineering.

In collaborative engineering, two or more workers gather at conference which repeats opinion exchange and an argument towards decision-making for engineering. In the conference, various documents, such as plans, drafts, drawings, are delivered and shared among workers, and workers modify or correct the documents. We define this conference as "a collaborative engineering conference", and develop "CMCES (Computer-Mediated Collaborative Engineering System)" as a system that supports engineering collaboration in distributed real-time environment. In addition, we make the trial that applies CMCES to learning software engineering.

Acquiring business process model is performed to analyze business process for improving the efficiency or to systematize the business process with computer. Well business process models are acquired by domain experts. However domain experts don't have enough time to perform analysis because they have their own daily work. In this paper, we propose sheets for describing IDEF0. Acquiring process of IDEF0 is subdivided into nine sheets so that the domain expert can analyze the business process in a limited time. Domain experts can identify the issues in the business process and acquire a model to improve the process.

To make collaboration processes working effectively, it is very important to analyze what collaborators are doing, which position they are, and how they communicate with each other. Multi-Context Map (MCM) and Collaborative Linkage Map (CLM) are developed to meet such demands. These methods analyze each collaborator in precise, so the model consists much important information in the process. In this paper, we propose to extract E-R models, which are widely used to design databases in the early phases, from MCM and CLM. E-R models do not have a standard method of composing, and rely on the designer's intuition. Our extraction provides a method of designing data models.

This report is the record of activities by the working group for Analysis and Modeling. In 1993 and 1994, this group was a research group of IPSJ. Since 1995, this group has been a working group of SigSE of IPSJ.

Domain analysis and modeling(DAM)enables efficient system developments. Domain model which is acquired through DAM process takes various forms such as analysis method, glossary, specifications, library and source codes. Since domain model makes the best use of the domain characteristics for the reuse within that domain, it is highly dependent on the domain and needs extra efforts for reuse to another domain. The authors have recognized common facets acknowledged across several domains and called them generic task. Generic task includes trading task, allocation task, monitoring task, and collaboration task, etc. In order to validate the reusability of generic task beyond a particular domain, this paper deals with prototyping cycle of generic tasks as a domain model to be reused. Prototyping cycle is a method which allows to analyze, design, and evaluate a system in an interactive manner while executing a prototype of the system. Prototyping cycle of the generic task can be reused to different domains. We analyze the domain for academic affairs in terms of collaboration task and trading task and develop a prototyping tool for the domain. The tool integrates the two prototyping cycles of the generic taskes. The tool allows to analyze the system in terms of collaboration task, while simulating and evaluating it in terms of efficiency of collaboration. The output of the analysis in terms of the trading task is obtained in the form of SQL description for the evaluation of database behaviors.

Collaboration task is a process, which involves diversified individual and organizations. They have different perspectives and common resources. Capturing general workflow and state of resources enables collaborators and developers to analyze, identify, and organize collaboration task in the initial stage of system development. We employ Multi-Context Map(MCM)for the description of general workflow. MCM define the various works that exists in collaboration task by combining Context Map(CM). We employ Collaborative Linkage Map(CLM)for the description of state transitions of resources that are transferred among collaborators. CLM indicates state transition of the transmission information and the resources information clearly by combining three kinds of Map, such as Personnel-State Transition Diagram(P-STD), Material-STD(M-STD), and Collaboration-STD(C-STD).

協調作業は複数の作業者と組織による協調的な業務プロセスである.そこに関与する作業者及び組織は, 保有する資源や立場がそれぞれ異なるため, 異なる情報の捉え方をする一方で, 全体の業務として特定の目的を達成することか求められる.協調作業を分析するためには, 業務全体の流れとその業時にかかわる資源(作業者, 物, 情報)の状態変化を分析し, 把握することが必要であると考えられる.協調作業の全体を捉えるためにMulti-Context Map(MCM)を用いた.MCMは, Context Map(CM)を結合して協調作業に存在する様々な作業を定義する.協調作業に関わる作業者, 物, そして情報などの資源の状態変化を捉えるためにCollaborative Linkage Map(CLM)を用いた.CLMは, Personnel-State Transition Diagram(P-STD), Material-STD(M-STD), Collaboration-STD(C-STD)という3種のマップを結合することによって, 業務プロセスにおける伝達情報と資源情報の状態遷移を明示する.

IDEF3 is an business process analysis and modeling methodology which has two different diagrams. PFD (Process Flow Diagram) describes the knowledge of collaborators as a flow of UOBs (Unit Of Behavior). OSTD (Object State Transition Diagram) describes a state translation of objects that characterize the flow. We consider that the business process includes some collaborations among the collaborators. In such process, it is important to describe some relations among the collaborators. In this paper, in order to capture the relations among the collaborators, the authors establish the stepwise construction method of IDEF3 using the collaboration. Describing the relations among the collaborator in PFD, we define a collaboration UOB using each elaboration. In the same way, capturing the relations among the object in OSTD, we define a collaboration state using object state. We check the validity of construction method using the STEP AP221 usage scenario as an example.

This paper proposes a domain model and a related developing process for assignment business. For example the railway business has entities of rail section, workers, and vehicles. To provide transportation business, these entities should be assigned in proper manner. With use of the proposing domain model, the user is led from the perspective view of the whole transportation business to the microscopic view of each assignment task. The authors proposes ECA and APO charts to express this domain model with good understandability, and also reusability to another business.