Multiple C# Programs

5/5.docx

STEP 1: Understand the UML Diagram

Analyze and understand the object UML diagram, which models the structure of the program.

· There are two new Employee derived classes (1) Salaried and (2) Hourly that are derived from the Employee class.

· The Employee class contains a new attribute employeeType and a new constructor that accepts as an argument the assigned employee type.

· Both the Salaried and the Hourly classes override only the CalculateWeeklyPay method of the Employee class (note, this is the method without any parameters.)

· The Salaried class has one attribute "managementLevel" that has possible values from MIN_MANAGEMENT_LEVEL to MAX_MANAGEMENT_LEVEL and a BONUS_PERCENT.

· The Salaried class has a default constructor and parameterized constructor that accepts all the general employee information plus the management level.

· The Hourly has a wage attribute, which respresents the hourly wage that ranges from MIN_WAGE to MAX_WAGE, a hours attributes, which represents the number of hours worked in a week that ranges from MIN_HOURS to MAX_Hours, and a category attributes that accepts string values.

· The Hourly class has a default constructor and parameterized constructor that accepts all the general employee information plus the hours and wage value.

· The Presentation Tier contains two new classes (1) The EmployeeInput class and the EmployeeOutput class

· The EmployeeInput class contains three static methods (1) CollectEmployeeInformation, which accepts any type of Employee object as a argument; (2) CollectHourlyInformation, which accepts only Hourly objects as an argument, and (3) CollectSalariedInformation, which accepts only Salaried objects as an argument.

· The EmployeeOutput class contains two methods (1) DisplayEmployeeInformation, which accepts any Employee type as an argument and (2) DisplayNumberObjects method.

· All the access specifers for the Employee attributes are changed to protected and are depicted with the "#" symbol.

Presentation Tier Description

The image of the presentation tier depicts 5 classes, the Program Class, ApplicationUtilities, InputUtilities, EmployeeInput, and EmployeeOutput. Only the EmployeeInput and EmployeeOutput classes are describe here. Both utility classes are the same as they were since given in Week 2. Program changes based on lab specification, not formal definition other than the Main method is specified.

EmployeeInput Class Diagram Description

What is depicted is a single column table with 3 rows. In the first row is the large word "EmployeeInput". The second row is blank. In essence there are no constructors since the methods in this class are all static. In the third and final row beneath this is a list of public methods, indicated with a "plus" symbol before them (but no space after). As stated previously, all these methods are static. These are: +CollectEmployeeInformation(in theEmployee : Employee) +CollectHourlyInformation(in theEmployee : Hourly) +CollectSalariedInformation(in theEmployee : Salaried) Lastly, there is a line between the Program class and EmployeeInput class indicating the uses relationship. The Program class uses the static methods from EmployeeInput.

EmployeeOutput Class Diagram Description

What is depicted is a single column table with 3 rows. In the first row is the large word "EmployeeOutput". The second row is blank. In essence there are no constructors since the methods in this class are all static. In the third and final row beneath this is a list of public methods, indicated with a "plus" symbol before them (but no space after). As stated previously, all these methods are static. These are: +DisplayEmployeeInformation(in theEmployee : Employee) +DisplayNumberObjects() Lastly, there is a line between the Program class and EmployeeOutput class indicating the uses relationship. The Program class uses the static methods from EmployeeOutput.

Logic Tier Description

The image of the logic tier depicts 4 classes, the Employee Class, the Benefits Class, the Hourly Class (derived from Employee), and Salaried Class (also, derived from Employee).

Employee Class Diagram Description

Note: no change in structure from Week 4 What is depicted is a single column table with 3 rows. In the first row is the large word "Employee". In the row beneath this is a list of private parameters, indicated with a "minus" symbol before them (but no space after), and protected members parameters, indicated with a “pound” sign. These are: -MIN_DEPENDENTS int =0 -MAX_DEPENDENTS int = 10 -MIN_SALARY double = 20000 -MAX_SALARY double = 20000 -DEFAULT_NAME string = "Not given" -DEFAULT_GENDER char = 'U' #firstName : string = DEFAULT_NAME #lastName : string = DEFAULT_NAME #gender : char = DEFAULT_GENDER #dependents : int = MIN_DEPENDENTS #annualSalary : double = MIN_SALARY #static numEmployees: int = 0 #benefit : Benefits #employeeType : string Note: only the instance members need to be set to protected, the Properties themselves will remain public. In the third and final row beneath this is another list of public parameters, indicated with a "plus" symbol before them (but no space after). These are: +Employee() +Employee(in type : string) +Employee(in type : string, in first : string, in last : string, in gen : char, in dep : int, in salary : double, in benefits : Benefit) +ToString : string +CalculateWeeklyPay() : double +CalcuateWeeklyPay(in modifiedSalary :double)

