aspose file tools*
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes Web frameworks and LDAP Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "Web frameworks and LDAP" Watch "Web frameworks and LDAP" New topic
Author

Web frameworks and LDAP

Andy Turner
Greenhorn

Joined: Jun 07, 2010
Posts: 2
Morning all,

I've recently started on the second part of the exam, so I'm using the "study guide" as a reference guide. However, I have two quick questions. In the example provided in chapter 9, it talks about JSF, JSP's etc, however, no where in the requirements does it state that a web front end is required, are we just supposed to assume that this is the requirement?

Also, in the requirements for the chapter 9 example, it doesn't mention user security, or login requirements, etc, but in the deployment diagram it references an LDAP server, user admin pages, and reporting pages, again are we just supposed to assume that ALL of the examples require LDAP, user admin pages and reporting? I originally thought we should only be providing details on what is provided, not "reading between the lines", would I lose marks if I didn't put in an LDAP server and the admin pages?

Thanks
Andy
Teja Saab
Rancher

Joined: Mar 08, 2010
Posts: 152
Andy Turner wrote:I've recently started on the second part of the exam, so I'm using the "study guide" as a reference guide. However, I have two quick questions. In the example provided in chapter 9, it talks about JSF, JSP's etc, however, no where in the requirements does it state that a web front end is required, are we just supposed to assume that this is the requirement?

You are right about the fact that it does not explicitly mention that a thin client is required. However, there are other aspects in the requirements that might narrow down the choice for you. For example, the non functional requirements might state certain stringent scalability requirements which might be impossible to achieve with anything other than a thin client architecture. Also, if your system will be accessed by an unknown number of users who won't install anything on their systems, you just narrowed down the choice to one.

The politically correct answer is that any kind of front end that can satisfy the stated functional and non functional requirements will work. However, it will be very difficult to justify how a 2 tier architecture can meet the requirements better than a 3 or N tier architecture in the context of the SCEA assignment. So the blunt answer IMHO is to just architect for a web front end.

Andy Turner wrote:
Also, in the requirements for the chapter 9 example, it doesn't mention user security, or login requirements, etc, but in the deployment diagram it references an LDAP server, user admin pages, and reporting pages, again are we just supposed to assume that ALL of the examples require LDAP, user admin pages and reporting? I originally thought we should only be providing details on what is provided, not "reading between the lines", would I lose marks if I didn't put in an LDAP server and the admin pages?

I think that the requirements provided will almost always have some gaps in them. As an architect, you will probably have to fill in the gaps. Besides, even though some of the diagrams show LDAP, admin and reporting information, it might be depicted there just so that the architecture diagrams would be complete. It does not necessarily mean that reporting or admin pages will be developed by the developers at the current time.

In the context of the SCEA assignment, it probably would demonstrate to the evaluator that you have thought through some of these common challenges and addressed them appropriately in your diagrams though not necessarily in the implementation.

Just my thoughts though....

SCEA 5, SCJD,SCWCD,SCJP,PMP,IBM-SOA Solution designer,IBM-XML
Mihai Lihatchi
Ranch Hand

Joined: Oct 28, 2005
Posts: 138

After looking at the example in chapter 9 I find something else puzzling : Pricing System . What on earth would make me think about a pricing server ? Really for me it does not make sense.
I can see how the LDAP can be used for user authentication but the Pricing System is a new external system that I could not identify in the example in the book . Somebody must code it and develop it and .. pay for it right ?
Maybe I do not understand the business domain but in that book example it is not something that makes a lot of sense.

Better, faster, lighter Java ... you mean Ruby right ?
SCEA5,SCBCD1.3,SCWCD5,SCJP1.4 - memories from my youth.
Andy Turner
Greenhorn

Joined: Jun 07, 2010
Posts: 2
Ah, good to know it's not just me then!

So, in a nutshell, I'll just have to go against the books recommendations and include some things that I would class as outside the scope of the requirements (advantages of actually communicating the client in the real world, you can clarify!), and just hope we don't lose too many marks for additional details.

Thanks (and sorry for the late response)!.
Andy
sivan jai
Ranch Hand

Joined: Feb 24, 2010
Posts: 115
Thats where the asssumptions come in - if you think an external system is left out of the original description you just state it in your assumption and add it to your model.
Jakeer Md
Greenhorn

Joined: Sep 17, 2010
Posts: 1
Hello Ranchers,

I have completed my assignment and scheduled part 3 in a week.
I have one question regarding usage of ldap server, Mark Cade book recommends ldap server
in chapter 9 deployment diagram.
Authentication and authorization can be done by database than why add ldap server for authentication
unless the company is using a central user access system.
My concern is if the users are not administered by ldap server is it a big architectural flaw
that might lead to loose some marks?
Did anyone successfully completed SCEA without using ldap for authentication?

Your thoughts are appreciated .

Thanks,
J
Jeanne Boyarsky
author & internet detective
Marshal

Joined: May 26, 2003
Posts: 30918
    
158

This website does not use LDAP. It is a valid design choice. As long as you can justify why you didn't use LDAP, this is fine.


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Web frameworks and LDAP