Reference no: EM132667266

Assignment - Team-based Enterprise Application Development Project

This assignment is a team-based software development project. You will work in a small team for the design and development of a 3 -tier enterprise appl ication. You will practise to work collaboratively and communicate effectively as part of a productive team.

You will need to negotiate with your fellow students to form a team of at least 2 students and at most 3 students; each team needs to elect a team leader. The online students will be facilitated by the unit coordinator to form teams.

Team Membership Agreement - By default, a team works collaboratively; with all members p erforming their duties timely. The team leader submits the project and each member must submit his/her own teamwork report of Template A (see Part 2 of this document) by the assignment due time.

A large emphasis of this group project is solving minor collaborative problems as a part of teamwork and this should be reflected upon in the teamwork report. Each team should minimise contacts with lecturer/tutor/coordinator for minor collaborative problems, as too many contacts show the ineffectiveness or inefficiency of the team for solving minor problems and will result in loss of marks.

Each team member should use the following agreement if a major problem arose. The unit coordinator should be contacted as a last resort, only when the dispute cannot be solved by the following agreement.

When forming a team, each team member must agree that the whole team is to take its own risk when including an individual member and that the project progress can be delayed by that individual member. Some circumstances are:

1. A team member cannot take his/her allocated duty normally for a particular reason, e.g. health condition.

If an extension is given to that particular member, the extension is applied to the whole team. If there is no extension granted for that particular member, the whole team is to take the risk of a late penalty. In addition, the whole team is to take its own risk of any other impact, e.g. influence on schedule of other units of study, which may be caused by the improper delivery of duty of that team member.

2. The other members of a team are to complete the whole project if a team member leaves in the middle of project for any sound reasons or no reasons.

3. If a team splits into individuals in the middle of the project, each individual needs to complete the whole project separately.

4. If a team member does not take his/her allocated duty and cannot be contacted, the team can provide evidence of 3 contacts without responses or other relevant evidence to the unit coordinator. The unit coordinator reserves the final right to decide whether the member should be excluded from the team. However, as mentioned in point 2 previously, the rest of the team needs to complete the whole project if a team member is excluded from the team.

5. Any individual, who separates/quits from a team for any reasons in the middle of the project, needs to complete the whole project and the teamwork report of Template B (see Part 2 of this document).

This assignment consists of 2 parts.

Part 1: Software Development and Documentation

This part is to design, implement, test and document a complete 3 -tier enterprise application. The application scenario and project specification are as follows.

The application scenario

This assignment is to scale the application scenario of Assignment 2 to a typical Java EE web application. You are to implement the business tier and presentation tier and integrate them with the persistence tier that you have already implemented in Assignment 2 into a complete 3 -tier online e -business system.

The project specification

In Assignment 2, you have used a simple tester (a Java standalone application) to demonstrate the persistence and retrieval of entities. I n this assignment, you are to:

1. Develop a business tier by using Enterprise Java Beans (EJB). The business tier processes the data persistence or retrieval requests from a user and interact s with the persistence tier for accomplishing the requests.

Note: to interact with the persistence tier, the EJBs need to use JPA to persist entities and JPQL to query entities and return the processed results to the presentation tier.

2. Develop a presentation tier by using JavaServer Faces (JSF) . The presentation tier will provide a web -based user interface, which will allow user s to use any web browser to save car details, customer details and order details and retrieve the persisted information later on. Note: you need to review backing beans (managed beans) as the core/gateway of presentation tier for delegating requests processing to EJBs and navigating JSF pages.

3. Integrate with the existing persistence tier. To reuse the entities that have been successfully developed by Assignment 2, you are to seamlessly integrate the entities and related JPQL named queries with the business tier through interacting with the EJBs.

The whole team will need to negotiate and divide the whole project into multiple tasks, which are allocated to the team members. The team members need to communicate frequently so that each member's software modules can be integrated into a complete system to fulfil the project specification.

Part 2: Teamwork Report

A student, who completes the whole project as a member of a productive team, is to prepare a document in the following format and address the following questions.

Template A - Teamwork Report

a. Describe team forming, task assigning, your role and responsibility and the project timeline.

b. List 2 technical problems in the project development and describe how the problems have been solved by the team.

c. List 2 collaborative problems in the teamwork and how the problems are negotiated and solved by the team.

d. Describe and justify what are important for the success of teamwork.

e. Describe the communication skills that you have developed in this small team-based project.

Template B - Teamwork Report

a. Describe team forming, task assigning, your role and responsibility and the project timeline.

b. Describe what major problems that cause you leave the team or cause the team break into individuals.

c. Describe and justify the impact on you and other team members caused by your leave or the break of the team.

d. Describe and justify what are important strategies for successful teamwork.

e. Describe and justify how you can avoid such hindrances of teamwork in future opportunities of teamwork.

Attachment:- Enterprise Application Development Project Assignment Files.rar