Application of high-level methods of compromise optimization for control of autonomous robotized open pit mining

In most software engineering approaches, software design begins with defining functional requirements, which is well suited to web-based software development projects. When designing high-critical large-scale software intended for industrial use, accounting for non-functional software requirements is also required. The main idea of the proposed document-oriented approach is to design a stable architectural solution as early as possible, taking into account the nonfunctional characteristics of the software: reliability, security, maintainability and performance (quality attributes). At the same time, the key issue is the coordination of functional requirements, taking into account technical limitations and business requirements achieved during the steady interaction of customer and developer teams. To increase the flexibility of the designed solutions and prevent crisis situations when developing highly critical large-scale software, it is proposed to use the approach integrating the architecture-centric design method (ACDM), the architecture-tradeoff analysis method (ATAM) with a matrix enterprise architecture matrix (EAM). This allows getting a result that is adequate to the required level of responsibility and reliability. Consideration of quality attributes within the framework of the method of compromise analysis makes it possible to select and make certain decisions in software design taking into account the scale of the software and its scope. The main attributes of product quality are highlighted (ISO 25010 standard), critical scenarios are defined for each of them (templates and use cases). The use of these templates for detailed software design with the necessary parameters of functional requirements, business conditions and technological limitations reduces the risk of developing unpredictable and uncertain system behavior. Based on the proposed approach, an architectural solution is presented for highly critical, responsible, large-scale software for managing autonomous robotic open-pit mining of minerals. Critical attributes for creating the specified software were identified and ranked, and the architecture of the solution according to the SWEBOK software development standard was described. Further, taking into account the nature, scale and scope of the software solution, recommendations are given on high-level architectural templates for the system design, including layers, pipelines and microservices. The proposed architecture-oriented development method is suitable for industrial-level software in various subject areas.

software development, functional requirements, quality attribute, architecture of software solutions, architecture-centric design method (ACDM), method of architectural compromise analysis (ATAM), enterprise architecture matrix (EAM)

1. Maranzano J.R., Rozsypal S.A., Zimmerman G.H., Warnken G.W.,Wirth P.E. Architecture reviews: practice and experience. IEEE Software. 2005;22(2):34-43. https://doi.org/10.1109/MS.2005.28

2. Ferber S., Heidl P., Lutz P. Reviewing Product Line Architectures: Experience Report of ATAM in an Automotive Context. In: van der Linden F. (Ed.) Software Product-Family Engineering. PFE 2001. Lecture Notes in Computer Science, V. 2290. Heidelberg Berlin, Heidelberg: Springer; 2002. P. 364-382. https://doi.org/10.1007/3-540-47833-7_33

3. Harley N. 11 of the most costly software errors in history, 2018. https://raygun.com/blog/costly-software-errors-history/

4. Clements P., Kazman R., Klein M. Evaluating Software Architecture: Methods and Case Studies. Addison-Wesley; 2002. 304 р.

5. Bass L., Clements P., Kazman R. Software Architecture in Practice (2nd Edition). Addison-Wesley; 2003. 560 p.

6. Carnegie Mellon University / Software Engineering Institute. The Capability Maturity Model: Guidelines for Improving the Software Process. Addison-Wesley; 1995.

7. Humphrey W.S. Introduction to the Team Software Process. Addison-Wesley; 1999. 496 p.

8. Boehm B. Software Engineering Economics. New Jersey: Prentice Hall; 1981. 767 p.

9. Patel J., Lee R.Y., Kim H-K. Architectural View in Software Development Life-Cycle Practices. In: 6th IEEE/ACIS International Conference on Computer and Information Science (ICIS 2007). Melbourne, Australia; 2007. https://doi.org/10.1109/ICIS.2007.64

10. Norman D.A. The Invisible Computer. Cambridge, MA: MIT Press; 1998. 340 p.

11. Cabrera A.A.A., Komoto H., van Beek T.J., Tomiyama T. Architecture-centric design approach for multidisciplinary product development. In: T. Simpson, J. Jiao, Z. Siddique, K. Hölttä-Otto (Eds.). Advances in Product Family and Product Platform Design. Methods & Applications. New York: Springer; 2014. P. 419-447. https://doi.org/10.1007/978-1-4614-7937-6_17

12. Lattanze A.J. Architecting software intensive systems: a practitioner’s guide. CRC Press; 2008. 416 p.

13. Zykov S.V., Singh A. Agile Enterprise Engineering: Smart Application of Human Factors. Models, Methods, Practices, Case Studies. Springer Nature Switzerland AG; 2020. 158 p. https://doi.org/10.1007/978-3-030-40989-0