Free Webinars

Before you can effectively: • Elicit/analyze/validate requirements information • Define/implement/improve your processes • Plan/track and control/execute your project you must identify and involve your relevant stakeholders. Identifying a complete list of product, process and/or project stakeholders keeps requirements from being missed, and provides access to a broader experience base and more extensive domain knowledge. This webinar demonstrates how to identify a more complete list of stakeholders. The presentation also discusses determining your key stakeholders and defining a stakeholder participation strategy for each of those key stakeholders. Click hare to view webinar recording.

Webinar Abstract:  If software requirements are not right, stakeholders will not end up with the software they need. This webinar will discuss:
• What: The various levels and types of requirements that need to be defined
• Why: The benefits of having the right software requirements
• Who: The stakeholders of the software requirements and getting them involved in the process
• When: Requirements activities throughout the software development life cycle
• How: Techniques for eliciting, analyzing, specifying, and validating software requirements

Extensive cost overruns are common and often associated with optimistic expectations about achievable program scope and technology that can be delivered on schedule and within budget. The problem is exacerbated by the fact that the estimates at the beginning of a program incorporate a great deal of uncertainty about large-scale, unprecedented systems that take years to develop and deploy. Needed capabilities and yet-to-be-developed technical solutions are not yet well understood. Early estimates, by necessity, rely heavily on expert judgment. Many assumptions about the desired end product are made in calculating the estimates. The estimation process does not capture information about program change factors that can dramatically influence cost over the lifecycle of program research, development, production, deployment and sustainment.

In this presentation we describe a new, integrative approach we call QUELCE (Quantifying Uncertainty in Early Lifecycle Cost Estimation). QUELCE synthesizes scenario building, Bayesian Belief Network (BBN) modeling and Monte Carlo simulation into an estimation method that quantifies uncertainties, allows subjective inputs, visually depicts influential relationships among change drivers and outputs, and assists with the explicit description and documentation underlying an estimate. We use scenario analysis and design structure matrix (DSM) techniques to limit the combinatorial effects of multiple interacting program change drivers to make modeling and analysis more tractable. Representing scenarios as BBNs enables sensitivity analysis, exploration of alternatives, and quantification of uncertainty. The BBNs and Monte Carlo simulation are then used to predict variability of what become the inputs to existing, commercially available methods and tools in use by cost estimators. As a result, interim and final cost estimates are embedded within clearly defined confidence intervals.

QUELCE aims to provide credible and accurate program cost estimates within clearly defined, statistically valid confidence intervals. By making visible the potential changes that may occur during program execution, our approach also supports quick revision of program estimates to mitigate risk and respond more quickly to the changes that often arise over a program’s lifecycle. The same flexibility enables early consideration of the likely impact of different possible future scenarios on the estimates. Intuitive visual representations of the data explicitly model influential relationships and interdependencies among the drivers on which the ultimate estimates depend. Assumptions and constraints underlying the estimates that may not otherwise have been considered are well documented, which contributes to better management of cost, schedule, and adjustments to program scope as more is learned and conditions change. Documenting the basis of an estimate also facilitates updating the estimate during program execution and helps others make informed judgments about estimation accuracy.

Webinar Abstract:  Use cases are an easy and effective technique for defining user-level requirements.  Through the addition of more detail to the use cases, they can also be used to define the product level requirements and even the design of the product.  This presentation defines an eight-step process for creating and documenting effective use cases.  A real world example is utilized throughout this presentation to illustrate each of the eight steps in an interactive exercise with the attendees. Topics covered during this webinar include:

  • Step 1: Define the System Boundaries
  • Step 2: Identify the Actors
  • Step 3: Identify Interactions
  • Step 4: Establish Pre and Post Conditions
  • Step 5: Document the Main Success Scenario
  • Step 6: Branch to Alternatives and Exceptions
  • Step 7: Merge or create sub-use cases as appropriate
  • Step 8: Record additional information

 

Webinar Abstract:  Peer reviews include a variety of review techniques, ranging from walkthroughs to inspections. Submitting ones work to a review by ones peers is a fundamental part of the scientific method that has evolved into a wide-ranging set of tools used to identify and remove defects efficiently and to prevent defects by building the knowledge of the team. While there are debates about the best way to run a peer review, there is a consensus that peer reviews are powerful tools for building high-quality software. In this webinar we will discuss a variety of peer review techniques, what distinguishes them, what their advantages and drawbacks are, and what results you should expect from implementing them. If your objective is to leverage quality to achieve lower cost, shorter release cycles, or greater customer satisfaction, then peer reviews should be among the tools in your kit. Consistently and correctly implemented peer reviews add business value to software projects.
 

Webinar Presenter:  Dr. Mark Paulk teaches software engineering at the University of Texas at Dallas and is a consultant and author in software engineering, software process improvement, high maturity practices, agile methods, and statistical thinking.

