Description model of programming style ecosystem

N.A. Sydorov, N.N. Sydorova, E.N. Sydorov


In the process of developing and maintaining a software product, many things are created and used that are called software artefacts. Software artifacts are changed, reused, and change relationships in the development and maintenance processes of a software product. The complexity and variety of software artifact relationships require adequate means of description and management. They may be a software artifact ecosystem. In the article, for the first time, a concept of a software artifact ecosystem is proposed. The concept describes a generalized model of the software artifact ecosystem, which is the Cornerstone ecosystem type and consists of three actors – the platform, the software, and the artifact. The roles of actors in the ecosystem are indicated, the relationships between actors are described. As an example, based on the generalized model of the software artifact ecosystem, a declarative model of the programming style ecosystem has been developed.

Problems in programming 2020; 2-3: 74-81


software engineering; software artifact; programming; programming style; software ecosystem; ontology

Full Text:

PDF (Russian)


Sydorov N.A. (2005) Software Stylistics, Problems of Programming. 2018. 2, 3. P. 245-254.

Sydorov N., Sydorova N., Sydorov E., Cholyshkina O., Batsurovska I. (2019) Development of the approach to using a style in software engineering, Eastern-European Journal of Enterprise Technologies. 2019. 4/2 (100). P. 41-51. CrossRef

Nuwangi S.M. & Darshana S. (2015) Software artefacts as equipment: a new conception to software development using reusable software artefacts. Thirty-Sixth International Conference on Information Systems, 2015, Texas, USA.

Heidegger, M. (1927/1962) Being and Time, Translated by John Macquarrie & Edward Robinson. USA: Harper & Row.

Bosch J.,(2002) Maturity and Evolution in Software Product Lines: Approaches, Artefacts and Organization, Software Product Lines, Second International Conference, SPLC 2, San Diego, CA, USA, August 19-22, 2002. CrossRef

Rational Unified Process: Best Practices for Software development Teams, Rational Software White Paper TP026B, Rev 11/01. 1998. 18 p.

Fernandez, D M., Bohm W., Broy M., (2018) Artefacts in Software Engineering: A Fundamental Positioning. International Journal on Software and Systems Modeling. 2018. 26. 9 p.

Glass, R. (1989) Software maintenance documentation, SIGDOC '89, Pittsburg, Pennsylvania, USA, ACM Press. P. 18-23. CrossRef

Dewar, R.G., (2005) Managing Software Engineering Artefact Metadata, Department of Computer Science, Heriot-Watt University, Edinburgh, UK.

Seichter D., Dhungana D., Pleuss A., Hauptmann B. (2010) Knowledge Management in Software Ecosystems: Software Artefacts as First-class Citizens, ECSA 2010 August 23-26, 2010, Copenhagen, Denmark. P. 119-126. CrossRef

Sadi M., Yu E. (2015) Designing Software Ecosystems: How Can Modeling Techniques Help?, Springer-Verlag, Berlin Heidelberg 2015. 15 p. CrossRef

Sydorov N. (2010) Software Ecology, Software Engineering. 2010. P. 53-61.

Yu E.: (1995) Modelling Strategic Relationships for Business Process Reengineering. Ph.D., thesis. Dept. of Computer Science, University of Toronto. (1995)

Knodel J., and Manikas K. (2015) Towards a typification of software ecosystems. In Fernandes et al. Software Business - 6th International Conference, ICSOB 2015, Braga, Portugal, June 10-12, 2015, Proceedings (2015), Vol. 210 of Lecture Notes in Business Information Processing, Springer. P. 60-65. CrossRef



  • There are currently no refbacks.