The Patient Billing application includes functionality to maintain the Patient logical file.

The user enters a patient id and presses the View button to display an existing patient record, including diagnosis description and insurance company name. An error message is displayed if the patient record does not exist.

The user Adds a new patient by entering a patient ID and the remaining values. The user completes the add by pressing the Add button. An error message is displayed if the patient id already exists.

The user Updates information about the patient. All attributes can be modified except for patient id. The user completes the update by pressing the Update button

A diagnosis code must be selected using a drop down list for the primary diagnosis and the secondary diagnosis. The drop down list function is identical for primary and secondary diagnosis. The Diagnosis logical file is maintained in the Patient Billing application and is the source for the Diagnosis Code Drop Down list. The Diagnosis Code Drop Down list displays the diagnosis code, description and authorized days of hospitalization.

An insurance company code must be selected using the Insurance Company Drop Down list. The Insurance logical file is used as the source. The Insurance Company Drop Down list displays the insurance company number, group type and name.

All other drop down lists use static data as the source.

Determine the complexity for the following functions:

Select the complexity for each function:

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

The application functional size after an enhancement project does NOT include the size of the:

The primary intent of an EI is to maintain:

Which of the following types of processing logic is (are) mandatory for an elementary process to be classified as an EQ?

Which is the correct formula for calculating the AFP after an enhancement project?

The Procurement application requires the ability to maintain information on each new supplier. The information that must be maintained on the Supplier logical file includes:

 Supplier id

 Supplier name

 Supplier mailing address

 Supplier skill

As a result of creating a new supplier record, the supplier ' s annual costs should be automatically calculated and saved with the other supplier information.

Orders are maintained in the Order logical file by the Procurement application. The Accounts Payable logical file is updated for each order. Line items for each order are stored in the Order Detail subgroup of the order logical file.

Backorders and delivery errors are tracked by the Procurement application on the Transparency Track Record logical file. This file is compared to each supplier ' s values in the Service Level Agreement logical file which is maintained by the Contract application. The Procurement application produces a report for the Legal Office of suppliers that are performing outside of their Service Level Agreement.

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

Identify the functions used.

LIBRARY INFORMATION SYSTEM (LIS)

The Lend Text functions allow the LIS user to register information about the texfs lending in the Lend logical file. Data stored and maintained in Lend are: ISBN code, enroll code, lend date, due date, return date.

LIS maintains information about the Distributors from whom the library orders books, magazines and other publications. Account number, distributor name and 10 other logical pieces of information are maintained.

Library Branch data is stored in LIS and is maintainable by the library staff. Information Is maintained on 10 branches. Data maintained includes branch id, branch name, location, directions, hours of operation, and 17 other logical pieces of information.

Purchase Wish List logical file is maintained by LIS. Employees enter books, magazines, video recordings, audio recordings and personal computer software that they believe the library patrons would be interested in borrowing. This list is used as a source when making purchase decisions. The information is grouped by media type and information is collected based on the media type.

There are 8 common pieces of data collected for all media types

book information contains 10 additional logical pieces

of data o magazine information contains 13 additional logical

pieces of data o video recordings information contains 12 additional

logical pieces of data o audio recordings information contains 14 additional

logical pieces of data

Employee logical file is maintained in the LIS application and contains information about the library staff, including employee id, name, address, full or part time status, and title.

Determine the complexity of the following functions:

Select the complexity for each function

EXAM SCHEDULING SYSTEM (ESS) - EXAM SCHEDULING FUNCTIONS

The controller uses the Maintain Exam Schedule screen to schedule exams for various courses and subjects.

The exam serial number from the University Master logical file is entered in the screen. On pressing the Retrieve key, the exam name, controller number, finals week start date and finals week end date efe displayed from the University Master logical file. In addition, exam status, course id, subject id, exam date, start time, end time, proctor and message are displayed from Schedule Information logical file.

The Add or Modify options allow addition/update to the course id, subject id, exam start date, start time, end time, proctor and message using the exam serial number as the key field. The data in the add/update mode gets saved in the Schedule Information logical file with the ' pending approval ' in the exam status, no other data is stored.

Course id, subject id and exam date pick lists provide data from static tables.

The exam dates should be within the finals week start and end dates

Determine the complexity for functions listed:

Select the complexity for each function:

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: