Free and Premium IFPUG I40-420 Dumps Questions Answers

An EO is defined as an elementary process that:

In the formula DFP = ADD + CFP, CFP denotes?

What is a (are) valid example(s) of code data?

Which of the following statements regarding an application is (are) true?

Which transactional function cannot alter the behavior of the application?

What is the definition of "consistent state?"

The functional complexity of an EO is based upon which of the following?

Which of the following is the definition of derived data?

Which term used in FP calculations reflects the size of the functions being changed by the enhancement project - as they are / will be after implementation?

Which elementary process processes data or control information sent from outside the application's boundary?

What is a "user"?

Which category (ies) of data entities is (are) usually identified to satisfy the Functional User Requirements?

Which statement(s) is (are) true regarding mandatory processing logic for an EQ?

The Robot Automation Program (RAP) is an application which allows factory technicians to create and edit the weld placement programs for various robots on the assembly line. Both transactions maintain the Weld Specification and Robot logical files.

The use may select and view reboot details:

The user may print individual welding program details:

From the Names of Possible Functions listed identify the transactional functions for the RAP application. Select N/A if a Name of Possible Functions does not apply.

Identify the functions used:

Data used by the Payroll Activity application is organized in the following logical groups:

The Absence file and Pay Period file were implemented as part of the technical solution to facilitate business transactions.

From the Names of Possible Functions listed identify the data functions for the Payroll Activity application. Select N/A if a Name of Possible Function does not apply.

Identify the data functions used:

ALERT SYSTEM - ALERT NOTIFICATION

• Brokers use the Alert Profile screen to maintain the Alert Profile logical file. They can Add, Change, Delete and View alert information.
• Brokers also maintain a list of many securities to monitor. The securities information is considered to be part of the Alert Profile.
• The Alert Profile record is not considered complete until at least one security has been entered. The account number, alert contact name, alert phone number, and security id are required fields. The user is required to enter at least one of the remaining fields: low price threshold, high price threshold, and high volume threshold, they may enter values in all three.
• When an Alert Profile record is Added a validation is performed on the account number against the Account Master logical file and a validation on the securities against the Securities logical file.
• When Alert Profile records are Changed a validation is on the account number against the Account Master. All fields can be modified.
• No validations are performed for the Alert Profile View.
• When an Alert Profile record is Deleted the user must enter the account number, alert contact name, alert phone number. The account number is validated against the Account Master.
• Error messages are displayed whenever validations fail

Select the complexity of each function:

A Call Center (CC) application is being enhanced to track two new pieces of Information. The CC will reference the two new DETs in five modified data functions.

• Productlogical file prior to the enhancement had 2 RETs and 25 DETs, the CC application had previously referenced 12 of those DETs.
• Literaturelogical file previously referenced 5 RETs and 19 DETs. The two new DETs are being added to another RET NOT previously referenced.
• Call Log logical file prior to the enhancement had 2 RETs and 19 DETs, the CC previously referenced all the DETs.
• Customerlogical file prior to the enhancement had 1 RET and 36 DETs, the CC previously referenced only 25 of the DETs.
• Contactlogical file prior to the enhancement had 1 RET and 68 DETs, the CC previously referenced all DETs.

Determine the complexity of the following functions:

Select the complexity for each function:

The High Point grocery store has implemented a frequent buyer program. Discounts on various products will be provided as an incentive for customers to register in the program. The Frequent Buyer (FB) application is being built to collect and store the customer information and to keep track of the purchasing patterns of the customers.

• The customers will fill out a form providing their contact information and other demographic information
• FB users will use the Customer screen to Add Customer information in the Customer Master logical file.
• FB users also use the Customer screen to View Customer information and Change Customer Information.
• The Customer List report lists all customers and is available for display by selecting the Customer List report option from the Main Menu.

• From the Names of Possible Functions listed identify the base functional components for the FB application. Select N/A if a Name of Possible Function Type does not apply.

A Call Center (CC) application is being enhanced to maintain and display 2 new pieces of information. The CC will add the 2 new DETs to all 5 of the modified transactional functions.

• The Product Summary Report had 2 FTRs and 12 DETs.
• Add Literature and Change Literature had 4 FTRs and 19 DETs.
• The Literature Report (no calculations or derived data) had 4 FTRs and 19 DETs.
• The Call Log Report (no calculations or derived data) had 1 FTRs and 19 DETs.

