Re: Software Life Cycle Development Templates
Ian: 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,
Re: Software Life Cycle Development Templates
Ian- If you don't mind reading a bit, I recommend two great books by Steve McConnell: 1)Rapid Development 2)Software Project Survival Guide He also has quite a bit of templates forms on his company's website.Of course they sell a package, but quite a bit is free for the taking. http://www.construx.com/cxone/basic/map.php Best Regards- Andrew 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]
Re: Software Life Cycle Development Templates
Here are a few more excellent books: -Fusebox: Developing ColdFusion Applications -The Inmates are Running the Asylum -About Face 2.0 -The Mythical Man Month The first book explains the FLiP process sin detail. The second 2 are on a subject called interaction design, which describe how to bring the end user back into the process. The last one is just a classic. Steve Andrew Spear wrote: Ian- If you don't mind reading a bit, I recommend two great books by Steve McConnell: 1)Rapid Development 2)Software Project Survival Guide He also has quite a bit of templates forms on his company's website.Of course they sell a package, but quite a bit is free for the taking. http://www.construx.com/cxone/basic/map.php Best Regards- Andrew 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]
Software Life Cycle Development Templates
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]
OOPS WAS: Software Life Cycle Development Templates
Meant to post this to the CF-Talk list.Feel free to ignore this if you believe it to be off topic. 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]
RE: Software Life Cycle Development Templates
I would like to have a look at the templates also if any of you have them. Thanks -Original Message- From: Ian Skinner [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 03, 2004 12:09 PM To: CF-Talk Subject: Software Life Cycle Development Templates 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]
Re: Software Life Cycle Development Templates
Ian, Before you commit to the BDUF (Big Design Up Front) philosophy of software development, I recommend you take a look at XP/Agile and their associated practices. There is a lot of extremism associated with XP, but underneath the shouting there are some very valid concepts (IMHO). For example, I've found Test-Driven Development (TDD) to have made a tremendous difference in the stability of my released code. The Planning Game, User stories, short iterative cycles have also proved valuable. Some adherents will claim unless you are doing all 12 principles of XP you aren't doing XP, which may be so, but I've found there is still value in adopting the pieces that provide immediate value. Plus, XP/Agile is a philosophy, not just practices, and by introducing some practices first, philosophical objections to XP/Agile might be more easily persuaded. Since you're starting from scratch and appear to have management behind you, I think you are in a good position to make XP/Agile work for you. Just my $.02. Dave Jones NetEffect At 12:09 PM 3/3/04 -0800, 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]
RE: Software Life Cycle Development Templates
Thanks. We actually have a fairly clean slate here and are free to pick most any process (or mix and match elements from various processes).The biggest culture shock is going to be using any kind of up front documentation.To date the nature of the projects done here has allowed the jump in and code, document afterwards -- if you get around to it development process to actually result in successful completion even though it also results in a lot of rebuilding the wheel coding. Any recommendations on a better then the other's overview of this [XP/Agile]?Before I jump in to Google and pick the top item returned? -- 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]
Re: Software Life Cycle Development Templates
I'm all about sharing with the community. But usually these sort of processes are not shared. In fact a business can even have them patented/copyrighted. -Original Message- From: Tim Do [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 3, 2004 08:19 PM To: 'CF-Talk' Subject: RE: Software Life Cycle Development Templates I would like to have a look at the templates also if any of you have them. Thanks -Original Message- From: Ian Skinner [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 03, 2004 12:09 PM To: CF-Talk Subject: Software Life Cycle Development Templates 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]
Re: Software Life Cycle Development Templates
Ian, The catch is of course the free versions of good software methodology is very complex and the more watered down version costs money. If you have a lot of time on your hands CMM or capability maturity model might do the trick. See http://www.sei.cmu.edu/cmm/cmm.html Be forwarned... CMM is very complex , lengthy and can be quite expensive to become a certified software company. However, there is a lot of great insight to be learned here -- since software metholody should work for any language Now moving this into the real world, where we have time pressures, no formalized stucture to force us into best practices... I'd suggest taking a look at Flip over at the Fusebox.org site. What's important here is how the software development cycle fundementals are managed (not the fact that the process uses Fusebox.. let me make that clear). To strip the process even further, let's take a look at the traditional Waterfall model. 1) Your functional requirements should flow from your project charter or approved proposal. Good requirement documents provide anaylsis of roles, the types of information the application needs to present, the types of reports needed, the audiance, and things like how they will access information. Requirements documents should be short and to the point... let the wireframe process take care of business rules as you discuss these with the client. 2) Your wireframes displaying the graphical functionality of your application should flow from your functional requirments. This is the palce where you begin to finalize the business rules and begin tracking change requests (and potentally assigning project steps) 3) Your Object model should be created in parrell with wireframe development. Object models being more important in flash, Java and .Net projects than CF, however with CFCs this step is now included. My object models include stored proceedures and any user defined functions I might need. 4) Your Data model should flow from the Object model and business rules decided though the wireframe process 5) Your application should flow from the data model, object model and wirefram 6) Your functional test plan should flow from the wireframe model. At some point around here there should be a functional freeze on your project. Ditto for the design test and useability test plans 6a) Useability and design tests occur here. This is where you'll recieve feedback from users. 7) Your deployment should follow 8) Your technical documentation should be explaining the data model, object model, and wireframes as well as production information 9) Your user guide should be a dressed up verion of the wireframe with the associated bells and whistles 10) In the waterfall model, the client looks at the application and makes changes based upon changes in the model and create another project charter if changes are needed. With all of this said, many followsome or may even add more steps to this process. If you're a MS project user, with this documentation you can assign tasks based upon your findings from these steps. Jeremy Brodie Edgewater Technology web: http://www.edgewater.com phone:(703) 815-2500 email: [EMAIL PROTECTED] 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
RE: Software Life Cycle Development Templates
I'm all about sharing with the community. But usually these sort of processes are not shared. In fact a business can even have them patented/copyrighted. That's what I'm learning from my Googling (scary that that is a word).It can cost serious money to get something like this.But there is no budget to do this so paying for something is not going to happen at this time. I'll may just have to try an create something home grown.Since I've and nobody here has ever done anything formal like this, I was hoping for a leg up.That maybe somebody had something they were willing to share. -- 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]
RE: Software Life Cycle Development Templates
Ian, Check out www.fusebox.org . You can't go wrong there. FLiP will do evrything you're asking. Greg -Original Message- From: Ian Skinner [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 03, 2004 3:09 PM To: CF-Talk Subject: Software Life Cycle Development Templates 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]
Re: Software Life Cycle Development Templates
One of the nice things about FLiP is that each step builds on the previous step. Each step is has a clear beginning and end. By the time you start writing cfml and sql you don't have to second guess yourself. For example. Start with a wireframe. It provides a skeleton of the process, nothing more. Unlike a flowchart or a UML model, it is made of actual HTML pages with links. The next step, the prototype, builds right on top of the wireframe. In the prototype, flesh out the look and feel of the text descriptions from the wireframe, nothing more. When the prototype is done, an architect breaks down each page into files and variables, nothing more. From these files and variables, Fusedocs are written providing every file in the application with documentation for afterwards and blueprints for writing the code. From the variables a database is easily designed and normalized. From the Fusedocs, html and database every page is coded with cfml and sql. From the Fusedocs, a test harness can be generated to test every file in the application. Then it all plugs back together. Besides the documentation/blueprints (who needs documentation right?), each of these steps are things all of us do at one point or another. For some cf developers, a step is done in their heads (the wireframe) , or steps are done at the same time (cfml + html) or steps are done in different orders (the database design first). The FLiP process is a very efficient way of ordering these development steps we all do. The benefits I have personally gained by using FLiP are so vast they are unmeasurable. Steve Nelson Greg Luce wrote: Ian, Check out www.fusebox.org . You can't go wrong there. FLiP will do evrything you're asking. Greg -Original Message- From: Ian Skinner [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 03, 2004 3:09 PM To: CF-Talk Subject: Software Life Cycle Development Templates 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]
