Final Research Paper in Css

FINAL RESEARCH
PAPER
IN
CSS
Table of Contents
1. BASIC COMPETENCIES
A. Demonstrate Work Values
B. Corporate Value
C. Examples of Company Policies & Procedures
D. 5 Factors That Demonstrate a Strong Work Ethic
2. Practice Career Professionalism
A. 10 Ways To Be Professional at Work
B. The Importance of Professionalism in Business
C. Professionalism in the Workplace: Definition & Maintenance
3. Practice occupational Health and Safety Procedures
A. OHS IMPORTANCE
B. Workplace health & safety
C. The Rundown about Workplace Health and Safety, Occupational Health
D. Sample Pre - Employment Requirements in the Philippines
4. PRE EMPLOYMENT REQUIREMENTS IN THE PHILIPPINES
A. Professionalism in the Workplace: Definition & Maintenance
B. Most Common Requirements by Employers in the Philippines
C. Applying for a job
D. Health Certificate in Pasig City
E. Steps/Procedure in Securing Health and Mayor’s Occupational Permit in Pasig City
COMMON COMPETENCIES
1. Perform Computer Operations
2. Use Hand Tools
CORE COMPETENCIES
1.Install and Configure Computer Systems
2.Set-up Computer Networks
3.Set-up Computer Servers
4.Maintain and Repair Computer Systems and Networks
- SELF ASSESSMENT GUIDE for COMPUTER SYSTEM SERVICING NC II
1. Assemble computer hardware
2. Prepare installer
3. Install operating system and drivers/peripheral installation work
4. Install application software based on software
5. Conduct testing and documentation about the system unit
Test devices/systems and/or installation
- Conduct stress test
BASIC COMPETENCIES:
1. Demonstrate Work Values
a. Demonstrating Value can help you take control of the data you collect, how it is used
and to communicate the performance and value of your organization, social enterprise
or program. In this activity guide, you will work out what your data needs are, how they
can be met, and design a ‘Performance Snapshot’ that will provide an engaging
summary of the performance and value of your organization.
b. Corporate Values
-The operating philosophies or principles that guide an organization's internal conduct as well
as its relationship with its customers, partners, and shareholders. Core values are usually
summarized in the mission statement or in the company's statement of core values.
c. Company policies and procedures establish the rules of conduct within an organization,
outlining the responsibilities of both employees and employers. Company policies and
procedures are in place to protect the rights of workers as well as the business interests of
employers. Depending on the needs of the organization, various policies and procedures
establish rules regarding employee conduct, attendance, dress code, privacy and other areas
related to the terms and conditions of employment.
d.A strong work ethic is vital to a company achieving its goals. Every employee, from the CEO
to entry-level workers, must have a good work ethic to keep the company functioning at its
peak. A work ethic is a set of moral principals an employee uses in his job. Certain factors come
together to create a strong work ethic.
2. Practice Career Professionalism

a. 10 Ways To Be Professional
Acting like a professional really means doing what it takes to make others think of you as
reliable, respectful, and competent. Depending on where you work and the type of job you
have, this can take on many different forms.
There are, however, quite a few common traits when it comes to being professional. This
includes the following:
1. Competence. You’re good at what you do – and you have the skills and knowledge that
enable you to do your job well.
2. Reliability. People can depend on you to show up on time, submit your work when it’s
supposed to be ready, etc.
3. Honesty. You tell the truth and are upfront about where things stand.
4. Integrity. You are known for your consistent principles.
5. Respect For Others. Treating all people as if they mattered is part of your approach.
6. Self-Upgrading. Rather than letting your skills or knowledge become outdated, you seek out
ways of staying current.
7. Being Positive. No one likes a constant pessimist. Having an upbeat attitude and trying to be
a problem-solver makes a big difference.
8. Supporting Others. You share the spotlight with colleagues, take time to show others how to
do things properly, and lend an ear when necessary.
9. Staying Work-Focused. Not letting your private life needlessly have an impact on your job,
and not spending time at work attending to personal matters.
10. Listening Carefully. People want to be heard, so you give people a chance to explain their
ideas properly.
b. Professional workplace behavior is necessary for the long-term success of a business,
whether it’s a big corporation or small business. Employee interactions and relationships with
customers are of vital importance to ensure that company goals and objectives are met. A
professional work place attitude and appearance allow employees to take pride in their work
and improve worker performance. Managers who behave professionally set an appropriate
example by encouraging their people to conduct themselves in a manner that supports
company-wide success.
c. We often hear how important it to behave “professionally” in the workplace. If you want to
get ahead, be taken seriously, and have your boss think of you as an asset to the team, doing
things in a professional way is vital.
d. Professionalism has to do with the way a person conducts himself or herself in the
workplace. An individual who shows consideration and respect for others demonstrates a
commitment to professionalism. Likewise, a person who keeps his or her word, demonstrates
loyalty, and exceeds expectations is demonstrating professionalism.
There are four key elements that demonstrate a professional attitude. These are:
1. Treat other with respect
2. Keep your word
3. Be loyal
4. Exceed expectations
3.Practice occupational Health and Safety Procedures
a. Most organisations have elements of an Occupational Health and Safety Management

System (OHSMS) in place, however it is less likely for organisations to have a system in
place that coordinates these elements to improve OHS. A systematic approach to OHS
ensures that important health and safety issues are brought to attention so they can be
fixed.
There are 5 keys to implementing a successful OHS Management System:
1. management commitment and policy
2. planning
3. implementation
4. measurement and evaluation
5. review and improvement
The importance of an OHSMS should not be underestimated. It allows your workplace to

systematically eliminate the possibility of accident, illness, injury or fatality caused by workplace
hazards. Not only is this obviously beneficial for anyone working in the organisation, it is also
beneficial for your organisation as a whole.
b. Workplace Health and Safety (WHS), often referred to as Occupational Health and Safety
(OH&S) involves the assessment and mitigation of risks that may impact the health, safety or
welfare of those in your workplace. This may include the health and safety of your customers,
employees, visitors, contractors, volunteers and suppliers. As a business owner there are legal
requirements that you must comply with to ensure your workplace meets WHS obligations.
c. The Occupational Safety and Health Act of 1970 is one very important topic to understand.
Although it seems fairly easy to comprehend, have you ever just asked yourself what exactly it
is and why it is important to know as a worker? This may apply to many individuals since the
OSHA regulations are not too clear and are not well explained by many companies. Many
people may also feel overwhelmed by the topic since it seems to cover a heavy load of
information that may be hard to absorb.
d.
e.Sample Pre - Employment Requirements in the Philippines
1. Resume
2. Application Letter
3. Residence Location Map
4. 2x2 and 1x1 colored ID picture
5. Birth Certificate
6. Marriage Certificate (if married)
7. Birth Certificate of Children
8. Transcript of Records
9. Diploma
10. Pre-employment Medical Exam
11. Drug Test
12. Police Clearance
13. NBI Clearance
14. Brgy. Clearance
15. Photocopy of SSS ID / SSS Number
16. Photocopy of BIR ID or BIR Form 1902
17. BIR Form 2316 from previous employer
18. PHIC Number
19. HDMF Number
20. SSS Loan Details if any
21. HDMF Loan details if any
22. Certificate of Employment from previous employer
4. PRE EMPLOYMENT REQUIREMENTS IN THE PHILIPPINES

a. Professionalism has to do with the way a person conducts himself or herself in the
workplace. An individual who shows consideration and respect for others demonstrates
a commitment to professionalism. Likewise, a person who keeps his or her word,
demonstrates loyalty, and exceeds expectations is demonstrating professionalism.
There are four key elements that demonstrate a professional attitude. These are:
1. Treat other with respect
2. Keep your word
3. Be loyal
4. Exceed expectations
b. Most Common Requirements by Employers in the Philippines
You may think that graduation marks the end chapter of your hardships in life but you are
mistaken – Graduation only starts your real life and you should be fully prepared for it. Having
yourself employed is a tough job, finishing all the requirements on time is another. For starters,
here are the basic and the most important legal documents that your employer will ask from
you.
Here are those needed:
GSIS (Government Service Insurance System)
SSS (Social Security System)
NBI (National Bureau of Investigation)
PhilHealth
Pag-IBIG or Home Developmental Mutual Fund (HDMF)

Medical Certificate
TIN (Tax Identification Number)
Birth Certificate
c. Applying for a job - The application and interview process
Applying for jobs you are qualified for and having a well-written CV means you stand more of a
chance of getting an interview. The better prepared you are for the interview, the more chance
you have of getting the job. Making sure your resume is correct, succinct and well written will
be a big help in the application process and may help you obtain a personal interview. The
Philippine application system is similar to that of the USA in that they prefer a resume over a
more European style Curriculum Vitae (CV). Job applications usually consist of the following:
● Covering letter explaining why you are suitable for the particular role
● Resume
● Any certificates you have that support your application
● Passport
d. Health Certificate in Pasig City

