Upcoming Webinars
Architectural Compliance in a DevOps Pipeline
Featuring Verifa
November 15th, 2018 at 12:00 pm EST
Verifa, a recognized leader in DevOps and Continuous Integration, focuses on continuous improvement and software quality across the entire software development lifecycle. Verifa has developed a unique DevOps pipeline that enables customers to shorten the build-test-debug lifecycle and automate many manual compliance, testing, security and quality related workflows.
Neil Langmead, CEO and President of Verifa, will discuss the challenges encountered when helping companies undergo digitization. Digitization means a significant expansion in the amount of software that is written and included in the products.
This webinar will cover:
• Quickly identifying critical defects due to architectural misuse
• Providing automated, continuous architectural compliance and verification
• Using software architecture to optimize testing
• Reducing build times with modularization (Smart Build)
• Securing your API’s using architectural data and dependency analysis
If you would like to register for this webinar, please click here
Recent Webinars
Reengineering Legacy Code to Reduce Technical Debt
This webinar will show you techniques on how to extract the design knowledge that is built into your legacy code. It will also provide suggestions on how you can make intelligent choices about when to refactor and when to rebuild.
• Make intelligent choices about when to refactor and when to rebuild
• Identify key components for reuse
• Make your code more modular through dependency management
• Implement architectural rules to prevent code erosion
If you would like to watch this webinar, please click here.
Continuous Integration with Lattix
This demonstration of Lattix Architect illustrates how the tool suite can be integrated into your build environment to improve the agility of your team. In this webinar you will learn how software architecture is the key to quality. You will see how to:
• Integrate with Hudson, Jenkins, and other environments.
• Identify and prevent architectural erosion as soon as it occurs.
• Maintain integrity of design and make architectural evolution explicit.
• Determine the changes and the impact of those changes across builds.
• Track and maintain architectural metrics
How to Maintain Quality by Preventing the Erosion of Software Architecture
One of the best ways to maintain the quality of code is to ensure that developers, managers and other stakeholders have a clear understanding of the software architecture. Unfortunately, nearly all software systems experience erosion of architecture over time as new features are added and developers change over time. If your team does not have a firm grasp of the intended architecture, not only will they continue to waste valuable development time but your code will erode.
• How to discover and visualize the architecture of the most complex software system
• How to improve modularity by removing unwanted dependencies
• How to enforce rules to prevent architectural erosion
• Why building a collaborative development tools environment is crucial to sustaining a stable codebase
The following topics are also available. You may register to be notified of when a specific session will next be offered by contacting us at sales@lattix.com. Upcoming sessions will also be announced via Twitter. Follow us at https://twitter.com/LattixDSM.
How Can I Control the Dependenices in My Software System to Reduce Risk?
Dependency Structure Matrix (DSM) is a technology that is used to visualize complex relationships and dependencies. For software it means that even when you have a system with 1000 files or 10,000 objects, you can get a grip of it within a few minutes. It means that you can quickly spot unwanted dependencies, code that needs refactoring or the impact on testing when a someone propose a change.
Join us for a live demonstration of how DSMs can help you minimize the risk in your project. we will show you how you can:
- discover your architecture even if it has deviated significantly from the original intent
- identify short-term opportunities to break couplings and improve the architecture by changing the code organization
- use just a few rules to prevent further erosion of the architecture
- determine the changes and the impact of those changes across builds
- measure, report, and track architectural metrics
Attendees will not need any previous knowledge of Lattix or DSM since we will be covering the basic concepts and use cases.
Continuous Integration with Lattix
Join us for a live demonstration of Lattix and learn how it can be integrated into your build environment to improve the agility of your team. You will learn how to:
- Integrate with continuous integration build environments such as Hudson, Jenkins, and others.
- Use Lattix to identify and prevent architectural erosion as soon as it occurs.
- Maintain the integrity of your design and make architectural evolution explicit.
- Determine the changes and the impact of those changes across builds.
- Track and maintain architectural metrics.
* Hudson and Jenkins logos are the property of their respective owners
Trying the Lattix Approach: How Should I Analyze My System?
To get the most from your Lattix evaluation or purchase, you should know a few basic techniques about the use of Lattix Architect and the DSM approach. Let us give you the benefit of our expertise and experience in assisting many Lattix customers to analyze their systems.
During this technical demonstration by Lattix founder Neeraj Sangal, you will learn how to:
- discover your architecture even if it has deviated significantly from the original intent
- identify short-term opportunities to break couplings and improve the architecture by changing the code organization
- use just a few rules to prevent further erosion of the architecture
Attendees will not need any previous knowledge of Lattix or DSM since we will be covering the basic concepts and use cases.
Architectural Analysis and Refactoring with Lattix
Lattix provides powerful capabilities to support a wide range of analysis and refactoring activities. Join us as we demonstrate the techniques and features necessary to quickly accomplish your reverse engineering and refactoring initiatives. During this live demonstration with Lattix LDM, you will learn how to:
- create a precise blueprint of your system by utilizing a Dependency Structure Matrix (DSM) of system interdependencies and identify issues
- utilize Lattix's architectural editing capabilities, apply DSM partitioning algorithms and explore "what-if" scenarios to create new logical groupings for layers and modules
- use reporting, tagging and impact analysis to extract components, services, and APIs
We will wrap up the session by showing the results of our analysis of the popular browsers, Firefox and Google Chrome, utilizing the new Klocwork integration with Lattix
Lattix for Rhapsody
The Lattix for Rhapsody module, a direct integration with IBM Rational’s Rhapsody. Join us for a live demonstration which will show how to use this new module to review, refactor and maintain architecture in large scale Rhapsody models. With Lattix for Rhapsody, a designer can readily identify undesirable interdependencies in the model which prevent modularity and increase complexity. As the model changes, Lattix for Rhapsody can be used to enforce the architecture and expose key design decisions for the entire team.
Advanced Techniques and Tips
To get the most of your Lattix evaluation or purchase, you should know a few key techniques about Lattix Architect and the DSM approach. Let us give you the benefit of our expertise and experience in assisting many Lattix customers. During this technical demonstration, you will learn how to:
- discover your architecture even if it has deviated significantly from the original intent through DSM partitioning and other advanced techniques to transform the DSM
- re-structure your system to modularize and extract components or services utilizing the tagging and reporting capabilities in Lattix Architect
- focus testing after each build using the update reporting and impact analysis features
- investigate the impact of proposed changes before implementation, including metrics to assess the impact on quality
We will also discuss how to accomplish these architectural improvements in an ongoing development environment.
Dependencies Beyond Code: The Big Picture View of Enterprise Java Systems
Most large scale enterprise systems are built using a variety of technologies. For instance, when developers create an enterprise application using the Spring Framework, they are dealing with not just java classes or interfaces but also Spring Beans. Spring Beans are entities that depend not just on each other but also on other entities such as java classes. Similarly, Hibernate is an object relational framework that maps java classes to database tables. Databases contain not just data entities such as tables and view but they also contain entities such as stored procedures and packages.
Lattix has extended the use of DSMs to represent Spring and Hibernate configurations as well as the structure of the code and database. This allows users to create a big picture view of their entire system and to better understand how changes can propagate throughout the system. Quickly learn how you can get this visibility into your system, identify opportunities to improve the architecture, eliminate bad dependencies, and systematically control your software. This interactive Webinar includes a live demonstration. You will be encouraged to ask questions of the presenter and have the added benefit of hearing the questions asked by your peers.
Applying Lattix on Ada and C/C++ Embedded Systems
Let us show you how to use Lattix Architect to analyze, refactor, test, and maintain the architecture of your Ada and C/C++ applications and embedded systems. During this live demonstration, you will learn how to:
- produce a precise blueprint of your system to share with your extended team and use to assess the impact of change
- identify short-term opportunities to break couplings and improve the architecture by changing the code organization
- create just a few rules which will prevent further erosion of the architecture