Re: Full life cycle development

Rof wrote:

> Can someone please explain this term? I know it means requiremsnts
> gathering, design, development and testing, but is there a specific
> methodology/tool, like UML or PRINCE, or is it just the latest buzzword
> that recruiters are using to mean "every stage of the design and
> development process" - which any analyst/programmer worth his/her salt
> has been fully aware of for years?

It is a recruiter term for "You didn't just write one module to spec. you
were with a project from inception to release to maintenance."

However, the target employer might now think that a "lifecycle" is like a
Waterfall, where you spend a time only collecting requirements, then spend
time only designing, then implementing, debugging, and testing. That doesn't
work because it isolates decisions from their effects. But many companies
think "if we can just do it better next time, we will stop having problems
with all these late change requests."

So if lifecycle is important to an employer, research what they [try to] use
before interviewing.

--
Phlip
http://www.c2.com/cgi/wiki?ZeekLand




.