I'm currently working on a revision of an application I wrote for
myself a while back which is basically a utility for the management of the
Application lifecycle from initial Project to Client Sales & Distribution.
It is primarily target for the single-seat Development shop or freelance
shareware developer.
There are currently Three main modules to the application, each one
in turn having it's own series of modules which may or may not be combined
with the secondary modules of the two other main Modules. ( Try to say THAT
fast! <g> )
The three Main Modules are:
Projects
Applications
Clients
Under "Projects", all pertinent information regarding the project is
added to a database list. So far this includes for each Project added to
the dB list:
Project name
Internal/Code name
Version
Build #
Compiler/Language
Date Started
Date Completed
Information Memo/Description etc.
From the Projects module one can then open up the following
secondary modules:
Archives...a dB of dated zip archives of all project files and dir structure
plus any additional files of any type or purpose. ( note this is not version
control, just dated Archives that can be created automatically or manually
and re-opened to a new or the same directory structure )
To Do List...each Project has it's own list of To do's and any relevant
notes, dated and with completion times/urgency
Journal...each Project has a dated Journal/diary to keep track of project's
progress, needs, problems, etc.
The "Applications" Module is a dB list of all completed projects
whether released and/or sold. It includes the same kind of pertinent info
that each Project contains as well as information areas for sales type,
price, tracking, etc., and indexes into the Project Archive for the final
compile. It also contains a separate Bug Tracking and completion Module dB
for keeping track of reported problems, needs, wants, as well as your own
ideas for future enhancements.
The "Clients" Module again is a dB of all clients and/or customers
who have contracted and/or purchased any of the Applications listed. Again
all pertinent information about the client and sales methods, contract or
sales price, any discounts given, other apps sold to same client, etc.
Although there are a number of various tables and child tables
involved in the database itself, everything is cross-indexed so that any
relationships between items listed in any module can be easily located from
any other module, and although the first version didn't include it I'm
considering adding a report form that can be run monthly for handling sales
and tax information.
Why am I telling you all about this? Because I've looked at quite a
few different applications meant to serve this same kind of purpose and have
attempted to streamline the information required and add in what others have
missed. If anyone has any particular areas of interest in an application
like this or one of it's modules, and has any suggestions for data items I
should not forget to include, or referencing methods I should be sure are
available, I'd like to hear from you. Even if you have a pet peeve about
apps of this type or have had problems with them in the past, any
information you might wish to share would be helpful as I want to make sure
this application is as broadly useful as possible.
Please send any responses directly back to me unless it's something
worth discussing that you think would be of value to the group as a whole.
Reply to me at: [EMAIL PROTECTED]
Thanx in advance!
from Robert Meek dba Tangentals Design CCopyright 2006
Proud to be a moderator of "The Delphi Lists" at elists.org
(["An unused program is the consequence of a higher logic!", nil]) As
written in The Compendium of Accepted Robotic and Surrlogic Theorems Used in
the Self Analysis of Elemental Positronic Pathways...1st Edition Revised
__________________________________________________
Delphi-Talk mailing list -> Delphi-Talk@elists.org
http://www.elists.org/mailman/listinfo/delphi-talk
