Install and configure a multi-user networked 114047

PURPOSE OF THE UNIT STANDARD This unit standard is intended: To provide proficient knowledge of the areas covered For those working in, or entering the workplace in the area of Data Communications & Networking

People credited with this unit standard are able to: Plan the installation of system software for a multi-user networked operating system Install a multi-user networked operating system Configure a multi-user networked operating system Test the installation and configuration of a multi-user networked operating system Document the installation of multi-user networked operating system The performance of all elements is to a standard that allows for further learning in this area.

LEARNING ASSUMED TO BE IN PLACE AND RECOGNITION OF PRIOR LEARNING The credit value of this unit is based on a person having prior knowledge and skills to: Describe data communications Describe types of computer systems and associated hardware configurations Apply problem solving strategies

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 21

INDEX

Competence Requirements Page Unit Standard 114047 alignment index Here you will find the different outcomes explained which you need to be proved 23 competent in, in order to complete the Unit Standard 114047. Unit Standard 114047 25 Plan installation of system software for a multi-user networked operating system 28 Install a multi-user networked operating system 33 Configure a multi-user networked operating system 37 Test the installation and configuration of a multi-user networked operating system 43 Document the installation of a multi-user networked operating system 51 Self-assessment Once you have completed all the questions after being facilitated, you need to check the progress you have made. If you feel that you are competent in the areas mentioned, 54 you may tick the blocks, if however you feel that you require additional knowledge, you need to indicate so in the block below. Show this to your facilitator and make the necessary arrangements to assist you to become competent.

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 22

Unit Standard 114047 – Alignment Index SPECIFIC OUTCOMES AND RELATED ASSESSMENT CRITERIA SO 1 Plan the installation of system software for a multi-user networked operating system The plan reviews the specification of the computer system software in order to identify and AC 1 explain the feasibility of the specification. The plan specifies milestones and estimates the time and resources required for the AC 2 installation AC 3 The plan ensures that the installation is scheduled to minimise disruption to the users The plan identifies tasks that are vulnerable to standard risks, and assesses the AC 4 probability and impact of those risks The plan identifies measures to be taken to minimise risk, and the contingency measures AC 5 to be adopted in the event of a risk manifesting itself The plan adopts a review procedure which ensures that the final outcome meets user AC 6 requirements according to service level agreements SO 2 Install a multi-user networked operating system AC 1 The installation procedure follows the manufacturer`s guidelines. The installation ensures that the system software operates according to manufacturer`s AC 2 specifications The installation ensures that the system software operates according to the installation AC 3 specification The installation ensures that the pre-installation environment is restored in the event of AC 4 an unsuccessful installation SO 3 Configure a multi-user networked operating system The configuration ensures that the system software is customised according to the AC 1 installation specification The configuration ensures that the customised system software performs according to AC 2 the manufacturers and company installation specifications SO 4 Test the installation and configuration of a multi-user networked operating system The test verifies that the system software functions according to the manufacturer`s AC 1 specification. AC 2 The test procedure meets the manufacturer`s guidelines AC 3 The test verifies that the system software functions in the specified environment The test verifies that the system software communicates with the hardware and other AC 4 application software according to the installation specification SO 5 Document the installation of a multi-user networked operating system AC 1 The documentation specifies the configuration and customisation AC 2 The documentation shows the results of testing AC 3 The documentation includes evidence of acceptance by the user AC 4 The documentation explains basic user operating procedures

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 23

CRITICAL CROSS FIELD OUTCOMES UNIT STANDARD CCFO WORKING Work effectively with others as a member of an organisation.

UNIT STANDARD CCFO ORGANISING Organise and manage him/her self and his/her activities responsibly and effectively.

UNIT STANDARD CCFO COLLECTING Collect, analyse, organise, and critically evaluate information.

UNIT STANDARD CCFO SCIENCE Use science and technology effectively and critically, showing responsibility towards the environment and health of others.

UNIT STANDARD CCFO DEMONSTRATING Demonstrate an understanding of the world as a set of related systems by recognising that problem solving contexts do not exists in isolation.

UNIT STANDARD CCFO CONTRIBUTING Contribute to his/her full personal development and the social and economic development of the society at large by being aware of the importance of: reflecting on and exploring a variety of strategies to learn more effectively, exploring education and career opportunities and developing entrepreneurial opportunities ESSENTIAL EMBEDDED KNOWLEDGE 1. Performance of all elements is to be carried out in accordance with organisation standards and procedures, unless otherwise stated. Organisation standards and procedures may cover: quality assurance, documentation, security, communication, health and safety, and personal behaviour. An example of the standards expected is the standards found in ISO 9000 Certified Organisations.

2. Performance of all elements complies with the laws of South Africa, especially with regard to copyright, privacy, health and safety, and consumer rights.

3. All activities must comply with any policies, procedures and requirements of the organisations involved, the ethical codes of relevant professional bodies and any relevant legislative and/ or regulatory requirements.

4. Performance of all elements should be performed with a solid understanding of the use of development tools needed in the areas applicable to the unit standard. Examples of such tools are, but is not limited to CASE tools, editors with syntax checking, program source version control systems

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 24

All qualifications and part qualifications registered on the National Qualifications Framework are public property. Thus the only payment that can be made for them is for service and reproduction. It is illegal to sell this material for profit. If the material is reproduced or quoted, the South African Qualifications Authority (SAQA) should be acknowledged as the source.

SOUTH AFRICAN QUALIFICATIONS AUTHORITY REGISTERED UNIT STANDARD: Install and configure a multi-user networked operating system

SAQA ID UNIT STANDARD TITLE 114047 Install and configure a multi-user networked operating system ORIGINATOR SGB Information Systems and Technology FIELD SUBFIELD Field 10 - Physical, Mathematical, Computer and Life Sciences Information Technology and Computer Sciences ABET UNIT STANDARD PRE-2009 NQF LEVEL NQF LEVEL CREDITS BAND TYPE Undefined Regular Level 5 Level TBA: Pre-2009 was 9 L5 REGISTRATION STATUS REGISTRATION START REGISTRATION END SAQA DECISION DATE DATE NUMBER Reregistered 2018-07-01 2023-06-30 SAQA 06120/18 LAST DATE FOR ENROLMENT LAST DATE FOR ACHIEVEMENT 2024-06-30 2027-06-30

