Software Quality Management
Useful Resources
Selected Reading
- The SQA Unit
- Role Of Management in QA
- Quality Assurance
- Software Process Assessment
- Standards and Certificates
- Measuring The Structure
- Albrecht’s Function Point Method
- Internal Product Attributes
- Analyzing Software Measurement Data
- Data Manipulation
- Software Metrics
- Software Measurement Validation
- Software Measurement
- Empirical Investigations
- Measurement Scales
- Measurement and Models
- Basics of Measurement
- Software Quality Metrics
- SQA Components
- Software Quality Factors
- Introduction
- Home
Useful Resources
Selected Reading
- Who is Who
- Computer Glossary
- HR Interview Questions
- Effective Resume Writing
- Questions and Answers
- UPSC IAS Exams Notes
Albrecht’s Function Point Method
Albrecht’s Function Point Method
功能点衡量标准为衡量软件应用的各种功能提供了标准方法。 它根据用户的要求和回报,从用户的角度衡量功能。 功能点分析是从用户角度衡量软件开发的标准方法。
最初由Albrecht设想的职能点措施随着1986年国际功能点用户小组(IFPUG)的成立而更加普及。 2002年,国际标准化组织功能点成为国际标准化组织标准——ISO/IEC 20926。
What is a Function Point?
FP(功能点)是可用于量化软件应用的最广泛功能类型指标。 它基于5个可识别的“功能”用户,分为2个数据功能类型和3个交易功能类型。 对于特定软件应用,每个要素都是量化和加权,计算其特征要素,如档案参考资料或逻辑框架领域。
由此产生的数字(未调整的FP)被归类为添加、修改或删除功能组,并与价值调整系数(VAF)合并,以获得最后数量的FP。 每种计数类型均采用不同的最终公式:申请、发展项目或增强项目。
Applying Albrecht’s Function Point Method
我们现在应了解如何运用Albrecht的职守点方法。 其程序如下:
Determine the number of components (EI, EO, EQ, ILF, and ELF)
<>> 外部投入的数量。 这些是数据从外部到内部跨越边界的基本过程。 举例来说,图书馆数据库系统进入了现有的赞助者图书馆卡号码。
Compute the Unadjusted Function Point Count (UFC)
每一构成部分的速率,平均或高。
关于交易(EI, EO, and EQ),评级以FTR和DET为基础。
根据下表,EI,参考文件2和10项数据内容将列为average。
| FTRs | DETs | |||
|---|---|---|---|---|
| 1-5 | 6-15 | >15 | ||
| 0-1 | Low | Low | Average | |
| 2-3 | Low | Average | High | |
| >3 | Average | High | High | |
(ILF and ELF), 评级依据RET和DET。
根据下表,ILF包含10个数据要素,5个领域将列为high。
| RETs | DETs | |||
|---|---|---|---|---|
| 1-5 | 6-15 | >15 | ||
| 1 | Low | Low | Average | |
| 2-5 | Low | Average | High | |
| >5 | Average | High | High | |
UFCs。
| Rating | Values | ||||
|---|---|---|---|---|---|
| EO | EQ | EI | ILF | ELF | |
| Low | 4 | 3 | 3 | 7 | 5 |
| Average | 5 | 4 | 4 | 10 | 7 |
| High | 6 | 5 | 6 | 15 | 10 |
Compute the Final Function Point Count (FPC)
补充价值调整系数(VAF),依据14个一般系统特性(GSC)。
| General System Characteristic | Brief Description | |
|---|---|---|
| GSC 1 | Data communications | How many communication facipties are there to aid in the transfer or exchange of information with the apppcation or system? |
| GSC 2 | Distributed data processing | How are distributed data and processing functions handled? |
| GSC 3 | Performance | Was the response time or throughput required by the user? |
| GSC 4 | Heavily used configuration | How heavily used is the current hardware platform where the apppcation will be executed? |
| GSC 5 | Transaction rate | How frequently are transactions executed daily, weekly, monthly, etc.? |
| GSC 6 | On-Line data entry | What percentage of the information is entered onpne? |
| GSC 7 | End-user efficiency | Was the apppcation designed for end-user efficiency? |
| GSC 8 | On-Line update | How many ILFs are updated by onpne transaction? |
| GSC 9 | Complex processing | Does the apppcation have extensive logical or mathematical processing? |
| GSC 10 | Reusabipty | Was the apppcation developed to meet one or many user’s needs? |
| GSC 11 | Installation ease | How difficult is conversion and installation? |
| GSC 12 | Operational ease | How effective and/or automated are start-up, back-up, and recovery procedures? |
| GSC 13 | Multiple sites | Was the apppcation specifically designed, developed, and supported to be installed at multiple sites for multiple organizations? |
| GSC 14 | Faciptate change | Was the apppcation specifically designed, developed, and supported to faciptate change? |
参照每个网站GSC,按0到5级计算,依据是它没有影响强势。
具体如下:
FPC = UFC * (0.65+(sum(GSC) * .01))
Complexity
复杂性是规模的单独组成部分。 两种类型:
解决办法的一致性 这是执行具体解决办法所需的资源。 它有两个方面。 它们是:
空间复杂度 这一资源是电脑记忆。
Measuring Complexity
复杂性的一个方面是效率。 它衡量任何能够作为算法模型的软件产品。
例如: 如果解决某一特定问题的所有案例的算法需要f(n) 计算,那么f(n)是最佳的,如果对于解决该问题的所有其他复杂算法,f是O(g)。 那么,特定问题的复杂性很大——问题解决办法最好算法的O。
Advertisements