Abstract
The purpose of technical architecture (TA) is to get an overall feel for the system that you’re going to be developing. Will it be a web-based system? Or a rich-client system in VB .NET or Java Swing? Does it need to use a specific application framework (e.g., a company-standard framework)?
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Hubert Matthews and Mark Collins-Cope, “The Topsy Turvy World of UML,” ObjectiveView Issue 4, available at http://www.softwarereality.com/ObjectiveView.jsp, 2000.
Rights and permissions
Copyright information
© 2007 Doug Rosenberg and Matt Stephens
About this chapter
Cite this chapter
(2007). Technical Architecture. In: Use Case Driven Object Modeling with UML. Apress. https://doi.org/10.1007/978-1-4302-0369-8_7
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0369-8_7
Publisher Name: Apress
Print ISBN: 978-1-59059-774-3
Online ISBN: 978-1-4302-0369-8
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books