CAO107 Computer Architecture & Operating Systems Report 2 Sample

Still, Looking for a CAO107 Computer Architecture & Operating Systems Report 2 Sample? Don't worry, You’ve reached the Right Place!

Order Now

CAO107 Computer Architecture & Operating Systems Report 2 Sample

Assessment Task

In this assessment, you are required to apply the theories and knowledge you have learned in Modules 5 to 7 to analyse the computer operating system, hardware, and software requirements and write a 1000-words report. You should include screenshots of the steps you took in performing the tasks.

Please refer to the Instructions for details on how to complete this task.

Context

In each organisation, the IT department is responsible to provide support related to computer hardware, software, network management, applications update, and keep the system running seamlessly that improves the organisation’s overall performance, production, and bring better return of the revenue. Due to the recent rapid business requirements changes like high performance computer hardware /software applications and secure from the cyber-attacks, the operating system keeps updates itself. If these updates are done on time, then, the system performance improves, and systems are also prevented from malware attacks. These changes can be done weekly, monthly, quarterly, or annually.

In this assessment, you are to demonstrate your understanding of the structure of modern operating systems, including types, features, and functions, and identify how these operating systems facilitate computer system components to work in the report.

Instructions

There are four tasks that you need to complete for Assessment 2. For each task, take note of the following:

• Each task carries an equal mark

• Answer all the questions for each task

• You should provide screenshots as supporting evidence

• For each task, the answer may be within the range of 250 words. When answering the questions for each task, it is important to note the total number of words.

Tasks:

1) Visit the Web site of a major operating system vendor and identify the patches that were issued in the last 12 months.

a. For each patch, find its criticality and size.

b. Then, as if you were assigned the task of installing these patches as manager of your company, decide the timing for their installation.

c. How many patches would you install immediately, and which ones could wait for the next patch cycle (assuming a four-per-year cycle)? Cite your sources appropriately.

2) You are given an opportunity to perform a software inventory of your (or your colleague’s) computer system to identify all applications resident on the computer.

a. If there are more than a dozen applications, choose 12 of them and check each for patches that are available for your software.

b. For each vendor, identify how many patches are available for that software, the number of critical patches, and what patch cycle you would recommend for that vendor’s patches: annual, quarterly, monthly, or weekly updates.

3) Perform an inventory of your (or your colleague’s) computer system to discover how many processes are active when it is connected to the Internet.

a. What is the total number of processes currently running?

b. For which processes can you identify the application?

c. How many processes are linked to applications that you cannot identify?

4) Describe how you would convince a co-worker to better manage a personal computer by performing regular backups and keeping the system patches. Compare and contrast availability and reliability. In your opinion, which is more important to a system manager?

Solution

Task 1

Patch management should be carried out in accordance with the established policies, procedures, and best practices of the organization. For the most recent information regarding patches and their importance, it is suggested that you adhere to the official website of the vendor or the release notes (Kwon et al., 2019). University Assignment Help, Additionally, in order to reduce the risks associated with patching, businesses should thoroughly test patches in a non-production environment prior to deploying them to production systems.

a. Criticality patch size: Patches can differ in criticality and size depending on the operating system and vendor. Typically, based on the severity of the vulnerability being addressed, patches are categorized as critical, important, moderate, or optional. Patches can be small updates that fix minor problems or big updates that fix multiple security problems and improve features.

b. Installation timing: The severity of the patches, the potential consequences of the vulnerabilities being fixed, and the risk tolerance of the organization all influence the installation schedule. To reduce the likelihood of being exploited, critical patches that address vulnerabilities with a high severity should typically be installed as soon as possible (Hajjaj, & Gsangaya., 2022). While moderate or optional patches can be postponed to a scheduled patch cycle, important patches should also be installed immediately.

c. Patch cycle Installation: The risk assessment of the vulnerabilities being addressed and the organization's risk management policies ought to serve as the foundation for the decision regarding which patches to install right away and which ones to hold off until the subsequent patch cycle. Installing critical patches that address vulnerabilities with a high likelihood of being exploited should be done right away.

Task 2

a. Prioritizing and selecting 12 applications for patch checks is crucial if the computer system contains more than a dozen applications. The choice can be made based on criticality, popularity, and how often it is used. The next step is to look for patches for each of the twelve software programs that have been identified.

b. For every merchant, it is fundamental to evaluate the number of patches accessible, the number of basic patches, and the suggested fix cycle (Al-Dmour, Abood, & Al-Dmour., 2019). Patch cycles can vary based on the software's nature and vendor. Most of the time, critical patches that fix security flaws should be applied first and as soon as possible. Regular patch cycles can be used to schedule non-critical patches that fix bugs or update features.

The recommended patch cycle for various vendors may differ, but the following could serve as a general guideline:

yearly updates: for vendors that either release major updates once a year or patches relatively rarely.

Updates every quarter: for vendors that either release patches on a moderately regular basis or every three months.

Updates every month: for vendors that either frequently issue patches or issue patches on a monthly basis.

Updates every week: for vendors that either issue patches on a weekly basis or extremely frequently.

