SCEA - a pragmatic pursuit
•
2 likes•797 views
The document summarizes the Sun Certified Enterprise Architect certification exam. It discusses the exam's objectives which cover application design concepts, common architectures, integration, business and web technologies, Java EE applicability, patterns, and security. The exam consists of a multiple choice part and an assignment part where candidates design architectures for a scenario. It provides tips for the exam such as useful resources on design patterns and sample diagrams for the assignment questions.
Recommended
More Related Content
Viewers also liked
Viewers also liked (12)
Similar to SCEA - a pragmatic pursuit
Similar to SCEA - a pragmatic pursuit (20)
More from Andy Pemberton
More from Andy Pemberton (12)
Recently uploaded
Recently uploaded (20)
SCEA - a pragmatic pursuit
- 1. The Sun Certified Enterprise Architect Certification a pragmatic pursuit
- 2. Agenda About Me Motivation The Exam
- 3. Tips I’ll use this icon for exam tips I found helpful.
- 4. About Andy
- 5. About Andy
- 7. An Example
- 8. Motivation
- 11. The SCEA
- 12. Objectives Section 1: Application Design Concepts and Principles Section 2: Common Architectures Section 3: Integration and Messaging Section 4: Business Tier Technologies Section 5: Web Tier Technologies Section 6: Applicability of Java EE Technology Section 7: Patterns Section 8: Security
- 13. Part 1: Exam
- 14. Part 1: Exam 64 question multiple choice
- 15. Part 1: Exam http://en.wikipedia.org/wiki/Design_pattern_(computer_science)
- 16. Part 1: Exam http://www.corej2eepatterns.com/Patterns2ndEd/
- 17. Part 1: Exam
- 18. Part 2: Assignment “You are the architect for JustBuildIt Corporation, [a] construction company with significant operations in the U.S. and Canada, Europe, and the Pacific Rim. JustBuildIt operates its own forests, quarries, and steel foundries to supply its own building sites with [materials]...” “JustBuildIt has decided to build a building commodities exchange to allow both it and some of its competitors to effectively pool excess capacity in a co-opetition model.” Humphrey Sheil, http://tr.im/sceabook
- 19. Part 2: Assignment UML Diagrams Component Class Deployment Sequence or Collaboration Risk & Mitigation List www.websequencediagrams.com
- 20. Part 2: Assignment Time Commitment Web Submission Format Source control everything Valid HTML Add a bit of CSS www.beanstalkapp.com
- 21. Part 3: Essay
- 22. Part 2 & 3
Editor's Notes
- Working on a take-away handout for tonight’s RJUGWill distribute if I get there
- - Steve Jobs, motivating the troops against a common enemy
- - not all who give to charity do so for the same reasons- you may not call all of those reasons "good" or the "right" reasons, does that mean you shouldn't be charitable?
- - Jared Richardson, "Intellectual Portfolio"- self-investment- pragmatically: establish expertise, marketability, can help obtain vendor partnerships - better yet: often your company will finance your self-investment!
- - SCEA is heavy on software architecture (duh)- concerned with software 'ilitys' / non-functional requirements / quality of service- my current view on the role of the architect is more about the processes an architect brings
- - dubbed "pinnacle" of java certs, though where most of the earlier certs rely on scjp, scea has no pre-reqs- updated in 2007/8 for JEE5 (reflect the world at that time)- upgrade to JEE5 version is a shortened version of part 1 only - exam format: 3 part process; certified only after all 3 complete- part 1: 64 question multiple choice (more like other sun certs, are specific to JEE5 / current version, but need to know older specs)- part 2: assignment (no time limit, but some estimate 40 hours)- part 3: 8 question essay (follow up on part 2, scored together)
- - these are the objectives for all 3 sections of the exam- Section 1: Application Design Concepts and Principles (OOA/D)- Section 2: Common Architectures (n-tiered architectures, how they speak to “illity”s)- Section 3: Integration and Messaging - Section 4: Business Tier Technologies (EJB, JPA, JMS)- Section 5: Web Tier Technologies (Servlets/JSP, JSF)- Section 6: Applicability of Java EE Technology - Section 7: Patterns (primarily GoF and Core J2EE)- Section 8: Security
- - 64 question multiple choice (57% to pass)- big pool of questions written by an expert group (including humphreysheil)
- - Design Patterns - obviously dartboard driven design not the goal ;) - ability to spot design patterns - ability to know when (and when not) to apply a design pattern - Core J2EE
- - Java EE Knowledge - APIs and specifications (not programming syntax) - applicability (SCBCD + SCWCD is ideal background)
- - What you're given: - "business" domain model (this will primarily be translated into class diagram in your architecture) - high-level use cases (stick figures; these will primarily be translated to sequence diagrams in your architecture) - additional description including NFRs and other constraints- UML - be simple but thorough (don't go overboard) - think of ways to make simpler (post conditions/pre conditions rather than repeating yourself) - UML needs to be valid (multiplicity, etc.) - I used Eclipse EMF UML tools (also tried netbeans + argo) - websequencediagrams.com for sequence diagrams - add notes to all of your diagrams
- - What you're given: - "business" domain model (this will primarily be translated into class diagram in your architecture) - high-level use cases (stick figures; these will primarily be translated to sequence diagrams in your architecture) - additional description including NFRs and other constraints- UML - be simple but thorough (don't go overboard) - think of ways to make simpler (post conditions/pre conditions rather than repeating yourself) - UML needs to be valid (multiplicity, etc.) - I used Eclipse EMF UML tools (also tried netbeans + argo) - websequencediagrams.com for sequence diagrams - add notes to all of your diagrams
- - Time - 30 - 40 Hour time commitment - leave yourself review cycles - 12 months to submit from the date of download
- - Comer quote "want to make sure you're the same person who did part 2"- defending your architecture- which web framework (if any) did you choose?- security implications of your decisions?- how do your choices affect "ility"s?
- - scored together- see where to focus