a reply to: wwe9112
If it were C# or VB based, I'd have you contact me via PM, as most of my work has revolved around applications that use SQL.
However, I can tell you some of the things to look up (just in case it is homework, I don't want to give away free answers).
1. If you are new to this, one of my first assignments besides the typical "Goodbye, Cruel World" application was to use the Swing framework to build
a simple GUI. Start there - build some kind of GUI/Front-end to give you an idea of what you want to store in the database.
2. Next, look up what kinds of database drivers are available for Java - There should be one called JDBC. Get familiar with using it in a non-Android
project (simple Java applet). This driver allows you to connect to a database.
3. Learn how to use and format SQL (if you don't know already). SQL is one way to "talk" to a database. At the very least, learn how to build the
connection string, and how to do SELECT, INSERT, UPDATE, and DELETE statements.
4. Don't start with something complex such as Microsoft SQL Server or Oracle. Instead, start with something like Microsoft Access, SQLLite, or even
XML (I wouldn't use XML for a database, but it's good for practice). These are relatively easy to setup and use.
5. Check some of the questions out on stackexchange - Just by searching for "Android Access Database", many questions (some with plenty of code
snippets) already came up.
Also, in regards to design cycle - Keep in mind, your customers are not developers: They want something that's flashy, sparkles, and does
what they want. So, how I'd design an app is:
1. Gather requirements from customers (via survey, demos, beta tests, etc).
2. Create Mockups (What the client will see, what client can expect when something is done).
3. Create the code + statements to retrieve values from the database.
4. Create database structure and schema.
5. Pray that client doesn't change requirements the day before release.
6. Come up with release schedule for future releases.
7. Cry under my desk when client complains that something isn't working right and demands a patch.
8. Revise code, schema, and test cases as new scenarios come up.