the language is visual c#  please following these requirements and the question is at the bottom PROCESSING LOGIC The processing should be defined by summarizing the control and data flow within the main program. Techniques of process specification include Program Design Language, Pseudo Code and Flow Charts. The main program flow must be supplemented with the flow of subroutines/methods/functions that are called from the main program. Any specific algorithms to be used should be stated or referenced.   DATA (INPUT/OUTPUT) The logical and physical data structure of files should be defined in detail. Data structure definitions must include the: a. description of each element, e.g. name, type, dimension; b. relationships between the elements, i.e. the structure and source; c. range of possible values of each element; d. initial values of each element. COMPONENTS (SOURCE CODE NAMES, CLASSES, METHODS) Describe the software components (names or classes) and purpose that will be used. Include UML class diagram showing the properties and methods of the class. Describe the properties of the class and any constraints upon their value. Indicate where the algorithms defined in processing logic are implemented. TESTING Present one or more named scenarios including the input data, expected output and the success criteria desired that will be utilized to test the application. The testing plan should be repeatable so discuss any ‘clean up’ that might be required to do so. Example Scenario 1 – divide by zero test Steps to test Enter zero in the divisor. Expected reaction Expected results is a message saying ‘Zero is not a valid input. Please try again’. question  (Composition vs. Inheritance) Many apps written with inheritance could be written with composition instead, and vice versa. Rewrite class BasePlusCommissionEmployee (Fig. 11.11) of the CommissionEmployee–BasePlusCommissionEmployee hierarchy to use composition rather than inheritance.

Programming Logic & Design Comprehensive
9th Edition
ISBN:9781337669405
Author:FARRELL
Publisher:FARRELL
Chapter11: More Object-oriented Programming Concepts
Section: Chapter Questions
Problem 15RQ
icon
Related questions
Question

 the language is visual c# 

please following these requirements and the question is at the bottom

PROCESSING LOGIC
The processing should be defined by summarizing the control and data flow within the
main program. Techniques of process specification include Program Design
Language, Pseudo Code and Flow Charts.
The main program flow must be supplemented with the flow of
subroutines/methods/functions that are called from the main program.
Any specific algorithms to be used should be stated or referenced.

 

DATA (INPUT/OUTPUT)
The logical and physical data structure of files should be defined in detail. Data
structure definitions must include the:
a. description of each element, e.g. name, type, dimension;
b. relationships between the elements, i.e. the structure and source;
c. range of possible values of each element;
d. initial values of each element.
COMPONENTS (SOURCE CODE NAMES, CLASSES, METHODS)
Describe the software components (names or classes) and purpose that will be used.
Include UML class diagram showing the properties and methods of the class.
Describe the properties of the class and any constraints upon their value.
Indicate where the algorithms defined in processing logic are implemented.

TESTING
Present one or more named scenarios including the input data, expected output and
the success criteria desired that will be utilized to test the application. The testing
plan should be repeatable so discuss any ‘clean up’ that might be required to do so.
Example Scenario 1 – divide by zero test
Steps to test
Enter zero in the divisor.
Expected reaction
Expected results is a message saying ‘Zero is not a valid input. Please try
again’.

question 

(Composition vs. Inheritance) Many apps written with inheritance could be written with composition instead, and vice versa. Rewrite class BasePlusCommissionEmployee (Fig. 11.11) of the CommissionEmployee–BasePlusCommissionEmployee hierarchy to use composition rather than inheritance.

 

