SentriaTM 2500

Catch. Report. Debug.

"The process of finding and fixing software problems has been hindered by a lack of reliable data on the precise nature of the problems customers encounter in the real world." (Steve Balmer, Microsoft)

ClearJump SentriaTM is a revolutionary system that raises the quality of software, improves the effectiveness of the beta testing process and saves time solving users' problems by providing the missing link between developers, quality assurance, beta testers, technical support and end users.

Sentria Release StudioTM does this by connecting automatically generated problem reports directly to the source code and debugging information of the product release that generated the report. This makes the overall product management process more effective, faster and simpler while providing more information about a problem to everyone involved, especially developers who are tasked with fixing the problems. In essence, Sentria is a unique combination of source control, bug tracking and debugging tools all in one easy to use product.

For the developer, Sentria not only provides a comprehensive view of software problems, more importantly, it presents the problems from the developer's perspective. Sentria doesn't just keep track of problems, it helps to diagnose a problem by pinpointing the exact location down to the line of code in the source file that caused it (a process called post-mortem debugging and tracing).

Full Lifecycle Management

Sentria is the heart of the product lifecycle. From development to in-house and beta testing to post-sales support, the information provided by Sentria Embedded ReporterTM combined with the source management and debugging tools of Sentria Release Studio enables rapid and accurate locating and repair of software faults. See how Sentria fits into each of the following phases of a product:

Don't Get Left Behind

More and more companies today desire this level of accuracy and feedback from their products. In fact, several of Microsoft's products already incorporate crash reporting. In his October 2, 2002 executive e-mail entitled, "Connecting with Customers," Steve Balmer, CEO of Microsoft, described the extraordinary effectiveness of crash reporting:

The process of finding and fixing software problems has been hindered by a lack of reliable data on the precise nature of the problems customers encounter in the real world. . . . [R]arely do customers contact technical support about them; instead, they close the program. Even when customers do call support and we resolve a problem, we often do not glean enough detail to trace its cause or prevent it from recurring.

To give us better feedback, a small team in our Office group built a system that helps us gather real-world data about the causes of customers' problems -- in particular, about crashes. . . . It enables customers to send us an error report, if they choose, whenever anything goes wrong.

With this immensely valuable feedback from our customers, we're now able to prioritize debugging work on our products to achieve the biggest improvement in customers' experience. . . . [E]rror reporting is now also helping us to resolve more problems before new products are released.

Although Windows® XP will send crash report data when an application crashes, that data is only sent to Microsoft, regardless of whose product actually crashed. Yet, implementing a full source management, reporting and debugging system in-house is a time-consuming distraction. With Sentria, this capability becomes a reality with very little effort.