Modeling the QuickExpense applicationThe following example patterns are provided, each building on the previous ones, or modeling a different component of the Wibble Software QuickExpense application: Footprint modeling using a simple SIThe application is modeled to the detail that there is a a database server running and that it is the prime process. This shows TPL files, modules, and patterns. It also introduces the following techniques:
Footprint modeling using basic versioning (path or command)The simple SI footprint pattern is extended with simple versioning. This introduces the following techniques:
Deeper modeling including dependency creationAnother part of the application is modeled, additional versioning techniques are used, additional configuration information is obtained, and a dependency created between the newly created SI and the one created in Footprint modeling using simple versioning and the commercial name of the application server is populated using a table. This introduces the following techniques:
Modeling a supporting componentA supporting part of the application is modeled including versioning information. This introduces the following technique:
Identifying minor components using Simple IdentifiersThe remaining 'uninteresting' components of the application are identified and assigned labels. This introduces the following technique:
Modeling the entire applicationThe entire application is modeled as a BAI. All supporting components are linked in to the BAI. Return to Application Modeling. |
- Loading...
Modeling the QuickExpense application
Labels:
None
Tideway BlogCopyright © 2012 BMC Software