Walkthrough: 

It is a step-by-step presentation by the author of a document in order to gather information and

to establish a common understanding of its content.

It is review of a software work product by colleagues of the producer of the product for the purpose of
identifying defects and improvements.

Inspection: It is a type of peer review that relies on visual examination of documents to detect defects, e.g.
violations of development standards and non-conformance to higher level documentation. The most formal
review technique and therefore always based on a documented procedure. Its purpose is to the identifying
defects and improvements.

But I always believe in remembering anything in my own language. And everyone should do in the same way. If
you will try to remember these definitions, you may not understand properly also you may forget soon.

Get my answer for the Difference below. This will be easy for you to understand terms also :

Walkthrough :-

1.) It's a type of Semi Formal Review.

2.) 2 to 7 People ate attaining it.
3.) Author is Presenter.
4.) Lead by Author only.
5.) Reviewers are not aware of the subject/topic.
6.) Other people are Inspectors or Reviewers.

Inspection :-

1.) It's totally a Formal Review.

2.) 2 to 10 or more People attaining it.
3.) Author is not presenter. Some one else is giving presentation.
4.) Lead by Moderator.
5.) Reviewers are aware & well prepared for the subject/topic.
6.) Other people are Inspectors or Reviewers.
7.) Minute Taker is writing MOM.
8.) Recorder is noting down everything. Like defects, changes, improvements etc.
9.) Moderator's responsibility is to make sure that meeting is successful.
Walkthrough is a Informal meeting. The motto of meeting is defined, but the members will come without any
preparation. The author describes the work product in an informal meeting to his peers or superiors to get
feedback or inform or explain to their work product.where as,
An inspection is formalized than a ‘ walkthrough ‘ – typical with group of people including a moderator,
mediator, reader & a recorder to take notes. The subjects of the inspection is typically a document such a
requirements specifications, or a test plan & two purpose is to find problems and see what is missing, not to fix
anything. The primary purpose of inspection is to detect defects of different stages during a project.

Walkthrough: Method of conducting informal group/individual review is called walkthrough, in which a

designer or programmer leads members of the development team and other interested parties through a
software product, and the participants ask questions and make comments about possible errors, violation of
development standards, and other problems or may suggest improvement on the article, walkthrough can be
pre planned or can be conducted at need basis and generally people working on the work product are involved
in the walkthrough process.
The Purpose of walkthrough is to:
· Find problems
· Discuss alternative solutions
· Focusing on demonstrating how work product meets all requirements.IEEE 1028 recommends
three specialist roles in a walkthrough:

Leader: who conducts the walkthrough, handles administrative tasks, and ensures orderly conduct (and who is
often the Author)
Recorder: who notes all anomalies (potential defects), decisions, and action items identified during the
walkthrough meeting, normally generate minutes of meeting at the end of walkthrough session.
Author: who presents the software product in step-by-step manner at the walk-through meeting, and is
probably responsible for completing most action items.
Walkthrough Process: Author describes the artifact to be reviewed to reviewers during the meeting. Reviewers
present comments, possible defects, and improvement suggestions to the author. Recorder records all defect,
suggestion during walkthrough meeting. Based on reviewer comments, author performs any necessary rework
of the work product if required. Recorder prepares minutes of meeting and sends the relevant stakeholders and
leader is normally to monitor overall walkthrough meeting activities as per the defined company process or
responsibilities for conducting the reviews, generally performs monitoring activities, commitment against
action items etc.
Inspection: An inspection is a formal, rigorous, in-depth group review designed to identify problems as close to
their point of origin as possible., Inspection is a recognized industry best practice to improve the quality of a
product and to improve productivity, Inspections is a formal review and generally need is predefined at the
start of the product planning, The objectives of the inspection process are to
· Find problems at the earliest possible point in the software development process
· Verify that the work product meets its requirement
· Ensure that work product has been presented according to predefined standards
· Provide data on product quality and process effectiveness
· Inspection advantages are to build technical knowledge and skill among team members by reviewing the
output of other people
· Increase the effectiveness of software testing.
IEEE 1028 recommends three following roles in an Inspection:

Inspector Leader: The inspection leader shall be responsible for administrative tasks pertaining to the
inspection, shall be responsible for planning and preparation, shall ensure that the inspection is conducted in
an orderly manner and meets its objectives, should be responsible for collecting inspection data

