Re: Full life cycle development

Not so fast Peter. What you received is not necessarily the stuff that
pours;-)

First of all your terminology is slightly off. What most of these good
people responded to is a question that might read, "What does a
full-life cycle Software methodology include?" What you asked is what
the software development cycle means.

Let me give you a slight heads up as to what some of these people are
arguing.

Generally speaking, a technique is a formal process for acheiving a
certain goal in a category of software automation. 'Use Case Analysis'
is an example of a technique used to formalize requirements. When these
techniques are customized they might be labeled with the 'guru's' name
and maybe have their own iconic notation. If that notation is
automated as well then it belongs to a toolset such as UML offered by
numerous Computer Aided-Software Engineering vendors, say, Rational.

A suite of many such techniques (sometimes further qualified as
'practices') can be bundled with a set of meta-materials and
automations to become a complete methodology. Some of the previous
comments are speaking of traditional (usually called heavyweight) and
newer methodologies (called lightweight). These things are sliced,
diced, and ordered by their advocates to suit the latest trendy
software engineering vernaculars.

When interviewing ask questions like, "What is the scope of the
lifecycle you're asking about?" In other words, "What will I be
involved with? Requirements gathering?, Design? Coding?, what?" Also
(diplomatically) ask if the employer is dogmatic about the stuff or
willing to take constructive feedback ("No offense but this isn't
working.").

If you are truly focusing on software development alone then you might
explore books like "The Practice of Programming" that are absolute gems
on becoming a better implementator of software. Other, language
specic, books exist as well and are usually best-sellers in their
genres. Do read - there's plenty of excellent prior art available.

Rof wrote:
> Whew! Thanks, folks. "You never know but it pours" - how true!
>
> 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?
> >
> > Cheers,
> > Peter Royle

.

Relevant Pages

  • Re: thesis topic
    ... Shayne Wissler wrote: ... > arguments for this or that tool, technique, or methodology, complete with ... (But recall Steve's somewhat against Emergent Design...) ...
    (comp.object)
  • Re: There are statistical flaws in Random Number Generators
    ... give you a 'slight' advantage over Online Casinos. ... The Gambling Geek has researched this and developed a methodology to take advantage of this anomaly. ...
    (rec.games.backgammon)
  • Re: Carevaro right hand studies...
    ... Try the Pujol books 2 and 3. ... methodology. ... If you follow his 2 year plan you will have a fantastic ... technique if studied properly. ...
    (rec.music.classical.guitar)