Computer-assisted analysis and refinement of informal software requirements documents

Cybulski, Jacob L.; Reed, Karl

doi:10.1109/apsec.1998.733606

Cited by 12 publications

(12 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This is true of community Web sites, site contents and hyperlinkage, source code directories, threaded email and bboard discussion forums, descriptions of known bugs and desired system enhancements, records of multiple system versions, and more. Persistence, hypertext-style organization and linkage, and global access to open software descriptions appear as conditions that do not receive much attention within the classic requirements engineering approaches, with few exceptions [9]. Yet, each of these conditions helps in the communication of open software requirements.…”

Section: Communicating Requirements Vs Global Access To Open Softwarmentioning

confidence: 99%

“…In the four communities examined in this study, software informalisms appear to be the preferred scheme for describing or representing open software requirements. There is no explicit objective or effort to treat these informalisms as "informal software requirements" that should be refined into formal requirements [9,17,22] within any of these communities. Accordingly, we can present an initial classification scheme that inventories the available types of software requirements informalisms that have been found in one or more of the four communities in this study.…”

Section: Informalisms For Open Software System Requirementsmentioning

confidence: 99%

See 1 more Smart Citation

Understanding the requirements for developing open source software systems

Scacchi¹

2002

IEE Proc., Softw.

299

284

View full text Add to dashboard Cite

This study presents an initial set of findings from an empirical study of social processes, technical system configurations, organizational contexts, and interrelationships that give rise to open software. The focus is directed at understanding the requirements for open software development efforts, and how the development of these requirements differs from those traditional to software engineering and requirements engineering. Four open software development communities are described, examined, and compared to help discover what these differences may be. Eight kinds of software informalisms are found to play a critical role in the elicitation, analysis, specification, validation, and management of requirements for developing open software systems. Subsequently, understanding the roles these software informalisms take in a new formulation of the requirements development process for open source software is the focus of this study. This focus enables considering a reformulation of the requirements engineering process and its associated artifacts or (in)formalisms to better account for the requirements for developing open source software systems.

show abstract

Section: Communicating Requirements Vs Global Access To Open Softwarmentioning

confidence: 99%

Section: Informalisms For Open Software System Requirementsmentioning

confidence: 99%

Understanding the requirements for developing open source software systems

Scacchi¹

2002

IEE Proc., Softw.

299

284

View full text Add to dashboard Cite

show abstract

“…This is true of community Web sites, site contents and hyperlinkage, source code directories, threaded email and other online discussion forums, descriptions of known bugs and desired system enhancements, records of multiple system versions, and more. Persistence, hypertext-style organization and linkage, and global access to OSS descriptions appear as conditions that do not receive much attention within the classic requirements engineering approaches, with few exceptions [51]. Yet, each of these conditions helps in the communication of OSS requirements.…”

Section: Global Access To Oss Webs Vs Communicating Requirementsmentioning

confidence: 99%

“…There is no explicit objective or effort to treat these informalisms as "informal software requirements" that should be refined into formal requirements [3], [51], [52] within any of these communities. Accordingly, each of the available types of software requirements informalisms have been found in one or more of the five communities in this study.…”

Section: Informalisms For Describing Oss Requirementsmentioning

confidence: 99%

Understanding Requirements for Open Source Software

Scacchi

2009

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. This study presents findings from an empirical study directed at understanding the roles, forms, and consequences arising in requirements for open source software (OSS) development efforts. Five open source software development communities are described, examined, and compared to help discover what differences may be observed. At least two dozen kinds of software informalisms are found to play a critical role in the elicitation, analysis, specification, validation, and management of requirements for developing OSS systems. Subsequently, understanding the roles these software informalisms take in a new formulation of the requirements development process for OSS is the focus of this study. This focus enables considering a reformulation of the requirements engineering process and its associated artifacts or (in)formalisms to better account for the requirements when developing OSS systems. Other findings identify how OSS requirements are decentralized across multiple informalisms, and to the need for advances in how to specify the capabilities of existing OSS systems.

show abstract

“…7. Cybulski and Reed [19] describe an elicitation method and a supporting management tool that help in analysing and refining requirements by using a parser, semantic networks, a domain-mapping thesaurus, and faceted classification schemes to allow proper formalisation of requirements written in natural language. 8.…”

Section: Related Workmentioning

confidence: 99%

A Feasibility Study of Automated Natural Language Requirements Analysis in Market-Driven Development

Dag

Regnell

Carlshamre

et al. 2002

Requirements Engineering

View full text Add to dashboard Cite

In market-driven software development there is a strong need for support to handle congestion in the requirements engineering process, which may occur as the demand for short time-to-market is combined with a rapid arrival of new requirements from many different sources. Automated analysis of the continuous flow of incoming requirements provides an opportunity to increase the efficiency of the requirements engineering process. This paper presents empirical evaluations of the benefit of automated similarity analysis of textual requirements, where existing information retrieval techniques are used to statistically measure requirements similarity. The results show that automated analysis of similarity among textual requirements is a promising technique that may provide effective support in identifying relationships between requirements.

show abstract

Computer-assisted analysis and refinement of informal software requirements documents

Cited by 12 publications

References 17 publications

Understanding the requirements for developing open source software systems

Understanding the requirements for developing open source software systems

Understanding Requirements for Open Source Software

A Feasibility Study of Automated Natural Language Requirements Analysis in Market-Driven Development

Contact Info

Product

Resources

About