A Design-Oriented Specification Language for defining software requirements

Lerina Aversano, Angelo Ciampa, Fabio Giovine, Giovanni Moriano, Antonio Pirozzi, Maria Tortorella


The most common difficulty of requirements elicitation is to define all components and aspects of a project by using the natural language without ambiguities, weak phrases and useless descriptions which make project outlines chaotic. In this paper, we present the Design Oriented Specification Language (DOSLang) that aims at reducing the gap existing among the project stakeholders, which are involved into the requirements specification and comprehension activities. The DOSLang language provides a free-form syntax with the introduction of constructs helping project stakeholders to reducing the ambiguity during definitions, descriptions, todos, actions, constraints and all the other aspects related to requirement definition, without sacrificing the ability of specifying loops and conditional constructs, small sets of data type and multiplicity between 'entities'. The DOSLang compiler is designed to be able to create a common baseline, which the project stakeholders can use during the first phases of the project elicitation. DOSLang is suitable for any kind of project that requires a precise description of all of its aspects. Moreover the language was created keeping the possibility to be used by all people working in a project development: from business people to programmers, including customers.



Programming language; requirements engineering; SRS; projects; stakeholders; baseline; compiler; abstract syntax tree; PKI; quality metrics.

Full Text:



L.H. Rosenberg, T.F. Hammer, L.L. Huffman, "Requirements, Testing and Metrics" - In 15th Annual Pacific Northwest Software Quality Conference, 1998

L.H. Rosenberg, T.F. Hammer, "A Methodology for Writing High Quality Requirement Specifications and for Evaluating Existing Ones", NASA Technical Reports Server (NTRS), 1999

A. Umber, I.S. Bajwa, "Minimizing Ambiguity in Natural Language Software Requirements Specification" - Digital Information Management (ICDIM), 2011 Sixth International Conference, 2011

B. Bertran, J. Bruneau, D. Cassou, N. Loriant, E. Balland, C. Consel, "DiaSuite: a Tool Suite To Develop Sense/Compute/Control Applications", Science of Computer Programming, Fourth special issue on Experimental Software and Toolkits, 2012

J. Mylopoulos, J. Castro, "Tropos: A Framework for Requirements-Driven Software Development", Information Systems Engineering: State of the Art and Research Themes, Lecture Notes in Computer Science, 2000

E. Yu, "Modelling Strategic Relationships for Process Reengineering", Ph.D. thesis, Department of Computer Science, University of Toronto, 1995

M. Smialek, T. Straszak, "Facilitating Transition from Requirements to Code with the ReDSeeDS Tool", Requirements Engineering Conference (RE), 20th IEEE International, 2012. http://dx.doi.org/10.1109/re.2012.6345825

A. Hellesoy, Matt Wynne, "The Cucumber Book: Behaviour-Driven Development for Testers and Developers", Pragmatic Bookshelf, 2012, p.313.

G.M. Christel, Kyo C. Kang, "Issues in Requirements Elicitation", Technical Report CMU/SEI-92-TR-0 12 ESC-TR-92-012, 1992

Leite, P.J. Cesar, "A Survey on Requirements Analysis", Advanced Software Engineering Project Technical Report RTP-071, 1987

DOI: http://dx.doi.org/10.21174/josetap.v1i1.30


  • There are currently no refbacks.

ISSN: 2377-3316

CC BY Google Scholar DOAJ  Crossref logo