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.
- Young, R. 2004. Requirements Engineering Handbook. Artech House, Incorporated, Norwood, Massachusetts.Google Scholar
- 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 Scholar
- 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 ScholarDigital Library
- Dick, J., Jackson, K., and Hull, E. 2002. Requirements Engineering. Springer Verlag London Limited, Great Britain.Google Scholar
- 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 Scholar
- 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 ScholarDigital Library
- Chung, L., Mylopoulos, J., Nixon, B., Yu, E. 2000. Non-Functional Requirements in Software Engineering. Kluwer Academic Publishers, Boston, Dordrecht, London.Google Scholar
- Yu, E. S. K. 1993. Modeling Organizations for Information Systems Requirements Engineering. Proceedings of the 1st IEEE International Symposium on Requirements Engineering.Google Scholar
- Bonitasoft S. A.. 2010. Bonita Studio. URL = http://www.bonitasoft.com/products/BPM_download.php (Last accessed on March 10, 2011)Google Scholar
- Soyatec Open Solution Company. 2010. eBPMN Designer. URL = http://www.soyatec.com/ebpmn/download.html (Last accessed on March 10, 2011)Google Scholar
- Kotonya, G., Sommerville, I. 2003. Requirements Engineering: Processes and Techniques. John Wiley and Sons Limited, England. Google ScholarDigital Library
- 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 ScholarDigital Library
- Sommerville, I. 1996. Software Engineering. Addison-Wesley, England.Google Scholar
- Deutsch, M. S., Willis, R. R. 1998. Software Quality Engineering. Prentice-Hall, New Jersey.Google Scholar
- 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 ScholarDigital Library
Index Terms
- An agile requirements elicitation approach based on NFRs and business process models for micro-businesses
Recommendations
Micro-business behavior patterns associated with components in a requirements approach
EESSMod '12: Proceedings of the Second Edition of the International Workshop on Experiences and Empirical Studies in Software ModellingMicro-businesses are the smallest enterprises and since they come in large numbers and are greatly diversified, they become difficult to define and classify. Micro-businesses also have several resource restrictions. These ambiguities and constraints ...
Requirements elicitation with business process modeling
PLoP '14: Proceedings of the 21st Conference on Pattern Languages of ProgramsRequirements Elicitation is the area of Requirements Engineering that deals with identifying system requirements. The paper documents a pattern showing how to elicit functional requirements for a software product in the form of User Stories through ...
Agile elicitation of scalability requirements for open systems: A case study
AbstractEliciting scalability requirements during agile software development is complicated and poorly described in previous research. This article presents a lightweight artifact for eliciting scalability requirements during agile software ...
Highlights- This article makes scalability requirements easier to capture for practitioners.
Comments