Derived Class BasePlus Commission Employee
Class BasePlus Commission Employee (Fig. 11.11) has several changes to its method imple-
mentations that distinguish it from the version in Fig. 11.9. Methods Earnings
(Fig. 11.11, line 43) and ToString (lines 46-47) each invoke property Base Salary's get
accessor to obtain the base-salary value, rather than accessing baseSalary directly. If we
decide to rename instance variable baseSalary, only the body of property BaseSalary will
need to change.
I // Fig. 11.11: BasePlus Commission Employee.cs
2
// BasePlusCommission Employee inherits from Commission Employee and has
// controlled access to Commission Employee's private data via
// its public properties.
using System;
te lines
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
public class BasePlus Commission Employee Commission Employee
{
private decimal baseSalary; // base salary per week
// six-parameter derived-class constructor
// with call to base class Commission Employee constructor
public BasePlus Commission Employee (string firstName, string lastName,
string social SecurityNumber, decimal gross Sales,
decimal commission Rate, decimal baseSalary)
: base (firstName, lastName, social SecurityNumber,
grossSales, commission Rate)
BaseSalary baseSalary; // validates base salary
{
}
mo)logusn}
// property that gets and sets
// BasePlus Commission Employee's base salary
public decimal BaseSalary
{
get
{
}
set
{
return baseSalary;
sulsy
couleversanotaaimmo
if (value < 0) // validation
{
15311
Man
oring
Fig. 11.11 BasePlusCommission Employee inherits from Commission Employee and has
access to Commission Employee's private data via its public properties. (Part I of 2.)
Transcribed Image Text:Derived Class BasePlus Commission Employee Class BasePlus Commission Employee (Fig. 11.11) has several changes to its method imple- mentations that distinguish it from the version in Fig. 11.9. Methods Earnings (Fig. 11.11, line 43) and ToString (lines 46-47) each invoke property Base Salary's get accessor to obtain the base-salary value, rather than accessing baseSalary directly. If we decide to rename instance variable baseSalary, only the body of property BaseSalary will need to change. I // Fig. 11.11: BasePlus Commission Employee.cs 2 // BasePlusCommission Employee inherits from Commission Employee and has // controlled access to Commission Employee's private data via // its public properties. using System; te lines 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 public class BasePlus Commission Employee Commission Employee { private decimal baseSalary; // base salary per week // six-parameter derived-class constructor // with call to base class Commission Employee constructor public BasePlus Commission Employee (string firstName, string lastName, string social SecurityNumber, decimal gross Sales, decimal commission Rate, decimal baseSalary) : base (firstName, lastName, social SecurityNumber, grossSales, commission Rate) BaseSalary baseSalary; // validates base salary { } mo)logusn} // property that gets and sets // BasePlus Commission Employee's base salary public decimal BaseSalary { get { } set { return baseSalary; sulsy couleversanotaaimmo if (value < 0) // validation { 15311 Man oring Fig. 11.11 BasePlusCommission Employee inherits from Commission Employee and has access to Commission Employee's private data via its public properties. (Part I of 2.)
35
36
37
38
39
40
31
12
43
14
-5
6
7
8 }
throw new ArgumentOutOfRange Exception (nameof (value),
value, ${nameof (BaseSalary)} must be >= 0");
baseSalary = value;
// calculate earnings
public override decimal Earnings () => Base Salary + base. Earnings();
// return string representation of BasePlusCommission Employee
public override string ToString() =>
$"base-salaried {base.ToString()}\nbase salary: {BaseSalary:C}";
.11.11 | BasePlus Commission Employee inherits from Commission Employee and has
ess to Commission Employee's private data via its public properties. (Part 2 of 2.)
Transcribed Image Text:35 36 37 38 39 40 31 12 43 14 -5 6 7 8 } throw new ArgumentOutOfRange Exception (nameof (value), value, ${nameof (BaseSalary)} must be >= 0"); baseSalary = value; // calculate earnings public override decimal Earnings () => Base Salary + base. Earnings(); // return string representation of BasePlusCommission Employee public override string ToString() => $"base-salaried {base.ToString()}\nbase salary: {BaseSalary:C}"; .11.11 | BasePlus Commission Employee inherits from Commission Employee and has ess to Commission Employee's private data via its public properties. (Part 2 of 2.)
Expert Solution
trending now

Trending now

This is a popular solution!

steps

Step by step

Solved in 2 steps

Blurred answer
Knowledge Booster
Software Development
Learn more about
Need a deep-dive on the concept behind this application? Look no further. Learn more about this topic, computer-science and related others by exploring similar questions and additional content below.
Similar questions
  • SEE MORE QUESTIONS
Recommended textbooks for you
Programming Logic & Design Comprehensive
Programming Logic & Design Comprehensive
Computer Science
ISBN:
9781337669405
Author:
FARRELL
Publisher:
Cengage