This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Situated Software: Concepts, Motivation, Technology, and the Future
November/December 2008 (vol. 25 no. 6)
pp. 50-55
ASCII Text
x 
 
Sriram Balasubramaniam, Grace A. Lewis, Soumya Simanta, Dennis B. Smith, "Situated Software: Concepts, Motivation, Technology, and the Future," IEEE Software, vol. 25, no. 6, pp. 50-55, November/December, 2008.
 
 
BibTex
x
 
@article{ 10.1109/MS.2008.159,
author = {Sriram Balasubramaniam and Grace A. Lewis and Soumya Simanta and Dennis B. Smith},
title = {Situated Software: Concepts, Motivation, Technology, and the Future},
journal ={IEEE Software},
volume = {25},
number = {6},
issn = {0740-7459},
year = {2008},
pages = {50-55},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2008.159},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Situated Software: Concepts, Motivation, Technology, and the Future
IS - 6
SN - 0740-7459
SP50
EP55
EPD - 50-55
A1 - Sriram Balasubramaniam,
A1 - Grace A. Lewis,
A1 - Soumya Simanta,
A1 - Dennis B. Smith,
PY - 2008
KW - Opportunistic
KW - integration
KW - glue
KW - mashups
KW - situational applications
KW - situated software
VL - 25
JA - IEEE Software
ER -
 
Sriram Balasubramaniam, Software Engineering Institute, Carnegie Mellon University
Grace A. Lewis, Software Engineering Institute, Carnegie Mellon University
Soumya Simanta, Software Engineering Institute, Carnegie Mellon University
Dennis B. Smith, Software Engineering Institute, Carnegie Mellon University
Situated software, a type of opportunistic software, is created by a small subset of users to fulfill a specific purpose. For example, business users have been creating situated software through mashups, which combine data from multiple sources on internal systems or the Internet. Situated software can change the way users access, perceive, and consume information, and can allow users to finally focus on what to do with information, rather than where to find it or how to get to it. However, situated software also has limitations. This article identifies situated software's role, provides examples of its use, traces the Internet's role in its rapid evolution, outlines areas where it is appropriate, describes its limitations, and presents enablers for adopting situated software in an enterprise.

1. C. Shirky, "Situated Software in Clay Shirky's Writings about the Internet," Networks, Economics, and Cul-ture,30 Mar. 2004, www.shirky.com/writingssituated_software.html .
2. B.A. Nardi, A Small Matter of Programming: Perspectives on End User Computing, MIT Press, 2003.
3. W3C Consortium, "Semantic Web Education and Outreach Interest Group: Case Studies and Use Cases," 2007; www.w3.org/2001/sw/sweo/publicUseCases.
4. T. O'Reilly, "What Is Web 2.0? Design Patterns and Business Models for the Next Generation of Software," 2005; www.oreillynet.com/pub/a/oreilly/tim/news/ 2005/09/30what-is-Web-20.html.
5. R. Veryard, "Towards the Lightweight Enterprise: Business Modeling and Design for SOA and Enterprise Mashups," Component Based Development and Integration J., Apr. 2006.
6. P. Boxer, S. Garcia, and D. Smith, "Framework Architectures: Using Stack Architectures to Address Issues in Opportunistic Software Development," white paper; contact boxer@sei.cmu.edu.
7. L. Cherbakov, A.J.F. Bravery, and A. Pandya, "SOA Meets Situational Applications, Part 1: Changing Computing in the Enterprise," IBM developerWorks; www.ibm.com/developerworks/webservices/library/ ws-soa-situational1index.html?S_TACT=105AGX04&S_CMP=ART .
8. L. Cherbakov, A.J.F. Bravery, and A. Pandya, "SOA Meets Situational Applications, Part 2: Building the IBM Situational Applications Environment," IBM developer Works; www.ibm.com/developerworks/webservices/library/ ws-soa-situational2index.html.
9. C. Anderson, "The Long Tail," Wired, Oct. 2004; www.wired.com/wired/archive/12.10tail.html .
10. P. Clements and L. Northrop, Software Product Lines: Practices and Patterns, Addison-Wesley, 2001.
11. A. Jhingran, "Enterprise Information Mashups: Integrating Information, Simply," Proc. 32nd Int'l Conf. Very Large Databases, VLDB Endowment, 2006, pp. 3–4.
12. J. Wong and J.I. Hong, "Making Mashups with Marmite: Towards End-User Programming for the Web," Proc. SIGCHI Conf. Human Factors in Computing Systems, ACM Press, 2007, pp. 1435–1444.
13. E. Rahm, A. Thor, and D. Aumueller, "Dynamic Fusion of Web Data," Database and XML Technologies, 2007, pp. 14–16.
14. R.J. Ennals and M.N. Garofalakis, "MashMaker: Mashups for the Masses," Proc. 2007 ACM SIGMOD Int'l Conf. Management of Data, ACM Press, 2007, pp. 1116–1118.
15. S. Hagemann, C. Letz, and G. Vossen, "Web Service Discovery: Reality Check 2.0," Proc. 3rd Int'l Conf. Next generation Web Services Practices (NWeSP 07), IEEE CS Press, 2007, pp. 113–118.

Index Terms:
Opportunistic, integration, glue, mashups, situational applications, situated software
Citation:
Sriram Balasubramaniam, Grace A. Lewis, Soumya Simanta, Dennis B. Smith, "Situated Software: Concepts, Motivation, Technology, and the Future," IEEE Software, vol. 25, no. 6, pp. 50-55, Nov.-Dec. 2008, doi:10.1109/MS.2008.159
Usage of this product signifies your acceptance of the Terms of Use.