iist@softdim.com
http://www.softdim.com/iist
Phone: 651 306 1387
FAX: 651 552 0791
Testing Internet and Web Applications
This session provides a quick start in what developers, testers and users
need to know
about testing software designed for use on the Internet, intranets and
extranets. The
testing process covered in this course can be used from testing simple web
pages to major
e-commerce and database applications.
Testing Client/Server Applications: A Risk-Based Approach
This course presents a practical "how to" approach for
testing client/server systems based on risk factors that have been
identified in
client/server projects. The course starts out by discussing the basics of
testing to
establish a common terminology and then proceeds to describe the risk-based
planning
process for client/server testing. Test planning and automated test tools
for client/server testing are discussed.
Team-based exercises reinforce the concepts of building a client/server test
strategy and performing a risk
assessment.
Test planning and automated test tools for client/server testing are discussed.
Team-based exercises reinforce the concepts of building a client/server test strategy and performing a risk assessment
Testing Object-Oriented Systems
This course is a must for test professionals who are charged with the
responsibility
of testing object-oriented. It offers clear understanding of what the
object technology
really is and how it impacts software testing. New techniques for testing
object oriented
systems are discussed.
In this course, you will learn: 1) A complete understanding of the object-oriented technology. 2) Learn the difference between object-oriented methods and structured methods. 3) Learn how the object-oriented technology impacts software quality. 4) Learn how testing object-oriented systems is different. 5) Learn effective techniques for testing object-oriented systems
Structured User Acceptance Testing
This course is designed for users, testers and developers who want to
learn how to test computer systems from the business or operational
perspective. This
testing approach is valuable for testing the changes required for the Year
2000.
The techniques presented are of a structural nature and the class exercises
take the
participants completely through the process of structured user acceptance
testing.
In addition to the process of acceptance testing, interpersonal issues are
discussed.
The workshop contains three team-based exercises which focus on
having the participants write a test strategy, define test scenarios based
on business
processes and define business test cases.
Becoming an Effective Test Team Leader
This two-day session is designed for test leaders and test managers, people
who expect
to be in a test leadership role, or people who lead other test managers and
test leaders.
The main objective of this session is to teach you how to be the very best
test manager
and leader. This course also answers the question, "What does it mean
to be the
best?" There are many people functioning as test managers, but how many
are really
leading the team? In leading a test team, you must not only understand the
basics of
software testing, but you must also understand your own organizational
culture. Team-based
exercises reinforce the concepts of facilitating team activities and
performing leadership
activities.
Software Test Planning and Design
This course is essential to every software professional involved
in software testing: Programmers interested in performing effective unit
testing,
development or test managers struggling to gain a better control over the
different test
activities and the quality of the software product, test engineers and test
analysts
interested in performing effective planning, designing, and monitoring all
test
activities. This course addresses both black-box and white-box test case
design
techniques, how to write a complete test plan and a complete test design
specification.
Software Risk Management Techniques
This course presents risk management methods that are different from
conventional
methods. It is based on the original work and 40 years practical experience
of the
instructor.
In this course, you will learn how to: 1) Identify even subtle risks. 2) Document risks permanently so they are not forgotten. 3) Evaluate the severity of risks. 4) Reduce risks once identified. 5) Reduce the ‘worst case’ by early frequent feedback. 6) Reduce risks by improving project management and software engineering processes. 7) Control risks that creep up during projects. 8) Keep risks under control even with relatively inexperienced staff. 9) Set management policy regarding risks. 10) Get out of project "jams". 11) Build a culture where everyone at every stage is risk conscious. 12) Motivate people to care about risks to project success
Practical Techniques for Software Quality Assurance
The software quality assurance function has been misunderstood by many
organizations.
This course is intended for every software quality professional looking for
practical
techniques and approaches to achieve software quality. It will provide
practical advice to
help organizations establish a quality assurance function. Although this
course does not
exclude testing as an effective means to controlling the quality of
software, it will
discuss many other approaches that can achieve much higher levels of quality
with less
resources. The course will focus on building quality into software rather
than just
controlling quality at the end.
Software Requirements Exploration and Definition
Experience shows that up to 80% of the maintenance effort is spent to fix
problems from
requirements errors. Although functional requirements seem to be the most
important to
the user, most software disasters result from poor quality software. Quality
requirements
are the least understood requirements by both customers and developers.
Although never
talked about, quality requirements seem to be an assumed customer
expectation.
Well-understood, well-defined and managed requirements are the basis for
effective testing
of the software system. Tracing requirements to other software and testware
components is
crucial to the gaining control over the development process.
In this course you will learn: 1) How to use effective techniques to explore and define system requirements. 2) How to refine requirements for both achievability and testability. 3) How to address both functional and quality requirements with different user groups. 4) How to maintain a robust requirement database throughout the development and maintenance phases. 5) How to systematically convert quality requirements to implementation actions.
Improving Software Quality with Inspections and Reviews
Software inspections have proved to be very effective in
capturing more defects early enough to avoid the cost of rework. Also, many
types of
defects can only be found by inspection. Yet, many organizations are
struggling to make
the inspection process effective and to achieve the real benefits of
inspections. This
course will examine the different elements that make an effective inspection
process and
help you establish a process which is customized for your organization. This
course is a
must for all software persons involved in the software development and
maintenance process
including managers of all levels.
In this course, you will learn: 1) What the real benefits of inspections are. 2) How to achieve the most value of your inspection effort. 3) The different factors affecting the inspection process. 4) The different forms of inspection and when to use each of them. 5) How to establish different process variations to fit different environment. 6) How to effectively monitor your inspection process to improve its effectiveness. 7) Most importantly, learn from instructor’s real experience with inspections.
Software Project Management: An Evolutionary Approach
The Evolutionary ("Evo") Project Management Method has proved to be the most
successful software project management method. It was used in the IBM
"Cleanroom" method and is a de facto DoD and IEEE standard and is used by
both HP and Microsoft. This course will make you aware of a powerful proven
method for getting control of projects through feedback and adjustment to
reality, rather than by guessing at unknowable factors in advance. This
method can also be used to restructure existing delayed projects and get
them delivered earlier than otherwise possible.
In this course, you will learn: 1) A systematic method for planning any project, which focuses on the customer end results, rather than technical. 2) Construction details. 3) How to quantify and specify the critical benefits and qualities of your project. 4) 18 specific tactics for how to decompose large project phases into smaller doable steps. 5) How to make use of the early implementation experience facts to adjust your project for desired success criteria. 6) How to prioritize some steps and calculate residual priority based on actual progress towards requirements.
Software Project Management: Essential Practices
"If you don’t know where you are going, any road will do",
and "If
you don’t know where you are, a map won’t help". It is of
critical
importance to develop a well defined plan based upon a structured planning
process before
beginning any software development effort. It is of equal importance to
incorporate the
use of that plan along with basic software project assessment and control
practices during
the development of the project. Essential Software Project Management
Practices
emphasizes the techniques, activities, and tools necessary to successfully
manage the
software process, i.e. the techniques activities and tools to develop a well
defined plan
(understand where you are going), to assess status (knowing where you are)
and to
institute corrective measures (getting you back on course).
In this course, you will learn: 1) An understanding of the major planning
activities. 2) What is a Work Breakdown Structure and how does it become the
basis for the project schedule. 3) Macro and Detailed Effort and Duration
Estimation. 4) What constitutes a Project Management Plan. 5) How to Manage
and Control Requirements. 6) How to Monitor Cost and Schedule using Earned
Value. 7) Critical Path Method. 8) What are the basic elements of Risk
Management. 9) Understand the need to assess the current process of
software development to establish plans to improve that process. 10) Tools
that support the project management process
Entry added February 22, 1999.
Return to Listings