Adaptation process control software developer team with the rules of logic

Authors

  • Сергей Федорович Чалый Kharkiv National University of Radio Electronics, Ukraine
  • Роман Николаевич Цымбаленко Kharkiv National University of Radio Electronics, Ukraine
  • Инна Борисовна Буцукина Kharkiv National University of Radio Electronics, Ukraine

DOI:

https://doi.org/10.15587/2312-8372.2013.14903

Keywords:

Information technology, development methodology, software product, iteration, task, logical rules

Abstract

The article describes the basic principles of the production process in the development of software products. It proposes to improve SCRUM methodology through the use of logical rules for automated adaptation of processes to increase the efficiency of the development process. It is also suggested to use business rules for declaring constraints on the processes that occur when using SCRUM methodology. The solution consists in the use of a business rules engine for managing business processes’ constraints.

Business rule is an expression that defines and limits some aspects of the current process. This may be an agreement or determination of the policy regarding the criteria of work with customers, partners or employees. Business rules typically consist of a set of terms, facts and rules. This term is a word or phrase in any natural language. A set of such rules expresses the knowledge that determines the policy of specific processes of an organization.

The key to the proposed approach is considered as rules of the process control. They include changes of the procedures of the process when changing its status.

The practical significance of the study is the possibility of application of the proposals, recommendations and developments related to the operation, in order to optimize business processes.

Thus, it is possible to improve the monitoring and management of the development team, using a defined set of business rules that govern behavior in the event of unplanned situations in the processes that occur when using SCRUM - methodology

Author Biographies

Сергей Федорович Чалый, Kharkiv National University of Radio Electronics

Doctor of Technical Sciences, Professor
Department of information control systems

Роман Николаевич Цымбаленко, Kharkiv National University of Radio Electronics

Department of information control systems

Инна Борисовна Буцукина, Kharkiv National University of Radio Electronics

Department of Economic Cybernetics

References

  1. Книберг, Х. Scrum и XP для тренеров [Текст] / Х. Книберг – Вильямс, 2010.– 268 с.
  2. Мартин, Р. Быстрая разработка программ. Принципы, примеры, практика. [Текст] / P. Мартин. – Tennessy, 2011.– 264 с.
  3. Ремси, A. Getting Real [Текст] / A. Ремси. – NY, 2011. – 191 с.
  4. Субраманиам, В. Этюды на тему быстрой разработки программного обеспечения [Текст] / В. Субраманиам. – Москва, 2009. – 302 с.
  5. Хамбл, Д. Непрерывное развертывание ПО. Автоматизация процессов сборки, тестирования и внедрения новых версий программ [Текст] / Д. Хамбл. – Вильямс, 2011. – 361 с.
  6. Расмуссон, Дж. Гибкое управление IT-проектами. Руководство для настоящих самураев [Текст] / Д. Расмуссон. – Вильямс, 2009. – 312 с.
  7. Мартин, Р. Чистій код [Текст] / Р. Мартин. – Висконсин, 2010. – 201 с.
  8. Поппедикс, K. Реализация разработки программного обеспечения: от концепции к деньгам [Текст] / K. Поппедикс. – Даллас, 2011. – 233 с.
  9. Ларман, C. Масштабирование Agile разработки [Текст] / C. Ларман. – Чикаго, 2012. – 259 с.
  10. Уэллс, Д. Производство без потерь. Канбан для рабочих [Текст] / Д. Уэллс. – NY, 2003. – 233 с.
  11. Kniberg, H. (2010). Scrum and XP from the Trenches Williams, USA, 268.
  12. Martin, R. (2011). Fast software development. Principles, examples, practices. Tennessy, USA, 264.
  13. Remsey, A. (2011). Getting Real. NY, USA, 191.
  14. Subramaniam, V. (2009). Studies on the rapid development of software. Moscow, Russia, 302.
  15. Humble, D. (2011). Continuous software deployment. Process automation assembly, testing and implementation of new software. Williams, USA, 361.
  16. Rasmusson, J. (2009). Flexible management of IT-projects. Guide for real samurai. Washington, USA, 312.
  17. Martin, R. (2010). Clean Code: A Handbook of Agile Software Craftsmanship. Viskonsin, USA, 201.
  18. Poppediecks, K. (2011). Implementing Lean Software Development: from Concept to Cash. Dallas, USA, 233.
  19. Larman, C. (2012). Scaling Lean & Agile Development Chicago, USA, 259.
  20. Wells, D. (2003). Production lossless. Kanban for workers NY, USA, 233.

Published

2013-06-20

How to Cite

Чалый, С. Ф., Цымбаленко, Р. Н., & Буцукина, И. Б. (2013). Adaptation process control software developer team with the rules of logic. Technology Audit and Production Reserves, 3(1(11), 53–55. https://doi.org/10.15587/2312-8372.2013.14903