![]() |
Use this diagram to help you navigate and understand the Cash Sales mini example.
There are many aspects of this runnable example to help demonstrate the full
capabilities of Together -- at a glance :=) When in doubt, explore properties/right-click... |
![]() |
Peruse the
diagrams: Links To: Package Diagram data_management, Package Diagram problem_domain, Package Diagram Requirements, Class Diagram System Overview, Package Diagram user_interface |
![]() |
Right-click, choose
open in new tab. |
![]() |
This is where the heart of the
Object Model lives. |
![]() |
A rather simple UI design.
Well, in terms of class count! |
![]() |
A simple JDBC sample with
real persistence and a mini
sample of O-R mapping :=) |
![]() |
Set up the
Database |
![]() |
Debug the App! |
![]() |
Document
the App! |
![]() |
Run the App! |
![]() |
Explore
Database
Features |
![]() |
Press F9 (or Run | Run) to invoke an automatic
build and run cycle. As long as no one made any adverse changes
to the code :=), the sample application should work. |
![]() |
Now, from the problem_domain class diagram (with code pane open)
select the calcTotal operation in CashSale class.
1) Move to the source code pane to add a breakpoint.
2) Click in the first line of source ("subtotal = calcSubtotal()").
3) Right-click on this line and choose "Set Breakpoint".
4) Run app in debug. Ctrl - F9 or Run | Debug.
5) Pretend to create some scans to add items.
Then press "Total" button. This should trigger the breakpoint.
Use step over (F8) and step into (F7) to debug. |
![]() |
Select Project | Documentation | Generate HTML
Choose "All"
Review cool docs in browser -- especially explore the various
hyperlinks (to files, other diagrams, etc.) |
![]() |
Have some
Fun! |
![]() |
Select the totalSale() method in the POSFrame class (ui package).
Right-click | Generate Sequence Diagram.
Unselect detail like: java.util, java.text, java.math, and java.swing.
Alternatively, under swing, leave only JButton selected.
Press OK and watch :=) |
![]() |
Go to Problem Domain class diagram.
By marking each class "persistent" we can generate a database schema
from the class diagram.
Select Tools | Generate | DDL.
Select Class Diagram and choose Problem Domain from drop-down.
Choose Generate DDL Only (or go ahead and write to a temp database).
Select DBMS of choice (that you have access to).
You can review the DDL file. |
![]() |
These sets of diagrams lay out
what the system should do. |
![]() |
To experience the persistence version of this example, you must set up
the database prior to running this example.
Please see the ER Diagram and the DemoGuide.HTML file. Basically, you
need to set USE_DB constant in POSFrame class, and set up the Database
itself (e.g., using ODBC Data Sources). |
Referenced Diagrams |
|||||||||
Package Diagram |
|||||||||
Package Diagram: The Problem Domain diagram is where business-level classes reside. |
|||||||||
Package Diagram: This top-level requirements diagram is used to help readers walk through the various requirements artifacts available for review. |
|||||||||
Package Diagram |
|||||||||
Class Diagram: This logical diagram walks you through the architectural views.
|
|||||||||
Package Diagram |