Benefits Class Diagram Description

Note: no change in structure from Week 4 What is depicted is a single column table with 3 rows. In the first row is the large word "Benefits". In the row beneath this is a list of private parameters, indicated with a "minus" symbol before them (but no space after). These are: -DEFAULT_HEALTH_INSURANCE string = “Blue Cross” -MIN_LIFE_INSURANCE double = 0 -MAX_LIFE_INSURANCE double = 1000000 -MIN_VACATION int = 0 -MAX_VACATION int = 45 -healthInsuranceCompany : string = DEFAULT_HEALTH_INSURANCE -lifeInsuranceAmount : double = MIN_LIFE_INSURANCE -vacationDays : int = MIN_VACATION In the third and final row beneath this is another list of public parameters, indicated with a "plus" symbol before them (but no space after). These are: +Benefit() +Benefit(in health : string, in life : double, in vacation : int) +ToString : string There is a line between the Employee class and Benefits class indicating the HAS-A relationship. The Employee class HAS-A Benefits class as a property. This denotes composition.

Hourly Class Diagram Description

Note: this is new this week What is depicted is a single column table with 3 rows. In the first row is the large word "Hourly". In the row beneath this is a list of private parameters, indicated with a "minus" symbol before them (but no space after). These are: -MIN_WAGE : double = 10 -MAX_WAGE : double = 75 -MIN_HOURS : double = 0 -MAX_HOURS : double = 50 -wage : double -hours : double -category : string In the third and final row beneath this is another list of public parameters, indicated with a "plus" symbol before them (but no space after). These are: +Hourly() +Hourly(in fname : string, in lname : string, in gen : char, in dep : int, in wage : double, in hours : double, in ben : Benefit, in category : string) +CalculateWeeklyPay() : double +ToString : string There is an arrow pointing from the Hourly class to the Employee class indicating the IS-A relationship. The Hourly class IS-A type of Employee. This is an example of inheritance.

Salaried Class Diagram Description

Note: this is new this week What is depicted is a single column table with 3 rows. In the first row is the large word "Salaried". In the row beneath this is a list of private parameters, indicated with a "minus" symbol before them (but no space after). These are: -MIN_MANAGEMENT_LEVEL : int = 0 -MAX_MANAGEMENT_LEVEL : int = 3 -BONUS_PERCENT : double = .10 -managementLevel : int In the third and final row beneath this is another list of public parameters, indicated with a "plus" symbol before them (but no space after). These are: +Salaried() +Salaried(in fname : string, in lname : string, in gen : char, in dep : int, in sal : double , in ben : Benefit, in manLevel : int) +CalculateWeeklyPay() : double +ToString : string There is an arrow pointing from the Salaried class to the Employee class indicating the IS-A relationship. The Salaried class IS-A type of Employee. This is an example of inheritance.

Press the ESC key to close the image description and return to lecture.

STEP 2: Create the Project

You will want to use the Week 4 project as the starting point for the lab. Use the directions from the previous weeks labs to create the project and the folders.

1. Create a new project named "CIS247_WK4_Lab_LASTNAME". An empty project will then be created.

2. Delete the default Program.cs file that is created.

3. Add the Logic Tier, Presentation Tier, and Utilities folders to your proejct

4. Add the Week 4 project files to the appropraties folders.

5. Update the program information in the ApplicationUtilities.DisplayApplicationInformation method to reflect your name, current lab, and program description

Note: as an alternative you can open up the Week 4 project and make modifications to the existing project. Remember, there is a copy of your project in the zip file you submitted for grading.

Before attempting this week's steps ensure that the Week 4 project is error free.

STEP 3: Modify the Employee Class

1. Change the access specifier for all the private attributes to protected.

3. Add a new constructor that only accepts the type attribute, which is then used to set the employeeType value. Also, this constructor should initialize all the default values. You can call the default constructor using the syntax: public Employee(string employeeType) : this() {}

4. Modify the parameterized constructor that accepts the employee information to accept the employee type, and then set the employeeType with this value.

5. Modify the ToString Method to include the employee type.

STEP 4: Create the Salaried Class

1. Using the UML Diagrams, create the Salaried class, ensuring to specify that the Salary class inherits from the Employee class.

2. For each of the constructors listed in the Salaried class ensure to invoke the appropriate super class constructor and pass the correct arguments to the super class constructor.

3. Override the CalculateWeeklyPay method to add a 10 percent bonus to the annualSalary depending on the management level. The bonus percent is a fixed 10 percent, and should be implemented as a constant. However, depending on the management level the actual bonus percentage fluctuates (i.e., actualBonusPercentage = managementLevel * BONUS_PERCENT).

