Analysis Complete


Conclusion of analysis phase, and MoSCoW feature list.

Old Article

This content may be out of date or broken, please take care.

After little work being done the week I prior, I decided to really crack the whip this week, and get my analysis done, in time for the deadline I set myself of having it done by this week.

I really wanted to try and get a good comparison between going web or going native, and so I spent quite a large portion of time researching. I kind of wanted to do the project as a web application, but I think that this is because I am familiar with web technologies. Native apps only won slightly in the end, mainly because of performance and device support. Sabisu has also expressed that with this being the case, we should go Android. I am happy with this; WP8 would have been good (I have done a lot of work with C#), but Android is more widely used, and I know Java about as well as C#.

I did research on the Mathmatical side of the project, we will require this to get bearings and such. I actually spoke to one of my friends – who is reading a masters in maths (or something involving deep field of maths…), to clarify some of the formulas I was using. In the end, it turned out there was an API function for Android that does it… Hind-sight is a great thing eh?

Needless to say, this week I concluded my Analysis phase! And I have a beautiful MoSCoW list of features based on research and facts:


  1. Must
  2. Show device location on 2D aerial map.
  3. Show Location of Instruments on 2D aerial map.
  4. Show basic data for instruments.
  5. Should
  6. Show instrument types on map.
  7. Show specific data for instruments.
  8. Could
  9. Allow filtering of device instruments – by type.
  10. Show specific data for instruments.

    2.1 Tank Levels

    2.2 Tank/Pipe Contents/Grade

  11. Pipe Flow.
  12. CO2 Emissions.
  13. Won’t
  14. Allow writing of data to database.

Iteration/Sprint 1

  1. Must
  2. Use Augmented Reality to show the location of plant instruments in relation to device.
  3. Should
  4. Use smart ordering to prioritise instrument’s on screen depending on distance
  5. Could
  6. Use a “radar-like” compass to show instruments as points on screen.
  7. Allow the writing of data.