Skip to content
Ekonomiczne Problemy Usług

Previously: Zeszyty Naukowe Uniwersytetu Szczecińskiego. Ekonomiczne Problemy Usług

nr 126 (2) 2017
OpenAlex

Data describes this article or chapter.

Record found in the database

Citations
0
References
7

Data retrieved:

Showing the last available data. An update is pending or has failed.

View source (new tab)
Semantic Scholar

Data describes this article or chapter.

Record found in the database

Citations
0
References
4
Citations highlighted by Semantic Scholar
0

Data retrieved:

Showing the last available data. An update is pending or has failed.

View source (new tab)
OpenCitations

Data describes this article or chapter.

Citations
0

Data retrieved:

Showing the last available data. An update is pending or has failed.

View source (new tab)
Google Scholar

Poprawa jakości specyfikacji wymagań za pomocą przykładów


(Improve the quality of requirements specification through specification by example)
DOI: 10.18276/epu.2017.126/2-08
Cite

The full text is available

Abstract

The aim ofthis study was to verify whether the two, variously called methods, can aid agile projects IT in an improving the quality of requirements specification. The basic principles of approaches of Adzie and EDD of North was discussed. The following is a list of the commonly used criteria of quality, which has been enriched with two criteria relevant to the problem under consideration. The results of the comparative analysis carried out due to the described criteria, indicate existing presented concepts, sought to improve the quality of requirements specification.
Preview PDF

Open PDF

Bibliography (15)
  1. Adzie, G. (2014). Specyfikacja na przykładach. Gliwice: HELION.
  2. Ambler, S. (2000). Surveys Exploring the Current State of Information Technology Practices.
  3. Pobrano z: http://www.arnbysoft.com/surveys/ (30.12.2016).
  4. Cohn, M. (2010). Succeeding with Agile. Addison-Wesley.
  5. Crosby, P.B. (1979). Quality is Free: The Art of Making Quality Certain. Nowy Jork: McGraw¬Hill.
  6. Evans, D. (2003). Domain-Driven Design: Tackling Complexity in the Heart of Software. Addi-son-Wesley Professional.
  7. Highsmith, J. (2009). Agile project Management: Creating Innovative Products. Addison-Wesley Professional.
  8. Hołodnik-Janczura, G. (2017). The Extension of U ser Story Template Structure with an Assess¬ment Question Based on the Kano Model. W: J. Świątek, Z. Wilimowska, L. Borzemski, A Grzech (red.), Information Systems Architecture and Technology: Proceedings of 37th International Conference on Information Systems Architecture and Technology - !SAT 2016 - Part III. Series: Advances in Intelligent Systems and Computing, Vol. 523, (s. 137-151), Springer.
  9. IEEE Standard 830-1998 (2009). Institute of Electrical and Electronics Engineers. ISO/lEC 9126-1:2000.
  10. Jones C. (2009-2012). Software Requirements and the Ethics of Software Engineering. Pobrano z: www.concpts.gilb.com (2.01.2017).
  11. Juran, J.M., Gryna, M. (1970). Quality Planning and Analysis: From Product Development through Use. Nowy Jork: McGraw-Hill.
  12. North, D. (2006). Introducing-EDD. Pobrano z: https://dannorth.net/introducing-
  13. bdd/(30.12.2016).
  14. North, D. (2012). EDD-is-like-TDD-if. Pobrano z: https://dannorth.net/2012/05/31/ bdd-is-like¬tdd-if/ (30.12.2016).
  15. Smart, J.F. (2016). EDD w działaniu. Gliwice: HELION. www.uio.no/studier/enmer/matnat/ifi/INF5181/hll/undervisningsmateriale/reading-materials/Lecture-06/04Zubrow IS025000 SW Quality Measurement. pdf (20. 07.2016). www.projectsmart.co.uk/white-papers/chaos-report. pdf (2014 ).