Software as a service

About: Software as a service is a research topic. Over the lifetime, 8514 publications have been published within this topic receiving 136177 citations. The topic is also known as: Service as a Software Substitute & SaaSS.

Generalized ocean color inversion model for retrieving marine inherent optical properties

Abstract: Ocean color measured from satellites provides daily, global estimates of marine inherent optical properties (IOPs). Semi-analytical algorithms (SAAs) provide one mechanism for inverting the color of the water observed by the satellite into IOPs. While numerous SAAs exist, most are similarly constructed and few are appropriately parameterized for all water masses for all seasons. To initiate community-wide discussion of these limitations, NASA organized two workshops that deconstructed SAAs to identify similarities and uniqueness and to progress toward consensus on a unified SAA. This effort resulted in the development of the generalized IOP (GIOP) model software that allows for the construction of different SAAs at runtime by selection from an assortment of model parameterizations. As such, GIOP permits isolation and evaluation of specific modeling assumptions, construction of SAAs, development of regionally tuned SAAs, and execution of ensemble inversion modeling. Working groups associated with the workshops proposed a preliminary default configuration for GIOP (GIOP-DC), with alternative model parameterizations and features defined for subsequent evaluation. In this paper, we: (1) describe the theoretical basis of GIOP; (2) present GIOP-DC and verify its comparable performance to other popular SAAs using both in situ and synthetic data sets; and, (3) quantify the sensitivities of their output to their parameterization. We use the latter to develop a hierarchical sensitivity of SAAs to various model parameterizations, to identify components of SAAs that merit focus in future research, and to provide material for discussion on algorithm uncertainties and future emsemble applications.

Collaboration in Software Engineering: A Roadmap

Abstract: Software engineering projects are inherently cooperative, requiring many software engineers to coordinate their efforts to produce a large software system. Integral to this effort is developing shared understanding surrounding multiple artifacts, each artifact embodying its own model, over the entire development process. This focus on model- oriented collaboration embedded within a larger process is what distinguishes collaboration research in software engineering from broader collaboration research, which tends to address artifact-neutral coordination technologies and toolkits. This article first presents a list of goals for software engineering collaboration, then surveys existing collaboration support tools in software engineering. The survey covers both tools that focus on a single artifact or stage in the development process (requirements support tools, UML collaboration tools), and tools that support the representation and execution of an entire software process. Important collaboration standards are also described. Several possible future directions for collaboration in software engineering are presented, including tight integration between web and desktop development environments, broader participation by customers and end users in the entire development process, capturing argumentation surrounding design rationale, and use of massively multiplayer online (MMO) game technology as a collaboration medium. The article concludes by noting a problem in performing research on collaborative systems, that of assessing how well certain artifacts, models, and embedded processes work, and whether they are better than other approaches.

Over the air mobile device software management

Abstract: An architecture for over the air management of software on a wireless device includes a software architecture supporting software patches, including secure downloading of software from a data network and robust installation of the same on the wireless device. Using this architecture, a network operator can notify a mobile device user about the software upgrade and send the upgrade to the mobile device over the air. Remote management of DSP software on mobile phones in GSM or GPRS networks uses an efficient installation algorithm with an error recovery mechanism. A digital signature is used for checking authenticity and integrity of the downloaded DSP software patch.

Synching or sinking: global software outsourcing relationships

Abstract: Global software outsourcing is the outsourcing of software development to subcontractors outside the client organization's home country, India is the leading GSO subcontractor, registering average annual growth of more than 40 percent over the last decade and developing nearly US$4 billion in software for foreign clients in FY 1999. Indian firms now develop software for nearly one-third of the Fortune 5002. The authors investigate the strategies that differentiate successful and unsuccessful value chain moves.

A strategic approach to software protection

Abstract: This paper demonstrates that there is a strategic reason why software firms have followed consumers' desire to drop software protection. We analyze software protection policies in a price-setting duopoly software industry selling differentiated software packages, where consumers' preference for particular software is affected by the number of other consumers who (legally or illegally) use the same software. Increasing network effects make software more attractive to consumers, thereby enabling firms to raise prices. However, it also generates a competitive effect resulting from feircer competition for market shares. We show that when network effects are strong, unprotecting is an equilibrium for a noncooperative industry.