Task 1.

1
There are objectives and main functions of IT/Technology solution testing:

Testing each functional component known as requirement part of

software development.
Any testing system always have a rage of stackholders and all of their
needs have been accommodated before the implementation of the
system, Typical testing include: functional testing, integration testing,
system testing, end user testing, etc.
The criteria for testing are taken from business requirements, expected
benefits, service management requirements, expectations of
stakeholders, etc. When testing activity do not meet these criteria, redesign and re-development activities will be implemented
Design of testing is combining the competencies needed to explain the
criteria for testing on a testing strategy
Test plans define who will test, what will be tested, with what data,
where and how testing is to occur and the expected result of tests

With 2 months experience in tester so I think IT/Technology solution Testing

level 2 (National Occupational Standards) is right for me. Base on NOS, my
skill, my knowlegde. There are the requirment must have, if i want to do
IT/Technology solution testing level 2(foundation).
Requirement performance criteria(Skills):
o Follow organisational standards for the systems development
lifecycle
o Correctly use specified IT/Technology solution testing procedures,
tools and techniques, as directed by superiors
o Comply with any relevant legislation, regulation and external
standards relating to IT/Technology solution testing activities
o Assist with the collation and documentation of information
relating to specified IT/Technology solution testing activities
o Perform specified IT/Technology solution testing activities as
directed
Requirement knowledge and understanding:
o The systems development lifecycle as it relates to testing
activities
o The difference between functional testing and other types of
testing
o The role and purpose of the range of different types of testing
activities
o The importance of documenting the deliverables from testing
activities in a clear and understandable manner

o The importance of undertaking testing activities accurately

o Use testing procedures, tools and techniques
o Comply with all relevant and applicable legislation, regulations
and external standards relating to testing activities

o Collate and document information:

Relating to the business requirements for tests
Relating to the range of appropriate and acceptable results
for any given test
o Operate with reference to
Organisational standards for testing activities
Professional and ethical standards relating to testing
activities
-

All the requirements above, I can response almost of which, here is

what I can do and understand:

Skill:
Follow organisational standards for the systems development
lifecycle
- Use organizational standards for work, it really important for me to
practice. One of my strength is easy to learn and get familiar with new
standards.
Correctly use specified IT/Technology solution testing procedures,
tools and techniques, as directed by superiors
Perform specified IT/Technology solution testing activities as
directed
- As a new one like me, work under the direction of superiors is useful
for me to get more experience. I am a listenable and love to do
teamwork so I will do this work fine.
Knowledge:
The systems development lifecycle as it relates to testing activities:
- SDLC(The systems development life cycle). Known as aplication
development lifecycle, is a term to describe a progress for planning,
creating, testing, and deploying an information system. SDLC applied
to hardware and software configurations, as a system can be
composed of hardware only, software only or a combination of both.

The difference between functional testing and other types of

testing:
- Now we have many type of testing: Functional testing, Non-functional
testing, system testing, software testing, ETC.
o Functional testing are test by feeding them input and examining
the ouput, and internal program structure is rarely considered.
Functional testing usually describe what the system does.
Functional testing ensures that your software is ready to for
release to the public. It also verifies that all the specified
requirements have been incorporated. Positive functional testing
involves inputting valid inputs to see how the application
responds to these and also testing to determine if outputs are
correct. Negative functional testing involves using different
invalid inputs, unanticipated operating conditions and other
invalid operations.
o Non-functional testing is designed to figure out does your
product will provide a good user experience?. For example, nonfunctional tests determine how fast the product is, how long it
takes to do a request. Non-functional tests include: performance
testing, compatibility testing, security testing, ETC.
-

The difference between functional and non-functional testing:

o Functional testing ensures that your product meets customer and
business requirements, and doesnt have any major bugs. On the
other hand, non-functional testing wants to see if the product
stands up to customer expectations.
o Basically, functional testing is designed to determine that the
applications features and operations perform the way they
should. Non-functional testing wants to know that the product
behaves correctly.
o Your application needs to pass both categories of testing. Failure
to release a working product that meets the needs of consumer
demands can damage your companys reputation and reduce
overall product sales.

The role and purpose of the range of different types of testing

activities
- Testing is find out errors/bugs, The test isnt confirm that functions
work right under all conditions, It can only confirm that it is not working
properly in the specific conditions.

The scope of software testing: involves checking code, made the code
under different conditions and testing aspects of the code.
The testing team can be separated from the software development
team to find out errors, Errors information obtained from the testing
can be used to impale the process of software development.

The importance of documenting the deliverables from testing