Dr. Paulk was a Senior Systems Scientist at the Institute for Software Research at Carnegie Mellon University from 2002 to 2012. From 1987 to 2002, Dr. Paulk was with the Software Engineering Institute at Carnegie Mellon, where he led the work on the Capability Maturity Model for Software.  He was co-project editor of ISO/IEC 15504-2 (Software Process Assessment: Baseline Practices Guide) and a contributor to ISO and IEEE standards. He is a co-author of the eSourcing Capability Model for Service Providers.  You can contact Dr. Paulk at Mark.Paulk@ieee.org or visit his website at http://mark.paulk123.com/

This is the recording of the 12 Step to Useful Software Metrics webinar repeated on 01/18/2013. 

This webinar introduces the attendee to a practical process for establishing and tailoring a software metrics program that focuses on goals and information needs. The process provides a practical, systematic, start-to-finish method of selecting, designing and implementing software metrics. It outlines a cookbook method that attendees can use to simplify the journey from software metrics in concept to delivered information.

Supporting paper/resources:

 

This webinar introduces the attendee to a practical process for establishing and tailoring a software metrics program that focuses on goals and information needs. The process provides a practical, systematic, start-to-finish method of selecting, designing and implementing software metrics. It outlines a cookbook method that attendees can use to simplify the journey from software metrics in concept to delivered information.

Attendees learn how to identify their software metrics customers and utilize the Goal/Question/Metric paradigm to select metrics that align with the organizational, project and process goals of those customers. The steps to designing metrics are discussed including:

• Standardizing entity and attribute definitions
• Choosing measurement functions
• Establishing measurement methods
• Defining decision criteria
• Designing reporting mechanisms
• Determining additional qualifiers

Issues involved with data collection are covered, including what data to collect, who should collect the data and how to collect it. Attendees learn to consider the human issues of implementing a measurement system and metric do’s and don’ts.

Supporting paper/resources:

There is a dichotomy in software configuration management.  On one side, individual developers need the flexibility necessary to do creative work, to modify code to try out what-if scenarios, and to make mistakes, learn from them and evolve better software solutions.  On the other side, teams need stability to allow code to be shared with confidence, to create builds and perform testing in a consistent environment, and to ship high-quality products with confidence.  This requires an intricate balance to be maintained.  Too much flexibility can result in problems including, unauthorized and/or unwanted changes, the inability to integrate software components, uncertainty about what needs to be tested and working programs that suddenly stop working.  On the other hand, enforcing too much stability can result in costly bureaucratic overhead, delays in delivery, and may even require developers to ignore the process in order to get their work done.

This webinar explores risk-based software configuration control.  It also examines techniques that can be used to help maintain this necessary balance between flexibility and stability, as software moves through the life cycle.  These techniques include:

    Selecting the appropriate type and level of control for each software artifact

    Selecting the right acquisition point for each configuration item

    Utilizing multiple-levels of formal control authority

There are many risks involved in creating high quality software on time and within budget.  With ever-increasing software complexity and increasing demand for bigger, better, and faster product, the software industry is a high-risk business.  When teams don't manage risk, they leave projects vulnerable to factors that can cause major rework, major cost or schedule over-runs, or complete project failure.  Adopting software risk management processes is a step the can help effectively manage software development and maintenance initiatives.  However, in order for it to be worthwhile to take on these risks, the organization must be compensated with a perceived reward.  The greater the risk, the greater the reward must be to make it worthwhile to take the chance.  In software development, the possibility of reward is high, but so is the potential for disaster.  Risk exists whether it is acknowledged or not.  People can stick their heads in the sand and ignore the risks but this can lead to unpleasant surprises when some of those risks turn into actual problems.  The need for software risk management is illustrated in Gilb’s risk principle.  “If you don’t actively attack the risks, they will actively attack you" [Gilb-88].  In order to successfully manage a software project and reap the rewards, software practitioners must learn to identify, analyze, and control these risks.  This webinar focuses on the basic concepts, processes, and techniques of software risk management.

(NOTE:  Because of a technical problem with this recording -- please skip the first 2minutes and 40 seconds of this recording)

If you are taking the next offering of the ASQ Certified Software Quality Engineer (CSQE) exam or are considering taking the CSQE exam in the future, this useful webinar can provide you with advice on how to prepare for the exam and tips for taking the exam.  It also covers what to bring and not to bring to the exam.  The types of questions on the exam are reviewed with examples and pointers to practice exam questions are provided.  CSQE Recertification is also discussed.

listen to this informative webinar from the lady who "wrote the book" literally.  Linda Westfall is the author of "The Certified Software Quality Engineering Handbook" available from ASQ Quality Press.  .

© 1999-2017 Westfall Team, Inc.