Software services: Scientific challenge or industrial hype?

José Luiz Fiadeiro

Research output: Chapter in Book/Report/Conference proceedingConference contribution

7 Citations (Scopus)

Abstract

Web-services keep making headlines, not only in technical journals but also in the wider media like The Economist. Is this just a sales plot of the fragile software industry targeted to the companies and organisations that want to operate in the new economy as enabled by the internet and wireless communication? Or is there a new paradigm as far as software development is concerned? Should we, scientists, regard this as a challenge? Or dismiss it as hype? In this paper, we analyse these questions in the context of the notions of complexity that arise in software development and the methods and techniques that can be offered to address them.

Original languageEnglish
Title of host publicationTheoretical Aspects of Computing - ICTAC 2004
Subtitle of host publicationFirst International Colloquium, Guiyang, China, September 20-24, 2004, Revised Selected Paper
EditorsZ. Liu, K. Araki
Place of PublicationBerlin
PublisherSpringer Verlag
Pages1-13
Number of pages13
ISBN (Electronic)9783540318620
ISBN (Print)9783540253044
DOIs
Publication statusPublished - 2005
EventFirst International Colloquium on Theoretical Aspects of Computing - ICTAC 2004 - Guiyang, China
Duration: 20 Sept 200424 Sept 2004

Publication series

NameLecture Notes in Computer Science
PublisherSpringer Verlag
Volume3407
ISSN (Print)0302-9743

Conference

ConferenceFirst International Colloquium on Theoretical Aspects of Computing - ICTAC 2004
Country/TerritoryChina
CityGuiyang
Period20/09/0424/09/04

Keywords

  • Software Development
  • Software Architecture
  • Software services
  • Architectural Style
  • Scientific Challenge

ASJC Scopus subject areas

  • Theoretical Computer Science
  • General Computer Science

Fingerprint

Dive into the research topics of 'Software services: Scientific challenge or industrial hype?'. Together they form a unique fingerprint.

Cite this