Abstract:ResuméDen här uppsatsen behandlar skapandet och designen av en arkitektur over ett system för behandling av depression och andra psykiska sjukdomar via internet, kallat Melencolia. Ett av kraven för detta projekẗ ar att skapa ett system som kan utökas i framtiden. Vi har härlett detta krav till begreppet modularitet och för att skapa en modulär arkitektur för Melencolia har vi undersökt vad begreppet innebär och härlett det till att vara ett kvalitetsdrag hos flera kvalitetsattribut däribland "maintainability"… Show more
“…Therefore, a vibrant app ecosystem is crucial to the success of a mobile platform, such as Android. A key challenge in conceiving such platforms, however, was encoding constraints and rules to enable a properly functioning ecosystem with certain norms of structure and behavior, yet remaining sufficiently flexible to allow the developers to fully exploit the capabilities available on modern mobile devices ( Eklund and Bosch, 2014 ).…”
a b s t r a c tThe meteoric rise of mobile software that we have witnessed in the past decade parallels a paradigm shift in its design, construction, and deployment. In particular, we argue that today's mobile software, with its rich ecosystem of apps, would have not been possible without the pioneering advances in software architecture research in the decade that preceded it. We describe the drivers that elevated software architecture to the centerpiece of contemporary mobile software. We distill the architectural principles found in Android, the predominant mobile platform with the largest market share, and trace those principles to their conception at the turn of century in software architecture literature. Finally, to better understand the extent to which Android's ecosystem of apps employs architectural concepts, we mine the reverse-engineered architecture of hundreds of Android apps in several app markets and report on those results.
“…Therefore, a vibrant app ecosystem is crucial to the success of a mobile platform, such as Android. A key challenge in conceiving such platforms, however, was encoding constraints and rules to enable a properly functioning ecosystem with certain norms of structure and behavior, yet remaining sufficiently flexible to allow the developers to fully exploit the capabilities available on modern mobile devices ( Eklund and Bosch, 2014 ).…”
a b s t r a c tThe meteoric rise of mobile software that we have witnessed in the past decade parallels a paradigm shift in its design, construction, and deployment. In particular, we argue that today's mobile software, with its rich ecosystem of apps, would have not been possible without the pioneering advances in software architecture research in the decade that preceded it. We describe the drivers that elevated software architecture to the centerpiece of contemporary mobile software. We distill the architectural principles found in Android, the predominant mobile platform with the largest market share, and trace those principles to their conception at the turn of century in software architecture literature. Finally, to better understand the extent to which Android's ecosystem of apps employs architectural concepts, we mine the reverse-engineered architecture of hundreds of Android apps in several app markets and report on those results.
“…However, one might wonder whether ecosystems developed in the same domain, such as GNOME and KDE, or Python and Ruby, exhibit more similarity in the way they are organised, governed or evolve than ecosystems from different domains. First steps towards understanding specificities of software ecosystems within a given domain have been made for embedded software [25] and the telecom industry [71].…”
The paper is a meta-analysis of the research field of software ecosystems, by method of surveying 26 authors in the field. It presents a relevant list of literature and six themes in which challenges for software ecosystems can be grouped: Architecture and Design, Governance, Dynamics and Evolution, Data Analytics, Domain-Specific Ecosystems Solutions, and Ecosystems Analysis. As such, it provides a roadmap for future research in the field.
Categories and Subject Descriptors
“…Furthermore, participants spent personal time on answering the on-line questionnaire. We can therefore assume that those who volunteered to spend time have no reason to be dishonest [9]. Still, there were couple of responses that were removed because it was clear that they were invalid (e.g., just indicating none benefits and none drawbacks, or introducing fake personal data).…”
Section: Internal Validitymentioning
confidence: 99%
“…A car includes a number of ECUs or micro-controllers (µC) modules, most of them dedicated to drive sensors and actuators [9]. For instance, the software than run on an ECU can first read data from the car sensors (e.g., engine speed and the speed that is requested by the driver), and then process such data to control actuators (e.g., changing the amount of fuel or the timing or its ignition).…”
The use of software reference architectures plays a fundamental role in software development, as it could bring several benefits such as providing means to design applications' software architectures with higher productivity and quality. However, many organizations still find scarce the existing empirical evidence about the benefits and drawbacks of software reference architectures. Organizations need such evidence to make informed decisions whether or not to adopt a software reference architecture for the development and maintenance of software applications. In this context, this paper aims to gather evidence on AUTOSAR, a mature and accepted software reference architecture for automotive applications used worldwide by more than 180 organizations. We designed and executed a web-based survey addressed to practitioners with experience in using AUTOSAR. We obtained 51 valid responses. The survey results indicate that the most popular benefits of AUTOSAR are standardization (88%), reuse (80%) and interoperability (51%) whereas its most important drawbacks are complexity (65%), initial investment (59%) and learning curve (51%). The respondents of the survey also gave directions to handle the major drawbacks of AUTOSAR, such as the need of a tool environment to improve its usability and handle its complexity, and the need of more stable releases of AUTOSAR to decrease the cost of migrating among versions.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.