architecting for the enterprise

24
Wednesday, November 17, 2010

Upload: sencha

Post on 04-Dec-2014

1.364 views

Category:

Technology


4 download

DESCRIPTION

Adopting early planning and architectural design strategies is essential to create scalable Enterprise apps that are ready to meet the demands of dynamic workforces, and can scale to meet future business needs. You'll learn how to leverage class-based UI development within evolving Agile/Waterfall development methodologies and how Ext.Direct, Connect, and Ext.data packages can assist with integration. We'll also review best practices for strong, unit-tested foundation classes that will support your 'next' enterprise solution.

TRANSCRIPT

Page 1: Architecting for the Enterprise

Wednesday, November 17, 2010

Page 2: Architecting for the Enterprise

Doug HendricksSolutions Architect

Sencha Services

Architecting for the Enterprise

Wednesday, November 17, 2010

Page 3: Architecting for the Enterprise

• Early Design Considerations

• Risks and Rewards

• Project Management Methodologies

Wednesday, November 17, 2010

Page 4: Architecting for the Enterprise

Early Design Focus:

Are value added services already structured for scalable delivery?

Wednesday, November 17, 2010

Page 5: Architecting for the Enterprise

Do we want to own the plumbing?

Will that choice scale to perceived demands if

necessary?

Wednesday, November 17, 2010

Page 6: Architecting for the Enterprise

Success Factors

Wednesday, November 17, 2010

Page 7: Architecting for the Enterprise

Time-to-Market?(Opportunity Cost)

Wednesday, November 17, 2010

Page 8: Architecting for the Enterprise

SOA or leverage existing legacy value chain?

Evolutionary Hybrid?

Wednesday, November 17, 2010

Page 9: Architecting for the Enterprise

Ongoing:Identity propagation

RegulatoryInfoSecurityAggregation

DRM Consumption patterns

Privacy policy

Wednesday, November 17, 2010

Page 10: Architecting for the Enterprise

Risk Factors:

Domain ExpertiseTransient Workforce

Agile vs Waterfall

Wednesday, November 17, 2010

Page 11: Architecting for the Enterprise

Questionable Act #1

“Let’s develop SOA and UX

CONCURRENTLY thus, saving time and money.”

Wednesday, November 17, 2010

Page 12: Architecting for the Enterprise

O M G !

Wednesday, November 17, 2010

Page 13: Architecting for the Enterprise

O M G !

HACKATHON

Wednesday, November 17, 2010

Page 14: Architecting for the Enterprise

Dual development tracks

Wednesday, November 17, 2010

Page 15: Architecting for the Enterprise

Dual development tracks

SOA UX

Visual Wireframes

CMMM

Service Value

Wednesday, November 17, 2010

Page 16: Architecting for the Enterprise

Questionable Act #2

“Java and Javascript are the same thing. They can build both sides, right?”

Wednesday, November 17, 2010

Page 17: Architecting for the Enterprise

Syntactic similarity is no guarantee of

success!

Wednesday, November 17, 2010

Page 18: Architecting for the Enterprise

Agile kicks in...

Wednesday, November 17, 2010

Page 19: Architecting for the Enterprise

Dual development tracks

SOA UX

Wednesday, November 17, 2010

Page 20: Architecting for the Enterprise

Dual development tracks

SOA UX

Stories

Wednesday, November 17, 2010

Page 21: Architecting for the Enterprise

Dual development tracks

SOA UX

Stories

Iterations are soon

Overwhelmed

Wednesday, November 17, 2010

Page 22: Architecting for the Enterprise

The Better Way

SOA

Ext.Direct

Ext.data( Proxies, readers, writers )

Jasmine Unit Test

Wednesday, November 17, 2010

Page 23: Architecting for the Enterprise

The Better Way

SOA

Ext.Direct

data( Stores, proxies, readers, writers )

Ext.Designer

Wednesday, November 17, 2010

Page 24: Architecting for the Enterprise

Questions?

Wednesday, November 17, 2010