e. STEPS / PROCEDURE IN SECURING HEALTH AND MAYORS OCCUPATIONAL PERMIT IN PASIG
CITY
STEP 1: VALIDATION
Mga kailangan:
1. Urinalysis
2. XRAY
3. Fecalysis
4. Drug test
5. Health certificate fee
6. Orientation fee
7. Validation fee
Ang maganda po sa kanila, kung meron na kayong MEDICAL sa ibang ospital o clinics, tinatanggap po nila yon.
Kaya ipe-present nyo yun sa window for VALIDATION. At kung may kulang ka sila na bahala mag note kung
ano pa kailangan mong tests.
STEP 2: PAYMENT
Pag nasabi na sayo kung ano pa ang kailangan mong tests, pwede na magbayad sa CASHIER nila. Kunwari
naman sa 7 babayaran mo, yung iba meron kana, meron naman silang separate billing para doon.
STEP 3
1. Magpa test na kayo, magpasa ng urine and stool o kung ano pa man. Magkakalapit lang naman yun kaya
wag mag alala :) Tanungin din kung anung oras makukuha ang resulta sa bawat tests nyo.
2. Kung meron na kayong mga kinakailangang resulta ay pumunta sa isang ROOM doon kung saan pipirma
yung doktor para tignan kung ok ba yung mga test results o kung ano pa man. Pero bago kayo pumunta doon
eh ipa-photocopy nyo muna lahat ng result nyo, tig iisa lang naman, kasi required nila.
3. Pumunta sa isang ROOM doon kung saan magfill up ng info na ilalagay sa inyong ID, tapos magpapaicture,
tapos signature, tapos aantayin nyo na lang yung oras ng seminar nyo.
4. Umatend ng seminar (manood ng video tungkol sa EL NINO, LA NINA at paghuhugas ng kamay,

magsasayaw pa kayo hahaha)
Doon na mismo sa seminar ibibigay yung HEALTH CARD nyo pagkatapos na pagkatapos nyo manood at
SUMAYAW (haha)
Tapos, tapos na uwi na :)
Ganun lang po kadali at kabilis kumuha ng health certificate sa Pasig City Hall. Ang mura pa kung tutuusin.
Komportable pa kasi naka aircon kayo doon, di kayo pagpapawisan. Kahit anong oras ata kayo pumila doon
kahit tanghali na eh wala gaanong pila (pwera sa drug test). Pero syempre kung gusto nyo maaga makuha ang
resulta at ang inyong health card, 8:00am palang eh pumunta na kayo doon sa City hall.
COMMON COMPETENCIES
1. Perform Computer Operations
-From keeping in touch with friends to performing financial transactions, these days we rely on
computers for just about everything. With PCs as advanced as they are, it's easy to forget the
fundamentals that have made modern technology possible. Computers do all the things they do
because they are able to perform four basic operations.
List of the Four Basic Computer Operations:

(Input,Processing,Output,Storage)
2. Use Hand Tools
Never push unless you hold the tool with your palm open. Point sharp tools (e.g., saws, chisels,
knives) laying on benches away from aisles and handles should not extend over the edge of the
bench top. Maintain tools carefully. Keep them clean and dry, and store them properly after
each use.
CORE COMPETENCIES
1. Install and Configure Computer Systems
In order to set up computers so that they are ready for use, students learn to install, configure
and customize Windows operating systems. After learning the unique features and functions of
operating systems including organizing and managing files and folders in the directory
structure, understanding and running commands, and start-up options, students learn how to
troubleshoot operating system configuration and tuning issues, as well as how to resolve
different peripheral and printer problems. They also learn how to partition and format a hard
disk into separate storage and boot areas, and how to add and remove hardware components
and software programs.
1. 1Click the Wi-Fi symbol
. It's in the lower-right corner of the screen. A pop-up window will appear.
○ If Wi-Fi is currently disabled, click the Wi-Fi button in the lower-left side of
the pop-up window before proceeding.
○ In some cases, you'll need to click the ^ icon in the lower-right side of the
screen to see the Wi-Fi icon.
2. 2
3. Select a network. Click the network to which you want to connect each of your
network computers.
4. Click Connect. It's in the lower-right side of the network's name box.
5. Enter the network's password. Type in the network's password when prompted.
6. Click Next. It's below the network. As long as the password is correct, doing so will
connect you to the network.
7. Connect other computers in the network to the Internet. For each computer that you
want to use in your network, repeat the Wi-Fi connection process. Once each computer
is connected to the Wi-Fi network, you can proceed with setting up file sharing.
8. Open Start .Click the Windows logo in the bottom-left corner of the screen.
9. Type in control panel. Doing so will search your computer for the Control Panel app.
10. Click Control Panel. It's a blue rectangle icon at the top of the Start menu.
11. Click Network and Sharing Center. This option resembles a set of blue monitors.
○ If you see "Category" in the upper-right side of the page, first click the
Network and Internet heading on the main Control Panel page.
12. Click Change advanced sharing settings. It's a link in the upper-left side of the page.
13. Check the "Turn on network discovery" box. This will ensure that your computer can
interact with other computers that are plugged into the Internet source.
○ You can also enable the "Turn on file and printer sharing" option and the
"Allow Windows to manage homegroup connections" option if they aren't
automatically selected.
14. Click Save changes. It's at the bottom of the page.

15. Enable network discovery on the other network computers. Once each computer in
the networked group has network discovery enabled in Control Panel, your wired
network will be ready to use.
3. Set-up Computer Servers
A computer network consists of two or more computers intended to share resources:
A client/server network is a system where one or more computers called clients connect to a
central computer named a server to share or use resources. Each client computer must use an
operating system that allows it to be identified to participate in the network.
Client/Server Networking
Steps:
1. Turn on your computer first.

2. Then insert the Windows Server 2012 R2 DVD/ or put USB bootable in the
USB port note: Access the BIOS setup program and change the boot
sequence so that the computer boots from the DVD or USB.
3. After a few minutes, you receive the Windows Server 2012 R2 screen shown
in Figure 2-1. Click Install now to begin the installation.
Starting the installation of

Windows Server 2012 R2.
4. Windows copies temporary files.
5.On the next Install Windows screen, click Install now.
6.You receive the options shown below. which enable you to install the complete
Standard or Datacenter version of Windows Server 2012 R2 with a GUI or Windows
Server 2012 R2 Server Core. Select the what ever you want.
Installing and Configuring Windows Server 2012 R2
Select either the complete

installation of Windows Server 2012 R2 or the Server Core option.
7.You are asked to accept the license terms. Select the check box labeled I accept
the license terms and then click Next.
8.You receive the options shown in Figure 2-4 to upgrade or install a clean copy
of Windows Server 2012 R2. Select Custom (advanced) to install a clean copy of
Windows Server 2012 R2.
[there is an option to upgrade when
run from Windows Server 2008/R2/2012.]
9.Select the disk on which you want to install Windows and then click Next.
10.This takes some time (particularly when installing OS), and the computer
restarts several times.
11. After 15–30 minutes (it depends your hardware), and Windows restarts a last
time and informs you that your password must be changed before logging on for the
first time. Click OK.
12.Type and confirm a strong password. When informed that the password is
changed, click OK. After a minute or more, the desktop appears, containing a
command window but no Start screen or desktop icons . This is the standard
Windows Server Core interface.
13.After the server reboots, press Ctrl+Alt+Delete and log on using the password
you set in.
14.Windows informs you that your password has been changed. Click OK.
15.Windows displays a Welcome message and prepares your desktop. Then the
desktop with Server Manager shown below.
12. Maintain and Repair Computer Systems and Networks
The COC 4 consists of competencies that a person must achieve in planning, maintaining,
diagnosing and repairing the computer systems and networks.
A person who has achieved this Unit/Cluster of competencies is competent to maintain and
repair the computer systems & networks and shall be awarded the Certificate of Competency
leading to Computer Systems Servicing NC II. The Units of Competency comprising this Cluster
include the following:
ELC724331 Install and configure computer systems

ELC724332 Set-up Computer Networks
ELC724333 Set-up Computer Servers
ELC724334 Maintain and Repair Computer Systems and Networks
A person who has achieved this COC is competent to be employed in any of the following
positions as:
q Computer Maintenance Technician

q Computer Service Technician
Individuals aspiring to be awarded the qualification of COMPUTER SYSTEMS SERVICING

NC II must acquire the remaining three (3) Certificates of Competency as follows:
COC 1: Install and Configure Computer Systems

ELC724331: Install and configure computer systems
COC 2: Set-up Computer Networks

ELC724332: Set-up Computer Networks
COC 3: Set-up Computer Servers

ELC724333: Set-up Computer Servers
SELF ASSESSMENT GUIDE for
COMPUTER SYSTEM SERVICING NC II
Topics:
1 Assemble computer hardware
2 Prepare installer
3 Install operating system and drivers/peripheral installation work
4 Install application software based on software
5 Conduct testing and documentation about the system unit
1. Assemble computer hardware

This set of instructions will help you assemble a basic computer capable of running most
modern software packages encountered by a casual user. Modern computers become more
affordable when users supplement their monetary investment with a few hours of effort. This
computer build will be very basic and will be the minimum hardware necessary to have a
functional system. After you have all of the parts and materials needed, it will take between 2
and 4 hours to assemble your computer and you will need to be able to use simple hand tools,
such as a screwdriver and a pair of pliers.
Step 1: Procuring Parts
First you will need to buy the parts necessary to build the computer. The parts we will use in
this project are labeled in figure 1:
1. Processor (CPU)
2. Computer Case
3. Optical Drive (DVD RW and SATA capable)
4. Memory (RAM)
5. Power Supply
6. SATA Cables
7. Motherboard (SATA Capable)
8. Processor Fan
9. Case Fan
10. Hard Drive (SATA Capable)
11. Assortment of case and drive screws (Not Pictured)
12. Flowers (necessary if you are invading the space of your significant other)
Step 2: Gather Tools and Supplies
Gather the tools you will need for the project:

● Screwdriver (for slotted and Phillips head screws)
● Wire cutters and strippers
● Needle-nosed pliers
● Utility knife
● Small flashlight
● Adjustable wrench
● Small container to hold screws
● Heat sink compound
● Grounding Strap
You may not use every single one of these tools in every installation, but it is best to have all of
them on hand in case you have a use for them.
Step 3: Open the Case

