Software ecosystem

Software Ecosystem is a book written by David G. Messerschmitt and Clemens Szyperski that explains the essence and effects of a "software ecosystem", defined as a set of businesses functioning as a unit and interacting with a shared market for software and services, together with relationships among them. These relationships are frequently underpinned by a common technological platform and operate through the exchange of information, resources, and artifacts.[1][2][3][4][5]

The term in software analysis

In the context of software analysis, the term software ecosystem is defined by Lungu [6] as “a collection of software projects, which are developed and co-evolve in the same environment”. The environment can be organizational (a company), social (an open-source community), or technical (the Ruby ecosystem). The ecosystem metaphor is used in order to denote an analysis which takes into account multiple software systems.[7] The most frequent of such analyses is static analysis of the source code of the component systems of the ecosystem.

gollark: I could probably get around that with enough work.
gollark: Either way, the real-world credit card system... honestly seems woefully insecure and the only reason it works most of the time is the law and people being somewhat trustworthy.
gollark: I think you either need physical presence of the card or some numbers on it.
gollark: I would be worried about the networking between the payment terminals and central server, too - if it's not secured properly people could intercept it and/or run attacks on it.
gollark: You *don't* trust the payment terminals, because people can go around editing the code on them to do basically whatever, and they have to read the card and contact the bank server.

References

  1. David G. Messerschmitt and Clemens Szyperski (2003). Software Ecosystem: Understanding an Indispensable Technology and Industry. Cambridge, MA, USA: MIT Press. ISBN 978-0-262-13432-3.CS1 maint: uses authors parameter (link)
  2. Slinger Jansen, Sjaak Brinkkemper, and Michael A. Cusumano (2013). Software Ecosystems: Analyzing and Managing Business Networks in the Software Industry. Edward Elgar. ISBN 978-1781955628.CS1 maint: uses authors parameter (link)
  3. Karl M. Popp and Ralf Meyer (2010). Profit from Software Ecosystems: Business Models, Ecosystems and Partnerships in the Software Industry. Norderstedt, Germany: BOD. ISBN 978-3-8423-0051-4.CS1 maint: uses authors parameter (link)
  4. Barbara Farbey and Anthony Finkelstein (2001). "Software acquisition: A business strategy analysis" (PDF). Proceedings of the Fifth IEEE International Symposium on Requirements Engineering. IEEE. pp. 76–83. doi:10.1109/ISRE.2001.948546.CS1 maint: uses authors parameter (link)
  5. Slinger Jansen, Anthony Finkelstein, and Sjaak Brinkkemper (2007). "Providing transparency in the business of software: A modeling technique for software supply networks". Proceedings of the 8th IFIP Working Conference on Virtual Enterprises. IFIP. doi:10.1007/978-0-387-73798-0. hdl:10773/9367. ISBN 978-0-387-73797-3.CS1 maint: uses authors parameter (link)
  6. Lungu, Mircea (2009). Reverse Engineering Software Ecosystems (Ph.D.). University of Lugano.
  7. "Archived copy". Archived from the original on 2013-01-20. Retrieved 2012-11-23.CS1 maint: archived copy as title (link)


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.