WEB代写｜Team Project Task Specification
For this module your team will produce a web application, whilst applying industry-standard development practice. Your project will apply Agile techniques and will involve selecting appropriate technology (programming languages, libraries, frameworks, etc) for your application. The application you develop will also be decided by your team.
We will provide guidance on application and technology selection, however your application must have certain core elements. These elements are listed in the section ‘Application Requirements’. You must use a shared git repository and you will be required to demonstrate a Continuous Integration (CI) pipeline.
The most important aspect of this module is that you work together in a team to create the product. The product must be the result of teamwork. As in real-world projects, you will be assigned to teams. We expect you to self-organise within your team and distribute work. You are strongly encouraged to create and assign roles to each team member. Your team must meet regularly to discuss and progress as a team. All members of the team are expected to attend these meetings and participate in discussions. You are required to keep a diary of team meetings.
We will provide you with resources including a tutor who will meet with your team each week and provide guidance and feedback. At these meetings, progress and attendance will be monitored and feedback given to help your team. Teams are expected to come to a consensus about the major decisions and delegate tasks amongst team members. Where you cannot come to a consensus, you are encouraged to discuss issues with TAs, lecturers and the module leader.
The teamwork in this project is formally assessed. Assessment is via three milestones that include presentations (screen recorded videos) and documentation. All team members must contribute to the assessments. Milestones are outlined below. Each milestone will be described in more detail in the separate documents. Marks will be reviewed in teams with unresolved professional issues. For example where teams allow one member to ‘storm’ ahead with the project; or where members are ‘passengers’ and do not contribute equally.
Your application must have a minimum level of sophistication described in this section.
The applications are expected to differ between each team. Your team must decide together the application you want to make. We have provided some suggestions and example applications.
1. Application concept. Your application must serve a useful purpose for real-world users (‘personas’).
One important assessment aspect will be the inclusiveness of your application, that is, how well does it adapt to a range of users with diverse needs: not every user can use a mouse, read the screen or hear sounds.
Your application must have some original aspect, so you cannot simply clone a successful or off-the-shelf application. You must also avoid developing solutions for problems that do not exist. We strongly suggest you find some real people who would benefit from an application. Some suggestions for application choice are provided below in the section ‘Selecting an Application’.
Assessment: Your application will be assessed on how well defined your users (‘personas’) are and how well the application meets the need of those intended users.