All sizes of projects are supported in all Together products including the free Together Whiteboard. Project size is technically limited only by file system itself. That means that as projects grow in size and scope, Together keeps pace. Because everything is file-based, there's no need for an intermediate repository, and it's easy to integrate with other file-based tools like version control systems.
Together's legendary smart parsing engine knows just when to kick in so you get optimal performance no matter how large the project.
You can easily use Together to help you manage your existing source code. Simply configure your reverse engineering options, create a project for your code, and Together reverse engineers your sources into class diagrams. Voilà... your visual UML model is ready! Now net-ready HTML or generic RTF documentation is just a menu click away.
Together will reverse engineer many code bases in their entirety with acceptable performance when run on an appropriate hardware configuration. If a project is quite large, however, even Together's highly efficient parsing engine may require more time than is practical. Since you probably deal with such large projects in smaller chunks anyway, you will find it more convenient to use some basic project management techniques to structure your Together projects to align more with the way you actually work. For example, you can...
Create multiple Together projects around major modules of your code base instead of the entire code base. This can reduce the scope of what is reverse engineered on demand.
Use the Advanced mode of New Project / Project Properties dialog to customize the content of your project to exclude unnecessary subdirectories or orther resources from round-trip engineering.
Create projects comprised of logical views and only bring in content that is of particular interest for some particular purpose.
For an example of how you can structure modular projects and sub-projects, check out the projects in the ./modules/components/CoadModelingComponents directory of your Together installation. That entire directory structure is not really a large project, but it can give you an idea how projects with sub-projects can work.
In this case, you could create a Together project in each of the first-level packages. Each of the would encompass only subpackages below the project root. For example, if you create a project in the CashSaleMgmt directory, it will parse that directory and the CashSale, CashSaleSession, and SummaryInPink subdirectories only.
Another way to deal with larger projects is to create custom views that show you only what you need to see when you need to see it. Create your own views using Class diagrams in which you place shortcuts to any classes, interfaces, etc. residing anywhere in your project. Bring in just what you need to focus on to get the job done.
To create a custom view:
Open the CashSales sample project ($TGHOME$/samples/java)
Select one of the Packages in the Model Tab of the Explorer
On the Main menu, choose File | New Diagram to display the New Digaram dialog.
Select Class as the Type, and enter a name in the Name field and click OK.
Right-click the diagram background and choose Add Shortcut to display the Add Shortcuts dialog.
Use the treeview to select one class from each of the three packages and add it to the list on the right. (For example, DataManagement.SaleDM, ProblemDomain.CashSale, and UserInterface.SaleUI) Click OK.
'Shortcuts' for each of the three classes are added to the diagram. You can view and edit properties in the class properties inspector (Alt+Enter). Even if the codebase were extremely large, you (and the parser) only have to deal with a subset that is in some way meaningful to your task at hand.