References of Natural_Language_Processing_in_Reverse_Specification

@InProceedings{	  nanduri.rugaber:requirements,
  author	= {Sastry Nanduri and Spencer Rugaber},
  title		= {Requirements Validation via Natural Language Parsing},
  booktitle	= {Proceedings of the 28th Hawaii International Conference on
		  System Sciences},
  address	= {Wailea, Maui, Hawaii},
  year		= {1995},
  month		= jan,
  abstract	= {Object Oriented Analysis (OOA) has become a popular method
		  for analyzing system requirements. Unfortunately however,
		  none of the current version of OOA have included a
		  validation technique tailored to the object oriented
		  approach. Most, instead, merely recommend document reviews
		  without specifying what kinds of problems to look for. This
		  paper explores the question by applying a natural language
		  parser to a requirement document, extracting candidate
		  objects, methods and associations, composing them into an
		  object model diagram, and then comparing the results to
		  those determined by manual OOA. To do this, we have adapted
		  an automated natural language parser and used it to examine
		  several high level specifications. The results indicate
		  that with a modest amount of effort, our technique can give
		  valuable feedback to the analyst.},
  ftp		= {ftp.cc.gatech.edu//pub/groups/reverse/repository/hicss.ps}
		  ,
  class		= {Software_Reverse_Engineering, Reverse_Specification,
		  Natural_Language_Processing_in_Reverse_Specification}
}

@Article{	  nanduri.rugaber:requirements*1,
  author	= {Sastry Nanduri and Spencer Rugaber},
  title		= {Requirements Validation via Automated Natural Language
		  Parsing},
  journal	= {Journal of MIS},
  year		= {1995},
  month		= jan,
  note		= {UpDated version of Nanduri:95a submitted for publication},
  abstract	= {Object Oriented Analysis (OOA) has become a popular method
		  for analyzing system requirements. Unfortunately however,
		  none of the current versions of OOA have included a
		  validation technique tailored to the object oriented
		  approach. Most, instead, merely recommend document reviews
		  without specifying what kinds of problems to look for. This
		  paper explores the question by applying a natural language
		  parser to a requirement document, extracting candidate
		  objects, methods and associations, composing them into an
		  object model diagram, and then comparing the results to
		  those determined by manual OOA. To do this, we have adapted
		  an automated natural language parser and used it to examine
		  several high level specifications. The results indicate
		  that with a modest amount of effort, our technique can give
		  valuable feedback to the analyst.},
  ftp		= {ftp.cc.gatech.edu//pub/groups/reverse/repository/jmis.ps},
  class		= {Software_Reverse_Engineering, Reverse_Specification,
		  Natural_Language_Processing_in_Reverse_Specification}
}

@InProceedings{	  wilde.gomez.ea:locating*1,
  author	= {Norman Wilde and Juan A. Gomez and Thomas Gust and Douglas
		  Strasburg},
  title		= {Locating User Functionality in Old Code},
  pages		= {200-205},
  booktitle	= {Proceedings of the  International Conference on Software
		  Maintenance ~1992},
  year		= {1992},
  publisher	= {IEEE Computer Society Press},
  month		= nov,
  abstract	= {Software maintainers often have to recover requirements
		  traceability in old code. In other words, they need to
		  answer the question: 'In which parts of this program is
		  functionality X implemented?' This paper proposes a
		  methodology for answering this question based on the use of
		  carefully designed test cases as probes into the code.
		  While the methodology is not applicable to all kinds of
		  requirements and may not find all relevant code components,
		  it should often provide a maintainer with good starting
		  points for studying a large and poorly documented system.
		  Two formulations of the methodology are suggested and some
		  encouraging experimental results are presented from a case
		  study of a typical old program.},
  class		= {Software_Reverse_Engineering, Reverse_Specification,
		  Natural_Language_Processing_in_Reverse_Specification}
}