That's ok, no need to apologise.
The second FYP is to create a solution to a case study which is based upon a software support department....it sucks because we have to research and analyise not only the software aspects of it but also the social interactions detailing the systems contexts, the service encounter and many other facets utilising blueprints, identifying touchpoints, using work system snapshots and using both the value chain and system life cycle frameworks to identify roles and responsibilities as well as utilising them to identify knock on affects caused by change to the system in general. We also have to take from many an IBM paper for example one guy....can't remember his name theorizes a unified process in which all the key through-put processes are identified first. Some of the IBM papers are good for example theres a paper by Glushko 2006, Fitzsimmons and Fitzsimmon 2008 and another by S. Alter (I think 2006) which proposes several methodologies, by using 3 of the main methodology papers we hope to create a methodology which is both feasible and applicable to the project and we'll have to document and demonstrate various tools that are recommended by them. Since the module is about service science the methodology that we create have to have consumer co-creation throughout the entire projects lifespan which can cause some difficulties given that the client is purely theoretical as far as implementation goes we've got to make good use of prioritisation as well as capacity management but we also have to document thoroughly which is difficult because all throughout our course we've been given a case study and taught to immediately identify the problems and propose suitable solutions which skips out a huge portion of work not to mention our research skills are below par in general.
How's things been going?
The second FYP is to create a solution to a case study which is based upon a software support department....it sucks because we have to research and analyise not only the software aspects of it but also the social interactions detailing the systems contexts, the service encounter and many other facets utilising blueprints, identifying touchpoints, using work system snapshots and using both the value chain and system life cycle frameworks to identify roles and responsibilities as well as utilising them to identify knock on affects caused by change to the system in general. We also have to take from many an IBM paper for example one guy....can't remember his name theorizes a unified process in which all the key through-put processes are identified first. Some of the IBM papers are good for example theres a paper by Glushko 2006, Fitzsimmons and Fitzsimmon 2008 and another by S. Alter (I think 2006) which proposes several methodologies, by using 3 of the main methodology papers we hope to create a methodology which is both feasible and applicable to the project and we'll have to document and demonstrate various tools that are recommended by them. Since the module is about service science the methodology that we create have to have consumer co-creation throughout the entire projects lifespan which can cause some difficulties given that the client is purely theoretical as far as implementation goes we've got to make good use of prioritisation as well as capacity management but we also have to document thoroughly which is difficult because all throughout our course we've been given a case study and taught to immediately identify the problems and propose suitable solutions which skips out a huge portion of work not to mention our research skills are below par in general.
How's things been going?