Recorder: The recorder should record inspection data required for process analysis. The inspection leader may
be the recorder.

Reader: The reader shall lead the inspection team through the software product in a comprehensive and
logical fashion, interpreting sections of the work product and highlighting important aspects

Author: The author shall be responsible for the software product meeting its inspection entry criteria, for
contributing to the inspection based on special understanding of the software product, and for performing any
rework required to make the software product meet its inspection exit criteria.

Inspector: Inspectors shall identify and describe anomalies in the software product. Inspectors shall be chosen
to represent different viewpoints at the meeting (for example, sponsor, requirements, design, code, safety,
test, independent test, project management, quality management, and hardware engineering). Only those
viewpoints pertinent to the inspection of the product should be present. Some inspectors should be assigned
specific review topics to ensure effective coverage. For example, one inspector may focus on conformance
with a specific standard or standards, another on syntax, and another for overall coherence. These roles should
be assigned by the inspection leader when planning the inspection.
All participants in the review are inspectors. The author shall not act as inspection leader and should not act as
reader or recorder. Other roles may be shared among the team members. Individual participants may act in
more than one role. Individuals holding management positions over any member of the inspection team shall
not participate in the inspection

Inspection Process: Following are review phases:

· Planning
· Overview
· Preparation
· Examination meeting

Planning:
· Inspection Leader perform following task in planning phase
· Determine which work products need to be inspected
· Determine if a work product that needs to be inspected is ready to be inspected
 · Identify the inspection team
· Determine if an overview meeting is needed.

The moderator ensures that all inspection team members have had inspection process training. The moderator
obtains a commitment from each team member to participate. This commitment means the person agrees to
spend the time required to perform his or her assigned role on the team. Identify the review materials required
for the inspection, and distribute materials to relevant stake holders

Overview: Purpose of the overview meeting is to educate inspectors; meeting is lead by Inspector lead and is
presented by author, overview is presented for the inspection, this meeting normally acts as optional meeting,
purpose to sync the entire participant and the area to be inspected.
Preparation: Objective of the preparation phase is to prepare for the inspection meeting by critically reviewing
the review materials and the work product, participant drill down on the document distributed by the lead
inspector and identify the defect before the meeting
Examination meeting: The objective of the inspection meeting is to identify final defect list in the work
product being inspected, based on the initial list of defects prepared by the inspectors [identified at
preparation phase and the new one found during the inspection meeting. The Lead Auditor opens the meeting
and describes the review objectives and area to be inspected. Identify that all participants are well familiar
with the content material, Reader reads the meeting material and inspector finds out any inconsistence,
possible defects, and improvement suggestions to the author. Recorder records all the discussion during the
inspection meeting, and mark actions against the relevant stake holders. Lead Inspector may take decision that
if there is need of follow up meeting. Author updates the relevant document if required on the basis of the
inspection meeting discussion

Rework and Follow-up: Objective is to ensure that corrective action has been taken to correct problems found
during an inspection.

Inspection is more formal meeting than walkthrough with 3-8 people which includes moderator, reader,
recorder etc. Documents like FRS, SRS, and Test plan are discussed here. Main aim of this meeting is just to
find what is missing not to fix any things
Walk through is an informal meeting for evaluation. No preparation is required
Inspection is a methog that deserves careful consideration by an organizatin concerned with the quality of the
product. It is conducted by quality control members.

3 What Is Risk With Respect To Information Systems?

Risk is the potential harm that may arise from some current process or from some future event. Risk is present in
every aspect of our lives and many different disciplines focus on risk as it applies to them. From the IT security
perspective, risk management is the process of understanding and responding to factors that may lead to a failure in
the confidentiality, integrity or availability of an information system. IT security risk is the harm to a process or the
related information resulting from some purposeful or accidental event that negatively impacts the process or the
related information. Risk is a function of the likelihood of a given threat-source’s exercising a particular potential
vulnerability, and the resulting impact of that adverse event on the organization.
3.1 Threats
One of the most widely used definitions of threat and threat-source can be found in the National Institute of Standards
and Technology’s (NIST) Special Publication (SP) 800-30, Risk Management Guide for Information Technology
Systems. NIST SP 800-30 provides the following definitions.
Threat: The potential for a threat source to exercise (accidentally trigger or intentionally exploit) a specific
vulnerability.
ii
Threat-Source: Either (1) intent and method targeted at the intentional exploitation of a vulnerability or (2) a
situation and method that may accidentally trigger a vulnerability.
iii

The threat is merely the potential for the exercise of a particular vulnerability. Threats in themselves are not actions.
Threats must be coupled with threat-sources to become dangerous. This is an important distinction when assessing
and managing risks, since each threat-source may be associated with a different likelihood, which, as will be
demonstrated, affects risk assessment and risk management. It is often expedient to incorporate threat

Examine your own skill set for business ideas.

Do you have a talent or proven track record that could become the basis of a profitable business?

The other day I spoke to a man who had spent years managing cleaning services at a hospital. Today he runs his own successful domestic and
business cleaning service. An ex-logger I know is now making his living as an artist; he creates "chainsaw sculptures" out of wood. And the
examples of professionals who have started their own agencies or consulting service businesses are legion.

To find a viable business idea, ask yourself, "What have I done? What can I do? Will people be willing to pay for my products or services?"

2) Keep up with current events and be ready to take advantage of business opportunities.