What is the complexity of the transactional functions after the enhancement?

Select the complexity for each function:

INTERNET APPLICATION (IA) -MAINTAIN INTERNET DATA

• From the IA main menu, the IA user selects the Purchase Item option.
• The Purchase Item option opens a screen which allows the user to pay their internet shopping bill after performing an inquiry of the items selected for purchase. The Pay Bill option updates the Customer logical file to store the date of last purchase. The Inventory logical file is updated to determine when stock is depleted. The Inventory logical file contains the following information: product id, units of measure, count of product on hand, count of product on order, count of product on back-order, and reorder point.
• The Product logical file is maintained by the PARTS application. Product contains product id, description, expected life of product, category, manufacturer, SKU, and weight.
• Upon the customer's first purchase, the Customer Information screen captures the following information about the customer and stores it on the Customer logical file which includes: customer number, name, street address, state/province/region, country, postal code, payment type, gender, and future email offer flag.
• The Purchase History logical file (PHF) is used to contain the history of customer purchases. The PHF contains a demographics section which contains the following: customer number, gender, product category, product id, and purchase frequency. The other part of the PHF contains information pertaining to the cost of purchases: customer number, purchase date, quantity, purchase cost, expected life of product. An additional part of the PHF contains information about email offers sent to the customer. This part of the PHF contains information: date of email, product id, sale price, sale end date, and offer end date.
• The purchase cost is stored in the PHF in US Dollars after conversion from the customer's local currency using the Currency logical file. The Currency logical file contains the following information: country currency converting from, country currency converting to, conversion rate, date and time of conversion rate.

Determine the complexity of the data functions:

Determine the complexity of the following function:

The Human Resources (HR) application contains 5 data functions.

Determine the complexity of data functions:

Select the complexity for each function:

PAYROLL APPLICATION - MAINTAIN EMPLOYEE TIME SCREEN

• Employees can Add or Update their weekly hours information by entering the project and absence data on the Maintain Employee Time screen. Data is saved to the Employee Payroll ILF.
• To begin the Add or Update from the Maintain Employee Time screen, the employee enters his/her employee badge number presses the Retrieve button. Retrieve will fill in the employee name and supervisor badge number from the Employee Master ILF, and will display the current pay period start date and end date from the Payroll Master ILF.
• Employees can Delete existing weekly hours information by entering his/her employee badge number and pressing the delete button on the Maintain Employee Time screen. When the employee presses the delete button the current pay period hours will be removed from the Employee Payroll ILF.

PAYROLL APPLICATION - EMPLOYEE PROJECT ACTIVITY REPORT

• The Employee Project Activity report is produced for each employee and routed electronically to that employee's email address. Each employee's project task hours for the current pay period are read from the Employee Payroll ILF. The report calculates and displays both daily and weekly total hours for the current pay period.

• From the Names of Possible Functions listed identify the transactional functions for the Payroll application. Select N/A if a Name of Possible Functions does not apply.

Identify the functions used.

The Procurement application user requires the ability to control how and when reports are printed. The following list shows the specific user requirements for generating reports:

• Display a list of reports that are available to be printed.
• The user selects a report to be printed. If report control information exists for the requested report, the report control is displayed from the Report Control logical file.
• If report control information has not been specified for the requested report, the user may add the following report controls:

• uk.co.certification.simulator.questionpool.PList@494c77f0

• If report control information exists for the requested report, the user may update or delete the report controls.

From the Names of Possible Functions listed identify the transactional functions for the Procurement application. Select N/A if a Name of Possible Function does not apply.

Identify the functions used:

Determine the complexity of the data and/or transactions identified in the following scenario:

• The Library Information System (LIS) user Adds new member information by entering the member code, the member name, the telephone number, the address and the starting membership date. Information is stored and maintained in the Member logical file.
• The LIS user Changes some member information or Deletes it, by entering the member code. The LIS retrieves all the information related to the member code and displays it on the screen. Then, the LIS user Changes all the data displayed, with the exception of the member code, or completely Deletes the member information. If the member code is not found in the Member logical file, then an error message is displayed to the user.
• The LIS user Views member information by entering the member code and/or the member name on the screen. All the member data is retrieved and displayed in the search results. If the member code and/or the member name is not found in the Member logical file, then an error message is displayed to the user.
• All functions are activated by pressing the OK button.

