Analysing Requirements For Virtual Business Alliances – The Case Of Spike - Digibiz'09

6,694 views

Published on

Published in: Technology, Business
1 Comment
0 Likes
Statistics
Notes
  • Be the first to like this

No Downloads
Views
Total views
6,694
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
0
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

Analysing Requirements For Virtual Business Alliances – The Case Of Spike - Digibiz'09

  1. 1. Analysing Requirements for Virtual Business Alliances – the case of SPIKE<br />Christian Broser, Christoph Fritsch, Oliver Gmelch, Günther Pernul, Rolf Schillinger and Sandra Wiesbeck<br />
  2. 2. Agenda<br />Motivation<br />The case of SPIKE<br />User Requirements Analysis Strategy<br />User Requirements Classification and Prioritisation<br />Conclusion<br />Analysing Requirements for Virtual Business Alliances – the case of SPIKE<br />
  3. 3. Motivation<br />Organisations are confronted with major challenges today:<br />Globalisation<br />Shorter innovation cycles<br />Increased competition<br />Additional external influential factors<br />Move from “traditional” companies to flexible and agile business networks as a solution<br />virtual partnerships<br />Quick time to market<br />SMEs as flexible players in the market<br />Analysing Requirements for Virtual Business Alliances – the case of SPIKE<br />
  4. 4. The case of SPIKE<br />SPIKE stands for Secure Process-oriented Integrative Service Infrastructure for Networked Enterprises. <br />The purpose of the project is to develop a software service platform for the easy and fast start-up of virtual business alliances.<br />Using SPIKE, enterprises will gain business opportunities with previously inaccessible customers and partnering organisations.<br />Analysing Requirements for Virtual Business Alliances – the case of SPIKE<br />
  5. 5. Objectives of the project<br />Outsourcing of parts of the value chain to business partners<br />Support of short-term and project-based alliances<br /><ul><li>Special focus on security and trust</li></ul>Simplify collaboration through dynamically created and pre-defined business processes<br />Achieve interoperability and integration between organisations of all sizes and all kinds of services<br />Analysing Requirements for Virtual Business Alliances – the case of SPIKE<br />
  6. 6. User Requirements Analysis<br />Analysis of user requirements as an integral part of the system design phase <br />Applied and presented in the paper: methodology originally proposed by Maguire and Bevan applied for SPIKE:<br />Information gathering<br />Identification of user needs<br />Envisioning and evaluation<br />Requirements specification<br />Analysing Requirements for Virtual Business Alliances – the case of SPIKE<br />
  7. 7. Identification of SPIKE requirements<br />Analysing Requirements for Virtual Business Alliances – the case of SPIKE<br />Overall user requirements strategy<br />
  8. 8. Alignment of SPIKE user requirements analysis with Maguire and Bevan<br />In general, only minor differences between the SPIKE adaptation and the original approach can be determined<br />SPIKE introduced an additional phase at the beginning of the process prior to the actual information gathering phase for clarification of the context<br />„Envisioning and Evaluation“ considered to be of less importance due to the nature of the SPIKE project <br />Analysing Requirements for Virtual Business Alliances – the case of SPIKE<br />
  9. 9. Requirements Analysis Strategy<br />Analysing Requirements for Virtual Business Alliances – the case of SPIKE<br />
  10. 10. Requirements Specification<br />Categorisation according to three axes:<br />User requirements<br />Focusing on functionality aspects of the system to be developed<br />Usability requirements<br />Covering usability concerns, such as effectiveness of the system, efficiency and user satisfaction<br />Organisational requirements<br />Implications on an individual organisation<br />A summary of all requirements mentioned on the following slides is available at http://www.spike-project.eu/index.php?id=136<br />Analysing Requirements for Virtual Business Alliances – the case of SPIKE<br />
  11. 11. Categorisation of User Requirements for Collaboration Platforms (1/2)<br />User Requirements<br />Workflow Management<br />Communication<br />Integration aspects<br />Content Management<br />Security Aspects<br />Platform independence<br />Federated Identity Management<br />Analysing Requirements for Virtual Business Alliances – the case of SPIKE<br />
  12. 12. Categorisation of User Requirements for Collaboration Platforms (2/2)<br />Usability Requirements<br />Intuitively usable User Interface<br />Performance aspects<br />Fault tolerance<br />Organisational Requirements<br />Privacy aspects of users<br />Structured processes, i.e. regarding deployment of the platform<br />Setup of the platform (alliance-wide administrators)<br />Time to market<br />Analysing Requirements for Virtual Business Alliances – the case of SPIKE<br />
  13. 13. Requirements Assessment and Prioritisation<br />All gathered requirements were assessed and prioritised according to the following axes:<br />MUST<br />MEDIUM<br />LOW<br />FUTURE<br />Treated with high priority within SPIKE:<br />Security aspects<br />Time to market, including short setup time of collaborations<br />Federated identity management<br />Integration aspects<br />Assigned with low priority:<br />All issues dealing with installation/operation of the system<br />Analysing Requirements for Virtual Business Alliances – the case of SPIKE<br />
  14. 14. Conclusion<br />Consideration of user requirements as a constant process from the beginning of a project on<br />Application of a methodology for gathering and analysing user requirements <br />Prove of significance within SPIKE<br />Provided an overview on current SPIKE requirements<br />Requirements herein are neither exclusive nor exhaustive<br />Further progress for SPIKE: usage of these intermediary results in the iterative user requirements handling process<br />Development within SPIKE to be validated within two trial phases, giving stakeholders the opportunity to redefine their needs prior to further development<br />Analysing Requirements for Virtual Business Alliances – the case of SPIKE<br />
  15. 15. Contact Information<br />Oliver GmelchDepartment of Information SystemsUniversity of Regensburgoliver.gmelch@wiwi.uni-regensburg.de<br />www.spike-project.eu<br />Analysing Requirements for Virtual Business Alliances – the case of SPIKE<br />The research leading to these results is receiving funding from the European Community&apos;s Seventh Framework Programme under grant agreement no. 217098. The content of this publication is the sole responsibility of the authors and in no way represents the view of the European Commission or its services.<br />

×