Field of Application
Lattix has been primarily used in the field of software/IT systems engineering across many industries, however it has also been applied to a wide variety of complex systems that include software, hardware, activities/processes, and organizations. Users include architects, engineers, and quality/test staff as well as managers.
- Create a system blueprint by mapping dependencies across the various domains of the system
- Analyze, optimize, and specify the system architecture through the DSM, diagrams, and dependency rules
- Identify dependencies which violate the architecture
- Identify and explore opportunities to improve the modularity of the system
- Measure quality with key metrics and track changes to the system architecture over time
- Assess the impact and risk of proposed changes to the system
- Hierarchical DSM/MDMs created manually or by automated extraction of dependency information from UML/SysML models, software codebases, SQL, databases, files (such as Excel and XML), and other tools.
- Numerous algorithms and editing features to analyze and re-engineer systems including activities, processes, requirements, software, hardware, tests, resources, and organizations.
- Rules engine to specify and automatically enforce the system architecture when project updates capture changes across the system.
- Web-based Repository and command-line utilities enable integration with data sources and enable users to automatically update, measure, track, and communicate the status of their projects.
- LattixWeb application provides interactive web-based access to the DSM and automated reports of key metrics and trends, as well as providing the ability to generate comparisons of selected versions of the project.
Supported use cases
Support for the following use cases is provided at each stage of the development lifecycle (forward engineering, reverse engineering, and round-trip engineering for ongoing redesign and system maintenance):
- Document and enforce the intended architecture, including component/interface corporate standards.
- Refactor or re-engineer the system to migrate to new technologies or platforms, in addition to improving quality, robustness, and maintainability.
- Conduct impact analysis across system domains, such as identifying which requirements are affected or which tests must be run when changes are made to the system software or hardware.
Address: Lattix Inc.
352 Park Street 203W