To determine what would be the most appropriate way to address and greet your teacher during an email, we should eliminate some greetings, such as:
"Yo wassup?", "How u doin?", or any other grammatical and socially inappropriate errors.
Let's look at our first option.
"Hi Joseph, How u doin??". This is incorrect as it is not appropriate to address anyone in such a manner and with grammatical errors.
Let's look at our second option.
"Dear Joseph Herman, how are you doing!!". This was on the right path, but didn't end well. The ending of the message, "how are you doing!!" is incorrect punctuation, and has too much excitement.
How about our third option?
"Dear Mr. Herman, I hope you're doing fine.". This is a great email. It has perfect punctuation, grammar, and is appropriate.
What about our fourth?
"Dear Joseph, i hope you are doing great.". This is a good email, but has incorrect punctuation.
Your answer is C.) Dear Mr. Herman, I hope you're doing fine.
Since both arrays are already sorted, that means that the first int of one of the arrays will be smaller than all the ints that come after it in the same array. We also know that if the first int of arr1 is smaller than the first int of arr2, then by the same logic, the first int of arr1 is smaller than all the ints in arr2 since arr2 is also sorted.
public static int[] merge(int[] arr1, int[] arr2) {
int i = 0; //current index of arr1
int j = 0; //current index of arr2
int[] result = new int[arr1.length+arr2.length]
while(i < arr1.length && j < arr2.length) {
result[i+j] = Math.min(arr1[i], arr2[j]);
if(arr1[i] < arr2[j]) {
i++;
} else {
j++;
}
}
boolean isArr1 = i+1 < arr1.length;
for(int index = isArr1 ? i : j; index < isArr1 ? arr1.length : arr2.length; index++) {
result[i+j+index] = isArr1 ? arr1[index] : arr2[index]
}
return result;
}
So this implementation is kind of confusing, but it's the first way I thought to do it so I ran with it. There is probably an easier way, but that's the beauty of programming.
A quick explanation:
We first loop through the arrays comparing the first elements of each array, adding whichever is the smallest to the result array. Each time we do so, we increment the index value (i or j) for the array that had the smaller number. Now the next time we are comparing the NEXT element in that array to the PREVIOUS element of the other array. We do this until we reach the end of either arr1 or arr2 so that we don't get an out of bounds exception.
The second step in our method is to tack on the remaining integers to the resulting array. We need to do this because when we reach the end of one array, there will still be at least one more integer in the other array. The boolean isArr1 is telling us whether arr1 is the array with leftovers. If so, we loop through the remaining indices of arr1 and add them to the result. Otherwise, we do the same for arr2. All of this is done using ternary operations to determine which array to use, but if we wanted to we could split the code into two for loops using an if statement.
Answer:
The correct answer is C) With respect to PERT and CPM, slack is the amount of time a task may be delayed without changing the overall project completion time.
Explanation:
The CPM (Critical Path Method) method is frequently used in the development and control of projects whose tasks have a fixed duration while the PERT (Program Evaluation and Review Techniques) method is a set of techniques with the same purpose but that allows to work with tasks with estimated probability duration but not deterministic.
Both methods are based on developing a complete scheme that includes all the tasks of a project linked to each other according to their sequence, determining the duration and analyzing different ways of reconfiguring the task planning to optimize the use of the resources of according to the general objectives of the project.
There are tasks that to start performing them must have been completed one or more previous tasks. The overall duration of the project is determined by the Critical Path, which is the sequence of tasks of greater duration. The tasks belonging to the critical path have to be carried out with special care because delays in them would cause delays in the total achievement of the project. That is why these tasks have no slack.
The rest of the tasks have some slack, which is determined by the time that a previous task can be delayed without delaying the total time of completion of the project, that is, not exceeding the duration determined by the critical path.
That is that why we say that the <em>slack</em><em> is the amount of time a task may be delayed without changing the overall project completion time</em>.
