Function Point Extraction Method from Goal and Scenario Based Requirements Text

  • Soonhwang Choi
  • Sooyong Park
  • Vijayan Sugumaran
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3999)

Abstract

Efficient processing of software requirements expressed in natural language is still and active area of research in systems development. Function Point is widely used as a basis to estimate software development cost and schedule. This paper discusses a method for extracting function point from requirements text gathered using the goal and scenario based requirements elicitation technique. The proposed method aims to establish and maintain traceability between function point and requirements text. Text based function point extraction guidance rules have been developed. The proposed method-ology has been applied to Order Processing System development.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Ambriola, V., Gervasi, V.: Processing natural langauge requirements. In: Proceedings of the 12th International Conference on Automated Software Engineering, p. 36. IEEE Computer Society, Los Alamitos (1997)CrossRefGoogle Scholar
  2. 2.
    Albrecht, A.J.: Measuring Application Development Productivity. In: IBM Applications Development Symposium, Monterey CA (1979)Google Scholar
  3. 3.
    Garmus, D., Herron, D.: Function Point Analysis. Addison Wesley, Reading (2001)Google Scholar
  4. 4.
    ISO-IEC, International ISO/IEC Standard 14143-1, Information Technology – Software measurement – Functional size, Part 1: Definition of Concepts (1998)Google Scholar
  5. 5.
    Uemura, T., Kusumoto, S., Inoue, K.: Function Point Measurement Tool for UML Design Specification. In: IEEE METRICS 1999, p. 62 (1999)Google Scholar
  6. 6.
    IFPUG, Function Point Counting Practice Manual Release 4.1.1, International Function Point User Group (2000)Google Scholar
  7. 7.
    Boehm, B., In, H.: Software Cost Option Strategy Tool (S-COST). In: Boehm, B. (ed.) Proceedings of 20th International Computer Software and Applications Conference (COMPSAC 1996), pp. 15–20 (August 1996)Google Scholar
  8. 8.
    Karlsson, J., Ryan, K.: A cost-value approach for prioritizing requirements. IEEE Software 14(5), 67–74 (1997)CrossRefGoogle Scholar
  9. 9.
    Boehm, B.: Software Engineering Economics. Prentice-Hall, Englewood Cliffs (1981)MATHGoogle Scholar
  10. 10.
    Yang, H., Kim, M., Park, S., Sugumaran, V.: A Process and Tool Support for Managing Activity and Resource Conflicts Based on Requirements Classification. In: Montoyo, A., Muńoz, R., Métais, E. (eds.) NLDB 2005. LNCS, vol. 3513, pp. 114–125. Springer, Heidelberg (2005)CrossRefGoogle Scholar
  11. 11.
    Dardenne, A., van Lamsweerde, A., Fickas, S.: Goal-Directed Requirements Acquisition. Science of Computer Programming 20, 3–50 (1993)CrossRefMATHGoogle Scholar
  12. 12.
    Rolland, C., Souveyet, C., Ben Achour, C.: Guiding goal modeling using scenarios. IEEE Transactions on Software Engineering 24, 1055–1071 (1998)CrossRefGoogle Scholar
  13. 13.
    Kim, J., Park, S., Sugumaran, V.: A Linguistics-Based Approach for Use Case Driven Analysis Using Goal and Scenario Authoring. In: Meziane, F., Métais, E. (eds.) NLDB 2004. LNCS, vol. 3136, pp. 159–170. Springer, Heidelberg (2004)CrossRefGoogle Scholar
  14. 14.

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Soonhwang Choi
    • 1
  • Sooyong Park
    • 1
  • Vijayan Sugumaran
    • 2
  1. 1.Department of Computer ScienceSogang UniversitySouth Korea
  2. 2.Department of Decision and Information ScienceOakland UniversityRochesterUSA

Personalised recommendations