基于大数据挖掘的高校知识管理系统

当前高校大数据应用面临数据集成困难、成果难以应用、知识难以管理等问题,急需加以解决.本文结合知识管理与软件工程方法,首先设计了基于CRISP-DM的高校大数据挖掘流程;在此基础上,设计了高校知识管理系统的总体架构和功能模型;然后对主要功能模型进行了详细设计,并对其关键技术——数据集成方法、大数据挖掘技术进行了分析和设计;最后给出了该系统的开发环境及测试情况.该系统设计方案对高校大数据应用提供了参考和借鉴.     

浅谈数据挖掘技术在软件工程中的应用

近年来,各个软件开发组织为了对他们的过程和数据更好的了解,收集大量产品和过程数据已经成为标准惯例。这就需要从数据库中抽取新的、重要和有用的信息,这个过程就是数据挖掘。当前,将数据挖掘的技术应用于软件工程是非常有用并且合理的。文中对数据挖掘的使用进行了综述,包括相关概念、过程、技术和研究现状的介绍,并在此基础上结合了作者的评论和观点对软件工程中数据挖掘的应用特点进行浅析和探讨。     

Improving academic software engineering projects: A comparative study of academic and industry projects

A project course in software engineering is often part of the curriculum in computer engineering or computer science. This paper studies the relationship between academic and industrial projects in software engineering. The purpose is to compare the practices followed in a project-course approach with the practices of professional software engineers. The approach is to compare the measurements obtained from academic and industrial projects. The critical factors regarding the process, the people and the project are discussed. The structure of the software processes and the measurement tools are presented. The data analyses show that the academic projects are found to be strongly dominated by programming activities. Based on the data from the industrial projects, we formulate seven recommendations to improve the software engineering practices in academic projects. They are related to management, predevelopment, development, testing, reviews documentation and team activities. The concluding remarks discuss some of the actions that could be taken to improve academic projects.     

集成逆向工程系统的误差分析与检测

针对当前企业产品快速开发和创新设计的要求,构建了具有误差分析与检测功能的集成逆向工程系统框架。通过对所存在的误差进行分析,以便对整个系统进行实时的闭环的检测和修复。在分析系统框架的基础上,提出两个不同的误差求取方案并简化了相应的误差模型,同时给出了模型配准算法。通过两个具体案例,展示了不同方案的模型配准过程。     

Toward objective software process information: experiences from a case study

A critical problem in software development is the monitoring, control and improvement in the processes of software developers. Software processes are often not explicitly modeled, and manuals to support the development work contain abstract guidelines and procedures. Consequently, there are huge differences between ‘actual’ and ‘official’ processes: “the actual process is what you do, with all its omissions, mistakes, and oversights. The official process is what the book, i.e., a quality manual, says you are supposed to do” (Humphrey in A discipline for software engineering. Addison-Wesley, New York, 1995). Software developers lack support to identify, analyze and better understand their processes. Consequently, process improvements are often not based on an in-depth understanding of the ‘actual’ processes, but on organization-wide improvement programs or ad hoc initiatives of individual developers. In this paper, we show that, based on particular data from software development projects, the underlying software development processes can be extracted and that automatically more realistic process models can be constructed. This is called software process mining (Rubin et al. in Process mining framework for software processes. Software process dynamics and agility. Springer Berlin, Heidelberg, 2007). The goal of process mining is to better understand the development processes, to compare constructed process models with the ‘official’ guidelines and procedures in quality manuals and, subsequently, to improve development processes. This paper reports on process mining case studies in a large industrial company in The Netherlands. The subject of the process mining is a particular process: the change control board (CCB) process. The results of process mining are fed back to practice in order to subsequently improve the CCB process.     

Defining assessment projects and scenarios for policy support: Use of ontology in Integrated Assessment and Modelling

Integrated Assessment and Modelling (IAM) provides an interdisciplinary approach to support ex-ante decision-making by combining quantitative models representing different systems and scales into a framework for integrated assessment. Scenarios in IAM are developed in the interaction between scientists and stakeholders to explore possible pathways of future development. As IAM typically combines models from different disciplines, there is a clear need for a consistent definition and implementation of scenarios across models, policy problems and scales. This paper presents such a unified conceptualization for scenario and assessment projects. We demonstrate the use of common ontologies in building this unified conceptualization, e.g. a common ontology on assessment projects and scenarios. The common ontology and the process of ontology engineering are used in a case study, which refers to the development of SEAMLESS-IF, an integrated modelling framework to assess agricultural and environmental policy options as to their contribution to sustainable development. The presented common ontology on assessment projects and scenarios can be reused by IAM consortia and if required, adapted by using the process of ontology engineering as proposed in this paper.     

Modeling process-related RBAC models with extended UML activity models

Context

Business processes are an important source for the engineering of customized software systems and are constantly gaining attention in the area of software engineering as well as in the area of information and system security. While the need to integrate processes and role-based access control (RBAC) models has been repeatedly identified in research and practice, standard process modeling languages do not provide corresponding language elements.

