Cognition Cockpit Connects with MS Visio to Streamline Requirements Analysis and Requirements Management Throughout the Entire Systems Engineering Process

Share Article

Cognition Corporation is capitalizing on the excitement from their new unified model approach to systems engineering and product development with the addition of MS Visio based modeling directly within the unified model. This new functionality further enhances requirements management and requirements analysis by providing a real time method to create system diagrams that automatically generate systems engineering structures in Cognition Cockpit.

Take Control Of Product Development

The speed and ease with which it allocates requirements and establishes traceability is astounding.

Cognition Corporation, a worldwide leader in Web 2.0 Product Development, Systems Engineering, and Requirements Management software, announced today the complete connection of Cognition Cockpit with MS Visio including bi-directional connectivity to all items and data fields. This allows persistent Visio documents to be used to produce formatted, interactive reports and generate structures directly within Cognition Cockpit. Visit the Cognition Cockpit site to learn about the new connection.

Visio is the most popular tool for creating engineering diagrams and models. There are more advanced modeling tools available but these all suffer the same problem: they are specialized, complex tools not viable for daily use by typical engineers. Visio is simple and engineers learn it in school so they are already familiar with its use. It may not have all the complexity and power as the expert tools but Visio has the advantage that, just like Cognition Cockpit, it will be used voluntarily by product development teams as part of their systems engineering process.

The Cognition Cockpit beta test community responded with enthusiastic feedback about the new Visio interface.

From a large defense contractor: " The speed and ease with which it allocates requirements and establishes traceability is astounding."

From a medical device company: "We are now able to produce complex management reports with the click of one button. This feature alone would free up 10-15% capacity to any product team, in regard to the resource drain that now occurs each time management reports are rolled up."

From an automotive supplier: "I finally have a way, all on the web, to use system models to drive my requirements and risk management process across all projects. Just what I have been looking for."

Visio data is connected to Cockpit by creating a series of sections (headings) within a Cockpit document. These sections describe how to translate between Cockpit objects and Visio shapes. They also describe what Cockpit relationships (e.g. hierarchical, sequential, or none) get associated with Visio connectors.

The fundamental section in the Native Visio document is the Visio Shape. It provides the translation between Visio and Cockpit data. It is used to define what data from the Visio shapes (both 1D and 2D) is available within the Cockpit. A shape section is created in the Cockpit document to represent each different type of Visio shape from the drawing to be connected to the Cockpit. Cockpit equivalents are only required for shapes in Visio if data is going to be exchanged with the Cockpit. This means that graphical elements that are not required in the Cockpit do not need to be defined in the native Visio document.

The second type of shape definition is the "Connector". This is used to represent 1D shapes in Visio. Unlike the "Data" shape, the "Connector" shape does not correspond to a specific object type in the Cockpit. Instead, these are used in conjunction with the "Visio Connector" sections to define what Cockpit object relationships (hierarchical or sequential) should be transferred to and from Visio.

Once the Visio shapes (both Data and Connector) exist, the Visio Connector section type is used to define what kind of Cockpit relationships should be synchronized with Visio. Visio Connector sections are not required as part of the link process but without them interconnections between shapes in Visio will not be synchronized with the Cockpit. Each user decides what information is important to them and makes the appropriate connections. Of course, the Web 2.0 environment makes it fast, easy, and fun for each user to configure their pages and models to fit their own needs.

This exciting new functionality has been created within the standard Cognition Cockpit application and, other than Visio, requires no additional software and no additional costs. We look forward to your feedback and first impressions about the new Visio integration.

The new version of Cognition Cockpit supporting Visio integration is now shipping to customers under current maintenance.

Watch (with sound) the Executive Overview of Cognition Cockpit Web 2.0 software.


Share article on social media or email:

View article via:

Pdf Print

Contact Author

David M Cronin
Visit website