activities in a clear and understandable manner
- Document writer must make a clear, understandable and correctly
document, it will help testing result more useful. Also help developer to
reduce error, update more functions and makes testing more accurate
in an organization.
- For big company good documentation can save more time and get
more success of product. Well document is part of successful project.
- In testing process, project requires planned and serialized
documentation for testing and development. Because most of
companies concentrate on creating documentation of software
development process (include testing).
The importance of undertaking testing activities accurately
- Must make a tests correctly to identify the problem of the software
( bug, error, ETC) and report to the parties concerned to modify the
product.
- There some importance of testing activities: find out defects, avoid
user detecting problem, ensure that product as customer expected,
reduce cost of defect fixing.
Use testing procedures, tools and techniques
- Nowaday we have a lot of tools and techniques (template tool,
software tool), more kind of tools more easier for me to find fault.
- For example I can use DTMtool which is a easy to use, but powerful,
within software development projects for Model Based testing. An easy
to use interface for drawing functional test models. DTMtool generates
in seconds test cases and complete written test design in Excel or PDF,
and will save up to 70% time. DTMtool fits excellent within Agile Scrum
based projects, and offers a solution to handle changes during projects
without investing additional time in generating test scripts.
-

And finally there are things I cant do and understand about

IT/Technology solution testing.

Skill:
Comply with any relevant legislation, regulation and external
standards relating to IT/Technology solution testing activities
- Its import for community of tester, I am a new one and I always comply
to thing I think right, not any relevant legislation. So it is unnecessary
for me to comply.
Assist with the collation and documentation of information relating
to specified IT/Technology solution testing activities
- In my opinion assist with the collation and documentation is the
needed for company at all time, but I dont have skill of assistance. I
will practise my assistance skill because it importaint for me too.
Knowledge:
Comply with all relevant and applicable legislation, regulations and
external standards relating to testing activities.
- As a new one like me, I dont have enough time to know about
regulation and external standards relating to IT/Technology solution
testing activities

Collate and document information:

- I dont have enough skill to know and collate relating to the business
requirements for tests, relating to the range of appropriate and
acceptable results for any given test
Operate with reference to:
- This thing are useful for me in the future, I will learn about
organisational standards for testing activities, professional and ethical
standards relating to testing activities.
Task 1.2
Follow requirement skill and knowledge of UK NOS, I still have some skill/
knowledge gaps. So therere my objectives and source to delete those gaps
(ascending priority order)
Knowledge

Comply with all relevant and applicable legislation, regulations and

external standards relating to testing activities
o Objectives: learn relevant and applicable legislation, find out
regulations and external standards.
o Sources: On the internet, document.
Collate and document information
o Objectives: Understand about business requirements for tests,
range of appropriate and acceptable results for any given test
o Sources: Study curriculum, on internet, from people with
experience, by experienced colleagues.
Operate with reference to
o Objectives: standards for testing activities, Professional and
ethical standards.
o Sources: with team.
Skill

Assist with the collation and documentation of information relating to

specified IT/Technology solution testing activities
o Objective: can make collation and documentation of information
o Sources: Practice on free time, do a research on internet, from
people with experience.

Task 1.3
Personal development plant:
Identified needs
Solution
Time
Professional skills
Comply with all relevant and search in internet, find Practice
in
applicable
legislation, document related
free time
regulations
and
external
standards relating to testing
activities
Assist with the collation and Do a research on
documentation of information internet,
get
help
relating
to
specified from
people
with

IT/Technology solution testing experience.

activities
Collate
and
document
information:
Relating to the business
requirements for tests
Collate
and
document
information:
- Relating to the range of
appropriate
and
acceptable
results for any given test

Study in class at
university, talk with
lecturers.
Observe the people
who
work
in
the
company
and
ask
them about problem I
have.
Participate in team
discussions of testing.

At
study
ciriculum
and
when
working and
training

Operate with reference to

Training
in
testing When
team
and
I
can
learn working and
- Organisational standards for
from part time job traning
testing activities
related to testing.
Operate with reference to
Professional
and
ethical
standards relating to testing
activities
Soft skills
Better English

Better communication skills

Self-confident
Play musical instruments
Reputable person

Learn english, selfstudy.

Take part in group of
foreigners
Take part in social
activity.
Take part in music
group in University.
Always practice

At study
ciriculum

When
working

Task 1.4
Advantages of environment:

I will try to learn to cultivate knowledge is lacking, try to work in a

company training in information technology.
I have done my project in University with testing report, I have done
my document of testing too.
Learn from people who have done their large project, large project will
give me more experiences.
Disadvantages of environment:

No work experience
I didnt work or train by a technology company
I have never done a large reality project

