Search

During the R&D project, a huge amount of documents are produced and shared with each other, and also the documents are related to software systems. Without careful management of the relationships, researchers cannot recognize an impact of the changes, which degrades the research quality. This paper presents new types of traceability for the software R&D project including traceability between documents, traceability between a document and its items, traceability between different versions of documents. We examply the traceability of documents in a R&D project. Based on the traceability, the stakeholders of the R&D project are able to recognize and monitor relationships between documents and research outcomes also, it can also eventually contribute to improving the quality of research outcomes and research progress.

For competing with other companies, IT companies are struggling to innovate their capabilities. Every companies invested research or research and development project for developing new technology and new products. Through the research process, there are so many valuable research deliverables. In this paper, we suggested to integrate the Product Data Management (PDM) system with Research Document Management (RDM).

Social BPM is considered as a promising tool to improve the performance of an organization by providing extensible communication tools, informal data handling functions, and knowledge based decision supports. In this study, we developed a Social BPM named ProcessCodi which is integrated by a social network service (SNS), a mind map, and a business process management system (BPMS). Integrating a SNS enables to involve members of the social network into a business process, and a mind map enables to manage the related knowledge as a formal data structure; knowledge tree. A BPMS is a framework to integrate these tools into a process oriented concept. ProcessCodi was implemented in a S/W company and the plausibility are investigated.

Quality control in medical is getting very important issue so that the importance of CDS(Clinical Decision Support) System has been increased. Local clinics as well as big hospitals are required to implement the CDS System. But the cost and complexity of CDS system implementation is so high since many different activities including knowledge authoring, software development, and integrating the legacy system are necessary. In this paper, we suggest the CDS system architecture to be sharable and interoperable and evaluate the availability and efficiency of this architecture.

The Moodle Customization requires correction of interface and functions to fit the characteristics of organization, operation method and characteristics of the students. There are User Management, Lecture Management, Functional Organization management and UX Management as the Moodle Customization methods. You can apply Moodle according to the characteristics of organization by customizing Moodle.

Application lifecycle management (ALM) integrates the lifecycle workflows such as, requirements management, architecture, coding, testing, tracking, and release management. Process automation and seamless traceability across the process are so important. But, different terminology and different model were used to implement the tool for specific workflow so that it is not possible to communicate between the tools. In this paper, we suggest new approach to achieve the seamless traceability and process automation. For these features, knowledge formalization is critical. Evidence-based medicine is good reference architecture to ALM2. Software Engineering ontology is powerful solution to semantic gap between tools and guideline-based process execution environment can be practical solution to process automation. In this paper, we suggest the architecture for automating the ALM using process management technology and guideline-based engineering

Critical value is defined as a result suggesting that the patient is in danger unless appropriate action is taken immediately. We designed an automated reporting system of critical values and evaluated its performance. Fifteen critical values were defined and 2-4 doctors were assigned to receive short message service (SMS).Laboratory results in LIS and EMR were called back to the DIA server. The rule engine named U-brain in the CDSS server was run in real-time and decision if the laboratory data was critical was made. The CDSS system for alerting of laboratory critical values was fast and stable without additional burden to the entire EMR system. Continuous communication with clinicians and feedback of clinical performance are mandatory for the refinement and development of user-friendly CDSS contents. Appropriate clinical parameters are necessary for demonstration of the usefulness of the system.

Recently, clinical field builds various forms of computerized medical knowledge and tries to use it efficiently. In general, to build and reuse knowledge easily, it is needed to build a knowledge repository. Especially, the credibility of knowledge is important in clinical domain. This paper proposes methods for supporting it. To perform it systematically, we propose the method of the knowledge management processes. The methods for knowledge management can serve equal quality, usability and credibility of knowledge. Knowledge management methods consist of 2 methods. They are the knowledge management processes and the specification of the management targets. And this paper proposes the requirement of a knowledge repository and the architecture of the knowledge repository.

This study was designed to evaluate the accuracy and performance of clinical decision support (CDS) architecture which consisted of a knowledge engine and data interface adaptor (DIA) developed as knowledge sharing tools. A laboratory alerting system was selected for the test field and 10 rules represented by SAGE formalism were used. Laboratory results (N=323,455) captured from a tertiary and teaching hospital over three months were retrospectively evaluated. We were able to confirm accuracy, stability, and feasibility of the CDS application architecture and the knowledge engine. However, DIA throughput time suggested the need for further improvements.

Application lifecycle management (ALM) facilitate and integrate facilitate and integrate requirements management, architecture, coding, testing, tracking, and release management. Process automation and seamless traceability among tools are getting important. In this paper, we suggest new approach to achieve the seamless traceability and process automation. For these features, knowledge formalization is critical. Evidence-based medicine is good reference architecture to ALM2. Software Engineering ontology is powerful solution to semantic gap between tools and guideline-based process execution environment can be practical solution to process automation.

Recently, many approaches have been studied to author medical knowledge and verify doctor’s diagnosis based on the specified knowledge. During the verification, intensive access to medical information is unavoidable. Also, the access approach should consider modifiability in order to cover diverse medical information from the variety of hospitals. This paper presents an approach to generating query language from medical knowledge, and shows software architecture for accessing medical information from hospitals by executing generated query languages. Implementation of this architecture has been deployed in a hospital of South Korea so that it shows the feasibility of the architecture.

SPLE is a process to analyze a set of products and to identify the reusable components in the product family. And these components can be used for developing a new product in the product domain. Insurance sales system is software intensive system and the competitive power of software system determines the growth rate of business in insurance market. Sale system of insurance product is main target for improving their competition. Since the number of new insurance product is increasing and time-to-market is getting shorten, the needs for software product line engineering adoption is increased. As new insurance products are released, small-sized projects should be launched to add new software insurance products into existing information system. Since a software product module was implemented for each insurance product, there are so many redundant parts among the software insurance modules. Redundant codes make the problems in updating the already registered insurance products and make the cost of maintenance increasing. Software product line engineering can be the solution for redundancies in software systems and for reducing the cost of maintenance. To adopt the software product line to insurance sales system, 2 areas can be candidates (1) insurance sales system, (2) software insurance products. To smooth the adaptation, software insurance products is the first target for SPLE.

In this paper we present how to use rule for manipulating the variability of a business. We can classify the business component as business domain components and business process components. The most important thing to design the component, designer should identify the variability among the same business components. If we put the variability into the components, we should modify those components whenever we reuse that. It is not easy to modify the component since the user of that component might not be same with the writer. We extend component property to business rules. We define the component property to customize the component execution environment. Like this, we can define the difference business strategy in rules. With our rule engine, the component can use the rule during the component execution time so that the user of component can redefine or rewrite the rules according to their business context. Based on this approach, the reusability of component is improved. In this paper we describe new component architecture including rule component, our rule engine and case study.