Open the computer case by removing the side panels. Find the screws that hold the side panels
in place and remove them (shown in figure 3 circled in red). The panel is removed by first sliding
it back (figure 4) then lifting it away from the case (figure 5).
Step 4: Prepare the Case for Assembly
Three things need to be done before assembly begins:
● Remove any parts or packaging materials that may have been shipped inside the case
(figure 6).
● Remove the cover for the optical drive. On our case, we will be removing the cover on
the highest drive bay to mount our DVD drive as shown in figure 7. Do this by pressing in
the retaining tabs shown in figure 8.
● Make note of the cables pre-installed in the case. These should be front panel
connections for features such as the power switch, audio jacks and usb ports. If they are
not labeled, consult the manufacturer’s documentation and label them yourself now
before other parts are installed in the case (figure 8).
Step 5: Ground Yourself
Put the grounding strap on your wrist (Figure 10) and connect the other end to the computer
case. If your strap is not equipped with a clip to hook to the case, find a place to wedge against
the metal as shown in figure 11. This will prevent any buildup of static electricity on your body
from damaging the computer components.
Step 6: Install Motherboard
To install the motherboard we need parts that should have been included with your purchased
components:
● I/O Bezel is a trim panel installed in the back of the case that surrounds the interface
ports on the motherboard. It should be included with the motherboard. Figure 12 shows
the contents of the motherboard box.
● Standoffs are installed in the case screw holes to create a riser that separates the case
and motherboard. The screws install into the standoffs as shown in figure 13. Screws
and standoffs should be included with the case, but it is a good idea to order these
items just in case they aren't included.
Follow these steps to install the motherboard in the case:
1. Install the I/O bezel plate into the opening in the back of the case (figure 14). It pushes
in from the inside.
2. Install standoffs in the case. The standoffs screw into the motherboard mounting holes
shown in figure 14. Check the screw hole locations on the motherboard for exact
placement.
3. Lower the motherboard into the case and align with the I/O bezel.
4. Install the screws.
Figure 15 shows the motherboard installed in the case. It works best to leave the screws loose
until all of them have been started and the board is aligned with the bezel.
Step 7: Install Hard Drive

The hard drive is the device that stores all of your data. It is 3.5" wide and needs to be mounted
so that you can gain access to the cable connections on the back (figure 16). If that is not
possible you may need to connect cables before you install the drive. To mount the drive:
1. Find a 3.5" drive bay to install the drive in. If you have trouble finding a place to mount
the drive consult your case documentation for suggestions.
2. Slide the drive into place until the screw holes on the sides are lined up with the holes in
the case.
Step 8: Install Optical Drive

The optical drive is 5.25" wide and is installed in the drive bay that we removed the cover from
in a previous step. Cable access considerations apply to this drive also. To install the drive:
1. Slide the drive into the drive bay until the screw holes are lined up and the front of the
drive is flush with the front of the case (figure 18). Make sure that it is orientated
correctly.
Step 9: Install the CPU

The CPU is the brain of the computer. It is installed on the motherboard in the socket shown in
figure 20.To install the CPU:
1. Find the corner marking that designates pin 1 of the CPU as shown in figure 19. On this
AMD brand processor, the corner is marked with an arrow. Consult the manufacturer's
documentation for specific information about your processor.
2. Lift the small metal rod next to the socket as shown in figure 20.
3. Find the corresponding marking on the CPU socket and insert the CPU so that the
markings are lined up.
4. Push the rod down to lock the processor in place (figure 21).
Step 10: Install RAM

The RAM is the temporary memory location that the processor works from. Permanently stored
data is pulled from disks and stored in RAM while the processor works with it. The memory is
easy to install:
1. Set the RAM board in the socket as shown in figure 22. Check to see that the notch in
the board is in the correct location. If it is not, turn it around 180º.
2. Press firmly on both ends of the board to set it into the socket. Make sure the tabs lock
into place as shown in figure 23.
Step 11: Install the CPU Fan

The CPU fan is really a combination of a heat sink and fan together. The unit draws heat away
from the CPU . To install the fan:
1. Place thermal compound to the CPU following the instructions provided with the
compound.
2. Set the fan assembly on the CPU with mounting tabs aligned.
3. Pull the locking rod down on the fan assembly to lock into place.
4. Connect the fan assembly's power connector to the motherboard. Consult the manual
to determine proper placement.
Caution: Failure to apply thermal compound will result in insufficient cooling and will cause
damage to the CPU and/or motherboard.
Step 12: Install Case Fan

The case fan is usually installed on the back panel of the case. If the fan mount is not obvious
consult the case documentation. To mount the fan:
1. Align the mounting holes by holding the fan to the mounting pad on the inside of the
case as shown in figure 25. The fan needs to be mounted so that it blows air out of the
case.
2. Insert the screws from the outside of the case and tighten.
Step 13: Install Power Supply
Consult your case documentation for details and then follow these directions to install the
power supply:
1. Align the mounting holes in the case and power supply as shown in figure 26.
2. Insert screws and tighten.
Step 14: Connect Cables
With all of the components installed in the case, the jungle of wires can be daunting. It is
important to consult the motherboard manual in order to make sure proper connections are
made. There are two kinds of connections, power and data.
● Every device that has been installed needs power. In figure 27, the power supply
connectors are shown. The motherboard has two power connections, and there are two
connectors specifically for SATA devices (drives). The other connectors will run fans and
other non-SATA devices.
● Data cables connect drives and front panel devices to the motherboard. Please consult
the motherboard documentation for the exact placement of connectors.
Step 15: Wrap-up

Now that the components are completely installed, the last thing to do is to reinstall the side
panels on the case. The computer is now ready to be turned on and to have software loaded on
it. If the computer has problems starting up, check all component connections and mounting to
make sure that you have hooked everything up correctly. Consult individual component
manuals for specific troubleshooting information if problems persist.
Prepare installer
This section discusses the following topics:
● Section 1.1, "Installation Modes"

● Section 1.2, "Installable Product Components"
● Section 1.3, "Product Distribution"
● Section 1.4, "Installation Prerequisites"
● Section 1.5, "Selecting Directories for Installation"
● Section 1.6, "Choosing the Type of Installation"
● Section 1.7, "Generating a Verbose Installation Log"
https://www.youtube.com/watch?v=tXphLUM_U08
Install operating system and drivers/peripheral installation work
1. 1. INSTALLATION OF HARDWARE COMPONENTS AND OTHER PERIPHERALS
2. 2. One of the basic skills that you must acquire in computer hardware servicing is to
independently assemble and disassemble a personal computer or simply setting up a

PC.
3. 3. Personal Computer Disassembly Before starting computer disassembly, make sure
you have the tools you need and they're all close by and handy and be sure to have a
container to keep the screws in so you have them when you want to put things back
together.
STEPS:
4. 4. Step1. Unplugging *The first thing you do is to unplug every cable that is plugged in to
your computer. That includes the cables such as Power, USB, Mouse, Keyboard,
Internet, Ethernet, Modem, AMFM Antenna, Cable TV, etc. Just unplug all the cables for
safety purposes. *Now that your computer is fully unplugged, move your PC to a clean
work space.
5. 5. Step2.Opening the Outer Shell/Case First, unscrew the four screws at the back of the
computer. On most computer cases, there will be large knobs that you can unscrew by
hand or by screw driver on the back-right side of the computer. The left side has small
screws because on that side you can't access much on the inside.
6. 6. Step2.Opening the Outer Shell/Case Figure 32. Screw at the back of computer chasis
7. 7. Once the screws are removed, you can remove the side panels. On most computers,
they just slide off. Start with the left side panel (the side that once had the knobs), slide
it towards the back of the computer. Now you can remove the left panel. Just like the
other side, slide it towards the back of the computer.
8. 8. NOTICE: If you are working on a carpet, about every five minutes touch something
that is grounded (Sink faucet / pipe, wire coming from the ground part of a wall outlet).
This is done so you do not shock your motherboard or other parts.
9. 9. Step3. Removing the System Fan First, unplug the fan from the motherboard. You can
find the plug by following the wire from the fan. It should be labelled "SYS_FAN1". Next,
you will have to unscrew the fan from the outside. You should now be able to lift the fan
out of the PC.
10. 10. Step4. Removing the CPU Fan The CPU fan is located right on top of the CPU heat
sink, which is a large piece of metal with fins on the top. The CPU fan plugs into the
motherboard in an awkward place, that is hard to access. But just follow the wires and
you should easily find it. It is labeled "CPU FAN1". To remove the fan from the heat sink,
remove the four screws securing it in place.
11. 11. Step5. Power Supply The first thing to do is unplug every wire coming from the
power supply. You must disconnect the motherboard (very large connector/plug),
CD/DVD drive(s) power, internal hard drive power and portable hard drive slot power.
12. 12. Once everything is unplugged, unscrew the four screws holding the power supply in
place, on the back of the computer. Next, push the power supply from the outside, and
then lift it out.
13. 13. Step 6. CD/ DVD Drive(s) First, unplug the ribbon from the back of the drive. Once
that is completed, pull on the tab securing the drive in place, then push it out from the
inside. Figure 37. Location of CD / DVD Drive
14. 14. Step7. Hard Drive First, unplug the connector at the back of the slot, and unplug the
other end from the motherboard. Also unplug the SATA cable from the motherboard
and the hard drive. The portable hard drive slot is secured the same way the CD/DVD
drive is, with a tab. Pull on the tab, then slide the slot out.
15. 15. To remove the hard drive from the side of the slot, unscrew the four screws
securing it in place. You must be very careful not to drop the hard drive, since it is very
delicate!
16. 16. Step8. Memory (RAM) To remove the RAM, push down on both tabs holding the
RAM in place, which are located at both ends of the RAM.