This unit standard does not replace any other unit standard and is not replaced by any other unit standard.

PURPOSE OF THE UNIT STANDARD This unit standard is intended:  To provide proficient knowledge of the areas covered  For those working in, or entering the workplace in the area of Data Communications & Networking

People credited with this unit standard are able to:  Plan the installation of system software for a multi-user networked operating system  Install a multi-user networked operating system  Configure a multi-user networked operating system  Test the installation and configuration of a multi-user networked operating system  Document the installation of multi-user networked operating system The performance of all elements is to a standard that allows for further learning in this area.

LEARNING ASSUMED TO BE IN PLACE AND RECOGNITION OF PRIOR LEARNING The credit value of this unit is based on a person having prior knowledge and skills to:  Describe data communications  Describe types of computer systems and associated hardware configurations  Apply problem solving strategies

Specific Outcomes and Assessment Criteria: SPECIFIC OUTCOME 1 Plan the installation of system software for a multi-user networked operating system. OUTCOME RANGE Software Specifications; Feasibility; Scheduling; Resources. ASSESSMENT CRITERION 1 1. The plan reviews the specification of the computer system software in order to identify and explain the feasibility of the specification. ASSESSMENT CRITERION 2 2. The plan specifies milestones and estimates the time and resources required for the installation. ASSESSMENT CRITERION 3 3. The plan ensures that the installation is scheduled to minimise disruption to the users.

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 25

ASSESSMENT CRITERION 4 4. The plan identifies tasks that are vulnerable to standard risks and assesses the probability and impact of those risks. ASSESSMENT CRITERION 5 5. The plan identifies measures to be taken to minimise risk, and the contingency measures to be adopted in the event of a risk manifesting itself. ASSESSMENT CRITERION 6 6. The plan adopts a review procedure which ensures that the final outcome meets user requirements according to service level agreements.

SPECIFIC OUTCOME 2 Install a multi-user networked operating system. OUTCOME RANGE Manufacturer specifications; Installation specifications; Backup procedures. ASSESSMENT CRITERION 1 1. The installation procedure follows the manufacturer`s guidelines. ASSESSMENT CRITERION 2 2. The installation ensures that the system software operates according to the manufacturer`s specifications. ASSESSMENT CRITERION 3 3. The installation ensures that the system software operates according to the installation specification. ASSESSMENT CRITERION 4 4. The installation ensures that the pre-installation environment is restored in the event of an unsuccessful installation.

SPECIFIC OUTCOME 3 Configure a multi-user networked operating system. ASSESSMENT CRITERION 1 1. The configuration ensures that the system software is customized according to the installation specification. ASSESSMENT CRITERION 2 2. The configuration ensures that the customized system software performs according to the manufacturers and company installation specifications.

SPECIFIC OUTCOME 4 Test the installation and configuration of a multi-user networked operating system. ASSESSMENT CRITERION 1 1. The test verifies that the system software functions according to the manufacturer`s specification. ASSESSMENT CRITERION 2 2. The test procedure meets the manufacturer`s guidelines. ASSESSMENT CRITERION 3 3. The test verifies that the system software functions in the specified environment. ASSESSMENT CRITERION 4 4. The test verifies that the system software communicates with the hardware and other application software according to the installation specification.

SPECIFIC OUTCOME 5 Document the installation of a multi-user networked operating system. OUTCOME RANGE Installation ; Configuration; Testing process; User acceptance. ASSESSMENT CRITERION 1 1. The documentation specifies the configuration and customisation. ASSESSMENT CRITERION 2 2. The documentation shows the results of testing. ASSESSMENT CRITERION 3 3. The documentation includes evidence of acceptance by the user. ASSESSMENT CRITERION 4 4. The documentation explains basic user operating procedures.

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 26

UNIT STANDARD ACCREDITATION AND MODERATION OPTIONS The relevant Education and Training Quality Authority (ETQA) must accredit providers before they can offer programs of education and training assessed against unit standards.

Moderation Process: Moderation of assessment will be overseen by the relevant ETQA according to the moderation guidelines in the relevant qualification and the agreed ETQA procedures.

UNIT STANDARD ESSENTIAL EMBEDDED KNOWLEDGE 1. Performance of all elements is to be carried out in accordance with organisation standards and procedures, unless otherwise stated. Organisation standards and procedures may cover: quality assurance, documentation, security, communication, health and safety, and personal behaviour. An example of the standards expected is the standards found in ISO 9000 Certified Organisations. 2. Performance of all elements complies with the laws of South Africa, especially with regard to copyright, privacy, health and safety, and consumer rights. 3. All activities must comply with any policies, procedures and requirements of the organisations involved, the ethical codes of relevant professional bodies and any relevant legislative and/ or regulatory requirements. 4. Performance of all elements should be performed with a solid understanding of the use of development tools needed in the areas applicable to the unit standard. Examples of such tools are, but is not limited to CASE tools, programming language editors with syntax checking, program source version control systems.

Critical Cross-field Outcomes (CCFO): UNIT STANDARD CCFO WORKING Work effectively with others as a member of an organisation. UNIT STANDARD CCFO ORGANISING Organise and manage him/her self and his/her activities responsibly and effectively. UNIT STANDARD CCFO COLLECTING Collect, analyse, organise, and critically evaluate information. UNIT STANDARD CCFO SCIENCE Use science and technology effectively and critically, showing responsibility towards the environment and health of others. UNIT STANDARD CCFO DEMONSTRATING Demonstrate an understanding of the world as a set of related systems by recognising that problem-solving contexts do not exist in isolation. UNIT STANDARD CCFO CONTRIBUTING Contribute to his/her full personal development and the social and economic development of the society at large by being aware of the importance of: reflecting on and exploring a variety of strategies to learn more effectively, exploring education and career opportunities and developing entrepreneurial opportunities.

