Application Engineering – Requirements Gathering

As a project for our Android Components course, we start development of the software by following the Guidelines for Rapid Application Engineering ( GRAPPLE).

The steps for development follow the acronym RADDD or RAD³. That is: Requirements Gathering; Analysis; Design; Development; and Deployment.

This post is the first part of the project and will be limited to Requirements Gathering.

My idea for the Android project, is a module for a native OCR component. There are many libraries tab allows for Optical Character Recognition. However, most of them require lots of configuration and code to achieve a reasonable outcome.

This new component would place all the elements for a workable OCR solution in a single component using the Open Source Tesseract library maintained by Google.

This post is the first of a series that will delineate the entire project development. We will start with Requirement Gathering as detailed on the SAMS’ book Teach Yourself UML in 24 hours, by Joseph Schmuller.