You have chosen to sponsor your bid up to a maximum amount of .
This project is primarily about enterprise software architecture – not coding. So, don’t waste a lot of time coding any individual service or client, or adding any functionality not explicitly required by the scenario. Each service and client should be relatively simple. It is the overall architecture that will be assessed, not the functionality of individual components. For assessment purposes, we will be treating each service and client application as a black box. We are looking for interesting service-oriented architectures, not complex individual services or applications.
An SOA system is made up of one or more software services that support one or more front-end client applications. You are required to implement a number of software services that fulfil the functional needs of the entities listed in the scenario. These software services should be exposed as web services, using the WS-* and/or RESTful architectural styles. Each software service may be implemented in any language (Java or C# preferred), and at least two languages must be used overall (for example, your assignment may implement some service(s) using Java, and some service(s) using C#). For C#, it is recommended that the WCF API is used (see Tutorial 6), and for Java the JAX-WS API is recommended (see Tutorial 5).
Front-end Client Applications
You are also required to implement a front-end client application to access your web services, simulating an in-store portal. The front-end client application may be implemented as a web-based application (hosted on a web server and accessed via a browser) or as a rich client application (run from the desktop). You may implement it using any programming language(s) (.NET-based or Java-based solutions preferred), and may use any IDE you have access to.
It is expected that your solution will display all information in a visually appropriate format. System users may be computer novices, so the application should be easy to use and reveal an understanding of the user perspective. Higher degrees of usability and overall professionalism will be expected of larger team