REREGISTRATION HISTORY As per the SAQA Board decision/s at that time, this unit standard was Reregistered in 2012; 2015.

UNIT STANDARD NOTES Supplementary information: 1. Installation and configuration of a networked operating system will be done on a "clean" server, or as an upgrade of an existing server. 2. The installation should reflect the principles and techniques of at least one given multi-user networked operating system, and the practitioner will be aware of other similar operating systems. 3. At least two different computer architectures should be used in the installation process, in ways that demonstrate the customisation process.

Sub-Sub-Field (Domain): Data Communications and Networking

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 27

Plan the installation of system software for a multi- user networked operating system Time: 90 minutes Activity: Self and Group

AC1 he plan reviews the specification of the computer system software in order to identify and explain the feasibility of the specification. T When preparing for the installation of a new operating system, you have to take into consideration the specifications of the existing software on the computer system in order to ascertain whether the new software is a feasible change for the users on the computer systems. There will be no use in changing the software of the computers, if the users are not able to use the software as their needs requires.

Most hardware and software products have the system requirements printed on the side or bottom of the product packaging. When you are shopping for computer software or hardware, it is a good idea to first find out exactly what your system's specifications are and write them down on a piece of paper.

The important information to record includes: Operating System (i.e. Windows XP, SP 2 or Mac OS X 10.3.8) Processor Speed (i.e. Pentium 4, 3.2 GHz or Power PC G5, 2.0 GHz) Memory, a.k.a. RAM (i.e. 512 MB) Graphics Card (i.e. ATI Radeon 9800 w/ 256 MB video memory) Hard Disk Space (i.e. 80 GB available) I/O Ports (i.e. USB, Firewire, Serial, Parallel, SCSI, VGA, DVI ports) By recording these specifications from your computer, you will be able to make sure your computer supports the products you are buying.

Whenever you purchase software or hardware for your computer, you should first make sure your computer supports the system requirements. These are the necessary specifications your computer must have in order to use the software or hardware. Therefore the planning of the installation is vitally important as the purchase of the software and required licencing cannot be reversed once purchased.

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 28

AC2 he plan specifies milestones and estimates the time and resources required for the installation T Installation (or setup) of a computer program (including device drivers and plugins), is the act of making the program ready for execution. Because the process varies for each program and each computer, programs (including operating systems) often come with an installer, a specialized program responsible for doing whatever is needed (see below) for their installation. Installation may be part of a larger software deployment process.

Installation typically involves code (program) being copied/generated from the installation files to new files on the local computer for easier access by the operating system, creating necessary directories, registering environment variables, providing separate program for un- installation etc. Because code is generally copied/generated in multiple locations, uninstallation usually involves more than just erasing the program folder. For example, registry files and other system code may need to be modified or deleted for a complete uninstallation.

Installations usually takes two to three hours to complete the actual installation of the software onto the hardware. Once the software has been installed, the timeous tasks start which requires the configuration of the software to suit the requirements of the users in order to fulfil the required needs for installing the software initially.

Common operations performed during software installations include:  Making sure that necessary system requirements are met  Checking for existing versions of the software  Creating or updating program files and folders  Adding configuration data such as configuration files, Windows registry entries or environment variables  Making the software accessible to the user, for instance by creating links, shortcuts or bookmarks  Configuring components that run automatically, such as daemons or Windows services  Performing product activation  Updating the software versions

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 29

AC3 he plan ensures that the installation is scheduled to minimise disruption to the users T The installation requires the full use of the computers and therefore there can, unfortunately, not be any other users busy using the computers at the same time. Computer software installations require the full use of the computers in order to ensure that there is no interference with the processors while installing the software; more importantly, the computer requires to use of software to operate, and installing additional software increases the risk of the software having compatibility issues while being in use.

AC4 he plan identifies tasks that are vulnerable to standard risks, and assesses the probability and impact of those risks T Installation or setup is the act of making the system or program ready for execution. Because the process varies for each program and each computer, programs (including operating systems) often come with an installer, a specialized program responsible for doing whatever is needed for their installation.

Configuration is an arrangement of functional units according to their nature, number, and chief characteristics. Often, configuration pertains to the choice of hardware, software, firmware, settings, and documentation. The configuration affects system function and performance while it is being installed and therefore should be left to complete in order to avoid any form of interference.

AC5 he plan identifies measures to be taken to minimise risk, and the contingency measures to be adopted in the event of a risk manifesting itself T On the following age there is an example of a planning document which can be used to plan the procedure for the installation of the software. Each process of installing software will require such a plan because each of the installations will differ from one another due to the requirements of the users that will be different.

Planning the processes for each of the users will ensure that all the possible areas of expected troubleshooting can be identified and avoided, if possible. The planning process must be completed with the actual users of the computer systems to ensure that your understanding of their requirements is . This will save time in the process of installation preparations as well as post-installation corrective actions.

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 30

Installation Planning Guide Software Platform Windows Server 2003 Multi-user Install Plan

Required Task / Resources Required Time Allocated Possible problems Activity

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 31

AC6 he plan adopts a review procedure which ensures that the final outcome meets user requirements according to service level agreements T As explained earlier, the planning process must include the users of the systems to ensure that their requirements can be catered for during the installation process. Not only does this ensure a faster turn-around time, but it also minimises post-completion corrective time where the user requirements have to be altered, which can be done in the initial installation.

Using a simple review system of the completed project will allow you to identify areas which happened that could have been avoided but also issues that occurred which could have been discussed with the users during the planning process to ensure remedial actions are minimised. Below you will find a very simple example of the planning phase condensed and the on the following page a simple feedback form which can be incorporated into the feedback to ensure all views are understood.

