In Switch_box, there is a free tool called the Logical Framework Tool
(LFT). With it a project manager can design the application for structure
of objects, methods, and actor messages using a tree menu. The tool allows
multiple top levels called design. Using the tree, add objects nodes that
form the structure of the application. And in each object, define nodes
that name of the methods. Using the cut and paste tools, objects and
methods can be moved from design to design or even within the design from
level to level. There is even a code generator that will write all the
structure templates and empty templates for the methods.
All the data from the LFT is stored in a database as a logical model. There
is no need for XML models, template models, modeling languages or graphic
drawings of the design. The framework is the tree. If some CF code is
necessary, run the generator for object or method nodes. All members of the
design team can work from the same on-line model. Because the model is kept
in a database, the project manager has all the benefits of the database to
manage, track, organized, plan and design. When an add, delete, change or
cut and paste is done on the tree, the changes are made in the database.
All records are stamped with who and when. Each node on the tree comes with
a form that captures design information. Since the code is open source GPL,
the forms can be changed to fit the user's business needs.
The real work in an application is in the methods. The LFT separates
structure from function. Need to change the structure, change the tree.
Structure can be automatically generated. That allows all programmer
resource for methods. (With my new CFSQL tools, a lot of the method code
for database can be generated with some checkbox selection.)
For software life cycle iterations, create a new top level design then copy
the logical framework for the previous design and paste into the new
design. All the sub-node object and methods from the old design are now the
starting point for the new design while keeping the old design in tact.
Switch_box itself is an object oriented execution (OOE) framework in which
the execution instructions come from a request message. Each request
message is compared to the logical model and runs the plan defined in the
LFT model. The software cycle benefit to this strategy is reduction of the
change cost using the OOE strategies from different designs by reusing the
same structures.
Joseph
At 01:09 PM 3/3/2004, you wrote:
>I'm taking the "opportunity to excel" here at work and trying to bring
>some order to our web application development. For the last year we have
>been a team of two experienced CF developers, the previous year there was
>only one. Pretty much working ad hock on projects as they came along with
>little formal documentation. A single developer was pretty much
>completely responsible for each project. This has worked well enough for
>the mostly smallish projects we have done to date.
>
>Success has lead to more confidence by management and they are beginning
>to authorize more ambitious projects that will be beyond the scope of what
>a single developer can do in a reasonable amount of time. Cool stuff with
>1+ man years of development.
>
>To accommodate these projects our team is expanding. We are adding 3
>junior CF developers to the team. I believe we need to grow up and become
>more professional. Start applying a standard, formal software development
>process. Allowing multiple team members with different skill levels to
>work on these large projects.
>
>What I'm looking for are Software Life Cycle documentation templates,
>preferably free. When I've tried to Google for this stuff I only find
>examples that somebody wants to sell me (or even more costly entire
>consulting packages). I'm hoping some of you may have worked, or better
>yet managed, larger teams responsible for creating ColdFusion web
>applications and are willing and able to share some templates for
>Requirements, Design, Detailed Design type documentation or maybe know of
>a good resource where I might get these type of templates.
>
>Also any nice suggestions for basic information on web application project
>management would be most appreciated. I've had overviews of analysis and
>design in classes, read about why formal processes good in many places,
>but this will be the first time I've ever tried to be anything like a
>"senior" developer after some seven years of mostly solo and duet work.
>
>scary, Scary, SCARY thought on many levels.
>
>Thanks for reading my combination plea/rant.
>Eternal thanks for any information.
>
>--------------
>Ian Skinner
>Web Programmer
>BloodSource
>www.BloodSource.org
>Sacramento, CA
>
>"C code. C code run. Run code run. Please!"
> - Cynthia Dunning
>
>Confidentiality Notice: This message including any
>attachments is for the sole use of the intended
>recipient(s) and may contain confidential and privileged
>information. Any unauthorized review, use, disclosure or
>distribution is prohibited. If you are not the
>intended recipient, please contact the sender and
>delete any copies of this message.
>
>----------
>[
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