Task2

The importance of communication skills

What is communication?
Communication define as the imparting or interchange of thoughts, opinions,
or information by speech, writing, or signs; a document or message
imparting news, views, and information; a sending of messages and orders;
activity by one that changes the behavior of another.
Communications are Critical

Communication is absolutely critical in any organization to become a world

class company. Without communications, it is not about the team (junior,
management , executives).
Management must know how to communicate, create an atmosphere for
staff to communicate, be able to teach communication, and have a
communication plan that is used, works, and is continued with
Real value of communication in an organization
Communication, by far, has a greater impact than any other skill in any
organization. Several realities take place with effective communication
Junior
Management
Executives
Coding time for product Brand identity and
Shorter meetings, more
takes less time;
promise are ensured
productive time, and
Greater effectiveness
and consistently
greater internal
with the mission,
represented to the
efficiencies take place;
vision, and goals;
product;
More successful
Junior commitment
Management of
organizational teams,
increase;
development team is
with clear roles and
Junior understand the
able to speak more
responsibilities;
need for change;
persuasively with
Change Management
Morale improves;
clients because they
understood by the
Problem solving skills
understand what the
leaders in the
improve;
organizational message organization;
is;
Productivity grows; and
Greater relationships
Reduced costs and
between: Management increased efficiencies!
and Junior;

What does all of this mean?

A direct, clear, and legal communication plan works very effectively when
organization leaders and management stand behind this plan through
creation, implementation, and continual follow through. The results and
benefits are greater by far than not having one.

Effective time management

It's important that you develop effective strategies for managing your time
to balance the conflicting demands of time for study, leisure, earning money
and jobhunting. Time management skills are valuable in jobhunting, but also

in many other aspects of life: from revising for examinations to working in a

vacation job.
Keep a to do list
You should have a reminder system to tell you of when you need to do what:
don't try to remember everything in your head as this is a recipe for disaster!
At the simplest level your reminder system could simply be to use your diary
to write down the things you need to do.
Use a time log
One useful way to eliminate wasted time is to use a time log. First you need
to make up a chart for the next seven days divided into half hour intervals
starting at the time you get up and finishing at the time you go to bed. Write
down what you did in each half hour of the day for the next seven days.

Task 3.1

Determine the role of each team member is key to an effective team, each
team must have below elements, In a team individuals have an important
role to success of the group.

Encourager: supports, and praises the efforts of fellow group

members. Demonstrates warmth and provides a positive attitude in
meetings.
Harmonizer: Seeks ways to reduce tension and diffuse a situation by
providing further explanations or using humor.
Compromiser: Offers to change his or her position for the good of the
group. Willing to yield position or meet others half way.
Gatekeeper/Expediter: Regulates the flow of communication. Makes
sure all members have a chance to express themselves by
encouraging the shy and quiet members to contribute their ideas.
Limits those who dominate the conversation and may suggest group
rules or standards that ensure everyone gets a chance to speak up.
Observer/Commentator: Provides feedback to the group about how
it is functioning. Often seen when a group wants to set, evaluate, or
change its standards and processes.
Follower: Accepts what others say and decide even though he or she
has not contributed to the decision or expressed own thoughts. Seen
as a listener not a contributor.

Task 3.2
Group dynamics is A group with a positive dynamic is easy to spot. Team
members trust one another, they work towards a collective decision, and
they hold one another accountable for making things happen. As well as this,
research have found that when a team has a positive dynamic, its members
are nearly twice as creative as an average group.
The term "group dynamics" describes the way in which people in a group
interact with one another. When dynamics are positive, the group works well
together. When dynamics are poor, the group's effectiveness is reduced.
Problems can come from weak leadership, too much deference to authority,

blocking, groupthink and free riding, among others.

Advantage of group dynamics:

Know your team.
Tackle problems quickly with good feedback.
Define roles and responsibilities.
Break down barriers.
Focus on communication.
Pay attention.
Keep in mind that observing how your group interacts is an important part of
your role as a leader. Many of the behaviors that lead to poor dynamics can
be overcome if you catch them early.
Disadvantage of group dynamics

Weak leadership: when a team lacks a strong leader, a more dominant

member of the group can often take charge. This can lead to a lack of
direction, infighting, or a focus on the wrong priorities.
Excessive deference to authority: this can happen when people want to
be seen to agree with a leader, and therefore hold back from
expressing their own opinions.
Blocking: this happens when team members behave in a way that
disrupts the flow of information in the group. People can adopt blocking
roles such as:
Some group members take it easy, and leave their colleagues to do all
the work. Free riders may work hard on their own, but limit their
contributions in group situations; this is known as "social loafing."
Team members' perceptions can also create a negative group dynamic.
Evaluation apprehension happens when people feel that they are being
judged excessively harshly by other group members, and they hold
back their opinions as a result.

