Prepare
Practice
Interview
Aptitude
Reasoning
English
GD
Placement papers
HR
Current affairs
Engineering
MCA
MBA
Online test
Login
Characteristics of Value Adjustment Factor(VAF) in Function Point Analysis
Home
>>
Category
>>
Software Engineering (MCQ) questions and answers
>>
Software Specification & Measurement
Q. How many characteristics does Value Adjustment Factor(VAF) in Function Point Analysis have?
- Published on 24 Jul 15
a.
11
b.
12
c.
13
d.
14
ANSWER: 14
Related Content
Software Management (
10
)
Introduction of Software Engineering (
37
)
Software Specification & Measurement (
23
)
Software Process (
9
)
Process Modelling and SDLC (
18
)
Planning and Managing the Project (
26
)
Capturing the Requirement (
22
)
Designing the System (
20
)
Objects Design (
20
)
Program Writing (
20
)
Formal Modelling & Verification (
20
)
Delivering the System (
18
)
Maintaining the System (
21
)
Evaluating Products, Processes & Resources (
17
)
Software Process Improvement (
28
)
Improving Predictions, Products, Processes & Resources (
16
)
Discussion
Nirja Shah
-Posted on 05 Oct 15
- The value adjustment factor (VAF) is based on 14 general system characteristics (GSC's) that rate the general functionality of the application being counted.
- The degrees of influence range on a scale of zero to five, from no influence to strong influence.
- The characteristics are as follows:
1. Data communications - How many communication facilities are there to aid in the transfer or exchange of information with the application or system?
2. Distributed data processing - How are distributed data and processing functions handled?
3. Performance - Was response time or throughput required by the user?
4. Heavily used configuration - How heavily used is the current hardware platform where the application will be executed?
5. Transaction rate - How frequently are transactions executed daily, weekly, monthly, etc.?
6. On-Line data entry - What percentage of the information is entered On-Line?
7. End-user efficiency - Was the application designed for end-user efficiency?
8. On-Line update - How many ILF’s are updated by On-Line transaction?
9. Complex processing - Does the application have extensive logical or mathematical processing?
10. Reusability - Was the application developed to meet one or many user’s needs?
11. Installation ease - How difficult is conversion and installation?
12. Operational ease - How effective and/or automated are start-up, back-up, and recovery procedures?
13. Multiple sites - Was the application specifically designed, developed, and supported to be installed at multiple sites for multiple organizations?
14. Facilitate change - Was the application specifically designed, developed, and supported to facilitate change?
➨
Post your comment / Share knowledge
Enter the code shown above:
(Note: If you cannot read the numbers in the above image, reload the page to generate a new one.)
MCQs
English
Tutorials
Download
▲