Start Estimated Actual Project Phase Date Completion Completion Comments Date Date Gather customer requirements Initial meeting and information Check hardware is compatible Hardware inspection with customer software requirements Software acquisition Identify and purchase software Gather required information Pre-installation customer wants software Information configured to Installation Install and configure software Customer use software for trial Customer Trial period to identify configuration changes required Customer Feedback Customer feedback session Final Adjustments Apply customer requirements Project Completion Customer signs off completion

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 32

Install a multi-user networked operating system Time: 90 minutes Activity: Self and Group

AC1 he installation procedure follows the manufacturer`s guidelines. An operating system (OS) is software that manages the interaction between T hardware resources and the programs or applications you use on a computer. Most PCs have a version of the Windows operating system on them but Macintosh, and are other popular operating systems.

Besides learning the name of your operating system, such as whether you have Windows 7, you can find other useful information about your system. If you are worried about taxing your computer's central processing unit (CPU), for example, you may be able to check your operating system's bit version. A 64-bit version of Windows can process higher amounts of random access memory (RAM) better than a 32-bit version

The Windows Server operating system software, using an example, is actually very easy to install. Once you have checked that the hardware specifications meet the requirements of the software installation, all which is actually required for you to do is to insert the installation discs and follow the instructions presented on your screen.

Microsoft’s Windows Server 2003 is designed to automate the installation process as to ensure for correct installation. The software on the /DVD ROM will automatically detect the hardware of the server computer and configure itself accordingly. The following is a typical installation guide to effectively install the operating system software on the server computer.

1. Insert Disc 1 into your CD/DVD-ROM drive, and then restart the computer. 2. Follow the instructions in your computer's start-up routine to start the computer from the CD/DVD. 3. Follow the instructions on your screen. When you are prompted to enter the Product Key, type the Product Key that comes with the two product discs. 4. After you install Disc 1, log on to the computer as an administrator. 5. At the prompt, insert Disc 2, and then click OK. 6. Follow the instructions on your screen.

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 33

Once the installation has been completed, you will be able to reboot the computer. Upon reboot completion, log in as administrator and load the hardware drivers for the server computer as supplied by the manufacturer. This disc will contain and load all the required drivers to run the hardware installed into the server computer.

Failure to complete this software installation of the drivers will result in some/all hardware not operating or functioning correctly. Installation instructions for the driver software supplied with the computer will depend upon the manufacturer itself and should be detailed in its installation guide supplied with the software itself

AC2 he system software operates according to manufacturer`s specifications Once the installation has completed, you will need to remove the necessary media T form the drives which used to install the software, or in the event of an on-line installation, this will not be required as the files will be in the temporary files folder and be removed by the operating system once the computer has been restarted.

Testing the functions of the operating system, once the system has been restarted will allow you to identify any areas where the software has issues or glitches with the hardware and allow you to inspect these areas and make the necessary changes to them. You should, at this stage also ensure that all the required drivers for the software is identified and that they are available for the completion of the installation of the software.

AC3 he system software operates according to the installation specification Once installed and checked for operational use, the software then needs to be T configured according to the clients or users, needs and specifications. Most software requires configurational changes purely because different users have various different user- preferences for the software they are using, albeit the same software.

The completed installation must also take into consideration the environment of the users and the requirements which the environment forces on the users that requires them to alter the user configurations in the software in order to use it successfully; a very simple example is if the environment dictates that the ambient lighting is very dark, the brightness settings on the software may be altered to avoid as very high level of contrast. This is a very simple example and thousands of others are valid.

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 34

AC4 he installation ensures that the pre-installation environment is restored in the event of an unsuccessful installation T You can do this on a Windows computer by inserting an operating system installation disk or drive and then starting the computer from the disk or drive. Brand new Mac computers will always come with an operating system installed, but you can reinstall your Mac's default operating system by using Internet Recovery if your Mac's hard drive is blank.

Insert the installation disk or flash drive. To install a new operating system on Windows, you must have the operating system's install tool on a DVD or flash drive, and the disk or flash drive must be inserted into your computer. If you don't have a version of the operating system you want to download, you can download one for the following operating systems:

Restart your computer. Press and hold your computer's Power button to turn it off, wait for a few seconds, and then press the Power button again to turn the computer back on.

Wait for the computer's first start-up screen to appear. Once the start-up screen appears, you'll have a very limited window in which you can press the setup key. It's best to start pressing the setup key as soon as the computer begins to restart.

Press and hold Del or F2 to enter the BIOS page. The key you're prompted to press might also be different; if so, use that key instead. This will load your computer's BIOS page, from which point you can select your installation disk or drive.  You'll typically use the "F" keys to access the BIOS. These are at the top of your keyboard, though you may have to locate and hold the Fn key while pressing the proper "F" key.  You can look at your computer model's manual or online support page to confirm your computer's BIOS key.

Locate the "Boot Order" section. This section is normally on the main page of the BIOS, though you may need to use the arrow keys to navigate over to the "Boot" or "Advanced" tab.  The "Boot Order" section varies from BIOS to BIOS. If you can't find your BIOS' "Boot Order" page, consult your motherboard's manual or look up your computer model online to find direct instruction for your specific BIOS page

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 35

Select the location from which you want to start your computer. In this case, you'll be starting your computer either from the disk drive or from an external drive, such as a flash drive.  The disk drive option is usually labeled CD-ROM Drive, while external drives will show up as Removable Devices.

Move your selected location to the top of the list. Typically, you'll press the + key with the boot location you want to use selected until it's at the top of the "Boot Order" list.  You can double-check the key that you're supposed to use in the legend that's usually on the right side or the bottom of the BIOS page.

Save your settings and exit the BIOS. There should be a "Save and Exit" key listed in the BIOS' key legend; press the key listed there to save your settings and exit the BIOS.  You may have to confirm this decision by pressing ↵ Enter with Yes selected.

Restart your computer. Once your computer begins to start up again, it will select your disk or flash drive as the boot location, which means that it will begin installing the operating system.

