|
The
Sun Certified Enterprise Architect for J2EE Technology (Step 2 of 3)
certification exam is for enterprise architects responsible for
architecting and designing Java 2 Platform, Enterprise Edition (J2EE)
platform compliant applications, which are scalable, flexible and
highly secure.
Description of the Sun Certified Enterprise Architect Assignment Exam
The
Sun Certified Enterprise Architect for J2EE (SCEA) is intended for Java
technology professionals responsible for architecting systems. It is
expected but not mandatory that a person taking the SCEA exam has
already passed the Java technology programmer and Java technology
developer certifications. The SCEA exam is broken down into three
parts. Part 1 is multiple choice and tests your knowledge in the areas
of general architecture and J2EE. Part 2 is an assignment that tests
your ability to apply the knowledge you were tested on in part 1. Part
3 is an essay that asks questions about your assignment.
Description of the Sun Certified Enterprise Architect Assignment
This
is a description of the nature, scale, and scope of the problem you
will be required to solve in the SCEA assignment. These notes do not
form any part of the actual assignment, and if you find a contradiction
between these notes and the actual assignment instructions, you must
adhere to the instructions in the assignment documents.
Nature of the Assignment
The
assignment requires that you architect a solution for a small but
plausible business system. To keep the amount of work involved to a
reasonable level, the programs you create will be much more restricted
in capability, and much cruder in overall presentation, than anything
you would actually create for a paying customer. However, the essence
of the problem will be the same. You will be graded on correctly
solving the technical and performance requirements, not on the
\"polish\" of the finished product.
Scale of the Assignment
Obviously,
the amount of time taken by a candidate to create a solution to the
assignment varies greatly. A fast candidate might create a solution in
about 40 hours, but a more typical time requirement might be about 80
hours. If you spend a lot more than 100 hours on the project, then you
might be creating something that is more detailed than the requirement,
or you are lacking some of the skills necessary to complete the
assignment.
Scoring Criteria
Your project will be evaluated on a large number of objective criteria that fall into three categories:
1)
Class Diagram: This category covers how well your class diagram(s)
address the object model needed to satisfy the requirements.
2)
Component Diagram: This category covers how well your component
diagram(s) convey the structure of the architecture in satisfying the
requirements.
3) Sequence/Collaboration Diagrams: This
category covers how well your sequence or collaboration diagrams
satisfy the requirements of the assignment.
Additionally, each category is evaluated on UML compliance.
The maximum number of possible points is 100. The minimum passing grade is 70. The maximum points per category are:
Categories - Maximum points
Class Diagram(s) - 44
Component Diagram(s) - 44
Sequence/Collaboration Diagrams - 12
APIs relevant to the Assignment
The
assignment requires that you have an in-depth understanding of the Java
programming language and J2EE APIs. You can choose to use any released
version of the J2EE APIs.
Suggested Reading Materials
Mark
Cade and Simon Roberts. Sun Certified Enterprise Architect for J2EE
Technology Study Guide, Third Edition, Prentice Hall, 2002.
Erich Gamma. Design Patterns, Boston: Addison-Wesley Publishing Co., 1995.
Richard Monson-Haefe. Enterprise JavaBeans, O'Reilly and Associates, 2001.
Martin
Fowler. UML Distilled: A Brief Guide to the Standard Object Modeling
Language, Third Edition, Boston: Addison-Wesley Publishing Co., 2003.
|