Has anyone else thought of this?
HP bought PALM for a billion dollars or more.
Then ALM was released. A billion bucks for the letter P.
I find the name ALM rather pointless/meaningless but I guess they are trying to sell its broader use, most places use it as a rather expensive defect manager only. Jira does a better job at that for no cost.
Test Director was a far better name, no idea why they dropped that. I guess it overlooked its requirements management capability but what does ALM mean ? Where I work now they write the requirements in a spread sheet as they have a specific format, same for the RTM ..... the TOMs are word documents ........ they only use the Test Case management/execution and defect management. Non-Testers (BA's, PMs and others) don't like the product at all as its too restrictive and clumsy. They may want it used for the full life cycle, all I see is a lot of information double handling when this tool is involved.
I like the concept of ALM, but I am yet to see anyone use it properly in a full collaborative way.
It means Marketing Managers love TLAs.
Originally Posted by rtehve
I worked on a project where I connected Excel to APIs in QC. The API documentation and examples were very cryptic. I was doing things such as looking at fields in defects and moving the defect to another state. I got it to work, but I was never sure if one API had a side effect on anytihing else. I think the term is non-orthoginal. Then the next version of QC had a load more APIs but the documentation did not improve. The product could be so much more useful if the API were explained better. The APIs were powerful and fun to tinker with but I was never absolutely sure if I broke anything.
The very fact you need to invoke API's to link it to excel defies the logic of the name.
If its an all encompassing SDLC too why do you want to use excel at all ?
What your trying to do is common practice as the general feed back is the tool does not have the reporting flexibility that most seem to want.
I like the concept of the tool, I just despise its incarnation. Our group has developed an engagement tracking web app which uses that API to give us a simple HTML/PHP representation of what we want to see from the tool. That way we don't suck up a concurrent user for this expensive tool for simple reporting, nor do we have to deal with is clunky interface.
I would prefer not to use the tool at all.