• Blog
  • Contact
Home
  • Products
    • Modules
      • ActionScript
      • Ada
      • C/C++ (with BSC, Doxygen, Klocwork, and Understand)
        • Klocwork
      • Delphi Pascal
      • Fortran
      • Java (with Spring and Hibernate)
      • JavaScript
      • .NET
      • Oracle
      • SQL Server
      • Sybase
      • UML/SysML (with XMI, IBM Rhapsody, SparxEA)
        • Rhapsody
      • LDI (with Excel)
    • LDM/LDV
      • Features
    • LDC
    • LattixWeb & Repository
    • Licensing & Pricing
    • FAQ
      • Installation
      • Approach
      • Howtos
      • Java Specific Issues
      • C/C++ Specific Issues
      • .NET Specific Issues
      • Database Specific Issues
      • Hibernate and Spring Specific Issues
  • Solutions
    • Embedded Systems
    • Enterprise Systems
    • Complex Systems
    • Case Studies
  • Services
    • Consulting
    • Training
    • Deployment/Integration
  • Technology
    • Analyzing Architecture
    • Example: A Dependency Model for ANT
    • Dependency Models and UML
  • News/Events
    • Lattix News
    • Events
    • Lattix Live Demos
      • What's New in Lattix 7.0
    • Buzz about Lattix
  • About
    • Partners
    • Management
    • Advisors
    • Corporate Fact Sheet
Lattix Demo
Watch Now
Attend a
Live Demo
Read our
Whitepapers

Value Scenarios

The Lattix approach can be applied at any point in the lifecycle of your projects: to proactively establish the architecture at the beginning, to coordinate change during ongoing development, and to facilitate testing and maintenance at the end of each release cycle.

Major Reinvestment in a Large Existing System Ongoing new requirements, changes in technology and new best practices drive large-scale change into an existing system.
Identifying Components for Re-use New projects need to leverage parts of the existing products that organization has produced
Unifying a Group of Systems Typically a result of reorganization or acquisition, this scenario requires unifying competing architectures and silos of functionality into a common architecture.
Evolution to a Next Generation Requirements, development platform, and technology eventually change to such an extent that a systems architectural underpinnings must be reconsidered.
New System (from inception) Forward engineering where architects decide layout and provide software factoring guidance to developers throughout implementation.
Keep a 1.0 System clean Initial implementation of the system is complete and ongoing investment has begun in functional enhancements and limited infrastructural improvements.
Lattix | North Reading MA 01864 | +1.978.664.5050 | copyright 2012