Project Vision and Scope Document Project Name: Read ‘n Say Team Members:1 Dave (leader: design and development) Sam (developer) Hannah (web site and documentation) Background to the Project The project is to build an iPhone application that reads text in images captured with the camera. The text is read in a spoken voice in the native language of the user which is specified in a settings dialog. The image text is assumed to be in the script and language which is most commonly used at the current locale of the phone. The project builds on Dave’s twenty years of experience in image processing and OCR and more recently on Dave and Sam’s expertise in developing in Cocoa and Objective-C 2.0 on the Mac and iOS platforms. The software would also run on the new iPod Touch, and on the next generation of iPad. The project was undertaken as it offers the prospect of a very high return on capital invested. The Stakeholders • Dave/Jane: The company (Legentis Ltd) is owned in equal shares by Dave and Jane. • Sam & Hannah: Employed as contractors on the projected and have a stake in the success of the business in the form of equity. They receive 5% of the company if it has a turnover of more than £1 million per annum at the end of its 2012 financial. • Apple: Apple will gain revenues of about £5 million per annum if the business proceeds to plan. The product is also likely to offer them a competitive advantage over other manufacturers. • Google: The Google translation software will be used and this may require a license fee if large volumes of use are generated. The Users The device should provide an easy-to-use and convenient translation service to tourists. It is anticipate that a suite of more sophisticated products will be produced for business users. 1 This document will be visible to the world so it is not sensible to put much in the way of personal details. However the version on dokuwiki will be private to the course as a login is required. You could put full names and email addresses and even mobile phone numbers (if you are happy with that) on the wiki version. Risks • It is known that Nokia and Google and academic teams in Germany and the USA are working to produce similar products. There is a risk that they will produce a better product or take some market share. • There is a risk that our device will be reverse engineered and stolen by a competitor who will then market the technology as their own. • There is a risk that large companies will issue law suits for patent infringement against Legentis. We are confident that the design does not infringe any patents but the cost of defence may well be damaging or even prohibitive preventing sales in the USA. • There is a technical risk that the performance may not be adequate for user acceptance. • There is a technical risk that an adequate algorithm will be infeasible given the memory and processor speed limitations of the iPhone. This might be ameliorated by running the application on a server using the phone for image capture, compression and speech generation. • Arabic and Chinese may prove difficult and expensive to read in comparison with Latin characters. Assumptions • That the application will not require a great deal of user support beyond a web page with FAQs. • That compiled Objective-C is challenging to reverse engineer. • That the task can be carried out with the existing staff in a timescale of eighteen months. • That no further financial resources are required beyond salaries for the development team. Vision of the Solution Vision statement2 We envisage the device being used as follows: An American tourist in Iraq would be able to hear Arabic notices and menus read in English while a Chinese tourist in Paris would hear French documents spoken in Cantonese. A successful application of this kind is likely to enjoy a mass market (about 50 million iPhones have been sold and this is increasing at about 5 million a quarter) and could be sold with minimal overheads on the App store. A 2% market penetration at a £10 sale price would generate net sales revenue of £16 million per annum and would be likely to lead to license deals with other phone 2 The Vision statement might well read much like the most typical Use Case. manufacturers. This would value the company at about £200 million and attract bids from major companies thus offering investors a profitable exit strategy. List of features3 To follow… 3 This is a very useful section as it drives the task list. Some agile programmers use Feature Drive Development (FDD).
Pages to are hidden for
"vs"Please download to view full document