"Architecture practices" refer to the activities, methods, and processes that architects and architectural firms employ in the design, planning, and construction of buildings and structures. These practices encompass a wide range of tasks and considerations, involving both artistic and technical expertise. Here's a detailed elaboration on various aspects of architecture practices: **1. ** Design and Conceptualization: Concept Development: Architects start by understanding the client's needs and aspirations. They develop creative and innovative design concepts that fulfill functional requirements while considering aesthetics, sustainability, and cultural context. Sketching and Visualization: Architects often use hand sketches, computer-aided design (CAD) software, and advanced visualization tools to illustrate and communicate design ideas effectively. **2. ** Technical Planning: Site Analysis: Architects evaluate the site's geographical, environmental, and social aspects to inform the design process. This analysis influences decisions related to orientation, materials, and sustainable design strategies. Building Codes and Regulations: Architects ensure that the designs comply with local building codes, regulations, and zoning laws. They are responsible for obtaining necessary permits for construction. **3. ** Collaboration and Communication: Client Interaction: Effective communication with clients is essential. Architects must understand the client's vision, budget constraints, and timeline expectations. Regular client meetings and presentations are common practices. Collaboration with Engineers: Architects collaborate with structural, electrical, and mechanical engineers to ensure that the building's design integrates all necessary systems seamlessly. Coordination with Contractors: During the construction phase, architects work closely with contractors to address any design-related issues, modifications, or clarifications that may arise. **4. ** Technology Integration: Building Information Modeling (BIM): BIM software allows architects to create detailed 3D models that include information about building components and systems. BIM facilitates better visualization, coordination, and project management. Sustainable Design Tools: Architects use various software tools to simulate energy usage, daylighting, and thermal performance, helping in the design of eco-friendly and energy-efficient buildings. **5. ** Project Management: Budgeting and Cost Estimation: Architects often assist clients in budgeting and estimating construction costs. They help in making decisions that balance design aspirations with budget constraints. Project Scheduling: Architects develop project timelines, outlining key milestones and deadlines. Efficient scheduling ensures that the project progresses smoothly and is completed on time. **6. ** Post-Occupancy Evaluation: Feedback and Assessment: After the completion of a project, architects may conduct post-occupancy evalu

1. Building an
Building an eCommerce
eCommerce
Solution Architecture
Solution Architecture
Vin D
Vin D’
’Amico
Amico
President
President
vin
vin@
@damicon
damicon.com
.com
January 2002
January 2002
New England Electronic Commerce Users' Group
New England Electronic Commerce Users' Group

2. Goals
Goals
Introduce Damicon, LLC
Define “Architecture”
Show Sample Architectures
Share Best Practices
Compare Web Services

3. Who is D
Who is DAMICON, LLC
AMICON, LLC?
?
Information Technology Advisors
IT Help Desk Enhancers
Adjunct CIOs
IT Change Agents
It
It’
’s not about technology, it
s not about technology, it’
’s about business!
s about business!

4. Core Competencies
Core Competencies
IT Process Reengineering
Technical Consulting
Program Management
Planning and Execution Methodologies
Joint Requirements Planning
IT Training and Mentoring
IT Staffing

5. What is Architecture
What is Architecture
and
and
Why is it Important?
Why is it Important?

6. “
“A common mistake that people make
A common mistake that people make
when trying to design something
when trying to design something
completely foolproof is to
completely foolproof is to
underestimate the ingenuity of
underestimate the ingenuity of
complete fools.
complete fools.”
”
-
- Douglas Adams, Author
Douglas Adams, Author

7. Formal description of a system at the
Formal description of a system at the
component level.
component level.
The structure of components, their
The structure of components, their
interrelationships, and the principles
interrelationships, and the principles
governing their design and evolution
governing their design and evolution
over time.
over time.
Architecture Definition
Architecture Definition

8. Why Architecture?
Why Architecture?
Lower software development, support, and
maintenance costs
Improved interoperability and easier system
and network management
Simpler upgrade and exchange of system
components
Reduced complexity in IT infrastructure
Flexibility to make, buy, or outsource IT
solutions

9. Architecture is Critical In
Architecture is Critical In…
…
Delivering an enterprise-computing system
Providing control points to manage complexity
Maintaining system integrity
Unifying component structure
Organizing people and processes
Generating rules for growing the system
Protecting an enterprise system

10. Architecture Goals
Architecture Goals
1. Accommodate Change
2. Adhere to Standards
3. Scale as Business Grows
4. Provide Full Functionality
5. Deliver Low Response Times
6. Be Reliable
7. Interoperate with Other Systems
8. Provide Robust Security
9. Be Simple to Manage
10. Service International Users

