Abstract
In the process of developing and maintaining a software product, many things are created and used that are called software artefacts. Software artifacts are created, 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 artifacts ecosystem. In the article, for the first time, a concept of a software artifact ecosystem is proposed. The concept describes a generic model of the software artifacts ecosystem, which is the Cornerstone ecosystem type and consists of three actors — the platform, the software, and the artifact. Based on the generic model, the SD model of the software artifacts ecosystem is described. The roles of actors in the ecosystem are indicated, the relationships between actors are described. The developer's activities will be more efficient, the software is understandable, and the development and maintenance is cheaper when the styles (standards) are used. As case study, based on the generic model of the software artifacts ecosystem, a declarative model of the programming style ecosystem has been developed. Three-level model of programming style artifact is proposed. The tools and processes for creating and using a programming style artifact are developed and described.
Publisher
National Academy of Sciences of Ukraine (Co. LTD Ukrinformnauka)
Reference25 articles.
1. 1. Nuwangi S.M., Darshana S. Software arte-facts as equipment: a new conception to software development using reusable soft-ware artefacts. Thirty-Sixth International Conference on Information Systems. 2015. Texas, USA.
2. 2. Heidegger M. (1927/1962) Being and Time, Translated by John Macquarrie & Edward Robinson. USA: Harper & Row.
3. 3. Bosch J. Maturity and Evolution in Soft-ware Product Lines: Approaches, Artefacts and Organization, Software Product Lines, Second International Conference, SPLC 2, San Diego, CA, USA, August 19-22, 2002,
4. 4. Rational Unified Process: Best Practices for Software development Teams, Rational Software White Paper TP026B, Rev. 11/01. 1998. 18 p.
5. 5. Glass R. Software maintenance documenta-tion, SIGDOC '89, Pittsburg, Pennsylvania, USA, ACM Press. 1989. Р. 18 - 23.
Cited by
1 articles.
订阅此论文施引文献
订阅此论文施引文献,注册后可以免费订阅5篇论文的施引文献,订阅后可以查看论文全部施引文献