面向对象的需求分析及其在MIS建模中的应用

面向对象的需求分析(OORA)是九十年代才开始研究的新技术。本文首先讨论OORA的基本概念,然后分析了几种传统的建模方法,最后提出将OORA应用于管理信息系统(MIS)建模的新思想。     

基于领域本体面向问题的需求分析与领域建模

为了解决传统的以应用领域为目标、以问题解决方案为中心的需求分析方法造成的开发人员与需求人员以及客户三者之间的误解,需求分析不可再次使用进而导致系统开发效率低下,客户满意度低等问题,文中提出了基于本体面向问题进行需求分析的方法。阐述了基于本体面向问题进行需求分析的必要性、本体的相关概念和设计原则、本体的描述语言以及基于LAU建立领域本体的实例与需求分析过程,并论证了利用该方法可进一步提高需求分析的质量。     

基于领域本体面向问题的需求分析与领域建模

为了解决传统的以应用领域为目标、以问题解决方案为中心的需求分析方法造成的开发人员与需求人员以及客户三者之间的误解,需求分析不可再次使用进而导致系统开发效率低下,客户满意度低等问题,文中提出了基于本体面向问题进行需求分析的方法。阐述了基于本体面向问题进行需求分析的必要性、本体的相关概念和设计原则、本体的描述语言以及基于LAU建立领域本体的实例与需求分析过程,并论证了利用该方法可进一步提高需求分析的质量。     

基于本体的领域需求分析方法与模型研究

领域需求分析是实施领域工程的重要内容,由于领域需求分析参与各方对领域知识理解的差异是领域需求分析的主要困难。该文提出了一种基于本体的领域需求分析方法,试图利用本体在知识表达方面形式化、规范化的优势统一领域内各方对知识的理解,最后给出了UML(统一建模语言)建立领域本体的实例与基于本体的领域需求分析的过程。     

本体与UML在领域需求分析中的研究与应用

领域需求分析是实现领域内软件复用的保证,而领域知识的高效表述与有效共享是领域需求分析的前提.为解决领域知识理解与共享的问题,利用本体在领域知识表达方面的优势,研究了一种基于本体与UML的领域需求分析方法,为领域需求各方提供了一种明确的,定义良好且统一的需求表达方式,解决了所谓"通信鸿沟"问题;采用基于UML的领域本体建模方法建立领域本体模型,为本体模型提供了图形化、直观的描述,进而详细分析了基于本体与UML的领域需求分析过程,最后给出了模具产品数据管理系统的领域需求分析过程的实例.     

一种面向方面需求模型的分析与验证方法

建立具有完整性和一致性的需求模型是软件项目成功的基础,验证需求模型是否具有相关性质在软件开发中具有重要的意义.文中针对面向方面文档驱动需求方法中的需求分析过程,给出了关注点建模过程中的若干验证策略,提出了基于本体的关注点模型验证的相关方法,并通过一个实例说明了文中方法的有效性.     

EIS需求分析的困难及方法

ＥＩＳ（ＥｘｅｃｕｔｉｖｅＩｎｆｏｒｍａｔｉｏｎＳｙｓｔｅｍ，经理信息系统）主要面向企业经理及高层管理人员，而经理信息需求分析是ＥＩＳ开发面临的主要问题。本文分析了经理信息需求的特点，讨论了当前几种经理信息需求分析的方法，然后提出了一种基于企业过程思想的经理信息需求分析的方法。     

面向组件对象的软件需求分析

文章提出了面向组件对象的软件需求分析的方法，给出了面向组件对象的需求分析模型。模型由五个主要组件对象组成。     

从时序图描述推导目标描述的方法研究

面向场景的需求建模方法自面世以来,在需求分析过程中被越来越广泛的使用.但是面向场景的需求分析方法在保证需求的一致性和完整性上存在着很大的困难.面向目标的需求分析方法,以目标需求为研究内容,目前已经成功的解决了需求完整性和一致性的判定问题.本文希望将场景描述转化为目标描述,然后通过保证目标的完整性和一致性来保证场景描述的完整性和一致性.因此,本文从场景的时序图描述出发,通过时序图的语义描述提出了一种时序图向操作目标集合的推导方法,并提供了判定推导等价的判定定理.     