17. 17. Step9. Motherboard The motherboard has seven screws holding it to the frame,
which are indicated by large white circles around them. Remove them and then lift the
motherboard out of the frame.
18. 18. Personal Computer Assembly Now that you have the skills in disassembling a
personal computer, I believe that you are ready to take another step of this module
which is assembling a personal computer. All you need to do is to follow the step by
step procedures provided in this module.
19. 19. Step 1. Prepare your workplace 1. Take Inventory: Before you start, take an
inventory of your parts. Do not begin assembling your computer if you don't have
everything you need. Begin the step-by-step process once you are ready with everything
you need.
20. 20. 2. Make Space, Make Time: Building a PC takes up space - about a dining room table
worth. So make sure you have plenty of working room and a few hours to proceed with
minimal interruption. Work on a flat, stable table top surface, or bare floor, where you
have room to layout all of the items.
21. 21. 3. Prepare Grounding Protection: Use an inexpensive antistatic wrist strap. Make
sure you are wearing your antistatic wrist strap correctly (it does you no good at all if
you do not wear it!), and you are ready to proceed. Look at Figure 43 for details.
22. 22. 4. Have the Drivers Ready: Assuming you have another internet connected PC,
download the latest drivers from the vendors' websites for each component you will be
installing. Sometimes drivers are updated between the time the component was
manufactured and the time you are installing it. It is always best to have the latest. Copy
them to a CD for easy access.
23. 23. Step 2. Prepare the Motherboard 1. Great care should be taken when installing the
motherboard. First, take the board out of its packaging and put it on top of the antistatic
bag it came in (see Figure 45). Remember, you always want to safeguard your
components from potentially hazardous static electricity (wear your strap). Figure 44.
Motherboard in an Antistatic Bag
24. 24. 2. Before you secure the motherboard onto the PC case/chassis, inspect it carefully
for any visible defects. 3. Next, review the motherboard manual, to make sure you are
familiar with the motherboard layout and understand which socket is which. Manuals
are extremely helpful, usually easy to read, and include illustrations. Below you can find
instructions on how to install the processor, the heat sink and the memory modules on
the motherboard. You should not place the motherboard in the computer case until you
are told to do so.
25. 25. Step 3. Install the CPU 1. Use the unlocking mechanism to open the CPU socket
which is usually a lever. 2. Carefully line up the pins and place the chip in its socket; it
will fit only when oriented the proper way. An arrow or a missing pin on one corner of
the chip will show you how to line things up. 3. Align Triangular CPU and socket key
marks as shown in Figure 46. 4. Lower the lever to lock the CPU into place.
26. 26. Step 4. Install the CPU Heat Sink 1. Follow the manufacturer's directions to install
the heat sink and the fan that will cool the processor. If you bought an OEM CPU and a
separate heat sink, you may need to spread a thin layer of the thermal grease that came
with the heat sink over the chip to ensure proper transfer of heat (some heat sinks
come with this grease already applied).
27. 27. 3. Attach the clip that holds the heat sink in place keeping in mind that it may
require a fair amount of force. Again, follow the instructions that came with the heat
sink. They will show you how to fit it correctly. If you are in doubt, you can visit the
manufacturer's website for more information. 4. Plug the CPU fan's power connector
into the proper connector on the motherboard.
28. 28. Step 5. Install Memory (RAM Modules) In order to install the memory modules,
insert them into the proper sockets (Figure 48) and push down firmly but evenly until
the clips on both sides of the socket pop into place. If your motherboard supports dual
channel memory, consult the user manual to determine which pairs of RAM sockets you
should use. The motherboard and the CPU are the brain and nerve center of your PC, so
selecting these components is the most important decision you'll make.
29. 29. Step 6. Place the motherboard into the case 1. Some PC cases have a removable
motherboard tray. If yours does, remove the screws holding it in place and pull it out of
the case (Figure 49).
30. 30. 2. Note the pattern of the holes in your motherboard (Figure 50), and screw brass
standoffs into the motherboard tray or into the PC case in the correct locations
(ALWAYS check the manual and follow their instructions to the letter). Figure 49. Screw
Brass Standoffs Into the Motherboard
31. 31. 3. Check the layout of the sockets on the motherboard, and confirm that the ports
on your motherboard's back panel match the holes on the case's Input/Output (I/O)
shield that is installed in your case. If necessary, remove the old I/O shield by tapping it
firmly a few times with the butt-end of a screwdriver, and then replace it with the shield
that came with the new motherboard. 4. Carefully position the motherboard on top of
the brass standoffs (Figure 51), line up all the holes, and use the screws that
accompanied the case to fasten down the motherboard. If you are using a removable
tray in your system, slide the tray and motherboard back into the case and then secure
the tray.
32. 32. Step 7. Connect the Power Supply Making the proper connections is crucial to
successfully assembling your PC system. Fortunately, manufacturers provide color-

coded power cables and unique connector shapes to make the job easy. 1. First, plug
the large ATX power connector (Figure 53) from your power supply into the matching
port on your motherboard. Look Figure X for details. 2. Locate the smaller, square
processor power connector (Figure 54) (you cannot miss it - it is the one sprouting the
yellow and black wires) and attach it to the motherboard.
33. 33. Note: your connector is usually located near the processor. As always, refer to your
motherboard's manual for the exact locations. 3. Use your motherboard user manual
and find the description about front-panel connectors.
34. 34. NOTE: You are going to be doing work that requires attention to detail and can be
quite frustrating if you do not go into it with the right attitude.

35. 35. 4. Attach each of the tiny leads from the power and reset switches (Figure 56), the
hard-disk activity lights, the PC speaker, and any front-panel USB and FireWire ports to
the corresponding pin on your motherboard. The needle -nose pliers are useful for
manipulating small pieces.
36. 36. Step 8. Install Graphics / Video Cards 1. Begin by removing the backplane cover from
the AGP or PCI Express X16 slot (the metal piece where the monitor connector will
emerge) (Figure 55)
37. 37. 2. Install the graphics board in that slot, and then secure the card with a screw
(Figure 56).
38. 38. Step 9. Install Internal Drives Now it is time to install your drives. This is an easy
process, but it requires attention to detail. 1. Make any necessary changes to jumpers
on the drives before mounting them in the case. A two-drive system (one or two SATA
(Serial ATA- is a standard hardware interface for connecting hard drives and CD/DVD
drives to a computer) hard drives, plus one parallel ATA (Advanced Technology
Attachment) optical drive, for example) is easy to set up; the SATA drives are jumper
less, and the optical drive can be set as master on its own parallel ATA channel. Many
cases have removable drive rails or cages to house drives
39. 39. 2. Use the included screws to attach your drives to the rails or cage, and slide them
into the case. For externally accessible drives such as a DVD recorder, you can save time
by installing one drive rail and sliding the drive in for a test fitting to make sure that its
front is flush with the case (Figure 57). 3. When the drives are installed, connect power
and data cables to each one. Parallel ATA drives use wide, flat data cables that can be
installed only in the correct way. Floppy drives use a similar but smaller cable; SATA
drives use a thin, 1cm-wide data cable. SATA drives use a new type of power connector
that many power supplies don't come with. Fortunately, many motherboards ship with
adapters for converting a standard four-pin power connector to a SATA power
connector (Figure 57).
40. 40. Step 10. Install the Add- in Cards 1. For each add-in card, you must choose a free PCI
slot. 2. Remove its backplane cover to allow access from the rear of the case. 3.
Carefully position the card above the slot, and press down firmly to seat the card (Figure
59). 4. Secure the card with a screw.
41. 41. Many motherboards have additional sound connectors or ports housed on small
add-in boards. Some of these plug into slots on the motherboard; others screw into the
back of the case in place of slot covers. Usually the additional ports are not essential to
your PC's operation. For example, if you install a sound card, you do not need
connectors to the motherboard's built-in sound chip. Check your motherboard manual
to determine what each of these boards does.
42. 42. Connecting Peripherals of a Personal Computer When attaching hardware and
peripherals of the computer, ensure that they are connected to the correct locations or
ports. For example, some mouse and keyboard cables use the same type of PS/2
connector. So, you must know first the different ports that can be found in the back
panel of the computer.
43. 43. Steps in Connecting Peripherals of a PC Step 1. Attach the monitor cable to the video
port. Step 2. Secure the cable by tightening the screws on the connector. Step 3. Plug
the keyboard cable into the PS/2 keyboard port. Step 4. Plug the mouse cable into the
PS/2 mouse port. Step 5. Plug the USB cable into a USB port. Step 6. Plug the network
cable into the network port. Step 7. Plug the power cable into the power supply.
44. 44. Computer Hardware Servicing
Install Application Software based on Software

A software generally refers to any type of executable code that can be launched in a computer
system. It is designed to implement and complete specific functions that are required by the
user in his activities. Software can be developed and distributed freely (freeware) by
programmers in various communities and forums, or they can be sold commercially either
online or in computer stores by software companies like Microsoft, Adobe, and Sony among
others. Some computer experts believe that software can be categorized as general application
(can be installed and used by any organization) or customized (developed to cater to the
specific needs of a particular group or enterprise). General application software like the
Microsoft Office Productivity Suite for example can also be customized and tailor fitted to the
needs of a specific organization. This is done by using macro commands and a bit of
programming.
Materials Needed:
- Computer
- CD or DVD drive
- Installation disc
- Internet connection
- Web browser
Step 1
The first most important step in software installation is to verify that the target system meets
the general hardware requirements of the application. Beginning the installation in a computer
machine which does not possess the minimum requirements can lead to either an unsuccessful
installation or failure of the program to run after installing it.
Step 2
Since programs in general are written to be Operating System dependent, make sure that the
version of the application you are installing corresponds to the Operating System platform
running on your machine.
Step 3
Aside from the general hardware requirements, some computer programs also have software
requirements prior to installation. Double check if you need to update or upgrade your
Operating System or if there is a need to download other tools or utilities.
Step 4
Once all the initial requirements have been met, make sure that there are no unnecessary
programs running before beginning the installation procedure. In some instances, applications
may require that the antivirus programs be disabled. Make sure that you are installing a
legitimate application before disabling your protection software.
Step 5
Software installation can be done either from the Internet (skip to step 8) or from an
installation disc provided by the software manufacturer. To install from the disc, simply open
the CD or DVD drive and insert the installer.
Step 6
A setup wizard window should be launched. In case there is none, open the Explorer and
navigate to the optical drive. Double click on either the Autorun or Setup file.
Step 7
Once the wizard is running, simply follow the prompts until the installation process is
completed. For novice users, accept the default values to minimize potential problems during
the procedure. Jump to step 10.
Step 8
For installation from the Web, launch your browser application and download the setup file to
your hard drive.
Step 9
After completion of the downloading process, run the setup program to execute the setup
wizard that will handle the automatic installation of the software. Do step 7.
Step 10
After the installation procedure has been completed and the setup wizard has terminated,
reboot your machine before launching the newly installed software.
The purpose of this document is to describe the standards and procedures to follow during the
software testing phases of the SYSTEM Z project. This document supports the section on
Testing and Validation in the Integration and Methods Quality Manual.
1. Scope
These standards and procedures state the general standards and procedures to follow to plan
and conduct software testing and validation. These standards and procedures may be changed
via a change control mechanism that allows all those concerned to be notified of changes made
to the steps .
2. SOFTWARE TEST PLANNING
2.1 Introduction
Software test planning is the process whereby the following are established for the testing of a
given project deliverable:
· Testing requirements (scope),
· Testing approach,
· Testing tasks and deliverables,
· Estimates,
· Testing phases,
· Testing schedule,
· Completion criteria,
· Test environment and team roles and responsibilities.
2.2 Application Level Planning