In order to reduce the likelihood of system disruptions or compatibility issues, patch management must be carried out in accordance with the organization's policies and procedures (Yao et al., 2020). Additionally, patches must be thoroughly tested prior to deployment. It is essential to regularly review and apply patches to protect against potential vulnerabilities and ensure the stability and security of the computer system.

Task 3

It has been identified that total number of processes are running in colleague’s computer is 92. 2 numbers of processors are application processor and 90 numbers of processors are background processors.

The processes that are directly initiated can be looked by the user or those that have an interactive interface to identify the application processes from the total number of processes running on a colleague's computer (Sun et al., 2019). Typically, these kinds of processes have a window that can be seen, indicating that they are running as an application. Web browsers, office applications, media players, and games are all examples of application processes. Along with this, foundation processes are commonly non-intelligent and run behind the scenes to help different framework works or administrations. These processes frequently operate without user intervention and do not have a window that can be seen. System services, device drivers, and background updates are all examples of background processes.

It is possible that some of the processes running in the background are connected to applications that either do not have a window that can be seen or are running as a service in the background. It is suggested that the list of running processes on a computer be reviewed on a regular basis to find any unknown or suspicious processes (Derbel, Derbel & Kanoun, 2019). The Task Manager or third-party software that provides more advanced monitoring and analysis tools can be used to accomplish this. Assuming any obscure cycles are recognized, it is ideal to examine further to guarantee the framework's security and strength.

Task 4

It is essential to emphasize the potential dangers of not doing so in order to persuade a collegues to better manage their personal computer by conducting regular backups and keeping patches of the systems up to date. Data loss, system crashes, security flaws, and the possibility of malware infections are just a few of the dangers that can result from not updating and backing up the system on a regular basis. These dangers have the potential to cause significant downtime, productivity degradation, and financial losses. Share real-world examples of situations in which data loss or system crashes have resulted in significant disruptions or financial losses to persuade the coworker. In order to safeguard sensitive data and prevent security breaches, it can be helpful to explain the significance of keeping the system patched. With regards to dealing with a PC framework, both accessibility and dependability are significant.

System managers place a greater emphasis on availability because it directly affects users' productivity and efficiency. Even if a system is always accessible, it may still result in task delays and frustration. Nonetheless, a framework that is solid yet not accessible can't be utilized by any means. Maintaining a computer system's availability and dependability requires regularly performing backups and updating system patches. Persuading a colleague to go to these lengths should be possible by underlining the expected dangers of not doing so and sharing genuine instances of the results (Radovici, & Culic, 2022). A system manager values both availability and reliability, but availability is more significant because it directly affects users' productivity and efficiency.

References

Al-Dmour, A. H., Abood, M., & Al-Dmour, H. H. (2019). The implementation of systrust principles and criteria for assuring reliability of ais: empirical study. International Journal of Accounting & Information Management, 27(3), 461–491. https://doi.org/10.1108/IJAIM-05-2017-0067

Derbel, F., Derbel, N., & Kanoun, O. (Eds.). (2019). Systems, automation, and control (Ser. Advances in systems, signals and devices, volume 9). De Gruyter Oldenbourg. https://doi.org/10.1515/9783110591729

Hajjaj, S. S. H., & Gsangaya, K. R. (2022). The internet of mechanical things : the iot framework for mechanical engineers (First). CRC Press Books. Retrieved April 13, 2023, from INSERT-MISSING-URL. https://lesa.on.worldcat.org/search/detail/1273728374?queryString=PRACTICAL%20IMPLEMENTATION%20OF%20HARDWARE%20AND%20OPERATING%20SYSTEMS&clusterResults=true&stickyFacetsChecked=true&groupVariantRecords=false&year=2019..2023

Kwon, D., Yi, H., Cho, Y., & Paek, Y. (2019). Safe and efficient implementation of a security system on arm using intra-level privilege separation. Acm Transactions on Privacy and Security (Tops), 22(2), 1–30. https://doi.org/10.1145/3309698

Radovici, A., & Culic, I. (2022). Getting started with secure embedded systems : developing iot systems for micro:bit and raspberry pi pico using rust and tock (Ser. Technology in action). Apress. https://doi.org/10.1007/978-1-4842-7789-8

Sun, K., Hou, Y., Sun, W., & Qi, J. (2019). Power system control under cascading failures : understanding, mitigation, and system restoration. John Wiley & Sons. https://doi.org/10.1002/9781119282075

Trubetskaya, A., McDermott, O., & McGovern, S. (2023). Implementation of an iso 50001 energy management system using lean six sigma in an irish dairy: a case study. The Tqm Journal, 35(9), 1–24. https://doi.org/10.1108/TQM-08-2022-0252

Fill the form to continue reading
Would you like to schedule a callback?
Send us a message and we will get back to you

Main Services

Highlights

Earn While You Learn With Us
Confidentiality Agreement
Money Back Guarantee
Live Expert Sessions
550+ Ph.D Experts
21 Step Quality Check
100% Quality
24*7 Live Help
On Time Delivery
Plagiarism-Free

Our Samples

Get Instant Help
University Assignment Help

Still Finding University Assignment Help? You’ve Come To The Right Place!


CAPTCHA
AU ADDRESS
81 Isla Avenue Glenroy, Mel, VIC, 3046 AU
CONTACT
+61 493416265
EMAIL
support@uniassignmenthelp.net