In C#$,$

Objectives:

$1.$ Design a Universal Windows Program $($UWP$)$

$2.$ Develop a Generic class that uses specific objects to support a business operation

$3.$ Reference business logic from a class Library to support the UWP

$4.$ Create a user friendly interface using XAML.

$5.$ Write event code to respond to user$$s actions and produce output

$6.$ Maintain business data using collections.

$7.$ Use LINQ to obtain results from a collection and produce output.

$8.$ Decouple programming logic and create an event based on business logic.

Preamble:

In Part A you developed an employee class hierarchy to represent the business logic of a payroll system. Part B is a

continuation of Part A$.$ Develop a UWP client application for maintaining Employee records and providing Payroll

information.

The key requirements of this Part include the following:

$1.$ Create a Generic class for Employee objects that encapsulates the payroll process for a given payroll period. The

class provides a method that returns a list of Employee payroll information for a given pay$-$period.

$2.$ Maintain Employee objects in a collection. Modify existing object data and Add new objects to the collection.

$3.$ Create an interface using XAML that provides the user components to locate employee records and maintain

employee data. This includes the option to create new Employees.

$4.$ Develop a custom event and use LINQ to provide Decision Support with a summary view

In this course you are expected to practice designing and building interfaces using XAML. Using your textbook and

researching on the Internet find examples of components from the tool box and learn how to apply them your UWP

solution for this assignment.

Instructions Part B:

$1.$ Complete the UWP assembly named PayRoll. Reference your Employee Class Library.

$2.$ Declare a class level collection of type $.$ At startup it should contain a sample of different employee

objects $(5$ of each type$).$ Add a method to your Library in the Data class that returns this collection of

Employees. In the Main Page constructor, call this method to retrieve the sample objects.

Note: The application retrieves, maintains, and adds employee objects using the collection.

$3.$ Create a generic class that works with Employee types to the Library assembly. Add a constructor with a

parameter that takes a DateTime representing the current pay period. A second parameter is a reference

containing a list $($collection or an array$)$ of Employees in the current pay period.

The generic class has one method named ProcessPayRoll that calls the methods of each employee type to

determine their pay, bonus, and deductions. The method returns a List collection where every element

in the collection contains a formatted string containing Employee information, current pay, bonus, and

PROG$1224$ Object Oriented Software Development

Programming Assignment Part B

deductions. The list is organized by type of employee. Example:

$123456789$ Peter Vanscoy $-$ Net: $5,400\mathrm{.}00-$ Bonus: $1,000\mathrm{.}00-$ Deductions: $1,200\mathrm{.}00$

Add read only properties to this class that return totals calculated for the current pay period including total

count of employees included in the pay period, total pay, total bonus, and a total for each of the deductions.

$4.$ Design a unique interface that contains the following. The interface may include several views $($Pages$).$

$$ The user selects employees from a list.

$$ Provide options using components the user interacts with to filter the list of employees. For example

filter by employee type $($Combo Box$),$ employee name or sin $($Text Box$),$ and employee start date $($Date

Picker$).$ The list should default to displaying employees in alphabetical order and only the employees

that match the user$$s filter. The list updates as the user changes or clears the filters.

$$ When a single Employee object is selected display their data in appropriate components such as Text

Boxes. The user makes changes to the data. Make sure the components match the employee type

selected. Components can be hidden or disabled when they are not applicable to the currently selected

employee.

Example: you have a Textbox for entering the hours worked but it should not be available when you

have a Salary employee selected. You can provide prompts in front of components that change as

different types of employees are selected to guide the user entering the data.

$$ Provide controls to Submit changes and to Add new Employee objects to the collection.

$$ Provide the user a way to select Employees for the current pay period and enter the Pay Period Date.

Display the current payroll information returned by the ProcessPayRoll method. A complete list of all

employee names and their pay information should be organized by employee type. You can provide this

view in many ways including a large Text Block.

$$ Optional Feature: Rather looking up Hourly employees to enter hours worked provide a list of all Hourly

employees where the user can easily e