基于软件产品线的需求分析研究

软件产品线方法是一种面向特定领域的、大规模、大粒度的软件复用技术.在软件产品线的开发过程中,产品线需求分析是软件产品线开发的关键活动之一,软件产品线需求分析奠定了产品线构架的基础.通过分析软件产品线开发过程和软件产品线需求分析的特点,阐述了软件产品线需求分析方法以及软件产品线需求分析的实践风险.以领域分析和建模为切入点,对软件产品线的领域分析、需求建模和用例建模等关键方法和技术进行了重点的研究.     

面向对象的软件需求分析

本文首先给出了面向对象的软件需求分析与面向过程分析方法的区别，并从软件需求的角度简要地讨论了ＯＯＲＡ所涉及的基本概念；依次评价了ＯＯＲＡ的四种起源。分析了ＯＯＲＡ的基本模型；比较了几种典型的ＯＯＲＡ途径。最后指出了从传统方法转向ＯＯＲＡ的几方面困难。     

Axiom-based ontology matching

Abstract: Managing multiple ontologies is now a core question in most of the applications that require semantic interoperability. The semantic web is surely the most significant application of this report: the current challenge is not to design, develop and deploy domain ontologies but to define semantic correspondences among multiple ontologies covering overlapping domains. In this paper, we introduce a new approach of ontology matching named axiom-based ontology matching. As this approach is founded on the use of axioms, it is mainly dedicated to heavyweight ontologies, but it can also be applied to lightweight ontologies as a complementary approach to the current techniques based on the analysis of natural language expressions, instances and/or taxonomical structures of ontologies. This new matching paradigm is defined in the context of the conceptual graphs model, where the projection (i.e. the main operator for reasoning with conceptual graphs which corresponds to homomorphism of graphs) is used as a means to semantically match the concepts and the relations of two ontologies through the explicit representation of the axioms in terms of conceptual graphs. We also introduce an ontology of representation, called MetaOCGL, dedicated to the reasoning of heavyweight ontologies at the meta-level.     

Applications of ontologies in requirements engineering: a systematic review of the literature

There is an increase use of ontology-driven approaches to support requirements engineering (RE) activities, such as elicitation, analysis, specification, validation and management of requirements. However, the RE community still lacks a comprehensive understanding of how ontologies are used in RE process. Thus, the main objective of this work is to investigate and better understand how ontologies support RE as well as identify to what extent they have been applied to this field. In order to meet our goal, we conducted a systematic literature review (SLR) to identify the primary studies on the use of ontologies in RE, following a predefined review protocol. We then identified the main RE phases addressed, the requirements modelling styles that have been used in conjunction with ontologies, the types of requirements that have been supported by the use of ontologies and the ontology languages that have been adopted. We also examined the types of contributions reported and looked for evidences of the benefits of ontology-driven RE. In summary, the main findings of this work are: (1) there are empirical evidences of the benefits of using ontologies in RE activities both in industry and academy, specially for reducing ambiguity, inconsistency and incompleteness of requirements; (2) the majority of studies only partially address the RE process; (3) there is a great diversity of RE modelling styles supported by ontologies; (4) most studies addressed only functional requirements; (5) several studies describe the use/development of tools to support different types of ontology-driven RE approaches; (6) about half of the studies followed W3C recommendations on ontology-related languages; and (7) a great variety of RE ontologies were identified; nevertheless, none of them has been broadly adopted by the community. Finally, we conclude this work by showing several promising research opportunities that are quite important and interesting but underexplored in current research and practice.     

Assessing semantic annotation activities with formal concept analysis

This paper describes an approach to assessing semantic annotation activities based on formal concept analysis (FCA). In this approach, annotators use taxonomical ontologies created by domain experts to annotate digital resources. Then, using FCA, domain experts are provided with concept lattices that graphically display how their ontologies were used during the semantic annotation process. In consequence, they can advise annotators on how to better use the ontologies, as well as how to refine these ontologies to better suit the needs of the semantic annotators. To illustrate the approach, we describe its implementation in @note, a Rich Internet Application (RIA) for the collaborative annotation of digitized literary texts, we exemplify its use with a case study, and we provide some evaluation results using the method.     

