Answer:
personnel strategy
Explanation:
Competitive analysis is a process that involves relating the company to its environment. Competitive analysis helps identify the strengths and weaknesses of the company, as well as the opportunities and threats that affect it within its target market. This analysis is the basis on which the strategy will be designed, for this we must know or intuit as soon as possible:
The nature and success of the probable changes that the competitor may adopt.
The probable response of the competitor to the possible strategic movements that other companies may initiate.
The reaction and adaptation to the possible changes of the environment that may occur from the various competitors.
The competition is made up of companies that operate in the same market and perform the same function within the same group of customers regardless of the technology used for it. It is not, therefore, our competitor that manufactures a generic product like ours, but one that satisfies the same needs as we do with respect to the same target or consumer audience, for example, cinema can be the theme parks competition, since both are embedded in leisure.
Answer:
Stack
Explanation:
Stack is a linear data structure that follows a particular order in the way an operation is done or sequence a job is completed.
It uses either LIFO ( Last In, First Out) which is also known as first come first served sequence or FILO (First In, Last Out) sequence.
There are several real life examples of which we can use the example of replacing the snack items Sarah brought for the customer.
If Sarah used the LIFO method, it means she replaced the snack items first ontop of the already existing snack items that's why there is a mismatch.
a. stateTaxRate - A good variable name because it represents what it holds, the state sales tax rate, without being too wordy. Also correctly capitalized in camelcase.
b. txRt - A bad variable name because while short and simple, it is too hard to understand what the variable represents.
c. t - A very bad variable name if you plan on using the variable often. Far too short and you will forget what it represents and is needed for.
d. stateSalesTaxRateValue - A bad variable name because it is just too wordy. Cutting it down to A's variable name is much more reasonable
e. state tax rate - A bad variable name and probably invalid because it has spaces in the name.
f. taxRate - A good variable name if there are no other tax calculations other than state tax rate. Otherwise you would confuse state vs local tax rate or something, making it a bad variable name.
g. 1TaxRate - A bad variable name because the number 1 has no reason being in the variable name. It doesn't add anything to the name.
h. moneyCharged - A bad variable name because it is not specific enough in explaining why the money is being charged and what for.
The TCP/IP stack is responsible for the "chopping up" into packets of the data for transmission and for their acknowledgment. Depending on the transport protocol that is used (TCP or UDP) each packet will be <span>acknowledged or not, respectively.
</span><span>the strategy when the file is chopped up into packets, which are individually acknowledged by the receiver, but the file transfer as a whole is not acknowledged is OK in situations (Applications) that do not need the whole file to be sent, Web site for example: different parts of the web site can arrive in different times.
The other strategy, in which </span><span>the packets are not acknowledged individually, but the entire file is acknowledged when it arrives is suitable for FTP (mail transfer), we need whole mail, not parts of it. </span>
