Designing Extranet
Linna, Annamari (2012)
Metropolia Ammattikorkeakoulu
2012
All rights reserved
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-201204295507
https://urn.fi/URN:NBN:fi:amk-201204295507
Tiivistelmä
This thesis is part of Industrial Management and Engineering degree programme of Metropolia, University of Applied Sciences. Neste Oil Ltd and, more precisely, Nordic Sales have decided to upgrade their existing extranet to a newer version. Their aim is to offer better quality customer service. The project to define pre-requirement specifications was accomplished between December 2011 and April 2012.
This study is part of the designing and definition phase of the pre-requirement specifications. It is based on theories concerning usability and user centered service design as well as heuristics from Nielsen and Scheiderman’s eight golden rules.
Besides these, the study draws on data gathered through benchmarking and interviews. Benchmarking was carried out among Neste Markkinointi extranet and the corporate intranet portal. Three interviews were held: first the domestic operations coordinators, second the coordinators responsible for Baltic and Swedish customer and third, with the 1st proto-type ready, with domestic Sales Managers and their coordinators. In the interviews the employees were encouraged to comment on the current system and prototype.
With the help of the designing guidelines, benchmarking, current state analysis and interviews the objective of this thesis was reached. The thesis had three objectives: to create a prototype of the new extranet, use case documentation and pre-requirement specifications in TestLink environment. These create the basis for the demo of the application and the final requirement specifications which will be sent to the software vendor.
Based on the first interviews with the operations coordinators the current state analysis was made. At this phase the current system was tested to see how the application worked at the time of testing, and if the comments of the coordinators were correctly understood. Based on the interviews with the Sales Managers and coordinators the first prototype will be modified until the point it will be the second and final prototype.
The use case documentation was created from the accepted version of the prototype to separate customers and consequent update frequency. The prototype and use case documentation served as sources for pre-requirement specifications in TestLink environment.
This study is part of the designing and definition phase of the pre-requirement specifications. It is based on theories concerning usability and user centered service design as well as heuristics from Nielsen and Scheiderman’s eight golden rules.
Besides these, the study draws on data gathered through benchmarking and interviews. Benchmarking was carried out among Neste Markkinointi extranet and the corporate intranet portal. Three interviews were held: first the domestic operations coordinators, second the coordinators responsible for Baltic and Swedish customer and third, with the 1st proto-type ready, with domestic Sales Managers and their coordinators. In the interviews the employees were encouraged to comment on the current system and prototype.
With the help of the designing guidelines, benchmarking, current state analysis and interviews the objective of this thesis was reached. The thesis had three objectives: to create a prototype of the new extranet, use case documentation and pre-requirement specifications in TestLink environment. These create the basis for the demo of the application and the final requirement specifications which will be sent to the software vendor.
Based on the first interviews with the operations coordinators the current state analysis was made. At this phase the current system was tested to see how the application worked at the time of testing, and if the comments of the coordinators were correctly understood. Based on the interviews with the Sales Managers and coordinators the first prototype will be modified until the point it will be the second and final prototype.
The use case documentation was created from the accepted version of the prototype to separate customers and consequent update frequency. The prototype and use case documentation served as sources for pre-requirement specifications in TestLink environment.