High level software test planning is conducted within the project planning phase to establish
the high level plan for testing.
2.2.1 Objectives
· To identify Testing Requirements (Scope):
· to identify the software to be tested
· to identify the testing objectives
· to identify the test phases (testing coverage) within the testing life cycle that is required
· To identify Testing Approach:
· to identify the methods and testing tools required
· to identify any client assumptions/dependencies/limitations
· To identify Testing Tasks and Deliverables:
· to identify the activities to perform within each testing phase.
· to identify the external (client) deliverable document.
· to identify the table of contents for each deliverable
· to identify the internal deliverable documents

· to identify document deliverable reviewer
· To compile Testing Estimates:
· to identify the budgetary estimate for each identified phase of software testing
· To determine Testing Schedules:
· to identify the start and end date for each phase of software testing
· to identify all testing phase overlaps in the schedule
· to identify delivery dates for all document deliverables
· To determine Testing Phase Completion Criteria:
· to identify the completion criteria of each identified software phase

· To determine Test Environments:
· to identify the software/hardware requirements for each test phase
· to identify the number of test environments
· To identify Test Team Roles and Responsibilities:
· to identify the overall testing management responsibility and for each test phase
· to identify client roles and responsibilities
2.2.2 Responsibilities
· Development Manager:
· ensures that proper analysis and planning is done for the unit testing phase
· Technical Services Manager:
· ensures that proper analysis and planning is done for performance testing
· Application Test Manager:
· ensures that proper analysis and planning is done for all other test phases
2.2.3 Inputs
· First Release:
· Statement of Compliance
· Contract Proposal
· System Blueprint
· Subsequent Releases:
· Previous Releases Internal and External Deliverables
2.2.4 Method
· see Testing Work Instructions
2.2.5 Working Documents
· Test Hardware and Software Requirements
· PWW plans
· Meeting Minutes
· Testing Work Instructions

2.2.6 Deliverables
· Program Plan
· Release Estimates
· SDE Requirements Report
· System Z Standards and Procedures
2.3 Test Phase Level Planning
2.3.1 Objectives
Software test planning is conducted at the testing phase level to establish a working plan for
each phase.
· To identify Testing Requirements (Scope):

· to identify the testing phase objectives
· to identify the testing activities for the phase
· to identify software load within a phase
· to identify contents of the software load(s)
· to identify special testing requirements of critical components
· To identify detailed testing tasks
· To identify the estimates for each task within the phase
· To determine Testing Schedules
· to identify the testing start and end date for each software load
· to identify internal completion dates for internal/external deliverables
· to identify start and end dates for resources (both human and physical)
· to identify training dates required for testing staff
· To specify SDE requirements
· to identify any specify setup requirements for desktop workstations
· to specify the schedule for the setup of test environment which requires SDE support
· to specify requirements for special tools (e.g., PRS, Functional Requirement Analysis
Matrix, etc.)
· To identify Test Team Roles and Responsibilities
· to identify team member's roles and responsibility
· to identify team member's skill set requirements

· to identify team member training requirements
2.3.2 Responsibilities
· Integration Test Manager:
· ensures that proper analysis and planning is done for Integration testing
· System Test Manager:
· ensures that proper analysis and planning is done for System testing
· Development Manager:
· ensures that proper analysis and planning is done for unit testing phase
· Technical Services Manager:
· ensures that proper analysis and planning is done for performance testing
2.3.3 Inputs
· First Release:
· Requirements Specification
· Functional Specification
· System Description
· System Blue Print
· Subsequent Releases:
· Test Hardware and Software Requirements

· Previous Releases Internal and External Deliverables
2.3.4 Method
· see Testing Work Instructions
2.3.5 Working Documents
· PWW plans
· Meeting Minutes
· Testing Work Instructions
https://www.youtube.com/watch?v=3xsDJUGTXcI
3. UNIT TESTING PROCEDURES
The goal of unit testing is to assure that all functions and features of a single compilable unit of
code perform as specified in the Design Specification.
A unit test covers the testing of a software unit, or a group of closely related units, as a single
entity. Unit testing is performed in isolation, using test drivers to simulate higher level units,
and/or stubs to simulate lower level units. Unit Testing Procedures consist of:
· Creating a Unit Test Plan
· Creating test data
· Conducting tests according to the Unit Test Plan
· Reporting and reviewing the results of the test
These procedures are performed by the team member responsible for programming and
testing of the unit.
A Unit Test Plan is a set of test cases arranged in the sequence of chronological execution. The
Unit Test Plan is created before the programming of the unit is started, and the test cases
should cover the functional, input, output, and function interaction of the unit.
3.1 Documents Required

