Abstract

Automatically mapping a requirement specification to design model in Software Engineering is an open complex problem. Existing methods use a complex manual process that use the knowledge from the requirement specification/modeling and the design, and try to find a good match between them. The key task done by designers is to convert a natural language based requirement specification (or corresponding UML based representation) into a predominantly computer language based design model—thus the process is very complex as there is a very large gap between our natural language and computer language. Moreover, this is not just a simple language conversion, but rather a complex knowledge conversion that can lead to meaningful design implementation. In this paper, we describe an automated method to map Requirement Model to Design Model and thus automate/partially automate the Structured Design (SD) process. We believe, this is the first logical step in mapping a more complex requirement specification to design model. We call it IRTDM (Intelligent Agent based requirement model to design model mapping). The main theme of IRTDM is to use some AI (Artificial Intelligence) based algorithms, semantic representation using Ontology or Predicate Logic, design structures using some well known design framework and Machine Learning algorithms for learning over time. Semantics help convert natural language based requirement specification (and associated UML representation) into high level design model followed by mapping to design structures. AI method can also be used to convert high level design structures into lower level design which then can be refined further by some manual and/or semi automated process. We emphasize that automation is one of the key ways to minimize the software cost, and is very important for all, especially, for the “Design for the Bottom 90% People” or BOP (Base of the Pyramid People).

Highlights

  • Converting requirement specification or model to design model followed by an implementation is an important part of software engineering, especially for a large scale software

  • Since software cost is an important factor for many organizations, it is important that we keep the software cost minimal

  • We focus on mapping Requirement Model to Architecture

Read more

Summary

Introduction

Converting requirement specification or model to design model followed by an implementation is an important part of software engineering, especially for a large scale software It is both information conversion and knowledge conversion, and it involves both art and science. The various levels of abstractions involved in such mapping (e.g. from requirement model to design model, to architecture, to implementation) make the process even more complex. Since software cost is an important factor for many organizations (it is a key factor for almost all countries as it is a significant part of GDP, Gross Domestic Products), it is important that we keep the software cost minimal. Minimizing software cost will help such countries afford ICT (Information and Communication Technologies) and associated software; and will provide the benefits of the Information Age to such

Objectives
Methods
Conclusion
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call