Questioin iLAB OVERVIEW Scenario and Summary The objective of the lab is to take
ID: 3678964 • Letter: Q
Question
Questioin iLAB OVERVIEW Scenario and Summary The objective of the lab is to take the UML Class diagram and enhance last week's Employee class by making the following changes: Create a static variable called numEmployees that holds an int and initialize it to zero. This will allow us to count all the Employee objects created in the main class. Increment numEmployees in all of the constructors. Add an overloaded method of CalculatePay that will accept a new, or modifed, annual salary value. We will then have two versions of the CalculatePay method (1) that uses the current value of the annual salary for the calculation and (2) one that updates the annual salary with a new value before the calculation. Using properties add accessor (get) and mutator (set) methods to access each of the private attributes and to validate the attribute values before they are set. 1. 2. 3. 4. Deliverables Due this week: · Capture the console output window and paste it into a Word Document. . Zip the project files. » Put the zip file and screen shots (Word document) in the Dropbox iLAB STEPS STEP 1: Understand the UML Diagram Analyze and understand the object UML diagram, which models the structure of the program There are no design changes to the Presentation Tier from the previous project and InputUtilities and ApplicationsUtilities classes are used without modification (except for changing the Application Information) The default values for each of the attributres have been declared as a constants, which is indicated by the ALL_CAPS in the name, and the attributes are then set using the default values . . . Each of the attributes have been specified as private The accessors (get) and mutators (set) are not shown on the class diagram, but it is ASSUMED that each private attribute has a corresponding property that contains the get and set methods The "static" modifier for the numEmployees attribute means that there is only one copy of the variable that is then shared by all the objects of the class. There is a second CalculatePay method that overloads the existing CalculatePay method . . .Explanation / Answer
Hi below i have written the code for your reference,