From: Majordomo (owner-re-online@it.uts.edu.au)
Date: Wed Apr 14 2004 - 10:07:35 EST
=09by marcie.it.uts.edu.au (PostfixFiltered) with ESMTP id C5D3D26239
=09for <re-online@it.uts.edu.au>; Tue, 13 Apr 2004 22:05:26 +1000 (EST)
Received: from hotmail.com (bay12-f67.bay12.hotmail.com [64.4.35.67])
=09by filter.it.uts.edu.au (Postfix) with ESMTP id 8D85B1D64D5
=09for <re-online@it.uts.edu.au>; Tue, 13 Apr 2004 22:05:20 +1000 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
=09 Tue, 13 Apr 2004 05:05:15 -0700
Received: from 151.201.122.175 by by12fd.bay12.hotmail.msn.com with HTTP;
=09Tue, 13 Apr 2004 12:05:15 GMT
X-Originating-IP: [151.201.122.175] X-Originating-Email: [donald_firesmith@hotmail.com] X-Sender: donald_firesmith@hotmail.com
Phil,
Not all requirements are of the same form and take the same amount of effor=
t
to produce. A single use case may have many paths and involve a lot of
ancellary information such as preconditions, interactions, and
postconditions. Whereas security and safety requirements may require
significant hazard/threat/risk modelling. There is also significant
differences in terms of the formality and completeness of use case modeling=
=2E
Therefore, a single metric such as requirements correctly completed per
person day may be overlysimplistic and may not be consistent from company t=
o
company or from project to project. You may need to provide some weighting
of the requirements by type.
That said, I can totally understand management's desire to understand the
productivity of the requirements effort (e.g., to be able to estimate neede=
d
staffing and help determine the need and effectiveness of training. I
suggest that you start by defining and collecting a reasonably small number
of metrics internally and then vet them based on input from the requirement=
s
engineers, management, and other requirements stakeholders.
Donald Firesmith
Senior Member of the Technical Staff
Acquisition Support Program
Software Engineering Institute (SEI)
Carnegie Mellon University (CMU)
Pittsburgh, PA 15213-3890
(412) 268-6874
dgf@sei.cmu.edu
http://www.donald-firesmith.com
>From: PFuhrer590@aol.com
>Reply-To: re-online@it.uts.edu.au
>To: RE-online@it.uts.EDU.AU
>CC: phillipfuhrer@sbcglobal.net
>Subject: [re-online] Question Efficiency and effectiveness of requirements
>processes and organization
>Date: Mon, 12 Apr 2004 19:58:52 EDT
>
>Friends,
>I have been working in the area of requirements engineering for many years=
,
>attended conferences, and monitored this forum for a long time.
>Now I am managing a small group (3 people) responsible for requirements an=
d
>I
>have been asked by my upper management to measure and optimize the
>efficiency
>of the group. The total size of the company is less that 25.
>My upper management thinks of efficiency as a simple mechanical measure of
>output divided by input where output is requirements and input is primaril=
y
>labor. I can envision some measure of effectiveness such as: amount of
>requirements identified; percentage of requirements captured correctly; or
>amount of
>rework required but I have no idea how to measure =E2=80=9Cmechanical
>efficiency.=E2=80=9D
>I would like the insight of this group to learn if anyone has used a =E2=
=80=9C
>mechanical efficiency=E2=80=9D model to measure and optimize the requireme=
nts
>efforts and to
>help with a simple measure of effectiveness that would work in a small
>company.
>Thank you Phil Fuhrer
This archive was generated by hypermail 2.1.6 : Mon Apr 19 2004 - 09:00:21 EST