Follow the on-screen prompts. Each operating system will have different steps to take when installing it, so just follow the on-screen directions to complete the installation.

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 36

Configure a multi-user networked operating system Time: 120 minutes Activity: Self and Group

AC1 he configuration ensures that the system software is customised according to the installation specification T Once the installation has been successfully completed, you will need to transfer all the back-up settings, files, folders and permissions over onto the new system. If a system settings back-up was created on an earlier version of this Software Platform, you will be able to easily transfer the back-up made onto the new installed platform.

You will need to create and set permissions, users and folders as per the requirements of the organisation, its network and operational needs. An account for each user must be created with permissions for access to the system. The folders and data which have been backed up will need to be restored for use and access as required.

A user profile describes the desktop computing configuration for a specific user, including the users environment and preference settings. A profile is created the first time that a user logs on to a computer running Windows or any other operating system. A user profile is a group of settings and files that defines the environment that the system loads when a user logs on.

It includes all the user-specific configuration settings, such as program items, screen colours, network connections, printer connections, mouse settings, and window size and position. Profiles are not user policies and the user have a profile even if you don't use Group Policy.

A user's data can be stored on the local hard disk drive, or IntelliMirror can be set so that the data roams with the user wherever he or she logs on. User data can include shortcuts to executable files, personal files, and user settings, such as a custom dictionary. Depending on how you manage your network, you or a user can define the desktop settings. The following user profiles are available in Windows and most other operating systems: • Local User Profile. Created the first time that a user logs on to a computer, the local user profile is stored on a computer's local hard disk. Any changes made to the local user profile are specific to the computer on which the changes are made.

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 37

• Roaming User Profile. A copy of the local profile is copied to, and stored on a server share. This profile is downloaded every time that a user logs on to any computer on the network, and any changes made to a roaming user profile are synchronized with the server copy upon logoff. • Mandatory User Profile. A type of profile that administrators can use to specify particular settings for users. Only system administrators can make changes to mandatory user profiles. Changes made by the user to desktop settings are lost when the user logs off. • Temporary User Profile. A temporary profile is issued any time that an error condition prevents the users profile from being loaded. Temporary profiles are deleted at the end of each session - changes made by the user to their desktop settings and files are lost when the user logs off.

Advantages of User Profiles A primary goal of user profiles is to separate each users’ settings and data from that of other users and the local computer. Separating each users state provides several advantages: • It allows for stateless computers. An organization can configure computers to store all the key user settings and data away from the local computer. This allows for much easier computer replacement and backup. When a computer needs replacing, it can simply be swapped out all of the users’ state information is safely maintained separately on the network and is independent of a particular computer. When the user logs onto the new computer for the first time, the server copy of the users’ state is copied to the new computer. • It allows a user’s system and desktop customizations to travel with the user from computer to computer, without requiring the user to reconfigure any settings. When a user logs on to any computer on the network that supports the roaming profile, the user’s desktop appears just as that user left it before logging off. With roaming user support, users can share computers, but each user has his or her personal desktop (both roaming and mandatory profiles support this functionality).

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 38

AC2 he configuration ensures that the customised system software performs according to the manufacturers and company installation specifications T In order to make sure that the configuration you have chosen works with the operating system that has been installed, you can complete the following steps when there are issues to check if there are known problems.

Sometimes not all known issues are published by the operating system manufacturer purely because they may not be aware thereof. There may also be instances where there are issues with specific hardware configurations when installing software; this may not always be known because of the billions of different possible hardware configurations. 1. Turn on your PC. Watch as the computer starts up.

2. Check whether your operating system name, such as "Windows Vista," is displayed. If you do not see your operating system or want more details about it, let your computer finish starting up.

3. Click the "Start" button if there is one. It is found in the lower left corner of the Desktop. A "Start" button means you have the Windows ____ OS or later. If you do not have a "Start" button, look for other indicators that show what operating system you have. If you see a in a corner of your screen, you are running the Red Hat Linux operating system. If you see a green or blue "L" in a screen corner, you have Lindows or Linspire.

4. A grey or black footprint in a screen corner indicates you are using a graphical (GUI) called GNU Network Object Model Environment (GNOME) on a form of Linux or UNIX. The Sun Solaris operating system is being used with X, a graphics system for UNIX, if you have a purple background with "Sun" or "Solaris" being visually indicated on your screen.

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 39

5. See if there is text written down the side of the "Start" menu. The text may name your PC's operating system and edition such as "Windows 95," "Windows 2000 Professional," "Windows XP Home," etc. If you are not sure if the text shown is the name of your operating system or you want more information on the OS, try 1 of the options below.

6. Type "winver" without quotation marks in the "Start" menu's search box, then press "Enter." You may need to choose "Run" in the "Start" menu, then type in "winver" without quotation marks. Press "Enter."

7. Look for an "About Windows" window to appear. The name of the OS should be in the top portion of the window. The version number of the operating system will be shown after the word "Version" and any service pack that has been installed as an upgrade will be displayed in parentheses. An example would be "Version 6.0 (Build 6001: Service Pack 1)."

8. Right click the "My Computer" icon as an alternative. It can usually be found on your Desktop or in your "Start" menu. Select "Properties" from the menu that appears.

9. Look at the "System Properties" window that displays. More detailed information on your operating system can be found under the "General" tab after "System:" or "System type," such as whether you are running a 64-bit or 32-bit version of Windows.

Portability testing Portability testing is a non-functional testing methodology that determines the ease or difficulty with which a software component or an application can be moved from one environment to another. The test results obtained from Portability Testing helps in finding out how easily a software component from one environment can be used in another environment.

The term ‘environment’ refers to moving from one operating system to another operating system, one browser to another browser or from one database version to another database version. A major thumb rule of Portability Testing is that it is to be used only if the software component is to be moved from one environment to another environment.

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 40