4. Override the ToString method to add the management level to the employee information.

STEP 5: Create the Hourly Class

1. Using the UML Diagrams, create the Hourly classes, ensuring to specify that the Hourly class inherits from the Employee class.

2. For each of the constructors listed in the Hourly class ensure to invoke the appropriate super class constructor and pass the correct arguments to the super class constructor. Notice, that the Hourly employee DOES NOT have an annual salary, which we will then have to calculate (see below).

3. Create a Category property (get/set) and the valid category types are "temporary", "part time", "full time".

4. Create a Hours property (get/set) for the hours attributes and validate the input using the constants shown in the UML diagram, but since an Hourly employee does not have a formal annual salary we will need to calculate this each time the hour (and wage) properties are set. Add the following code after the validation code in the hours property: base.AnnualSalary = CalculateWeeklyPay() * 48; (assumes working 48 weeks a year).

5. Create an Wage property (get/set) for the wage attributes and validate the input using the constants shown in the UML diagram. Add the following code after the validation code in the wage property: base.AnnualSalary = CalculateWeeklyPay() * 48; (assumes working 48 weeks a year)

6. Override the CalculateWeeklyPay method by multiplying the wages by the number of hours.

7. Update the ToString method to add the category, hours, and wages to the hourly employee information.

STEP 6: Create the EmployeeInput Class

1. Create a new class in the Presentation Tier folder called "EmployeeInput"

2. Create a static void method called CollectEmployeeInformation that has a single Employee parameter. The declaration should look something like the following: public static void CollectEmployeeInformation(Employee theEmployee)

3. Write code statements similiar to what you created in the Week 4 project to collect the generic employee information from the user, except instead of using specific employee objects use the "theEmployee" parameters. For example: In Week 4, you had something like: employee1.FirstName = InputUtilities.GetStringInputValue("First name"); In the CollectionEmployeeInformation method this can be translated to the following; theEmployee.FirstName = InputUtilities.GetStringInputValue("First name");

4. Write statements to collect all the generic employee information, including the Benefits information, as you did in the Week 4 project. However, since not all derived types have a AnnualSalary value, DO NOT collect the annual salary data.

5. Create a new static void method called CollectEmployeeInformation that accepts an Hourly employee object. Using the InputUtilities methods write statements to collect the wage and hours from the user.

6. Create a new static void method called CollectSalariedInformation that accepts a Salaried employee object. Using the InputUtilties methods write statements to collect the management level and the annual salary.

STEP 7: Create the EmployeeOutputClass

1. Create a new class in the Presentation Tier folder called "EmployeeOuput"

2. Create a static void method called DisplayEmployeeInformation that has a single Employee parameter. The declaration should look something like the following: public static void DisplayEmployeeInformation(Employee theEmployee)

3. In the DisplayEmployeeInformation method write an output statement that displays theEmployee object to string method to the console.

4. Create static method called DisplayNumberObject that displays the number of employees created.

5. Invoke these methods from the main program to display the employee information and number of objects created.

[Hint: move the the statements from the main program into these methods.]

STEP 8: Create the Main Program

1. Create an array of type Employee that will hold three employee objects. Create three new objects, one Employee, one Hourly and one Salaried in positions 0, 1 and 2 of the array respectively. Make sure to use the constructors the accept the employee type and provide appropriate values for the employee type (e.g. "Generic", "Hourly", "Salaried").

2. Using a FOR loop iterate through the array and collect all the generic employee information, using the EmployeeInput.CollectEmployeeInformation method.

3. If the current item in the array is an Hourly object, then use the EmployeeInput.CollectHourlyInformation method to collect the hourly information.

4. If the current item in the array is a Salaried object, then use the EmployeeInput.CollectSalariedInformation method to collect the salaried information. Use the following if statement to determine the specific type of object:

if (employeeList[i] is Hourly) EmployeeInput.CollectHourlyInformation((Hourly)employeeList[i]);else if (employeeList[i] is Salaried) EmployeeInput.CollectSalariedInformation((Salaried)employeeList[i]);

5. After the information has been collected display the employee information using the EmployeeOutput.DisplayEmployeeInformation method.

6. Before terminating the program display the number of employee objects that have been created.

STEP 9: Compile and Test

When done, compile and run your program.

Then debug any errors until your code is error-free.

Check your output to ensure that you have the desired output and modify your code as necessary and rebuild.

The output of your program should resemble the following:

total Number of Employess in Database: 3

Press the ESC key to close the image description and return to lecture.

STEP 10: Submit Deliverables

· Capture the console output window and paste into a Word document.

· Put the zip file and screen shots (Word document)