SRA service software

[martijn...@gmail.com]

Service Software

Current developments in ICT enable many business services to be
produced and/or delivered electronically. The technology which allows
to create new electronic services, based on assembly of remotely
running services of others is called Software-as-a-Service (SaaS).
The SaaS technology consists of not only of services running remotely,
but also of platforms allowing the connections between these services,
as shown in the
following diagram:

connectivity platform


SaaS


Software Service Business services

(helaas kunnen er geen plaatjes in gekopieerd worden vandaar de tekst
versie hierboven. Document staat ook op www.IIPSaaS.nl)


The research agenda for service software comprises both the technology
for creating (electronic) services and the technology to create the
connections via connectivity platforms.

Research agenda for software services

Creating a clear understanding and definition on “Services”
Naming policies: Software, Application, components, elements etc.
Establish a typology: e.g. business service, ITC service, security
service, information service, copumputational service, etc.
Position SaaS in relation to other technologies such as Open Source,
Ajax, SOA etc.
Define Component Development Guidelines which are:
Future proof
Based on standards
Are self contained
Are inter-operable with other components


Research agenda for connectivity platforms

Defining SaaS procedures and principles is order to achieve the
following:
Security
How can security be achieved an guaranteed to the end-user throughout
the application / component chain.
Identity management
How can a secure Single Sign On environment ensure safe and effective
identity management throughout the application / component chain.
Payments management
How can a payments be handled securely between different providers,
vendors and have a common administrative basis that is trusted and
manageable.
Service reliability
How can service reliability be achieved
SLA management
Monitoring
Best practice API exchange and formatting
Standards. How to use these and how to enforce these
Auditing & Certification
How can a objective 3rd party conduct audits and certify SaaS
applications on the above topics.
Who / Which party can and will do this and on what grounds?
Optimal interoperability
How to achieve optimal interoperability on different terminals,
networks, back offices and components also considering the above
mentioned topics.


In order to research the above mentioned Research Questions it has
been identified that there is a need for demonstrator projects that
focus on one or more of these topics and creates a best practise SaaS
implementation.