📄 function points step by step.htm
字号:
<td width="59%" valign="TOP"><font face="Arial">Was response time or throughput required
by the user?</font></td>
</tr>
<tr>
<td width="7%" valign="TOP"><font face="Arial">4.</font></td>
<td width="34%" valign="TOP"><font face="Arial">Heavily used configuration</font></td>
<td width="59%" valign="TOP"><font face="Arial">How heavily used is the current hardware
platform where the application will be executed?</font></td>
</tr>
<tr>
<td width="7%" valign="TOP"><font face="Arial">5.</font></td>
<td width="34%" valign="TOP"><font face="Arial">Transaction rate</font></td>
<td width="59%" valign="TOP"><font face="Arial">How frequently are transactions executed
daily, weekly, monthly, etc.? </font></td>
</tr>
<tr>
<td width="7%" valign="TOP"><font face="Arial">6.</font></td>
<td width="34%" valign="TOP"><font face="Arial">On-Line data entry</font></td>
<td width="59%" valign="TOP"><font face="Arial">What percentage of the information is
entered On-Line?</font></td>
</tr>
<tr>
<td width="7%" valign="TOP"><font face="Arial">7.</font></td>
<td width="34%" valign="TOP"><font face="Arial">End-user efficiency</font></td>
<td width="59%" valign="TOP"><font face="Arial">Was the application designed for end-user
efficiency?</font></td>
</tr>
<tr>
<td width="7%" valign="TOP"><font face="Arial">8.</font></td>
<td width="34%" valign="TOP"><font face="Arial">On-Line update</font></td>
<td width="59%" valign="TOP"><font face="Arial">How many ILF’s are updated by On-Line
transaction?</font></td>
</tr>
<tr>
<td width="7%" valign="TOP"><font face="Arial">9.</font></td>
<td width="34%" valign="TOP"><font face="Arial">Complex processing</font></td>
<td width="59%" valign="TOP"><font face="Arial">Does the application have extensive
logical or mathematical processing?</font></td>
</tr>
<tr>
<td width="7%" valign="TOP"><font face="Arial">10.</font></td>
<td width="34%" valign="TOP"><font face="Arial">Reusability</font></td>
<td width="59%" valign="TOP"><font face="Arial">Was the application developed to meet one
or many user’s needs?</font></td>
</tr>
<tr>
<td width="7%" valign="TOP"><font face="Arial">11.</font></td>
<td width="34%" valign="TOP"><font face="Arial">Installation ease</font></td>
<td width="59%" valign="TOP"><font face="Arial">How difficult is conversion and
installation?</font></td>
</tr>
<tr>
<td width="7%" valign="TOP"><font face="Arial">12.</font></td>
<td width="34%" valign="TOP"><font face="Arial">Operational ease</font></td>
<td width="59%" valign="TOP"><font face="Arial">How effective and/or automated are
start-up, back-up, and recovery procedures?</font></td>
</tr>
<tr>
<td width="7%" valign="TOP"><font face="Arial">13.</font></td>
<td width="34%" valign="TOP"><font face="Arial">Multiple sites</font></td>
<td width="59%" valign="TOP"><font face="Arial">Was the application specifically designed,
developed, and supported to be installed at multiple sites for multiple organizations?</font></td>
</tr>
<tr>
<td width="7%" valign="TOP"><font face="Arial">14.</font></td>
<td width="34%" valign="TOP"><font face="Arial">Facilitate change</font></td>
<td width="59%" valign="TOP"><font face="Arial">Was the application specifically designed,
developed, and supported to facilitate change?</font></td>
</tr>
</table>
<b><p><font face="Arial">Step 4 - Inventory of Transactions and Files</font></b></p>
<p><font face="Arial">A complete inventory of all Function Point Components (EI’s,
EO’s, EQ’s, ILF’s and EIF’s) should be completed prior to classifying
the individual components. It is best to inventory all transactions prior to taking an
inventory of the files. As transactions are inventoried, a listing of files needed for the
transactions should be maintained. After the inventory of transactions is complete the
file listing should be reviewed. Completing a the file inventory this way helps to insure
files that are not ILF’s or EIF’s have not been included.</font></p>
<p><font face="Arial">External Inputs (EI) - is an elementary process in which data
crosses the boundary from outside to inside. This data may come from a data input screen
or an other application. The data is used to maintain one or more internal logical files.
A good source of information to determine EI’s are Screen Layouts, Screen Formats
& dialogs, and layouts of any input forms. Additional inputs from other applications
should be inventoried here. Inputs from other applications must update ILF’s of
application being counted.</font></p>
<p><font face="Arial">External Outputs (EO) - an elementary process in which <strong>derived
</strong>data passes across the boundary from inside to outside. The data creates reports
or output files sent to other applications. These reports and files are created from one
or more Internal Logical Files A good source of information to determine the EO’s are
report layouts and electronic file formats that are being sent outside the application
boundary.</font></p>
<p><font face="Arial">External Inquiries (EQ) - an elementary process with both input and
output components that result in data retrieval from one or more Internal Logical Files.
The input process does not update any Internal Logical Files, and the output side does not
contain derived data. A good source of information to determine the External Inputs
(EI’s) are Screen Layouts, Screen Formats & dialogs, and layouts of any input
forms</font></p>
<p><font face="Arial">Internal Logical Files (ILF) - a user identifiable group of
logically related data that resides entirely within the applications boundary and is
maintained through External Inputs. A good source of information to determine the
ILF’s are logical and/or preliminary physical data models, table layouts, data base
descriptions. </font></p>
<p><font face="Arial">External Interface Files (EIF) - a user identifiable group of
logically related data that is used for reference purposes only. The data resides entirely
outside the application and is maintained by another application. The External Interface
File is an Internal Logical File for another application. A good source of information to
determine EIF’s are interfaces descriptions with other systems.</font></p>
<p><font face="Arial">The completed inventory of components should be distributed among
the project team to insure that everything has been included. Once it is confirmed that
all transactions and files have been included, then classifying individual components can
take place. </font></p>
<b><p><font face="Arial">Step 5 - Classification of Components</font></b></p>
<p><font face="Arial">It is important to understand the matrix’s associated with the
transactions (EI’s, EO’s, EQ’s) and files (ILF’s, EIF’s). The
counter should identify the appropriate row prior to determining the column. There is much
less granularity in determining the appropriate row (number of files referenced for
transactions and the number of record types for files) than determining the appropriate
column. This helps reduce the amount of effort required to complete a function points
count. </font></p>
<p><font face="Arial">Extending the above analysis, commonality should be considered prior
to counting transactions and files. The function point counter should ask the following
type of questions to help expedite the counting process.</font></p>
<blockquote>
<blockquote>
<p><font face="Arial">External Inputs - <i>Do external inputs need more or less than 3
files to be processed?</i> For all the EI’s that reference more than 3 files, all
that is needed to know is if the EI has more or less than 4 data element types referenced.
If the EI has more than 4 DET’s the EI will be rated as high, less than 4 DET’s
the EI will be rated as average. Any EI’s that reference less than 3 files should be
singled out and counted separately.</font></p>
<p><font face="Arial">External Outputs - <i>Do external outputs need more or less than 4
files to be processed?</i> For all the EO’s that reference more than 4 files, all
that is needed to know is if the EO has more or less than 5 data element types. If the EO
has more than 5 data element types then the EO will be rated as high, less than 5 the EO
will be rated as average. Any EO’s that reference less than 4 files should be singled
out and counted separately.</font></p>
<p><font face="Arial">External Inquires - the same analysis can be conducted as outlined
in EI and EO, but using the higher of the EI and EO as prescribed in the IFPUG counting
practices manual. </font></p>
<p><font face="Arial">Internal Logical Files and External Interface Files<i> - Do all
files contain one record type of more than one record type?</i> If all or many of the
files only contain one record type, then all that is needed to know if the file contains
more or less than 50 data elements types (DET’s). If the file contains more than 50
data elements the file will be rated as average, if less than 50 data element types the
file will be considered low. Any files that contain more than one record type can be
singled out and counted separately.</font></p>
</blockquote>
</blockquote>
<b><p><font face="Arial">Step 6 - Review 14 General System Characteristics</font></b></p>
<blockquote>
<blockquote>
<p><font face="Arial">The 14 GSC’s should be reviewed to insure accuracy. Each
GSC’s is rated on a scale from zero to five where from no influence to strong
influence. Once all the 14 GSC’s have been answered, they should be tabulated using
the IFPUG Value Adjustment Equation (VAF) --</font></p>
<font size="2">
</blockquote>
</blockquote>
<p><font face="Arial">14 where: Ci = Each General System Characteristic</font></p>
<p><b> </p>
<p></b><font face="Arial">VAF = 0.65 + [ ( ⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -