Pass the IFPUG Certification I40-420 Questions and answers with ExamsMirror

Has the primary intent to maintain one or more ILFs

An elementary process to hold data or control information from outside the boundary

Has the primary intent to alter the behavior of a transaction

Has the primary intent to reference one or more EIFs

To enable comparison of functionality delivered by two applications

To determine maintenance support cost per function point

To understand the percentage of lines of code that is being reused across three different applications

To determine the effort and duration of a development project

An EIF can only be counted as an EIF for one application

An EIF must be an ILF in another application

An EIF is only counted by the application that uses all of its DETs

All of the above

Any person that specifies functional user requirements

Any person that influences the integrated diagram procedures

Any person or thing that communicates or interacts with the software at any time

Both A and C

If an EIF is used in multiple processes, count the EIF as many times as the number of processes

Every physical file referenced by an application is to be counted as an EIF for the application

If a group of data was not counted as an ILF, then it should be counted as an EIF

None of the above

an EIF for the application under study

an EIF for the application under study and an ILF for the other applications

an EIF for each application that references the file

None of the above

The boundary indicates the border between data and transaction function types

The boundary indicates the presence of external users and application domains

The boundary indicates the conceptual interface between the software under study and its users

The boundary indicates the presence of internal users and application domains

FPA measures software by quantifying the tasks and services (i.e. functionality) that the software provides to the user based primarily on logical design

FPA measures software by quantifying software functionality based on architectural attributes

FPA is a standardized method for measuring software development from the developer's point of view

FPA is a standardized method for measuring software maintenance based on the technology used for implementation

Functionality provided to the user to meet internal or external data storage requirements

An attribute that further describes one or more attributes of another entity

Two types of the base functional components identified in the IFPUG International Standard

Unique, user recognizable, non-repeated attribute

Application FS

Adjusted FS

Enhancement project FS

Development project FS