skip to main content
10.1145/2181101.2181114acmotherconferencesArticle/Chapter ViewAbstractPublication PagesprofesConference Proceedingsconference-collections
research-article

An agile requirements elicitation approach based on NFRs and business process models for micro-businesses

Authors Info & Claims
Published:20 June 2011Publication History

ABSTRACT

Software empowers micro-businesses to be more competitive - be it accounting software, point-of-sales software, e-commerce software, and the like. Before having such software, micro-businesses must express their requirements properly to the software developers first. Since micro-businesses have restrictions with their budget, manpower, and technical exposure to software, some trade-offs must be addressed. In such case, a practical requirements approach must be used. This approach must be inexpensive, non-technical, and must not involve too much manpower. This paper will show how a software development company, Pentathlon Systems Resources Incorporated, has applied an agile requirements elicitation approach to a micro-business, an amusement arcade. This paper will demonstrate how several models and techniques such as goals, business process models, patterns, and non-functional requirements, have helped in defining the software requirements of the micro-business.

References

  1. Young, R. 2004. Requirements Engineering Handbook. Artech House, Incorporated, Norwood, Massachusetts.Google ScholarGoogle Scholar
  2. Respect-IT. 2007. KAOS Tutorial Version 1.0. URL = http://www.objectiver.com/fileadmin/download/document s/KaosTutorial.pdf (Last accessed on March 10, 2011)Google ScholarGoogle Scholar
  3. Lamsweerde, A. 2001. Goal Oriented Requirements Engineering: A Guided Tour. Invited mini-tutorial paper which appeared in Requirements Engineering, International Symposium on Toronto, August 2001, 249--263. Proceedings RE'01 5th IEEE. Ding, W. and Marchionini, G. 1997. A Study on Video Browsing Strategies. Technical Report. University of Maryland at College Park. Google ScholarGoogle ScholarDigital LibraryDigital Library
  4. Dick, J., Jackson, K., and Hull, E. 2002. Requirements Engineering. Springer Verlag London Limited, Great Britain.Google ScholarGoogle Scholar
  5. Object Management Group, Inc. 2008. Business Process Modeling Notation Version 1.1. URL = http://www.omg.org/spec/BPMN/1.1/PDF (Last accessed on March 10, 2011)Google ScholarGoogle Scholar
  6. Gröne, B. 2006. Conceptual Patterns. Proceedings of the 13th Annual IEEE International Symposium and Workshop on Engineering of Computer Based Systems. (Potsdam, Germany, March 27--30, 2006). Google ScholarGoogle ScholarDigital LibraryDigital Library
  7. Chung, L., Mylopoulos, J., Nixon, B., Yu, E. 2000. Non-Functional Requirements in Software Engineering. Kluwer Academic Publishers, Boston, Dordrecht, London.Google ScholarGoogle Scholar
  8. Yu, E. S. K. 1993. Modeling Organizations for Information Systems Requirements Engineering. Proceedings of the 1st IEEE International Symposium on Requirements Engineering.Google ScholarGoogle Scholar
  9. Bonitasoft S. A.. 2010. Bonita Studio. URL = http://www.bonitasoft.com/products/BPM_download.php (Last accessed on March 10, 2011)Google ScholarGoogle Scholar
  10. Soyatec Open Solution Company. 2010. eBPMN Designer. URL = http://www.soyatec.com/ebpmn/download.html (Last accessed on March 10, 2011)Google ScholarGoogle Scholar
  11. Kotonya, G., Sommerville, I. 2003. Requirements Engineering: Processes and Techniques. John Wiley and Sons Limited, England. Google ScholarGoogle ScholarDigital LibraryDigital Library
  12. Doerr, J., Marhold, C., Rohleder, C., and Salinesi, C. 2009. Clarifying Non-Functional Requirements to Improve User Acceptance --- Experience at Siemens. Proceedings of the 15th REFSQ International Working Conference on Requirements Engineering: Foundation for Software Quality (Amsterdam, The Netherlands, June 8--9, 2009). Google ScholarGoogle ScholarDigital LibraryDigital Library
  13. Sommerville, I. 1996. Software Engineering. Addison-Wesley, England.Google ScholarGoogle Scholar
  14. Deutsch, M. S., Willis, R. R. 1998. Software Quality Engineering. Prentice-Hall, New Jersey.Google ScholarGoogle Scholar
  15. Nuseibeh, B., and Easterbrook, S. 2000. Requirements Engineering: A Roadmap. Proceeding of the ICSE '00 Conference on Software Engineering. (Limerick, Ireland, June 4--11, 2000) Google ScholarGoogle ScholarDigital LibraryDigital Library

Index Terms

  1. An agile requirements elicitation approach based on NFRs and business process models for micro-businesses

    Recommendations

    Comments

    Login options

    Check if you have access through your login credentials or your institution to get full access on this article.

    Sign in
    • Published in

      cover image ACM Other conferences
      Profes '11: Proceedings of the 12th International Conference on Product Focused Software Development and Process Improvement
      June 2011
      159 pages
      ISBN:9781450307833
      DOI:10.1145/2181101

      Copyright © 2011 ACM

      Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

      Publisher

      Association for Computing Machinery

      New York, NY, United States

      Publication History

      • Published: 20 June 2011

      Permissions

      Request permissions about this article.

      Request Permissions

      Check for updates

      Qualifiers

      • research-article

    PDF Format

    View or Download as a PDF file.

    PDF

    eReader

    View online with eReader.

    eReader