Objective

In this paper, we are concerned with the definition of an integrated approach for modeling processes and process-related RBAC models - including roles, role hierarchies, statically and dynamically mutual exclusive tasks, as well as binding of duty constraints on tasks.

Method

We specify a formal metamodel for process-related RBAC models. Based on this formal model, we define a domain-specific extension for a standard modeling language.

Results

Our formal metamodel is generic and can be used to extend arbitrary process modeling languages. To demonstrate our approach, we present a corresponding extension for UML2 activity models. The name of our extension is Business Activities. Moreover, we implemented a library and runtime engine that can manage Business Activity runtime models and enforce the different policies and constraints in a software system.

Conclusion

The definition of process-related RBAC models at the modeling-level is an important prerequisite for the thorough implementation and enforcement of corresponding policies and constraints in a software system. We identified the need for modeling support of process-related RBAC models from our experience in real-world role engineering projects and case studies. The Business Activities approach presented in this paper is successfully applied in role engineering projects.     

Agent-based framework for integrated facility engineering

An agent-based framework for the development of integrated facility engineering environments in support of collaborative design is introduced. This framework aims at integrating design software by allowing better software interoperability. Within their framework, design agents represent various existing design and planning systems that communicate their design information and knowledge partially and incrementally using the Agent Communication Language (ACL). ACL is a formal language proposed as a communication standard for disparate software. It is based on a logic-based language called Knowledge Interchange Format (KIF) and a message protocol called Knowledge Query Manipulation Language (KQML). Design agents are linked and their communication of design information is coordinated via system programs called facilitators in a federation architecture. The federation architecture specifies the way design agents and facilitators communicate in an integrated software environment. In concert with pursuing fundamental research concepts, we have been developing an integrated design software environment that spans different phases of the facility life cycle. This environment serves to demonstrate the primary aspects of this research methodology. In this paper, we first discuss the integration problem and review related research projects. We then present the major aspects of agent-based software engineering methodology and its application to integrated facility engineering. A highlight of the current integrated design environment development is given to illustrate the advantages of this approach. Finally, we summarize and discuss some of the important research issues in light of previous research.     

Software system engineering: a tutorial

Applying system engineering principles specifically to the development of large, complex software systems provides a powerful tool for process and product management. The application of system engineering principles to the development of a computer software system produces activities, tasks, and procedures called software system engineering, or SwSE. Many practitioners consider SwSE to be a special case of system engineering, and others consider it to be part of software engineering. However, we can argue that SwSE is a distinct and powerful tool for managing the technical development of large software projects. The article integrates the definitions and processes from the IEEE software engineering standards into the SwSE process     

STEP-based product modeling system for remote collaborative reverse engineering

Production of high-quality products with lower cost and shorter time-to-market is an important challenge in the face of increased global competition, and reverse engineering plays an important role in accelerating product and process development. With the advent of new technologies such as network, multimedia and product data exchange standard STEP (STandard for Exchange of Product model data), there are many advantages to adopt these technologies to enhance the competitiveness of an enterprise. In this paper, a product information recording module for reverse engineering is developed to enhance the performance of product development. A STEP development tool, ST-Developer, and Visual C++ were used to develop this module, which can be used to record key information expeditiously during a collaborative process, and can also be used for further exchange of information, or as the basis for manufacturability evaluation. In this paper, the developed STEP-based information recording system is further integrated with the conventional Computer Supported Cooperative Work methods such as videoconferencing and application-sharing to form a remote collaborative reverse engineering system, which can provides a new strategy for an enterprise to speed up the product development cycle, reducing production cost, as well as sharing knowledge and experience.     

软件工程数据挖掘研究进展

随着计算机软件的规模不断扩大,手工获取、开发和维护软件所需的信息越来越困难。数据挖掘技术可从软件工程数据中自动发现所需信息,加快软件开发进程。对软件工程数据挖掘的研究进展进行了综述。概述了软件工程数据挖掘的基本概念与技术挑战;详细评述了在软件工程各个阶段,数据挖掘技术所能发现的信息/知识,以及获取这些信息/知识的意义、难点、步骤和方法,重点介绍了数据预处理和数据表示方法;对软件工程数据挖掘研究的发展趋势进行了展望。     

A cost model to estimate the effort of data mining projects (DMCoMo)

CRISP-DM is the standard to develop Data Mining projects. CRISP-DM proposes processes and tasks that you have to carry out to develop a Data Mining project. A task proposed by CRISP-DM is the cost estimation of the Data Mining project.     

Requirements engineering within a large-scale security-oriented research project: lessons learned

Requirements engineering has been recognized as a fundamental phase of the software engineering process. Nevertheless, the elicitation and analysis of requirements are often left aside in favor of architecture-driven software development. This tendency, however, can lead to issues that may affect the success of a project. This paper presents our experience gained in the elicitation and analysis of requirements in a large-scale security-oriented European research project, which was originally conceived as an architecture-driven project. In particular, we illustrate the challenges that can be faced in large-scale research projects and consider the applicability of existing best practices and off-the-shelf methodologies with respect to the needs of such projects. We then discuss how those practices and methods can be integrated into the requirements engineering process and possibly improved to address the identified challenges. Finally, we summarize the lessons learned from our experience and the benefits that a proper requirements analysis can bring to a project.     

How ontologies are made: Studying the hidden social dynamics behind collaborative ontology engineering projects

Traditionally, evaluation methods in the field of semantic technologies have focused on the end result of ontology engineering efforts, mainly, on evaluating ontologies and their corresponding qualities and characteristics. This focus has led to the development of a whole arsenal of ontology-evaluation techniques that investigate the quality of ontologies as a product. In this paper, we aim to shed light on the process of ontology engineering construction by introducing and applying a set of measures to analyze hidden social dynamics. We argue that especially for ontologies which are constructed collaboratively, understanding the social processes that have led to their construction is critical not only in understanding but consequently also in evaluating the ontologies. With the work presented in this paper, we aim to expose the texture of collaborative ontology engineering processes that is otherwise left invisible. Using historical change-log data, we unveil qualitative differences and commonalities between different collaborative ontology engineering projects. Explaining and understanding these differences will help us to better comprehend the role and importance of social factors in collaborative ontology engineering projects. We hope that our analysis will spur a new line of evaluation techniques that view ontologies not as the static result of deliberations among domain experts, but as a dynamic, collaborative and iterative process that needs to be understood, evaluated and managed in itself. We believe that advances in this direction would help our community to expand the existing arsenal of ontology evaluation techniques towards more holistic approaches.     

石化企业生产计划与能量系统集成研究

应用并行工程方法对生产计划与能量系统的集成进行了分析,提出了用于确定业务流程和信息流的业务过程模型,明确了系统的并行特性,采用并行工程方法建立了并行业务过程模型,并确定了用于数据建模的数据流,从而为集成效据库管理和集成软件系统的开发奠定了基础。     

面向数据库的化工软件集成环境的设计

对于化工领域,用户若能够在一个软件集成环境上对现有的化工软件进行集成,则可以很大程度上节省用户软件二次开发或掌握集成技术所耗费的人力物力。本文试图研究开发一种化工软件集成的环境。利用Windows自身的特点,以及其管理应用程序的一般方法,设计了化工软件的集成环境。该集成环境由界面集成模块、代码集成模块、数据集成模块和数据库管理子系统4个模块组成,对于4个模块分别给出了界面集成策略、代码集成策略、数据集成策略、数据库和数据库管理子系统的建立策略。     

Understanding the characteristics of quality for software engineering processes: A Grounded Theory investigation

ContextSoftware engineering organizations routinely define and implement processes to support, guide and control project execution. An assumption underlying this process-centric approach to business improvement is that the quality of the process will influence the quality, cost and time-to-release of the software produced. A critical question thus arises of what constitutes quality for software engineering processes.ObjectiveTo identify criteria used by experienced practitioners to judge the quality of software engineering processes and to understand how knowledge of these criteria and their relationships may be useful for those undertaking software process improvement activities.MethodInterviews were conducted with 17 experienced software engineering practitioners from a range of geographies, roles and industry sectors. Published reports from 30 software process improvement case-studies were selected from multiple peer-reviewed software journals. A qualitative Grounded Theory-based methodology was employed to systematically analyze the collected data to synthesize a model of quality for software engineering processes.ResultsThe synthesized model suggests that practitioners perceive the overall quality of a software engineering process based on four quality attributes: suitability, usability, manageability and evolvability. Furthermore, these judgments are influenced by key properties related to the semantic content, structure, representation and enactment of that process. The model indicates that these attributes correspond to particular organizational perspectives and that these differing views may explain role-based conflicts in the judgement of process quality.ConclusionConsensus exists amongst practitioners about which characteristics of software engineering process quality most influence project outcomes. The model presented provides a terminological framework that can facilitate precise discussion of software engineering process issues and a set of criteria that can support activities for software process definition, evaluation and improvement. The potential exists for further development of this model to facilitate optimization of process properties to match organizational needs.     

Formal methods software engineering for the CARA system

This paper discusses the application of formal methods software engineering (FMSE) to the development of the Computer Automated Resuscitation A (CARA) medical device at Walter Reed Army Institute of Research. Because this system is potentially life critical, a high level of quality was required. A formal engineering approach to the software development activities was chosen to satisfy this need. Specifically, a technique called sequence enumeration was applied to elicit and refine requirements while deriving a formal specification. The fundamentals of the specification process that was used on the project are described along with a brief summary of the project experience in the development and testing phases. The project employed recent advances in Cleanroom software engineering methods along with older box-structured development and usage-model-based statistical testing techniques.