Methodologies for Building MS Access Application

Hello,

I am looking for recommendations on what software development methodologies
to use for developing a Microsoft Access application. I know there are many
different types of methodologies/steps for going through the process, and I
am looking for recommendations from the experts on what they would recommend.


In terms of my experience, I have strong knowledge of the business side of
what we are trying to accomplish, but not as much software development
experience. I use Access often and build small databases, but what I am
trying to build now will be more in depth (I estimate having 11 – 13 separate
tables, lots of forms, reports, and queries). I want to be sure that I am
systematic about putting this together so nothing is missed and that it is
tested correctly.

Also, if you have any "must have" literature recommendations, that would be
appreciated.

Thanks in advance.

Scott

First, JOPO (just one person's opinion)...

Second, forget about "... so nothing is missed ..." No matter how hard you
and your user(s) work at defining the requirements, what you write down as
requirements and what the "finished" (forget "finished", too) system does
will not match. Requirements change over time, as the environment and
technology change, users are known to say "oh by the way, did I mention
....?", and YOU may not interpret what THEY define the same way they meant it
("I know you think you know what I said, but ...").

Given all that, my preference (remember, JOPO) is to build a
system/application in partnership with a client. The first thing we do is
define the 1 or 2 most critical aspects. If the application will not be
able to do those, we kill the project before spending any more time/money on
it. If the client is willing, I estimate the cost of getting to, at a
minimum, "proof of concept"/prototype demonstration of those one or two
critical items. If the client is still willing, s/he ends up with a
functional proof of those critical items.

At this point, we start over! What are the (remaining) 1 or 2 most critical
items? Rinse & repeat until the client decides s/he has sufficient
functionality (and user-proofing) to get his/her job done.

After coming up with this approach on my own, I was informed that I had
reinvented a variant on the "iterative" or "agile" design process g.

Good luck!

Regards

Jeff Boyce
Microsoft Office/Access MVP

"ScottMsp" wrote in message
...
Hello,

I am looking for recommendations on what software development
methodologies
to use for developing a Microsoft Access application. I know there are
many
different types of methodologies/steps for going through the process, and
I
am looking for recommendations from the experts on what they would
recommend.


In terms of my experience, I have strong knowledge of the business side of
what we are trying to accomplish, but not as much software development
experience. I use Access often and build small databases, but what I am
trying to build now will be more in depth (I estimate having 11 - 13
separate
tables, lots of forms, reports, and queries). I want to be sure that I am
systematic about putting this together so nothing is missed and that it is
tested correctly.

Also, if you have any "must have" literature recommendations, that would
be
appreciated.

Thanks in advance.

That's a big question, there will hopefully be several other responses. I
just have a few notes that will go to your core starting issue, avoid the
most common pitfalls.

Start by developing an organized picture of the information / process that
you are going to database. This includes figuring out what the information
"entities" are, and the relationships/links between them. Such links
themselves are information.

Keep your GENERAL end goal in mind when doing this.

Then design a normalized and effective table structure to support
accomplishment of the above. Ask questions in this forum as needed.

On Mon, 20 Apr 2009 07:48:01 -0700, ScottMsp
wrote:

I am looking for recommendations on what software development methodologies
to use for developing a Microsoft Access application. I know there are many
different types of methodologies/steps for going through the process, and I
am looking for recommendations from the experts on what they would recommend.

I agree with Jeff and Fred that it's a huge topic. In our shop we've
developed techniques, standards and templates over 15 years and we
continue to improve them all the time. I teach full-day training
classes on this stuff and just scratch the surface.

We don't make estimates for projects until we have enough information.
If an initial consultation isn't enough, we define a Phase 0 project
to define the requirements - THEN we try to build an estimate for
Phase 1. And after the design stage of Phase 1 is complete, we
re-estimate *again*.

Speaking of Phase 1, we try to make the first phase of delivered
system as *small* as possible while still being useful. Then we
iterate through more phases. Agile, right?

We describe our whole process he
http://www.jstreettech.com/cartgenie...ng-process.asp

I'm interested to see how other developers weigh in on this.

Armen Stein
Microsoft Access MVP
www.JStreetTech.com

Hi guys,

I could΄t resist the challenge.

Is not an easy or a real straight forward answer to this, I believe.
Sometimes is better to think about the ending reporting section of the
project, i.e. what analysis and reports does your customer needs? This will
help you a lot to realize better the businees requirements. Always have in
mind to ask questions, to ask more questions and to ask again and again in
order to realise and clarify how the project must be carried out - Have in
mind that your customer (if you are the developer) knows better the
requirements in "plain text". Also, ask for any handwritten
/semi-computerized jobs currently used. - You will define
fields/tables/relationships required.

After realising most of the requirements I beleive you may have an
approximate estimation of the work to be carried out. To be sure of that ask
from your customer his/her prior approval (what should be included and what
not to).

Hope this helps too,

GeorgeCY

Ο χÏ�ήστης "ScottMsp" Î*γγÏ�αψε:

Hello,

I am looking for recommendations on what software development methodologies
to use for developing a Microsoft Access application. I know there are many
different types of methodologies/steps for going through the process, and I
am looking for recommendations from the experts on what they would recommend.


In terms of my experience, I have strong knowledge of the business side of
what we are trying to accomplish, but not as much software development
experience. I use Access often and build small databases, but what I am
trying to build now will be more in depth (I estimate having 11 – 13 separate
tables, lots of forms, reports, and queries). I want to be sure that I am
systematic about putting this together so nothing is missed and that it is
tested correctly.

Also, if you have any "must have" literature recommendations, that would be
appreciated.

Thanks in advance.

It sounds like / I figured ScottMSP is developing the application for his /
their own use.

Here are my 2 cents worth.

I used to sit down and try and develop specifications for each of my db to
be developed (tables, data to be tracked, required reports,....). in the
end, as many people stated, things are always forgotten and it becomes an
iterative process.

Instead, I have started using a loose version of the Case Approach and find
it to be much better when working with clients and non-technical people.
Talking tables, data... with them is useless, they just want a functional
tool. As such, you start from the end result (with them) and then reverse
engineer the required tables,queries.... to achieve what they want! I know
it sound a little ass backwards, but it really does work!!! Sit down and
draw up the desired forms and reports with the client/manager/boss. Then
take that information and go and determine the required tables, queries....
to make it happen and then built it.
--
Hope this helps,

Daniel Pineault
http://www.cardaconsultants.com/
For Access Tips and Examples: http://www.devhut.net
Please rate this post using the vote buttons if it was helpful.



"ScottMsp" wrote:

Hello,

I am looking for recommendations on what software development methodologies
to use for developing a Microsoft Access application. I know there are many
different types of methodologies/steps for going through the process, and I
am looking for recommendations from the experts on what they would recommend.


In terms of my experience, I have strong knowledge of the business side of
what we are trying to accomplish, but not as much software development
experience. I use Access often and build small databases, but what I am
trying to build now will be more in depth (I estimate having 11 – 13 separate
tables, lots of forms, reports, and queries). I want to be sure that I am
systematic about putting this together so nothing is missed and that it is
tested correctly.

Also, if you have any "must have" literature recommendations, that would be
appreciated.

Thanks in advance.

ScottMsp wrote:

I am looking for recommendations on what software development methodologies
to use for developing a Microsoft Access application. I know there are many
different types of methodologies/steps for going through the process, and I
am looking for recommendations from the experts on what they would recommend.


In terms of my experience, I have strong knowledge of the business side of
what we are trying to accomplish, but not as much software development
experience. I use Access often and build small databases, but what I am
trying to build now will be more in depth (I estimate having 11 – 13 separate
tables, lots of forms, reports, and queries). I want to be sure that I am
systematic about putting this together so nothing is missed and that it is
tested correctly.

I tell prospective clients that my first system to them will only be
70% right. It will do what they want basically but there will be
lots of little things that they will then tell me that they need.

Or sometimes they want bigger things. But I will then tell them that
bigger things are for the next phase.

It's very much an iterative approach. When working on site I use the
free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the
FE on each PC up to date.

When working off site and the users have started entering data then I
use Compare'Em
http://home.gci.net/~mike-noel/Compa.../CompareEM.htm to update
thier backend MDB table, fields, indexes and relationships.

Also see Ultra Frequent Application Deployment
http://www.granite.ab.ca/access/ufad.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/