 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
| |
|
|
| |
|
|
|
Upcoming
Webinars
|
|
Mon,
Dec 14, 2009
|
|
|
|
| Wed,
Dec 16, 2009 |
|
|
 |
|
|
|
Participant
Companies
|
 |
Daimler
Chrysler, UK
|
 |
British
Telcom, UK
|
 |
Foxtel,
Australia
|
 |
Juniper
Networks, USA
|
 |
Wamu,
USA
|
 |
Lockheed
Martin, Australia
|
 |
Citi
Group, Australia
|
 |
Boeing,
Australia
|
 |
Singapore
Airlines
|
 |
Motorola
|
 |
Thales
|
|
|
| more
|
Feedback
on Sunil
"It
was great attending the Architecture workshop. It
was really one of the most inter-esting and intense
workshop on software architecture I have attended.
Congra- tulation for achieving it and making it available
to software community. This will enable to move up
in the ladder of Zachman model "
|
|
|
|
|
|
|
 |
| Architecture Polls v1.0 |
| |
| 1 |
What are the key metrics for architecture governance? |
| |
• Eliminating Obsolescence

• Business Process Standardization

• Shared Infrastructure Layer

• Enterprise Data Layer

• Other
|
|
| 2 |
Are there too many IT people doing very little for business growth |
| |
• Agree
• Disagree
• Not sure |
|
| 3 |
Agile methodologies & techniques are very useful when |
| |
• Team is relatively inexperienced (freshers to 12 months development experience)
• Team members lacks domain Knowledge
• Customer lacks clarity about the target system
• System is not very complex
• None of the above
• All of the above |
|
| 4 |
What role does architect play in Agile software development? |
| |
• Defining technology standards
• Continuous guidance, mentoring & conflict resolution
• Defining QoS aspects of the system including longevity, maintainability • Owner of prototypes
• None |
|
| 5 |
How does architecture ensures system flexibility? |
| |
• Increasing the Scope
• Well defined component contracts & constraints
• Identifying the metrics for modifiability
• Define the system life
• Identify the domains of influence
• Other |
|
| 6 |
What makes more sense |
| |
• agile programming (fast & quick)
• lean programming (do more with less) |
|
| 7 |
What are the key "behavioral" challenges in designing & developing reusable assets |
| |
• No commitment from managers for time, efforts etc
• Teams are always in "delivery/crisis mode
• Short /mid term gains are not visible
• No designated roles like "Asset managers"
• Other |
|
| 8 |
What are the key "engineering" challenges in designing & developing reusable assets |
| |
• Issues with functional decomposition & granularity
• Lack of knowhow of cross-dependency among assets (code, components, services)
• No 'reuse" repository
• Lack of matured RAS based repository tools
• Issues with domain models / components
• Lack of governance / metrics for measurement |
|
| 9 |
A good programmer is one who can write code that compiles and |
| |
• is easy to modify
• is reliable
• is usable
• is high performance
• is well documented
• is delivered quickly without support for above parameters
• All |
|
| 10 |
The biggest bottleneck in using MDA is |
| |
• Modellers
• Modeling tool vendors
• Development tool vendors
• IT Services Vendors as they perceive MDA eating away their profit margin
• Not sure
• Other |
|
|
|
|
|
|
Follow Us
|
|
 |
|
|
|
|
|
case
studies
|
|
 |
Defining
ROI on architecture. (Align Business ROI with Technology
ROI
|
|
|
Mapping
of Performance Metrics
from the Technology to the Business Outcomes
|
|
|
How
to apply Zachman & RM-ODP frameworks and how to
use them in your enterprise
|
|
|
Applying
RUP/UML Models with Zachman RM-ODP & TOGAF
|
|
|
Product
Line Architecture, COTS selection and component assembly
|
|
|
Component
Modeling with UML2.0
for Business domains
|
|
|
Use
MDA for developing architecture models, model-to-model
transformation and model-to-code generation.
|
|
|
Deployment
architecture using distributed clustering, fail-over,
load-balancing for large-scale business applications
|
|
|
The
process and role of Architecture
in a SEI-CMM enterprise and strategy to introduce
architecture team
|
|
|
Legacy
transformation and defining product vision and rationalization
|
|
|
Enterprise
SOA initiatives for mid-size
to large enterprises
|
|
|
|
|
|
|
|
|
|
|
|
|
|