Early Bug Detection for Software Analysis and Design

For large software development projects, the most important decisions and the most expensive mistakes are made at the beginning of the project. At the same time, the initial amount of quality control is minimal and then grows as development moves forward. This results in costly rework (often hidden) at the late stages of the project.

Attend this tutorial to learn how to reduce delays between bug insertions and bug fixes and distribute the quality control activities over the entire project almost proportionally to the importance of (possible) errors. You will learn practical techniques to discover and fix critical analysis and design mistakes virtually immediately - when introduced - not in the late phases where they are the most expensive to resolve.

Participants must have at least one year experience of using UML for analysis and design. Three hours of the tutorial will be organized as a “speechless” design session: participants will be required to collaborate and produce a UML design model without speaking regular languages, as the use of English, Spanish, etc. (both spoken and written) will be forbidden. Only UML will be used for communication. You should not attend this tutorial if you have any condition that could prevent you from participating in the speechless exercise.

Bio

Vladimir L Pavlov is the chairman and chief strategy officer of the International Software and Productivity Engineering Institute (INTSPEI). He founded INTSPEI (www.intspei.com) to launch new software development methodologies resulting from his experiments and research. A leading expert in software development, Vladimir has previously served as director and/or CTO for top high-tech companies, including Intel and Microsoft, in the US, Ukraine, Russia, and Poland. A frequent speaker at scientific and industrial conferences, he has authored major publications on computer science and software engineering. For more information about the International Software and Productivity Engineering Institute, visit www.intspei.com . For more information about Vladimir L Pavlov, visit www.vlpavlov.com

Goal

You will learn practical techniques to discover and fix critical analysis and design mistakes virtually immediately - when introduced - not in the late phases where they are the most expensive to resolve. You will learn how to fine-tune the development process in the company and make it really effective.

Audience

Analysts, architects, leading software developers, project managers and similar engineering roles who are motivated to shorten the development time and improve software quality. Participants must have at least one year experience of using UML for analysis and design. Participants will have to pass the qualification test to be accepted for the tutorial. The test is usually contacted by email within 2 weeks before the tutorial.

Program

  1. What problem we solve? – For large software development projects, the most important decisions and the most expensive mistakes are made at the beginning of the project. At the same time, the initial amount of quality control is minimal and then grows as development moves forward. This results in costly rework (often hidden) in the late stages of the project.
  2. What methods of early bug detection do exist today? – Review of architectural bug detection approaches and methods of software design verification.
  3. How to avoid architectural mistakes in processes based on popular methodologies: RUP, MSF, OpenUP, XP, etc.? – Participants will learn principles, methods and techniques that allow to prevent architecture mistake in the most popular SDLCs
  4. What is reverse semantic traceability? – Review the key bug prevention technique – reverse semantic traceability method - which allows significantly improve quality of your software products and project documentation
  5. How to incorporate reverse semantic traceability into your process? – 5. How to incorporate reverse semantic traceability into your process? – Practical assignments and case-studies will help participants to learn how to implement the reverse semantic traceability method in their companies to avoid information loss in project artifacts.
  6. How to maximize ROI of your process reengineering? – Participants will learn how to identify processes bottle-necks, how to prioritize them and how to decide which of the identified bottle-necks should be covered by additional quality assurance techniques.
  7. How to fine-tune the SDLC in your company? – Participants will review the most popular reengineering options and learn how to pick the one which suits the best to their particular situations.

Length and format

  1. Tutorial takes two full business days (16 h);
  2. Group size is from 10 to 18 people.
  3. Participants are required to pass email UML test to be accepted to the tutorial.

Prise

14500 roubles.

Participants’ Feedback

Vladimir Pavlov’s tutorial has an unusual format as for educational event. This workshop is not a lecture or a questions-and-answers session, or a discussion (though it includes all of this). The tutorial is an action. During this training participants gain unique experience in UML modeling and requirements analysis; they get a vivid proof of the expressive power of modeling languages and food for further thoughts, experiments, and practice; they gain the experience of using the cutting-age approaches for solving complex architectural tasks. Practically, this tutorial sums up the key techniques you should implement in your company.

This state-of-the-art tutorial stays at the edge of the newest software development methodologies. Vladimir doesn’t teach you in a formal scholastic way. Learning through practical case-studies, participants face the real problems of software process, discover different views to the same issues and find effective solutions to address them.

I would highly recommend this tutorial to analysts, project managers, architects and software developers.

Professor Andrey N. Terekhov,
Head of Software Engineering Department,
Saint-Petersburg State University

The strong conceptual approach, developed by INTSPEI, is supported by tools and techniques which are compatible with IBM Rational Unified Process. A brilliant speaker and tutor, Vladimir Pavlov illustrates the approach with real-life examples. I am very impressed by the workshop and the new INTSPEI method of UML modeling, and highly recommend it to everyone.

Professor Vsevolod Kotlyarov,
Principal Engineer,
Motorola