11. Architecture Elements
Architecture Elements
Personal Systems
– Desktops, PDAs, Phones, Pagers, etc.
Network Components
– Routers, Load Balancers, Switches, etc.
Security Elements
– Firewalls, Encryption, VPNs, etc.
Servers
– Web, App, DB, Directory, etc.
Application Components / Web Services
– Packaged and/or Custom
Data
– Local, Remote, Internal, External

12. Examples of Architecture
Examples of Architecture

13. Basic 3
Basic 3-
-Tier Architecture
Tier Architecture
Database Server(s)
Application Server(s)
Database(s)
Database(s)
The Internet
Web Server(s)
Users

14. Physical Architecture
Physical Architecture

15. Infrastructure Services
Infrastructure Services
Complex Distributed Architecture
Complex Distributed Architecture
Administration Services
Administration Services
Transaction Processing
Transaction Processing
Data Management
Data Management
Presentation Services
Presentation Services
Personal Services
Personal Services
Network
Overlay
Network
Overlay
Security
Overlay
Security
Overlay

16. • Any Browser-based
Device:
• Desktop
• Laptop
• Handheld
• Phone
• Appliance
• etc.
Personal Services
Personal Services
• Best Practices:
• Adhere to Standards
• Avoid Browser-
Specific Features
• Minimize Decision
Logic
• Use Java or C# for
Complex Functions

17. Presentation Services
• Formatting Logic
• Dynamic Content
Delivery
• Portlets
• Reporting
• Internationalization
• Best Practices:
–Separate Data
Retrieval from
Formatting
–Don’t Mix Business
Rules and Display
Logic
–See Model-View-
Control and Layer
Patterns

18. Data Management Services
• Searching
• Categorization
• Content Aggregation
• Group Collaboration
• Personalization
• Distribution
• Best Practices:
• Identify User Types
• Focus on User Goals
• Consider Performance
• See Presentation-
Abstraction-Control
and Chain of
Responsibility Patterns

19. Transaction Processing Services
• Transaction
Management
• Metadata Control
• Application Interfaces
• Business Rules
• Data Interchange
• Best Practices:
• Focus on Interfaces
• Beware Incomplete
User Activities
• Think Services
• Do Not Hard Code
Business Rules
• See Adapter, Façade,
Proxy, Observer and,
Broker Patterns

20. Administration Services
• Directory Services
(LDAP)
• System Administration
• State Management
• Session Management
• User Controls
• Rules Definition
• Best Practices:
• Define Policies
• Control System
States
• Anticipate Growth
• See Command and
Microkernel Patterns

21. Infrastructure Services
• Data Access
• Communications
• Process and Thread
Management
• Sun One and MS .Net
• Content Repositories
• Best Practices:
• Adhere to Standards
• Understand Data
• Model Data
• Manage Data
• See Abstract Factory
and Mediator
Patterns

22. Security Overlay
• Hardware Firewalls
• Software Firewalls
• SSL and WTLS
• VPN’s
• Encryption
• Best Practices:
• Establish Policies
• Secure the Perimeters
• Monitor for Intrusions
• Stay Aware
• Patch, Patch, Patch

23. Network Overlay
• Routers
• Load Balancers
• Switches
• Gateways
• Modems
• Hubs
• Cabling
• Best Practices:
• Separate Major
Workgroups
• Separate Major
Applications
• Constantly Review
Structure
• Document, Label,
Diagram

24. Physical Architecture
Physical Architecture

25. Web Services
Web Services
Major Players
– IBM (WebSphere)
– Microsoft (“.NET”)
– Sun Microsystems (Sun ONE)
Problem Space
– Distributed Applications
– Interoperability
Solution Space
– XML
– Interfaces

26. Sun ONE
J2EE
JDBC
JVM
Java
EJB
JSP
JNDI
JAX_
MS .Net
Win XP
ODBC
MSIL
CLR
C#
VB.Net
ASP.Net
ADO.Net
SOAP
WSDL
UDDI
XML
Web Services
Web Services
Think Interfaces!
Think Interfaces!

27. Resources
Resources
The Open Group (TOGAF)
– http://www.opengroup.org
Portland Pattern Repository
– http://c2.com/cgi-bin/wiki?PatternIndex
– http://c2.com/cgi-bin/wiki?AntiPatterns
Microsoft (“.NET” initiative)
– http://www.microsoft.com/net
Sun (“Sun ONE” initiative)
– http://www.sun.com/sunone
Acronym Finder
– http://acronymfinder.com

28. New England Electronic Commerce Users' Group
New England Electronic Commerce Users' Group