knowledge-database (beta)

Current group: comp.software-eng

Methodology Goal *Redefined*

Methodology Goal *Redefined*  
MethodMan
 Re: Methodology Goal *Redefined*  
Phlip
 Re: Methodology Goal *Redefined*  
Victor
 Re: Methodology Goal *Redefined*  
MethodMan
From:MethodMan
Subject:Methodology Goal *Redefined*
Date:19 Jan 2005 05:27:03 -0800
Following the thread of Methodology Goals, I originally defined the
goal of a methodology to "develop software faster, cheaper, and
better." That thread seemed to evolve into something else so I started
a new one. After discussion, I think I will refine the goal of a
methodology.


The goal of a software development methodology is to meet the needs of
the business. Typical business needs could include controls on
quality, schedule, and cost.


This new definition is even more high level and is not exclusive of
business needs not mentioned. But it does imply that software is
driven by the business and should address business needs. I think that
is an import thing to distinguish. I think it is important to keep it
high level because the needs of business are not always the same from
company to company.

Does anyone not agree with this redefined definition of the goal of
software development methodologies? Please provide citations if you
can guide me to a better definition of the goal.
From:Phlip
Subject:Re: Methodology Goal *Redefined*
Date:Wed, 19 Jan 2005 14:07:03 GMT
MethodMan wrote:

> The goal of a software development methodology is to meet the needs of
> the business. Typical business needs could include controls on
> quality, schedule, and cost.

The goal of Software Engineering is to boost user productivity.

The goal of a "methodology" is to describe to software engineers, and their
business partners, how to boost user productivity.

--
Phlip
http://industrialxp.org/community/bin/view/Main/TestFirstUserInterfaces
From:Victor
Subject:Re: Methodology Goal *Redefined*
Date:Thu, 20 Jan 2005 16:32:29 +0200
Phlip wrote:
> The goal of a "methodology" is to describe to software engineers, and their
> business partners, how to boost user productivity.

What about

"The goal of a "methodology" is to describe to software engineers how to
boost THEIR productivity"?
From:MethodMan
Subject:Re: Methodology Goal *Redefined*
Date:20 Jan 2005 09:48:21 -0800
<
I just don't agree with that. That might be one of *your* goals, but
goals are business driven. This is the reason that the goal needs to
be more abstract so that it doesn't exclude any of your business goals.
Your business objectives might not be the same as mine.

I am trying to define the goals so that they apply to you and every
other business which is why it must be very high level.
   

Copyright © 2006 knowledge-database   -   All rights reserved