Identification of Information System Functional Problems Using the Model of Requirements and Cause-effect Relationships


The paper defines the models of the objective tree and the current reality tree. Such models allow to define problems on the basis of cause-effect relations. The paper provides general recommendations for the application of these models. It describes their application on the example of an information system, a compound program complex. The information is accompanied by visual images in the form of diagrams. The information system is used in the field of retail to solve many different problems. The paper explains the need to identify problems. Within the framework of the example, the system’s stakeholders are defined and their interaction with the objective tree is given. After that, a certain objective is considered and the reason for that is given. As a result of using the current reality tree, the paper compiles a list of root problems.  At the end, it proves the connection between the solution of low-level problems and the implementation of high-level objectives. Finally, it provides recommendations for further work related to the selected list of problems.

Keywords: current reality tree, system, stakeholders, objective tree, retail, problems definition

[1] Lam S., Vandenbosch M., Pearce M. Retail sales force scheduling based on store traffic forecasting //Journal of Retailing. – 1998. – Т. 74. – №. 1. – C. 61-88.

[2] Chapados N. et al. Retail store scheduling for profit //European Journal of Operational Research. – 2014. – Т. 239. – №. 3. – C. 609-624.

[3] Lusch R. F., Jaworski B. J. Management controls, role stress, and retail store manager performance//Journal of Retailing. – 1991. – Т. 67. – №. 4. – C. 397.

[4] Porter M. E. et al. How information gives you competitive advantage. – 1985.

[5] Bartolomei, J.E., Hastings, D.E., de Neufville, R., and Rhodes, D.H. 2006. ”Screening for Real Options ”In” an Engineering System: A Step Towards Flexible Weapon System Development. ” 4th Conference on Systems Engineering Research.v Los Angeles, CA, USA. April 2006

[6] Conrow, E. 2008. ”Risk Analysis for Space Systems”. Space Systems Engineering and Risk Management Symposium, 27-29 February, 2008, Los Angeles, CA, USA.

[7] ISO/IEC/IEEE. 2015. Systems and Software Engineering – System Life Cycle Processes. Geneva, Switzerland: International Organisation for Standardisation / International Electrotechnical Commissions/ Institute of Electrical and Electronics Engineers. ISO/IEC/IEEE 15288:2015.

[8] Guide to the Systems Engineering Body of Knowledge, Part 3 version 2.1

[9] ISO/IEC/IEEE. 2011. Systems and software engineering - Requirements engineering. Geneva, Switzer- land: International Organization for Standardization (ISO)/International Electrotechnical Commission/ Institute of Electrical and Electronics Engineers (IEEE), (IEC), ISO/IEC/IEEE 29148.

[10] ISO/IEC/IEEE. 2011. Systems and Software Engineering - Architecture Description. Geneva, Switzer- land: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE), ISO/IEC/IEEE 42010.

[11] Doran, G. T. (1981). ”There’s a S.M.A.R.T. way to write management’s goals and objectives”. Management Review. 70(11): 35–36.

[12] Keeney, R.L. 2004. ”Making Better Decision Makers.” Decision Analysis, 1(4), pp.193–204.

[13] Dettmer, H. W., (1997) Goldratt’s Theory of Constraints: a systems approach to continuous improvement. ASQC Quality Press, pp. 62–119.