UN-LENCEP: A controlled language for pre-conceptual schema specification

Carlos Mario Zapata Jaramillo, Alexander Gelbukh, Fernando Arango Isaza

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

1 Scopus citations

Abstract

Controlled languages are useful tools for tasks like Knowledge Representation, Technical Documentation Writing, Information Extraction, and so on. There have been some attempts to use controlled languages in software development specification, and these attempts have just tried to describe system specification instead of the stakeholder domain. In this paper we define UN-LENCEP, a controlled language which helps to specify Preconceptual Schemas, a kind of ontology for software development process based on stakeholder discourse. At the end of this paper, we show an example of the use of a UN-LENCEP specification.

Original languageEnglish
Title of host publication7th Jornadas Iberoamericanas de Ingenieria de Software e Ingenieria del Conocimiento 2008, JIISIC 2008
Pages269-276
Number of pages8
StatePublished - 2008
Event7th Jornadas Iberoamericanas de Ingenieria de Software e Ingenieria del Conocimiento 2008, JIISIC 2008 - 7th Ibero-American Symposium on Software Engineering and Knowledge Engineering 2008, JIISIC 2008 - Guayaquil, Ecuador
Duration: 30 Jan 20081 Feb 2008

Publication series

Name7th Jornadas Iberoamericanas de Ingenieria de Software e Ingenieria del Conocimiento 2008, JIISIC 2008

Conference

Conference7th Jornadas Iberoamericanas de Ingenieria de Software e Ingenieria del Conocimiento 2008, JIISIC 2008 - 7th Ibero-American Symposium on Software Engineering and Knowledge Engineering 2008, JIISIC 2008
Country/TerritoryEcuador
CityGuayaquil
Period30/01/081/02/08

Keywords

  • Controlled languages
  • Pre-conceptual schemas
  • Requirements elicitation
  • Software development specification

Fingerprint

Dive into the research topics of 'UN-LENCEP: A controlled language for pre-conceptual schema specification'. Together they form a unique fingerprint.

Cite this