Applying ontology-based blog to detect information system post-development change requests conflicts

Post-development change requests are user requirements for information systems changes after development. Conflicts might occur as contradictive or inconsistent relationships between requests and existing system design. Detecting conflicts in post-developmenet change requests is an important task during requests management processes. To address this topic, this article proposes an ontology-based blog for automatically discovering conflicts in the extended use-case models of requests from users. This study proposed an information system maintenance process. The proposed approach applies ontologies to represent domain knowledge. A set of rules are used to detect conflicts. This study developed a prototype and invited two companies to evaluate it. Usage feedback opinions about ontology-based blog from two companies indicated the usefulness. The ontology-based blog is a relatively new approach which bridge requirements blogs with a formal and machine interpretable representational model. The automatic conflicts detection capability of the ontology-based blog can reduce the labor cost in requirements analysis phase.     

Requirements-oriented methodology for evaluating ontologies

Many applications benefit from the use of a suitable ontology but it can be difficult to determine which ontology is best suited to a particular application. Although ontology evaluation techniques are improving as more measures and methodologies are proposed, the literature contains few specific examples of cohesive evaluation activity that links ontologies, applications and their requirements, and measures and methodologies. In this paper, we present ROMEO, a requirements-oriented methodology for evaluating ontologies, and apply it to the task of evaluating the suitability of some general ontologies (variants of sub-domains of the Wikipedia category structure) for supporting browsing in Wikipedia. The ROMEO methodology identifies requirements that an ontology must satisfy, and maps these requirements to evaluation measures. We validate part of this mapping with a task-based evaluation method involving users, and report on our findings from this user study.     

Reference ontologies to support the development of global production network systems

In competitive and time sensitive market places, organisations are tasked with providing product lifecycle management (PLM) approaches to achieve and maintain competitive advantage, react to change and understand the balance of possible options when making decisions on complex multi-faceted problems, global production networks (GPN) is one such domain in which this applies. When designing and configuring GPN to develop, manufacture and deliver product–service provision, information requirements that affect decision making become more complex. The application of reference ontologies to a domain and its related information requirements can enhance and accelerate the development of new product-service systems with a view towards the seamless interchange of information or interoperability between systems and domains.This paper presents (i) preliminary results for the capture and modelling of end-user information, (ii) an initial higher level reference core ontology for the development of reference ontologies and (iii) the formal logical modelling of Level 1 of the FLEXINET reference ontology using a Common Logic based approach.     

Requirements and languages for the semantic representation of manufacturing systems

In the last years, attention has been devoted to the development of ontologies, which are ICT conceptual models allowing a formal and shared representation of a particular domain of discourse, and to the use of these representations in a variety of contexts, among which also the industrial engineering can be counted. Within the industrial engineering field, the manufacturing domain has not yet seen a wide application of ontologies. This paper firstly shows the use of ontologies for the semantic annotation of a Web Service-based architecture for the control of manufacturing systems; and then contributes to the research field of manufacturing domain ontologies by proposing a thorough literature review and analysis of the available languages supporting such objective. The paper collects the main requirements that semantic languages must meet to be used in the manufacturing domain with the outlined purpose. In fact, the available semantic languages are several and characterized by different features: the paper identifies the most proper ones for the manufacturing domain representation thanks to their analysis against the main requirements. Lastly, the paper shows how the discussed topics are deployed in a real industrial example.     

Ontology-based automated support for goal–use case model analysis

Combining goal-oriented and use case modeling has been proven to be an effective method in requirements elicitation and elaboration. To ensure the quality of such modeled artifacts, a detailed model analysis needs to be performed. However, current requirements engineering approaches generally lack reliable support for automated analysis of consistency, correctness and completeness (3Cs problems) between and within goal models and use case models. In this paper, we present a goal–use case integration framework with tool support to automatically identify such 3Cs problems. Our new framework relies on the use of ontologies of domain knowledge and semantics and our goal–use case integration meta-model. Moreover, functional grammar is employed to enable the semiautomated transformation of natural language specifications into Manchester OWL Syntax for automated reasoning. The evaluation of our tool support shows that for representative example requirements, our approach achieves over 85 % soundness and completeness rates and detects more problems than the benchmark applications.