I do not need any solutions I'm simply searching for a failure in laymans relation to what this essay is requesting.

I've done medicare part a its very easy however I don't know what he means as he describes Programs. Part d can also be not so difficult.

My primary issue is I'm battling using the context of medicare part b, c. For reasons uknown the question (possibly the wording) is certainly going straight over my mind. If anybody could simply breakdown and explain medicare part b and c I'd very grateful, I'm able to finish this essay up.

Any links could be an additional benefit and surely unlikely thank men.

a) Discuss the two-tier architecture and also the 3-tier architecture of database application processing when it comes to architectural layout, programs, performance, security, pros and cons for such atmosphere. (40 marks)

b) Discuss the program atmosphere of both architectures including using higher level and mark-up languages, servers with connects on different platforms, communication links and tools used. (20 marks)

c) Discuss future planned developments during these two architectures conditions when it comes to hardware configuration, software utilisation and programs areas. (20 marks)

d) Give a conclusion from the report showing a listing of your analysis by quarrelling the viability of architectural layout software atmosphere and application areas with reasoning. (10 marks)

Thanks greatly


Okay men if anybody is ever assigned with somthing such as this training. Medicare Part A describes an evaluation from the Architecture designs of two and three tiered architecture, discuss the layers of every and also the performance and security difficulties with each. Medicare Part B is asking to go over HTML SQL along with other languages accustomed to communicate each architecture like a Java Application using JDBC, at this time I talked about the SQL Api etc.. Part C I talked about the design from the client and servers in hardware terms, API distirbuted database etc... I really hope this might help someone later on. Si