Difference between Portability and Compatibility testing The points below briefly distinguish the differences between Portability and Compatibility.  Compatibility deals with whether two or more components can be run in the same environment at the same time without adversely affecting the behavior of each other. Example: A word processor and a calculator running on the same OS such as Windows 10 can be said to be compatible with each other as running one application will not affect the behavior of the other application.

 Portability deals with moving the component from one environment to another. Example: A game running on Windows XP is said to be portable if the same game can be run on Windows 7 without any change in the behavior of the game.

In short, portability testing deals with software components across multiple environments, while compatibility testing deals with testing two different applications in the same environment.

Objectives The following are the objectives of this testing:  Determine if a system can be ported to each of the environmental characteristics, such as Processor speed, Disk space & RAM, monitor resolution, OS and browser versions.  Determine if the look and feel of the application with respect to UI and functional features are similar to multiple OS and multiple browsers.  This testing helps to determine if the system can be ready for release, especially when there is an awareness that the customers of the product will use multiple operating systems with multiple browser versions.  This testing is usually performed against a pre-defined set of portability requirements, which help to find the defects that are missed as part of the unit and integration testing of the application.  Defects found in this testing need to be fixed and delivered as a part of the product release by the Developers.  This testing is generally performed in an incremental manner throughout the software development lifecycle.

Attributes Software testing board has defined certain major attributes of this testing. They are:

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 41

#1) Installability: Installability is performed on a software that needs to be installed in a target environment. The following characteristics are validated as part of Installability testing: Operating System requirements for installation. Browser requirements for an application usage. Memory or RAM requirements. Installation procedure. Uninstallation procedure. Installation interruption exceptions. Pre-requisites for software installation.

#2) Adaptability: Adaptability testing is the process of validating if the system is adaptable to each of the target environments. Using common communication standards between multiple systems can help in improving the adaptability of the system as a whole. Adaptability Testing includes the following characteristics: Hardware dependency. Software dependency. Standard language. Communication of system with each of the target environments. Dependency encapsulation. Dependency representation across multiple systems.

#3) Replaceability: Replaceability is the ability to replace one software component with the another. The component that is replacing the previous component must produce the same results as the previous component on all target environments. Ideally, it should serve the same purpose as the component that is replaced. Competitive products of the same domain will be the ideal candidates for replaceability as the product that is being replaced can be much cheaper than the existing product of a competitor.

#4) Compatibility or Coexistence: Compatibility is the ability of two or more components to the existing one in the same environment without adversely affecting the behavior of each other. This testing is especially useful in large systems which include multiple subsystems as part of it.

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 42

Test the installation and configuration of a multi-user networked operating system Time: 120 minutes Activity: Self and Group

AC1 he test verifies that the system software functions according to the manufacturer`s specification. T Once the operating system software is correctly configured for use and deployment, it is time to test it against the specifications and requirements of the organisation and the manufacturer’s instructions. Each account for each identified user/computer station is now in place with the required permissions set for them to access the system. Each user must have access to the data and permissions as identified.

Normal LAN deployment and installation can now be verified and checked to ensure that the network is fully set-up and functional. Each remote computer or work station can now be tested to gain access into the system as required and set-up for use.

Any SQL server configurations which are required will need to be made according to each database requirements. Any other add-on software will need to be checked for correct functionality and deployment within the system. Such testing will depend upon the software manufacturer and the instructions for that specific program.

Security measures such as antivirus programs and measures will need to be checked for full functionality and use. Permissions for such antivirus programme to use connections to update its database through an internet connection will need to be set-up and deployed. As each organisation’s requirements and software needs will vary, it will depend largely on you to ensure that all the required systems are in place for the network to function effectively after the installation.

Your test must be aimed at the verification of the requirements from the operators versus the deliverables of the operating system; which must be able to do what is required by the operators thereof. No use, for example, in installing an operating system know for its wide compatibility with other programs, if none of the programs are functional to the operator of the computer with the specific operating system.

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 43

Portability Testing Checklist The checklist includes the requirements that are to be tested as part of Portability Test. Before proceeding with preparing a checklist, it is imperative to make sure that all the individual components of the system are thoroughly tested and integrated with one another to form one large system.

All the objectives of Portability Testing should be kept in mind for the checklist to be an effective and efficient one.  This testing must fulfill all the portability requirements.  Testing the application on multiple Operating Systems must be performed.  Testing the application on multiple browser versions must be performed.  This testing can be automated for continuous regression testing.  This testing must be done in an incremental and iterative manner throughout the software development lifecycle.

Pros And Cons Portability Testing has its own merits as well as demerits like any other testing. Let's take a look at them. Pros:  It helps in identifying the dependencies between multiple components.  This testing is especially useful in large systems, which have several subsystems that interact with one another.  This testing is preferred when the customers of a product use multiple operating systems with multiple browser versions.  Bugs that are missed during unit and integration testing can be uncovered using this testing.  Installation and uninstallation of software can also be tested as part of this testing.  The responsiveness and performance of an application can be tested across multiple browsers and multiple operating systems.  Look and feel of the application on multiple browsers and multiple operating systems can be validated using this testing.  This testing helps to determine if the functionality of the application is as expected on multiple operating systems and multiple browsers.  It also helps to eliminate the propagation of errors between multiple systems.

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 44

Cons:  This testing is not preferred when a time constraint is on the software testing cycle.  This testing requires a lot of budget from the organization as it requires multiple configurations for testing such as multiple operating systems and multiple browsers.  All the setup hardware configurations must be available for portability testing to be performed. This means an organization must pay to provide support for maintenance of the setup hardware configurations.  Portability Testing is a repetitive process which means testers can lose their focus during testing.  Automation of Portability Testing is a tedious task and requires skill and patience of testers to be successfully implemented.  Execution of portability tests in a multi-user environment can be very tricky. Also, it requires a lot of data workload for the testing to be successful.  Storage space for hosting environments can become costly for an organization.

Examples of Portability Testing Given below are few classic examples: Software designed to run on both Windows 7 and Macintosh operating systems. Applications designed to run on Apple iOS and google android devices. Software designed to be compatible with Edge browser and Google Chrome browser. Video games designed to run on Windows 10 and Apple Macintosh operating systems. Software designed to run on Windows 7 MySQL server and Macintosh Oracle database. Installation of software on Windows 10 and Windows XP operating systems. Uninstallation of software on Macintosh and Linux operating systems.

Portability Testing is generally preferred when there is a requirement for the software component to be moved from one environment to another environment. This testing helps to uncover the defects that are not identified as part of unit testing and system integration testing.

One major disadvantage of Portability Testing is the amount of budget to be allocated to this testing since it demands the use of multiple hardware configurations. Maintenance and providing support for these hardware configurations can be a very tedious and time- consuming task. Hence, portability testing is generally preferred when the benefits outweigh the disadvantages.

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 45

AC2 he test procedure meets the manufacturer`s guidelines An operating system is a base stone of any computer system. Failures and bugs in T an operating system impact the functionality of the system as a whole, that is why correctness and reliability of operating systems are so important. A variety of circumstances make verification and testing of operating systems a complicated issue. The list includes high dependence of operating systems on hardware, their massive internal concurrency, huge number of configuration options, required tolerance to aggressive actions of counteragents and hardware faults, a need for long continuous work without reboot, etc.

