Generating natural language specifications from UML class diagrams

Early phases of software development are known to be problematic, difficult to manage and errors occurring during these phases are expensive to correct. Many systems have been developed to aid the transition from informal Natural Language requirements to semistructured or formal specifications. Furthermore, consistency checking is seen by many software engineers as the solution to reduce the number of errors occurring during the software development life cycle and allow early verification and validation of software systems. However, this is confined to the models developed during analysis and design and fails to include the early Natural Language requirements. This excludes proper user involvement and creates a gap between the original requirements and the updated and modified models and implementations of the system. To improve this process, we propose a system that generates Natural Language specifications from UML class diagrams. We first investigate the variation of the input language used in naming the components of a class diagram based on the study of a large number of examples from the literature and then develop rules for removing ambiguities in the subset of Natural Language used within UML. We use WordNet,a linguistic ontology, to disambiguate the lexical structures of the UML string names and generate semantically sound sentences. Our system is developed in Java and is tested on an independent though academic case study

Tools for producing formal specifications : a view of current architectures and future directions

During the last decade, one important contribution towards requirements engineering has been the advent of formal specification languages. They offer a well-defined notation that can improve consistency and avoid ambiguity in specifications. However, the process of obtaining formal specifications that are consistent with the requirements is itself a difficult activity. Hence various researchers are developing systems that aid the transition from informal to formal specifications. The kind of problems tackled and the contributions made by these proposed systems are very diverse. This paper brings these studies together to provide a vision for future architectures that aim to aid the transition from informal to formal specifications. The new architecture, which is based on the strengths of existing studies, tackles a number of key issues in requirements engineering such as identifying ambiguities, incompleteness, and reusability. The paper concludes with a discussion of the research problems that need to be addressed in order to realise the proposed architecture

Demonstrative Paradigms in English and Ibibio: Some Contrastive Observations

This paper describes demonstrative paradigms in English and Ibibio based on their syntactic and semantic behaviours, especially with English as the language of education in Nigeria. This study is anchored on Chomsky (1986) generative grammar paradigm to explain the structures of demonstratives in the two languages and argues that the structures resemble and differ from each other in some respects and gives possible linguistic implications for Ibibio speakers of English. While data for English were extracted from English grammar texts, those of Ibibio were extracted by the researcher’s native speaker’s knowledge of the language. From the analyses, it is discovered that while demonstrative paradigm in English is a two-way opposition, Ibibio has a three-way opposition. It explains that all demonstratives in English inflect for person and number whereas of the two classes of demonstratives in Ibibio one class inflects for number while the other does not. It establishes that this grammatical unit functions as subject and determiner in the two languages while in Ibibio it further functions as an article and a verb

A Theory of Structured Propositions

This paper argues that the theory of structured propositions is not undermined by the Russell-Myhill paradox. I develop a theory of structured propositions in which the Russell-Myhill paradox doesn't arise: the theory does not involve ramification or compromises to the underlying logic, but rather rejects common assumptions, encoded in the notation of the $\lambda$-calculus, about what properties and relations can be built. I argue that the structuralist had independent reasons to reject these underlying assumptions. The theory is given both a diagrammatic representation, and a logical representation in a novel language. In the latter half of the paper I turn to some technical questions concerning the treatment of quantification, and demonstrate various equivalences between the diagrammatic and logical representations, and a fragment of the $\lambda$-calculus

Entity Relationship Approach to Knowledge Base Systems.

A unified framework for knowledge base systems is proposed based on Entity-Relationship (ER) approach. Following the analysis and the specification of the real-world using Entity-Relationship approach, the knowledge base is implemented as a first-order logic system, a production system, or a frame-based system by mapping the appropriate symbolic data structures. An approach for analyzing and specifying real-world perceptions must provide appropriate semantic primitives. Therefore, a justification is provided for the semantic primitives proposed in Entity-Relationship approach by considering the fundamental issues in perception. A notation that allows Entity-Relationship approach to be used as a holistic representation is presented. Translation rules are provided for the conversion of ER-diagrams into symbolic data structures of first-order logic systems, production systems, and frame-based systems. The feasibility of using Entity-Relationship approach to support a natural language front-end of a knowledge base system is examined by analyzing the representation of surface and deep structures of a sentence in Entity-Relationship approach

An affinity analysis based CIM-to-PIM transformation

To tackle the problems such as the imperfection and inconsistency in software requirements in traditional Computation Independent Model (CIM) modelling, the low degree of automation as well as the imperfection in the description of Platform Independent Model (PIM) in CIM-to-PIM transforming, in this article, we propose a Business-Process-based CIM modelling method and a CIM-to-PIM transformation approach. Business Process Model is used to express CIM, and UML‘s Sequence Diagram, State Chart Diagram as well as Class Diagram are used to express PIM. Firstly, the users’ requirements are obtained through business process models. We extract use cases from business processes and create use case specifications. A verification mechanism is also added for the use case specification. Secondly, we transform CIMs into PIMs automatically with use case specifications as the inputs as well as combining with use case based thinking, responsibility based thinking and affinity analysis. Finally, by comparing with the methods in other studies, we conclude that methods proposed in this article can ensure model integrity and increase the degree of model transformation automation