Determine the complexity for the following functions:

Select the complexity for each function:

ITEM CHECK-OUT SCREEN

• Library employees use the Item Check-Out screen when a member is ready check out the book(s) and/or magazine(s) he wishes to borrow. The library employee enters the member id number, and when the employee exits the member id attribute, if the member id is valid, the member name is retrieved from the Member Information logical file and displayed in the member name attribute. The library employee enters the item type (b for book, m for magazine) and the item code; the item title is retrieved from the Book Information logical file and displayed in the item title attribute. The library employee then enters the lending date and the due date, and presses the Add button. The information is stored in the Check-Out logical file.
• Library employees use the Item Check-Out screen to update the due date of a book or magazine if a member requests additional lending time. The employee enters the member id number, and when the employee exits the member id attribute, if the member id is valid, the member name is retrieved from the Member Information logical file and displayed in the member name attribute, the library employee enters the item type (b for book, m for magazine) and the item code; the item title is retrieved from the Book Information logical file and displayed in the item title attribute and the lending date and due date are retrieved from the Check-Out logical file. The library employee then updates the due date, and presses the Update button. The new due date is stored in the Check-Out logical file.
• The head librarian receives two reports from the Library Check-Out application. The first report is the Overdue Report which is a list of overdue items categorized into < 30 days overdue, 30 - 90 days overdue and > 90 days overdue.
• The second report is the Low Usage Report that calculates which fiction books have not been checked out in the last 24 months and lists the title of those books. This report is run on demand. A High Usage Report with the number of times an item has been checked out has been put on hold and will not be released.
• A proposed Member Check-Out Report with a list of books checked-out and recommended titles will not be developed until privacy issues have been resolved.
• From the Names of Possible Functions listed identify the transactional functions for the current Library Check-Out application. Select N/A if a Name of Possible Function does not apply.

Identify the functions used:

The Stock Purchasing (SP) and Point of Sale (POS) applications have the following requirements.

• The POS application maintains details of customer purchases in the Item Purchases logical file.
• The SP application is used to place orders with suppliers based on daily inventory levels.
• The SP application is used to maintain supplier information. The Supplier Information logical file contains descriptions of items the supplier stocks and supplier contact information.
• The Inventory logical file is maintained by the SP application through a daily batch process which references the Item Purchases logical file.
• When the batch process is complete, the SP application displays a list of items that are below 20% of normal inventory levels. The user selects items to be ordered and specifies the supplier. The SP application then generates a purchase order for each supplier. The purchase orders are sent electronically to each supplier and stored in the Order logical file.
• From the Names of Possible Functions listed identify the data function both the SP and POS applications. Select N/A if a Name of Possible Function does not apply.

Identify the functions used:

A transaction file contains records to maintain the Master file. A flag is included on each incoming record to indicate if the Master file record is to be added, changed or deleted. A batch job is developed to process the transaction file. How many transactional functions would be counted?

A Human Resources application has online field help for the add, change and delete transactions. The help facility is maintained by a separate application. How would the field help be measured for the Human Resources application?

An enhancement involves changing an EQ with 12 fields to include 3 extra fields. The EQ referenced 3 files before the change, and one extra file needs to be referred to as part of the change. How would the enhanced EQ be counted?

A database table is maintained by the application being counted. It has state code as the key attribute and state name as the only other attribute. How would this table be counted?

An enhancement adds 3 update screens to the application. Each of these screens updates 2 files and displays 17 data attributes. What is the functional size of the transactional functions after the enhancement?

An EO maintains 1 ILF and references 3 ILFs. What is the minimum number of DETs necessary for it to be valued at 7 UFP?

A Trading application introduces a new subsystem. The enhancement includes 6 new EIs, 3 modified EIs, 2 new EQs, 1 modified EO. 1 existing EO is eliminated from this application by this enhancement. There are 3 conversion EIs to convert existing data. All the transactional functions are average complexity. What is the functional size of the transactional functions for the enhancement?

How would you count the pie chart below?

Which is (are) method(s) of sharing data?

A file of user maintained help messages is kept current using the business administrator functionality of the system. How would this help message file be counted?

Which can NOT be en EQ?