Testing methods applied to operating systems include functional testing, backward compatibility testing, robustness testing, performance testing, configuration testing and others.

Functional testing should be based on specifications of functional requirements to interfaces provided to applications and supported by test generation and coverage analysis tools. Model-based methods are very effective here. Backward compatibility testing includes both structural and semantic compatibility testing. Robustness testing includes detecting specific defects like memory leaks, data races and instability when processing incorrect data.

Performance testing and benchmarking is of most importance for real-time operating systems. It includes definition of characteristics to be measured and development of benchmarking methods with predictable accuracy for each characteristic.

Finally, composite approach to testing of operating systems is very important. The most appropriate testing method should be identified for each component or a subsystem of an operating system. An integrated testing control system helps making the testing process effective, especially when regression testing during operating system development and improvement.

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 46

AC3 he test verifies that the system software functions in the specified environment T The overall procedure of creating tests to be run on multiple operating systems contains the following steps: 1. Plan steps your test will perform and determine which steps will be common for all operating systems and which steps will be specific to particular operating systems. 2. Implement test steps. It is recommended that test steps be implemented as separate script routines, keyword tests, low-level procedures, and so on. 3. Group created steps so that steps specific to operating systems are run only on corresponding operating systems and common steps are run on all operating systems. To manage created steps, you can use test items or you can manage them from other tests. 4. Select the environment where your tests will be run. You can either use physical computers, or virtual computers with desired operating systems installed. Make sure you have network access to computers where the tests will be run and those computers have Test Complete installed. 5. Select an approach you will use to control test runs on other operating systems: . You can control the tests manually, that is, you have to log in to computers with the desired operating system running, copy the tests there and initiate a test run. . To control the tests, you can use the Test Complete feature that allows managing test runs on different computers.

A power-on self-test (POST) is a process performed by firmware or software routines immediately after a computer or other digital electronic device is powered on. The results of the POST may be displayed on a panel that is part of the device, output to an external device, or stored for future retrieval by a diagnostic tool. Since a self-test might detect that the system's usual human-readable display is non-functional, an indicator lamp or a speaker may be provided to show error codes as a sequence of flashes or beeps.

In addition to running tests, the POST process may also set the initial state of the device from firmware. In the case of a computer, the POST routines are part of a device's pre-boot sequence; if they complete successfully, the bootstrap loader code is invoked to load an operating system.

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 47

AC4 he test verifies that the system software communicates with the hardware and other application software according to the installation specification T In compatible computers, the main duties of POST are handled by the BIOS, which may hand some of these duties to other programs designed to initialize very specific peripheral devices, notably for video and SCSI initialization. These other duty-specific programs are generally known collectively as option ROMs or individually as the video BIOS, SCSI BIOS, etc.

The principal duties of the main BIOS during POST are as follows:  verify CPU registers  verify the integrity of the BIOS code itself  verify some basic components like DMA, timer, interrupt controller  find, size, and verify system main memory  initialize BIOS  pass control to other specialized extension BIOSes (if installed)  identify, organize, and select which devices are available for booting

The functions above are served by the POST in all BIOS versions back to the very first. In later BIOS versions, POST will also:  discover, initialize, and catalogue all system buses and devices  provide a user interface for system's configuration  construct whatever system environment is required by the target operating system  (In early BIOSes, POST did not organize or select boot devices, it simply identified floppy or hard disks, which the system would try to boot in that order, always.)

The BIOS begins its POST when the CPU is reset. The first memory location the CPU tries to execute is known as the reset vector. In the case of a hard reboot, the northbridge will direct this code fetch (request) to the BIOS located on the system flash memory. For a warm boot, the BIOS will be located in the proper place in RAM and the northbridge will direct the reset vector call to the RAM.

(In earlier PC systems, before chipsets were standard, the BIOS ROM would be located at an address range that included the reset vector, and BIOS ran directly out of ROM. This is why the motherboard BIOS ROM is in segment F000 in the conventional memory map.)

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 48

During the POST flow of a contemporary BIOS, one of the first things a BIOS should do is determine the reason it is executing. For a cold boot, for example, it may need to execute all of its functionality. If, however, the system supports power saving or quick boot methods, the BIOS may be able to circumvent the standard POST device discovery, and simply program the devices from a preloaded system device table.

The POST flow for the PC has developed from a very simple, straightforward process to one that is complex and convoluted. During the POST, the BIOS must integrate a plethora of competing, evolving, and even mutually exclusive standards and initiatives for the matrix of hardware and OSes the PC is expected to support, although at most only simple memory tests and the setup screen are displayed.

In earlier BIOSes, up to around the turn of the millennium, the POST would perform a thorough test of all devices, including a complete memory test. This design by IBM was modelled after their larger (e.g. mainframe) systems, which would perform a complete hardware test as part of their cold-start process.