If you read or watch the news regularly with the conscious intent of finding business ideas, you'll be amazed at how many business opportunities
your brain generates. Keeping up with current events will help you identify market trends, new fads, industry news - and sometimes just new ideas
that have business possibilities.

For instance, same-sex marriages are now legal in Canada. There are now also entrepreneurs who are selling tourist travel packages that include a
marriage ceremony to same-sex couples from other countries. Would you have identified that business opportunity when you heard that the Canadian
marriage laws had changed?

3) Invent a new product or service.

Think back 30 years ago. Was there a huge demand for anti-virus software, Internet Service Providers, or desktop computers? No! The key to coming
up with business ideas for a new product or service is to identify a market need that's not being met. The clamor for ever-increasing security, for
instance, has led to an explosion of new security products and services, ranging from iris-recognition machines through home security services.

Look around and ask yourself, "How could this situation be improved?" Ask people about additional services that they'd like to see. Focus on a
particular target market and brainstorm business ideas for services that that group would be interested in. For example, there are millions of aging
gardeners across North America. What products or services could you create that would enable them to garden longer and more easily?

4) Add value to an existing product.

The difference between raw wood and finished lumber is a good example of putting a product through an additional process which increases its
value, but additional processes are not the only way value can be added. You might also add services, or combine the product with other products.
For instance, a local farm which sells produce also offers a vegetable delivery service; for a fee, consumers can have a box of fresh vegetables
delivered to their door each week. What business ideas can you develop along these lines? Focus on what products you might buy and what you 5)
Investigate other markets.

Some business ideas aren't suited to local consumption - but appeal greatly to a foreign market. My own little town is surrounded by acres of wild
blueberries. For years the bushes produced berries that mainly fed bears and birds; B.C. has a thriving blueberry industry that doesn't leave room for a
wild blueberry market. But one entrepreneur realized that there is a high demand for products such as these in Japan - and those same wild
blueberries are now being harvested and shipped. Finding out about other cultures and investigating other market opportunities is an excellent way to
find business ideas.

6) Improve an existing product or service.

You know what they say about the person who builds a better mousetrap. That person could be you! A local entrepreneur has created an improved
version of the hula hoop; it's bigger and heavier so hula-hoopers can control it more easily and do more tricks. How did she come up with this
business idea? She thought hula hooping would be a fun thing to do with her daughter, but found the commercially available product too flimsy.

There are very few products (or services) that can't be improved. Start generating business ideas by looking at the products and services you use and
brainstorming ideas as to how they could be better.

7) Get on the bandwagon.

Sometimes markets surge for no apparent reason; masses of people suddenly "want" something, and the resulting demand can't be immediately met.
For example, during the SARS epidemic, there was an insatiable demand for facial masks in several countries - and many entrepreneurs capitalized
on this business idea.

A "bandwagon effect" is also created by larger social trends. There is much more of a demand for home-care services for the elderly than is currently
being supplied. And the trend for pets to be treated as family members continues, creating demand for all kinds of pet-related services that didn't exist
even ten years ago.

Look at existing businesses and the products and services they offer and determine if there's a need for more of those products or services. If there is,
develop business ideas to fit the market gap.
might do to them or with them to create a profitable business. sources into threats