Answer:
The correct answer to the following question will be Option B (Hardware strategy).
Explanation:
<u>Hardware strategy:</u>
It looks at existing infrastructure for software, hardware, and services and discusses the designs of physical databases.
Hardware Strategy should try and identify any technological threats or limitations surrounding the following:
- Quality
- Maintenance
- Delivery
- Scalability
- Disaster recovery
- Sizing
This approach also aims at maximizing the importance of existing technical resources. The team looks at the efficient use of software and their overall transition to company and technological environments.
Therefore, Option B is the right answer.
This gap between user-designer communications <span>can cause a good project to go bad i</span>f the user is not able to process what is required to be fixed in order for the project to run smoothly. The user may have one way of fixing something while the designer has another. In this case, the designer understands how the project fully works while the user does not and this may end up compromising the whole project.
The law that “designers are not users” and “users are not designers” should always be followed.
Answer:
Explanation:
#include <iostream>
using namespace std;
int main()
{
int secondsElapsed, hours, minutes, seconds;
const int secondsPerMinute = 60;
const int secondsPerHour = 60 * secondsPerMinute;
cout << "Please enter the number of seconds elapsed: ";
cin >> secondsElapsed;
hours = secondsElapsed / secondsPerHour;
secondsElapsed = secondsElapsed % secondsPerHour;
minutes = secondsElapsed / secondsPerMinute;
seconds = secondsElapsed % secondsPerMinute;
cout << hours << ":" << minutes << ":" << seconds << endl;
return 0;
}