Skip to main content

A Proposal of Requirement Definition Method with Patterns for Element / Network Management

  • Conference paper
  • 541 Accesses

Part of the book series: Lecture Notes in Computer Science ((LNCCN,volume 4238))

Abstract

For the efficient development of Operation Support Systems (OSSs), we propose a requirement definition method to help specifiers create high quality specifications easily and quickly. A feature of the method is that it uses requirement definition patterns based on common knowledge. The patterns provide solutions to problems in the definition process and help specifiers. We construct requirement definition patterns for Element / Network Management Systems, such as a pattern with effectiveness to unify sequence diagrams related to system behavior. The method also includes a mechanism to help anyone to use the patterns easily that is characterized in using roles in sequence diagrams. To verify the effectiveness of our proposal, we use two case studies to show that our method has reduced the time needed to create specifications, and has improved their quality.

This is a preview of subscription content, log in via an institution.

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   84.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   109.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Frankel, D.: Model Driven Architecture. John Wiley & Sons, Chichester (2003)

    Google Scholar 

  2. The Standish Group: The CHAOS Report (1994)

    Google Scholar 

  3. Boehm, B.W.: Software Engineering Economics. Prentice Hall, Englewood Cliffs (1981)

    MATH  Google Scholar 

  4. Gamma, E., Helm, R., Johnson, R., Vlissides, J.: Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley, Reading (1995)

    Google Scholar 

  5. Buschmann, F., Meunier, R., Rohnert, H., Sommerlad, P., Stal, M.: Pattern-Oriented Software Architecture: A System of Patterns. John Wiley & Sons, Chichester (1996)

    Google Scholar 

  6. Hagge, L., Lappe, K.: Sharing requirements engineering experience using patterns. IEEE Software 22(1), 24–31 (2005)

    Article  Google Scholar 

  7. Borland Software Corporation: Together, http://www.borland.com/

  8. IEEE: IEEE 830 Documentation Standard for a Software Requirements Specification (1998)

    Google Scholar 

  9. Jacobson, I., Booch, G., Rumbaugh, J.: The Unified Software Development Process. Addison-Wesley, Reading (1999)

    Google Scholar 

  10. ITU-T: ITU-T Recommendation M.3010 (2000)

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2006 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Sato, M., Inoue, M., Inoue, T., Yamamura, T. (2006). A Proposal of Requirement Definition Method with Patterns for Element / Network Management. In: Kim, YT., Takano, M. (eds) Management of Convergence Networks and Services. APNOMS 2006. Lecture Notes in Computer Science, vol 4238. Springer, Berlin, Heidelberg. https://doi.org/10.1007/11876601_22

Download citation

  • DOI: https://doi.org/10.1007/11876601_22

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-45776-3

  • Online ISBN: 978-3-540-46233-0

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics