Application life cycle includes various steps involved to have the system ready for use. For example, waterfall method is one famous software life cycle which includes
There are similar life cycle steps for other systems/applications.
You might try posting in the appropriate forum, here[^], for starters, as this has nothing at all to do with application lifecycle. Of course I would wait until after you read the "How to ask a question" posting that has already been suggested to you.
We are currently evaluating a GUI testing tool for Qt which can also do some automated white box testing.
The two candidates left are Squish and Ranorex. Does any of you guys already have experience either with Ranorex or Squish?
Those who are ignorant of history are doomed to repeat it. This is not only true of great conflicts, but equally true in the IT world. Too often costs exceed estimates, and we are ignorant as to why, or by how much. We do not have data to help us understand what went wrong, what went right, or how to apply it to the next project. We are ignorant of our history as a department, a company, and an industry.
If you all you have is a hammer, you tend to see every problem as a nail. Problem Solving 101: identify the problem, figure out what you need to fix it. If we agree that the problem is inadequate data to reconcile estimates and real costs, and use that information for future projects, then the solution is a tool that will collect, organize and distill that data into something usable. In other words, the solution is software. Not just any software, but software designed and tested by the boots-on-the-ground IT professionals who need and use the data.
I am interested to learn from the community what software or other mechanism people use to address software project estimation needs and cost/effort actuals analysis, as well as for project accounting.
Last Visit: 31-Dec-99 19:00 Last Update: 30-Jan-23 4:04