The following documents provide information required to create the Unit Test Plan and are
recommended reading before creating the Unit Test Plan.
· Design Report
· Requirements Reports
· Change Requests
3.2 Unit Test Design Guidelines
The guidelines to be followed during the creation of Unit Test Plans are:
· A test case must exist for every branch in the code
· Design test cases and test data which reveal errors in software
· Design test data that will ensure all conditions and quality of data edits are covered
· Create test cases for special formulae and extreme conditions (e.g., Test case "File is
Empty" shall be used for all files.)
· Test the interaction between units within the task
· To minimize the number of test cases, combine test cases into one if they test the same
feature. (i.e., can cover a group of units or a full task)
· Use test cases which already exist wherever possible. Include the generic test plan
· Arrange test cases in the order that minimizes the effort required for test setup and that
keeps related functions together
· Where possible, arrange the test cases in the chronological order in which they will be
performed
https://www.youtube.com/watch?v=MBB2dJKmQWU
3.3 Unit Testing Steps
Unit tests are created and executed by the developer of the unit. The procedure for unit
testing is as follows:
· Create a unit test plan following the Unit Test Plan guidelines
· Conduct the unit test as specified in the test cases
· Identify and fix or report any problems encountered
· Re-run the necessary tests
· Sign the Test Plan Cover Page (Tested By and Date)
· Package the Test Documentation and pass it to the development team leader
· The development team leader is to verify that the documentation is complete, sign the
Test Plan Cover Page (Reviewed By and Date) and submit the package to Quality Assurance for
review and Configuration Management for promotion
· Promote script or command files used to run the tests along with the unit
3.4 Create Unit Test Plan
· Identify Features to Test
· Using the Functional Specification, Preliminary and Detailed Design Specification (Unit
Procedural Description) identify:
· All Functions performed by the Unit
· All Inputs to the Unit

· All Outputs from the Unit
· Define all ranges and discrete values of the test data necessary to run the tests
· Prepare the Unit Test Plan following the Unit Test Plan guidelines
Note: See the Appendix entitled Templates for the template to be used and a description of
the cover page contents.
· Design a set of Test Cases
· Use the checklists for the five types of coverage and outlined functions, inputs and
outputs to create the minimum set of test cases for testing the functionality of the unit
· For each test case identified in the first point:
· State the condition that will be tested by the test case (this should be used as the title of
the test case)
· List the steps/actions to be performed in order to accomplish the test
· For each action performed identify the expected result
· Create test data necessary to create the condition being tested and for each piece of
data, indicate the expected results
For example, a test case for an invalid id on a data entry screen could be named "Invalid
id". The title states the condition of the test. The procedure for testing this condition should
indicate in which data entry field the cursor should be positioned and what key should be
pressed to trigger the edit. A table containing the various data elements to be entered can be
attached and referenced by one of the steps in the procedure. This data table could also
contain the expected results for each data item to be entered.
Note: Skeletons for the test plan and test case are available as templates in Word for Windows
3.5 Conduct Unit Test
Unit testing is performed according to the following procedures:

· Unit tests will be run according to the Unit test Plan created by the developer
· If any of the actual results do not agree with the expected results, the developer fixes
the code and re-runs the test. There is a possibility that the Unit Test Plan will need to be
updated if it is determined that the Unit Test Plan is not correct or no longer up-to-date
· Once all test cases have been successfully completed the developer signs the top page
of the test plan, completes a promotion request form and passes the package to the developers
team leader
· The team leader verifies that the unit test has been performed and the team leader (or
developer) passes the promotion request to Configuration Management
4. INTEGRATION TESTING PROCEDURES
The goal of integration testing is to ensure that all interacting subsystems in a system interface
correctly with one another to produce the desired results. Furthermore, in trying to attain this
goal, integration tests will ensure that the introduction of one or more subsystems into the
system does not have an adverse affect on existing functionality.
An integration test covers the testing of interface points between subsystems. Integration
testing is performed once unit testing has been completed for all units contained in the
subsystems being tested. Integration Testing Procedures consist of:
· Creating and integration test plan
· Conducting tests according to the integration test plan

During this phase, the interaction between subsystems is tested. This includes interfaces
through Inter Process Communications (IPC) and files. This phase is performed by an
independent test team. This team prepares and executes integration tests, generates problem
reports and is responsible for passing the integrated system on to the System Test Team for
system testing. The Integration Test team then enters a support mode in which it will test
problem reports generated by the System Test team before forwarding code fixes to the
System Testing environment.
This phase is sometimes combined with the system test phase as per the client's request.
The following documents provide information required to create the Integration Test Plan and
are recommended reading before starting the planning phase.
· System Blueprint
· High Level Design overview from the developers
· Detailed Design
· Entity Relationship Diagrams
· System Requirements Report
· Change Requests
4.2 Integration Test Design Guidelines
The guidelines to be followed during the creation of Integration Test Plans are:
· The number of new units or tasks to be tested by one Test Plan should not exceed five.
· To minimize the number of test cases, combine test cases into one if they test the same
interface point.
· Use test cases which already exist. Portions of available Unit Test Plans or System Test
Plans can be used where applicable.
· When testing few or minor changes to an existing subsystem, structure the Test Plan
such that the bulk of it will be regression testing using an existing Integration or System Test
plan. New test cases can then be added to cover the detailed testing of changes.
keeps related functions together. Where possible, arrange the test cases in the order they will
be performed.
· Whenever possible, design test plans to run independently of other test plans.
· Design test cases and test data which reveal errors in the interaction between the
software components. (Check the various response codes to calls to external interfaces.).
4.3 Integration Testing Steps
Integration tests will be created and performed by designated members of each team. Each
individual will be responsible for the preparation of all test cases, procedures and data, as well
as for conducting and documenting the tests. Each individual will also be responsible for the
specification of all additional tools and facilities required for the integration testing of their
tasks. The procedure for integration testing is as follows:
· Review all relevant design documentation and attend all design

overviews/walkthroughs.
· Create an integration test plan.
· Where possible, create scripts to automate the execution of the test case.
· Arrange to have Integration Test Plans reviewed by Development for technical accuracy.
The Test Plans may have to be updated after these reviews to incorporate changes suggested
by the Developers.
· Conduct the test as specified in the test cases.
· Identify any problems which are encountered or where the actual results do not agree
with the defined expected results. Complete a Problem Report. (see the TBU Problem Report
and System User Guide for the procedure to follow for handling problem reports.) Update Test
Plan execution status in the tracking document (see the appendix entitled Matrices, Logs and
indices).
· Once all problems have been resolved, re-run the necessary tests.
4.4 Create Integration Test Plan
This section provides a guide for creating an Integration Test Plan. Skeletons for the test plan,
test case and results summary are available in Word for Windows. By using this template and
the style codes defined, table of contents can be created that are used to create the tracking
document.
· Identify subsystem interface points:
· The Design Reports identify subsystem interface points. This should provide a high level
view of which subsystems are changing and what, if any, new subsystems will be created to
bring the system in line with requirements.
· A review of the Detailed Designs is conducted to determine which units (and therefore,
which subsystems) are changing .
· For new subsystems, or major changes to existing subsystems, the interface points must
be identified by using the Detailed Designs--these contain IPCs, Tables/Files accessed and
process descriptions which will help the tester to identify critical interface points.
· If the subsystem in question is not new and will not require major changes, then this
points to the need for regression testing of existing interface points to test that the subsystem
functions as it did before any changes were implemented .
· Divide the interface points into logical groupings (test plans). Draw the IPC diagram
illustrating the interface points.
· Create test cases to test each interface:
· Enter a purpose for each test case. Identify the conditions being tested. Ensure that
each statement in the purpose is proven in the Expected Results.
· Using the Detailed Design Report, identify the processes within the subsystems that are
the actual interfaces. These could be messages passed between processes or data written by
one process and read by another. List these processes under Interface Components Tested. If
the interface is by file, identify the tables being read, written or updated and list them in the
File/Table Interface Points section.
· List the steps to be followed in order to accomplish the purpose of the test:
· List the sub-test that identifies the interfaces being tested in each test case.
· Below each sub-test heading, list the steps required to accomplish the test.
· In test cases for interactive functions, describe the actions to be performed by the tester
followed by the result expected from the action.
· For non-interactive tests, list the steps to be performed. This usually involves running a
command file, but may also consist of listing the steps required to use an emulator or other test
tool.
· Expected results statements must describe only that which is visible to the tester.
Processing which cannot be proven is not to be included.
· Create test data where applicable.
· Establish the expected results for each test case:
· The Expected Results section describes the outcome of an event that was triggered by a
step in a test plan. For example it may be expected that after an IPC is sent from one process
and successfully received by another, a database change is made. In this instance, the Expected
Results section would describe how the database should look (i.e. the changes to a file/table
caused by the IPC). Once all the test cases in a test plan are defined, update the Interface
Points Tested and File/Table Interface Points sections of the test plan introduction page. It is
not necessary to list every software component being used in the test cases, only the specific
ones being tested by the test cases. (i.e., do not repeat software components tested fully by a
previous test plan, unless the software component is being used for re-configuration of the
system.)
· Test Setup Notes: Identify special instructions for the test case.
· List any requirements for the test cases in the Test Setup Notes section. For example, it
might be stated that it will be necessary for the tester to backup the data files used in the test
case so that they may be restored for running subsequent test cases. Where possible, create
scripts to automate the execution of each test case. The name of this script should be listed in
the Notes section of the test case.
· Develop procedures to execute (scripts) and evaluate each test plan (i.e., produce SQLCI
reports to list the contents of tables).
· Identify command files that will back up or restore the data base to the state it was in at
the start or completion of each test plan and list these command file names in the NOTES
section of the test case.
· Create a Test Case Tracking document.
· After completing all the Integration Test Plans, create a Tracking document (see the
appendix entitled Matrices, Logs and Indices) using a spreadsheet such as Microsoft Excel.
4.5 Conduct Integration Test
Integration testing will be performed according to the following:
· Integration tests will be run according to the Integration Test Plans by the Test Team
Leader or Test Team Member.
· Actual results of the test runs are presented by printing documentation (reports, file
dumps) or by demonstration (screen, panel displays).
· If any of the actual results do not agree with expected results, the person performing
the test will complete a Problem Report (PR).
· After the necessary action has been taken to resolve the problem, the test run will be
performed again from the beginning of the test step .The Test Plan may need to be updated,
depending on the results of the test.
· Update the Tracking document at least once a day. As a test is completed, either
successfully or unsuccessfully, the tester should update the Tracking document. The tester's
initials are to be updated each time a different person performs the test. If a test step is
completed without any problem reports, the test step is considered "closed". However, if a
problem is raised after running a test step, the tester will indicate this in the tracking document.
The tester updates the tracking document to reflect both the number of problem reports raised
by, and the problem report PRS numbers associated with, the particular test step executed.
(see tracking document template in the appendix entitled Matrices, Logs and indices). The
Integration Test Team meets frequently to discuss the testing activities, possible conflicts and
to review Problem Reports.
· The Integration Test Manager meets frequently with the Development Team Leaders to
review Problem Reports, negotiate priorities for code fixes, and discuss support issues.
· When an error is found, do not spend a lot of time trying to debug the problem.
Instead, raise a problem report providing as much details as possible so that the person or
persons resolving the problem will know what to look for. Whenever possible, dump screens,
logs, or tables to files or paper and forward a copy to whomever the problem reports are
assigned. This will help everyone to get the problems reports answered as efficiently as
possible.
5. SYSTEM TESTING PROCEDURES
5.1 Introduction
The goal of System Testing is to ensure that the system performs as per the functional
requirements specified by client.
A system test covers the testing of functions within the system. System testing is performed
once integration testing has been completed. System Testing procedures consist of:
· Creating Test Plans
· Conducting tests according to the System Test Plan
Features to be tested during System Testing are:

· Functional Requirements
· Depending on the project, any regression tests deemed necessary
The following documents provide information required to create the System Test Plan and is
recommended reading before starting the planning phase.
· High Level Design overview
· Problem Report Analysis Report
· Database Design Report
· FRAM
· Requirements Reports
· Change Requests
· Appropriate 3rd Party Interface Specifications
5.3 System Test Design Guidelines
The following are recommended guidelines when designing system tests:
· Design test cases to ensure that all requirements identified in the Functional
Requirements Analysis Matrix document are tested by one or more test cases.
· In order to minimize the number of test cases required, design test cases to establish
the presence of several related requirements.
· Each logical test case should test related functionality.
· Use test cases that already exist wherever possible.
keeps related functions together.
· Where possible, arrange the test cases in the order the function would be performed
from a business perspective.
· Design test plans to run independently of other test plans.

· Identify a procedure to set up the database as required at the start of the test.
· Design test cases and test data that reveal errors in software.
· Design test data that will ensure all conditions and qualities of data edits are covered.
· Use live or representative data as much as possible in order to provide realistic

functional tests. Any comments about setting up the test data are to be documented.
· Data for most reports should come from the data prepared for testing the interactive
processes. It is acceptable to have the reports contain existing data from the database.
5.4 System Testing Steps
System Tests shall be run by the System Testing Team. A skeleton for the system test plan is
available in Word for Windows. The procedure for system testing is as follows:
· Review all requirements and design documents.
· Attend system reviews presented by Development and Analysis Team members.
· Create and maintain a detailed System Test Project Plan.
· Divide the FRAM Requirements into logical groupings or scenarios. These scenarios
should reflect the business or operational approach to the system.
· Define any necessary regression tests.
· Create a System Test Plan.
· Where possible, create scripts to automate the execution of a test case.
· Ensure the System Test Plan is reviewed by appropriate parties (Development and
Quality Assurance).
· Verify that the System Test Environment has been created.
· Conduct the test as specified in the test cases.

· Identify any problems that are encountered or where the actual results do not agree
with the defined expected results and complete a Problem Report.
· Record in the Tracking document the steps executed, relevant PRs, and test cases
completed.
· Update test plans after the testing is complete.
· Produce Post Project System Testing Reports
5.5 Create System Test Plan
· Obtain a copy of the Requirements Report, FRAM document, Database Design Report,
and Detailed Design Report.
· Determine a table of contents for the system test plan and assign the individual test
plan scenarios to testers.
· Inform QA and publishing of delivery dates for QA review and publishing. Inform QA of
any special testing strategies which will be adopted.
· Review the above-mentioned documents for the test plan scenarios to be written.
· Schedule a testing overview with the analysis and/or development teams to gather the
necessary information for writing the test plan scenario.
· Determine the test cases for the test plan scenario.
· Allocate the FRAM to the appropriate test case.
· Write the test plan scenario using the system test plan template.
· Submit a copy of the test plan scenario to the appropriate parties (Analysis and
Development teams) for review. The appropriate parties include a System Test peer and
development. Depending on the project, the client may participate in a system testing role and
may also review the test plan scenario prior to publication.
· Submit a copy of the allocated FRAM to test plan/test case to the FRAM officer. Obtain
an updated FRAM document allocated to test plan/test case.
· Submit a copy of the test plan scenario which has been reviewed in a previous step to
QA. Along with the test plan scenario, submit a copy of the FRAM which has been allocated to
test plan/test case level.
· Upon QA review, make any updates to the test plan scenario which are deemed
appropriate.
· Resubmit the test plan scenario to QA for final review.
· Submit the test plan scenario to publishing.
· Create the System Test Tracking Report once all test plan scenarios have been reviewed
by QA.
· Submit the System Test Tracking Report to Publishing
5.6 Conduct System Test
· Verify that the System Test Environment has been created and that it is functional.
· Create any test data necessary for executing the system test plan scenarios.
· Execute the system test plan scenarios as assigned to each test team member.
· Create a problem report for deviations from the expected results documented in the
system test plan scenario.
· Interact with support team to help resolve problem reports.
· Update the tracking report to reflect test step execution and completion.
· Depending of the project, interface with the client testing prime to communicate the
system test status and issues.
· Communicate the system test status and issues to management.
· Ensure execution of the system test plan as per acceptance criteria.
· Upon system test completion, refine system test plans for final publication.
· Produce Post Project System Test Reports.
5.7 Quality Records

The following system testing documents are kept as permanent records:
· Test Plans
· Client Access Memo
· Test Results
· Integration and/or System Test Report
· Status Reports
6. Performance Testing
6.1 Introduction
A performance test is planned and executed on all components for which performance
requirements and targets have been agreed to with the client. The complexity of the
Performance Test is a function of both the number of test cases required and the level of
difficulty to set up and execute each test case.
The following documents provide information required to create the Performance Test Plan
and are recommended reading before starting the planning phase.
· Standards and Procedures Manual
· Overview Design Report
· System Description
· Database Design Report
· Detailed Design Report
· Requirements Report
· FRAM
6.2 Performance Testing Guidelines and Steps
In general, the following steps highlight what is required:

· Ensure that all performance requirements and/or objectives, agreed to with the client,
are known and documented.
· Define the test cases that are required for performance testing.
· Gather all information pertinent to volumetrics for issues of sizing as well as

performance (i.e., estimated file sizes, normal and peak throughput, etc.).
· Create the Performance Test Plan.
· Ensure transaction drivers and other required utilities are developed, tested and
configured prior to the commencement of testing.
· Determine the tools and methodologies required to measure the performance.
· Create the Performance Test environment.
· Create and populate the Performance Test database.
· Update all system and application configurations to reflect the test site environment.
· Execute test cases as specified in the Performance Test Plan
· If one or more performance requirements cannot be met, introduce changes to the

system configuration and/or corrections to the affected unit(s).
· If the performance requirement(s) in question still cannot be met, complete a Problem

Report.
· Complete analysis of performance test results and document.
6.3 Quality Records
The following Performance Test documents are kept as permanent records:
· Performance Test Plan
· Performance Test Report
· Performance Test Results

Preparing for Installation
This chapter describes the type of WebLogic Server installers and how they are distributed. It
also describes installation prerequisites, the installation directory structure, installation modes,
types of installation, and installable components.
● Types of Installers
● Product Distribution
● Installation Prerequisites
● Selecting Directories for Installation
● Installation Modes
● Choosing the Type of Installation
● Installable Product Components
● Generating a Verbose Installation Log
Types of Installers
The following types of WebLogic Server installers are available:
● OS-specific Package installer—This type of installer is a standalone version of the

installation program that includes the JDKs for the selected platform. The installer may
be either an .exe file or a .bin file, depending on the selected platform.
● Generic Package installer—This type of installer is a .jar file. It does not include the
JRockit SDK and Sun JDK. You can use this type of installer to install the product on any
supported platform on which Java is already installed.
● Upgrade installer—Upgrade installers allow you to upgrade an existing WebLogic
Server installation to the current patch release. For example, if you have WebLogic
Server 10.3.0 installed, you can use an Upgrade installer to upgrade your installation to
WebLogic Server 10.3.6. If a patch release is available for your current WebLogic Server
installation, you can download an Upgrade installer from My Oracle Support.
● Development-only and supplemental installers—The development-only installer is a
ZIP file that you extract to a Middleware home directory to create a WebLogic Server
installation. It contains a WebLogic Server installation that includes all of the artifacts
needed for development. You must not use this WebLogic Server installation for
production.
2. INSTALLING COMPUTER PERIPHERALS
In previous Tech Tips, we covered how to choose and install your computer components and
how to install the internal system components for your computer from the motherboard to the
CPU and heatsink/fan combo. In this tip we cover the installation of peripherals including
monitor, keyboard, mouse and so on. Installing peripherals is just about the easiest task you
will tackle when building a computer. Check the list below for the peripherals we will be
covering in this Tech Tip. Keyboard Mouse Monitor Speakers Webcam Printer Scanner
3.Installing Application Software
Once the operating system and associated software is installed, the first line support technician
will be required to install and configure the application software that the user requires.
Application software is software that allows a user to perform a particular task, e.g. typing a
letter, or searching a database.
Typically, a first line support technician will be installing commercial software, such as
Microsoft Office. There are different ways in which commercial software is distributed, such as
'off the shelf' where the software in sold in a box containing a CD and associated
documentation, or downloaded from the developer's web site.
Most commercial software is protected in some way and could require an End User Licence
Agreement (EULA)being agreed on during the installation and the entry of a special code to
unlock the software for use.
4. Software Testing Documentation Guide:
In my Software Testing career, I never heard people talking much about software testing
documentation. The general opinion about testing documentation is that anyone who has free
time can do the documentation like a Test case, Test plan, status report, Bug report, project
proposal etc.
Even I did not stress more about the documentation, but I can say it’s my habit to place all the
data in black and white and to update others about that as well.
5. Conduct testing and documentation about the system unit
Step 1: Define the criteria.

a) What are you expecting to find? You can look for things like:
● Standards followed – naming conventions, consistent numbering …etc.
b) Make
or
as checking
as simple
a checklist–
ON
as aorgrocery
OFF.
Checklists
list. All are
it takes
very isversatile.
some time It can
to make
be as complicated
it and once you
as ado,
review
it is as
checklist
simple
c) How
be recorded
to report
and tracked.
the results? – Choose whatever is convenient, preferably a method that can
● A list in an email
Step 2: Perform the check