As the PC platform evolved into more of a commodity consumer device, the mainframe- and minicomputer-inspired high-reliability features such as parity memory and the thorough memory test in every POST were dropped from most models. The exponential growth of PC memory sizes, driven by the equally exponential drop in memory prices, was also a factor in this, as the duration of a memory test using a given CPU is directly proportional to the memory size.

The original IBM PC could be equipped with as little as 16 KB of RAM and typically had between 64 and 640 KB; depending on the amount of equipped memory, the computer's 4.77 MHz 8088 required between five seconds and 1.5 minutes to complete the POST and there was no way to skip it. Beginning with the IBM XT, a memory count was displayed during POST instead of a blank screen.

A modern PC with a bus rate of around 1 GHz and a 32-bit bus might be 2000x or even 5000x faster, but it might have more than 3 GB of memory—5000x more. With people being more concerned with boot times now than in the 1980s, the 30 to 60 second memory test adds undesirable delay for a benefit of confidence that is not perceived to be worth that cost by most users.

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 49

Most clone PC BIOSes allowed the user to skip the POST RAM check by pressing a key, and more modern machines often performed no RAM test at all unless it was enabled via the BIOS setup. In addition, modern DRAM is significantly more reliable than DRAM was in the 1980s.

As part of the starting sequence the POST routines may display a prompt to the user for a key press to access built-in setup functions of the BIOS. This allows the user to set various options particular to the mother board before the operating system is loaded. If no key is pressed, the POST will proceed on to the boot sequence required to load the installed operating system.

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 50

Document the installation of a multi-user networked operating system Time: 120 minutes Activity: Self and Group

AC1-4 he documentation specifies the configuration and customisation Test documentation is documentation of artefacts created before or during the T testing of software. It helps the testing team to estimate testing effort needed, test coverage, resource tracking, execution progress, etc. It is a complete suite of documents that allows you to describe and document test planning, test design, test execution, test results that are drawn from the testing activity.

Why Test Formality? For a newbie, it's easy to assume that Testing is executing the various section of code on an ad-hoc basis and verifying the results. But in the real world, Testing is a very formal activity and is documented in detail. Test Documentation makes planning, review, and execution of testing easy as well as verifiable. The degree of test formality depends on  The type of application under test  Standards followed by your organization  The maturity of the development process.  Testing activities generally consume 30% to 50% of software development project effort. Documentations help to identify Test process improvement that can be applied to future projects.

Best practice to Achieve Test Documentation  QA team needs to be involved in the initial phase of the project so that Test Documentation is created in parallel  Don’t just create and leave the document, but update whenever required  Use version control to manage and track your documents  Try to document what is needed for you to understand your work and what you will need to produce to your stakeholders  You should use a standard template for documentation like excel sheet or doc file  Store all your project related documents at a single location. It should be accessible to every team member for reference as well as to update when needed  Not providing enough detail is also a common mistake while creating a test document

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 51

Examples of Test Documentation Here, are important Types of Test Documentation:

Types of Testing Description

Test policy It is a high-level document which describes principles, methods and all the important testing goals of the organization.

Test strategy A high-level document which identifies the Test Levels (types) to be executed for the project.

Test plan A test plan is a complete planning document which contains the scope, approach, resources, schedule, etc. of testing activities.

Requirements This is a document which connects the requirements to the test Traceability Matrix cases.

Test Scenario Test scenario is an item or event of a software system which could be verified by one or more Test cases.

Test case It is a group of input values, execution preconditions, expected execution postconditions and results. It is developed for a Test Scenario.

Test Data Test Data is a data which exists before a test is executed. It used to execute the test case.

Defect Report Defect report is a documented report of any flaw in a Software System which fails to perform its expected function.

Test summary report Test summary report is a high-level document which summarizes testing activities conducted as well as the test result.

Advantages of Test Documentation  Creating test documentation reduces or remove uncertainties about testing activities. Helps remove ambiguity which often arises when it comes to the allocation of tasks  Documentation not only offers a systematic approach to software testing, but it also acts as training material to freshers in the software testing process  It is a good marketing & sales strategy to showcase Test Documentation to exhibit a mature testing process  Test documentation helps offer quality product to the client within specific time limits  In Software Engineering, Test Documentation also helps to configure or set-up the program through the configuration document and operator manuals  Test documentation helps you to improve transparency with the client

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 52

Disadvantages of Test Documentation  The cost of the documentation may surpass its value as it is very time-consuming  Many times, it is written by people who can't write well or who don't know the material  Keeping track of changes requested by the client and updating corresponding documents is tiring.  Poor documentation directly reflects the quality of the product as a misunderstanding between the client and the organization can occur

Summary  Test documentation is documentation of artifacts created before or during the testing of software.  The degree of test formality depends on 1) the type of application under test 2) standards followed by your organization 3) the maturity of the development process.  Important types of Test Documents are Test policy, Test strategy, Test plan, Test case etc.  QA team needs to be involved in the initial phase of the project so that Test Documentation is created in parallel  The main reason behind creating test documentation is to either reduce or remove any uncertainties about the testing activities.  The cost of the documentation may surpass its value as it is very time-consuming

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 53

You are now ready to go through a check list. Be honest with yourself Tick the box with either a √ or an X to indicate your response

□ I am able to plan the installation of system software for a multi-user networked operating system

□ I am able to install a multi-user networked operating system

□ I am able to configure a multi-user networked operating system

□ I am able to test the installation and configuration of a multi-user networked operating system.

□ I am able to document the installation of multi-user networked operating system

You must think about any point you could not tick. Write this down as a goal. Decide on a plan of action to achieve these goals. Regularly review these goals.

My Goals and Planning: ______

Module 4 – Operating system support skills Author: LEARNER MANUAL Rel Date: 27/01/2018 Rev Date: 01/06/2023 Doc Ref: 48573 LM Mod 4 v-1 PAGE 54