Task 4.1
Brainstorming(Mindtool.com)
Brainstorming is a group process that involves the spontaneous contribution
of ideas from all members of the group. This is one of the most widely used
decision making strategies. This tool is used to by teams to identify solutions

to problems. Brainstorming has a tendency to produce old and familiar ideas

so it is important that the facilitator encourage creative thinking.
During brainstorming sessions, people should avoid criticizing or rewarding
ideas. You're trying to open up possibilities and break down incorrect
assumptions about the problem's limits. Judgment and analysis at this stage
stunts idea generation and limit creativity.
When managed well, brainstorming can help you generate radical solutions
to problems. It can also encourage people to commit to solutions, because
they have provided input and played a role in developing them.
The best approach combines individual and group brainstorming. During the
process, there creativity should be encouraged.
Trial and Error(mindtool.com)
Trial and error method is a way of solving problems in which numbers are
different but those are not function. This is an alternative method and users
use it when all other alternatives are not working. When there are available
alternatives, than it is not necessary to use this technique to solve problem.
There are four basic strategies for resolving a particular problem. These are
discussed below:
Understand the problem
In an organization to solve a particular problem one has to understand the
problem first. Understanding means find out the type and depth of problem.
In this stage problem is identified and the type of problem is discovered
Set plan
The next step is to set plan to solve the problem. Planning is deciding what is
to be done. Here planning is done to solve the specific problem. As per it is
identified in previous stage at this stage organization should develop some
tools and techniques to solve the problem. Alternatives should be developed
to solve the problem
Implementation
At this stage those who charged with responsibility will implement the plan
that decided in previous step. As there are several alternatives best
alternatives should be selected to get best possible output in relation to
situation
Evaluation
Evaluation means checking the steps in problem solving stage. After getting
the result it should be find out whether there are any defects or not. If there

are any defect that it should be found out and reason behind this defect
should be determined.
Below is some model to system development:
Task 4.2
Prototype model (http://istqbexamcertification.com/)
Advantages of Prototype model:
-

Customer are actively involved in the development

Since in this methodology a working model of the system is provided,

the users get a better understanding of the system being developed.

Errors can be detected much earlier.

Quicker user feedback is available leading to better solutions.

Missing functionality can be identified easily

Confusing or difficult functions can be identified

Requirements validation, Quick implementation of, incomplete, but

functional, application.

Disadvantages of Prototype model:

-

Leads to implementing and then repairing way of building systems.

Practically, this methodology may increase the complexity of the

system as scope of the system may expand beyond original plans.

Incomplete application may cause application not to be used as the

full system was designed

Incomplete or inadequate problem analysis.

When to use Prototype model:

-

Prototype model should be used when the desired system needs to

have a lot of interaction with the end users.

Typically, online systems, web interfaces have a very high amount of

interaction with end users, are best suited for Prototype model. It
might take a while for a system to be built that allows ease of use and
needs minimal training for the end user.

Prototyping ensures that the end users constantly work with the
system and provide a feedback which is incorporated in the prototype
to result in a useable system. They are excellent for designing good
human computer interface systems.

As an IT professional in a company and have been asked to develop a

business information system for a retail store. I will choose Prototype model
By using this prototype, the client can get an actual feel of the system,
since the interactions with prototype can enable the client to better
understand the requirements of the desired system. Prototyping is an
attractive idea for complicated and large systems for which there is no
manual process or existing system to help determining the requirements.
Following the requirement of the company as the system should provide
different functionality to different users, Some requirements are more
important than the other and your client wants some requirements to be
delivered first. However, some requirements are not clear at the moment.So
when apply prototype model will handle the requirements mentioned above
which will also be improved.
Task 4.3
And can result in unrealistic schedule and budget expectations.
If apply Prototype model for system a retail store would bring efficiency
to company.
Is models for users actively engaged in the development, the update
will be done continually, through which creation of the system of
quality, because most of the functions will be evaluation and feedback
by users.
Repetitive nature of model develpment making it difficult for
management
Not easy to plan and schedule.
Working prototypes may lead management and customers to believe
that the final product is almost ready for delivery.
Prototypes generally lack security, auditing, and other controls, and
data integrity may be difficult to ensure.
Often inefficient and difficult to maintain.
Tendency not to document.
Customers may feel uncomfortable of feedback required for iterative
prototyping.
Schedule can be delayed with business have no experiences.