a) Using the checklist you made earlier, verify the document and provide your feedback.
Step 3: Record your results

a) Again, using the method decided in step 1, record and report your results.
b) When reporting
reporting a defect. your
Don’tcomments
overlook anything.
or suggestions
Be detailed.
for change, treat it no differently than
Step 4: Share, discuss and implement the changes required

a) Nobodyguidelines
following likes to bewhen
told that
you their
are providing
work is incorrect
negative or
feedback.
incomplete. So keep in mind the
● Give reasons to back your comments
b) Obtain a sign-off.
c) Have the changes made
Step 5: Version control the documents involved
a) Don’t
them in adelete
centralized
the older
project
versions
folder.
of After
any ofall,
thethis
documents.
is the evidence
Nameto
them
all our
appropriately
work and keep
Step 6: Sign off and use the doc as intended.

a) Once
move onall
tothe
using
changes
the document
are incorporated,
for what itversion
was created
saved, for.
give the review process a sign-off and
b) Another
times is thisquestion
process going
that comes
to go on
up –is work-
– do we
review-fix-and
recheck afterthen
the changes
reviewedareagain?
made? Until
Howwhen?
many
No, a review
focuses
documentson verifying
are
does
impossible.
not
if the
havetesting
So
to ahappen
reasonable
aidesover
are created
and
levelover
of right
review-
again.
or not.
Itone
is aAs
time
quality
always,
by acontrol
peer
zeroisdefect
activity
acceptable.
that
then
are
undergo
government's
likely
look
Conduct Thesuch
to
atidea
stress go
how
abanking
under
test
testofbad
awas
banking
and
the
plan
one
books
which
a of
stress
couple
Tim
could
ones
test
Geithner's
weeks
can
get
is be
in
pretty
ago.
asalvaged.
variety
few
appealing.
specific
ofThat
scenarios
proposals
You
banks
goto
would
in,get
when
look
abe
sense
at
he
required
the
unveiled
ofbooks,
which
to the
and
banks
But how
inspectors
could getdo
agoing
handle
you actually
into
onthe
thedo
banks
safety
it? Some,
are
of away
bank
liketoo
Yves
assmall,
large
Smith,
and
as Citi.
have
that argued
there's that
no way
the 100
numbers
bureaucrats
of
that Falkenstein
Eric won't just be notes
arbitrary,
another political
problem: and There's
subject noto gaming.
accepted way of conducting a stress test
Any quick,
assessing
(tier
(OAEM,1, tier
Substandard,
economic
nationwide
2, total), risk
andDoubtful,
stress
capital
thentest
make
to
Loss).
will
'good'
sure
be arbitrary.
various
assets. Historically,
level
Regulators
of bad theyloans
do not
merely
arehave
in their
check
a lotproper
leverage
of experiencing
buckets
ratios
So, naked
necessarily
AAA
the
historical
large
important,
for
quickly,
asame
rated
test
amount
it loss
might
probability
is
opportunism.
bonds,
real,
penalizes
counterproductive
of
rates,
be
differences
differentiation
and
something
looking
of
banks
even
going
It iswith
of
at
inherently
into
like,
opinion,
the
to
and
lots
the
attempt
default.
institution
assume
complexity,
recent
of complicated,
and
highA
aall
surprises,
sheer
quality
quick
stress
and
assets
andindustry-wide
politics
solution
test
assets,
this
and
can
one
should
would
lose
even
as
should
in
because
some
10%
this
though
apply
generate
data,
not
situation.
of
use
itthe
their
assume
but
treats
we
legitimate
stress
awould
that
value.
lotBB
every
of
would
based
rated
like
haggling
This
issues
liability
agenerate
on
bonds
solution
astheir
over
cover
has
likea
Now, doing this quickly would stop the contagion issue, but only by being arbitrary.
Now,
running
at
system.
candidates
all. we
But
In
around
imagine
arbitrariness
an arbitrary
and
some
thatsystem,
iswill
an
what
dismiss
arbitrary
makes
all banks,
this
stress
it impossible
on
regardless
the
testidea
is better
to
that
ofinvest
their
we
thanhealth,
just
private
what
can't
are
we
capital
have
nationalization
have, these
into
which
the
zombie
banking
is nothing
banks
Video: https://www.youtube.com/watch?v=PXay0q1kJVw
Follow 5S and 3Rs according to environmental policies
Sort – This step focuses on the elimination of any unnecessary workplace clutter. In a process
called “red tagging,” all workplace items are sorted through, with a red tag placed on any that
are not absolutely necessary for completing a task. Once tools, supplies, materials and
equipment have been tagged, they are then relocated to a holding area for a follow up
evaluation. Items that are only seldom used can be stored closer in proximity to the workspace,
while obsolete clutter should be discarded.
Sorting’s benefits include: a more effective use of space, simplified tasks, a reduction in
hazards, and a significant decrease in distracting clutter.
Set in Order – The goal of this step is to examine methods of storage that are effective and
efficient, sometimes referred to as “visual management,” and then create a work environment
that is organized, ergonomic, uncluttered and easily navigable. Some questions to ask during
this step might be: Which specific items are needed to perform a task? How many items need
to be readily accessible and where should they be located?
The methodical storage of materials means that every item has a predetermined location
where it will remain until it used, and then it will be returned immediately following its use.
Labels and color coding are also helpful techniques to use in this step. With an organized and
efficient use of storage, everyone is easily able to locate important items and enjoy a less
stressful work environment.
Shine – With the clutter gone and the storage organized, the next step is to properly and
thoroughly clean the work area every day. This step is critical as a way of sustaining the
improvements begun in the Sort and Set phases. All storage areas, machines, equipment, tools
and work surfaces must be cleaned and checked regularly. Employees will feel more
comfortable in this clean and uncluttered environment, which could also lead to increased
ownership of the organization’s goals and vision.
Standardize – Now that the first three steps are in play, it’s time to standardize these new
practices. All employees need to be included in the creation of a set of standards that will
become the new norm for the workspace. When these new standards and best practices are
implemented, the old habits will soon die out and be replaced by the more efficient patterns of
behavior. New standards, however, will probably require some oversight and enforcement until
they are habitual; reminders such as visuals and emails are effective tools to help these new
standards become set in stone.
Sustain – The final step of 5S is certainly the most challenging: remaining disciplined enough to
sustain the positive changes made in the first three steps. It is critical that the new system be
maintained or the efforts and costs put into developing the new system will be pointless. By
putting a formal system in place that includes regular training and communication, employees
will be able to comfortably conform to the company’s 5S procedures.
The 5S system is not complicated to understand; the challenges lie in successfully implementing
the steps and sustaining the practices. Among other things, a successful 5S implementation will
improve workplace safety, develop self-esteem among employees and reduce training time for
new employees.
over-packaged
REDUCE –litterless
throw products.
away less
theby buying only what you need and by buying fewer disposable and
1.
2.
3.
4.
5. Use awashable
Bring
Pack
Have afurniture,
your
reusable
owndishes
water
toys
bag
lunchto
and
instead
bottle
withappliances
grocery
only
instead
ofor
paper
containers
store.
repaired
ofplates
singlethat
and
instead
serve
can
cups.
water
be
ofrecycled
tossing
bottles.them
or washed.
and getting new ones.
REUSE – use items over and over give gently used items to others.
1. Take
2.
recycling.
charity
3.
4.
5. Reusedown
Pass
Collect
or
“garbage”
your
containers,
rain
havefood
outgrown
water
a yard
scraps
andin
bags
sale.
make
aclothing,
rain
and
boxes,
ityard
barrel
into
tubs,
books
waste
something
to cups,
use
and
andtotoys
bottles
start
water
newtoato
younger
the
and
compost
use
garden.
jars
or brothers
over
to
binplay
in
and
your
with.
and
over
back
sisters,
before
yard.
donate
discarding
to or
RECYCLE – as much as you can by collecting recyclable materials to be picked up at the curb or taken to
amotor
1.drop-off
community
2.
phones,
3.
4.
and
5. Have
Collect
Look
Encourage
paper
oil,
forlocation
your
bottle
paper
aluminum
paints,
towels.
the and
soschool
your
they made
recycling
caps
and
and
parents
can
or
work
cans
beverageinto
electronics
aluminum
be
symbol
and
with
to
made anew
look
take toproducts.
containers
and
recycling
into
for
tabs.
for buy
recycling
your
recycled
recycling
recycled
and
partner
local
find
too.
paper
centers
metal
products
to
thecollect
and
recycler
best
that
new
way
like
and
accept
beverage
for
recycled
to
recycle
redemption.
recycle
things
ink
containers.
content
like
them
jettires,
cartridges,
inpaper,
your
batteries,
cards,
cell
Video: https://www.youtube.com/watch?v=8gKJ3_Hm3dM
Video: https://www.youtube.com/watch?v=WG_ybcmj6y4
Prepare and forward documentation to appropriate personnel

Step 1: Printing Your Document Type Targets
Your first step is to identify the document types consistent within each employee file.
Document types like new hire, benefits, and performance. Once you tell us what your specific
document types are, we will provide you with PDFs for each document type, along with a
barcode. Please print these on lightly colored paper such as yellow or green. REMEMBER –
please do not photocopy these target sheets.
Step 2: Matching Targets to HR File Sections

Next, take your HR file and open it to the first section. In this example, the first section is the
“new hire documentation”. You are going to place the document type sheet on top of this
section.
A very important step on the FIRST page of the FIRST section of EACH employee file – is to have
the employee number clearly written or circled. You only need to do this on the first page of
the first document within a file. If you do not use employee numbers – do not worry about this
step.
Once completed, place the first section face down in the box. We will then move on to the next
document type section…and so on until each file is completed. There is no need to send us the
folder, just the paper! Remember – keep these files face down!
That’s it – it really is that easy.
Video: https://www.youtube.com/watch?v=cIL5sb3buis

Final Research Paper in Css

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Final Research Paper in Css

Hochgeladen von

Copyright:

Verfügbare Formate

FINAL RESEARCH

1. Demonstrate Work Values

2. Practice Career Professionalism

4. Integrity. You are known for your consistent principles.

1. Treat other with respect

2. Keep your word

3.Practice occupational Health and Safety Procedures

a. Most organisations have elements of an Occupational Health and Safety Management

There are 5 keys to implementing a successful OHS Management System:

1. management commitment and policy

5. review and improvement

The importance of an OHSMS should not be underestimated. It allows your workplace to

4. PRE EMPLOYMENT REQUIREMENTS IN THE PHILIPPINES

1. Treat other with respect

2. Keep your word

b. Most Common Requirements by Employers in the Philippines

Here are those needed:

GSIS (Government Service Insurance System)

SSS (Social Security System)

NBI (National Bureau of Investigation)

Pag-IBIG or Home Developmental Mutual Fund (HDMF)

TIN (Tax Identification Number)

c. Applying for a job - The application and interview process

● Any certificates you have that support your application

d. Health Certificate in Pasig City

5. Health certificate fee

4. Umatend ng seminar (manood ng video tungkol sa EL NINO, LA NINA at paghuhugas ng kamay,

Tapos, tapos na uwi na :)

List of the Four Basic Computer Operations:

2. Use Hand Tools

1. Install and Configure Computer Systems

1. 1Click the Wi-Fi symbol

14. Click Save changes. It's at the bottom of the page.

3. Set-up Computer Servers

A computer network consists of two or more computers intended to share resources:

1. Turn on your computer first.

Starting the installation of

4. Windows copies temporary files.

5.On the next Install Windows screen, click Install now.

Select either the complete

12. Maintain and Repair Computer Systems and Networks

ELC724331 Install and configure computer systems

ELC724333 Set-up Computer Servers

ELC724334 Maintain and Repair Computer Systems and Networks

q Computer Maintenance Technician

Individuals aspiring to be awarded the qualification of COMPUTER SYSTEMS SERVICING

COC 1: Install and Configure Computer Systems

COC 2: Set-up Computer Networks

COC 3: Set-up Computer Servers

1 Assemble computer hardware

3 Install operating system and drivers/peripheral installation work

4 Install application software based on software

5 Conduct testing and documentation about the system unit

1. Assemble computer hardware

Step 1: Procuring Parts

3. Optical Drive (DVD RW and SATA capable)

7. Motherboard (SATA Capable)

10. Hard Drive (SATA Capable)

11. Assortment of case and drive screws (Not Pictured)

Step 2: Gather Tools and Supplies

Gather the tools you will need for the project:

● Wire cutters and strippers

● Small container to hold screws

● Heat sink compound