Fluent Essays

Case study and data model: Productive Tech case study and data model.pdf   Below are the tasks for the Individual (30\%) component. Note these are tasks you must complete, and submit, individually.CW2: individual tasks Page 1 of 1 7COM1081 Software Development Exercise Productive Tech 4 Work System Project: CW2 Individual Tasks This document gives details about the tasks you need to complete individually (NOT with your team). Please see the separate ‘team tasks’ document for details about the team element of this assessment. The tasks are described below in part 1 with the key summary against mark weightings listed as User Acceptance Tests (UATs) in part 2. 1. Individual Tasks In around 750 words, critically reflect on your experience of project and team management, based on the work you carry out for this assessment in a team. Note: this is an independent piece of work that you must complete on your own, despite references in your discussion to tasks you did with others. In your reflection, include discussions of all of the following: i. Reflection on technical knowledge gained Reflect on what you learned from this project. Which skills did you find the most beneficial/ interesting/challenging and why, e.g. data analysis, user interface design, coding, etc. ii. Reflection of project against software process model(s) characteristics Consider ways that Agile and/or Waterfall carry out design/implementation/testing and reflect with 1-2 examples of how your team may have adhered to these ways of working or those you did not adopt but feel may have been beneficial based on your experience. E.g. an Agile characteristic is the potential for Pair Programming during implementation. iii. Reflection of team roles Reflect on what YOUR role was in the team. Discuss the tasks you carried out with 1-2 examples of how you worked with others to complete tasks, challenges faced, and whether there were any changes to planned roles against reality. iv. Reflections for future projects: lessons learned Summarise your experience with key takeaways. Consider 1-2 examples of what you have learned and how you might approach project/team management again in future projects. 2. User Acceptance Tests (UATs) – Individual Tasks Final (raw) total out of 100 will be scaled to be worth 30\% for the module overall. For example, a raw total of 60 out of 100 means accumulating 18\% out of the possible 30\% for the module overall (calculation: 60 x 0.30 = 18). 1 Individual reflection on project and team management Mark a) Reflection of technical knowledge /25 b) Reflection against software process model(s) /25 c) Reflection of team roles /25 d) Reflections for future projects /25 FINAL TOTAL /100 2020-21CW2: team tasks Page 1 of 3 7COM1081 Software Development Exercise Productive Tech 4 Work System Project: CW2 Team Tasks This document gives details about the tasks you need to complete as a team. Please see the separate ‘individual tasks’ document for details about the individual element of this assessment. As a team, produce a design/implementation of the Productive Tech 4 Work System in the form of either a web- based prototype or wireframe-based prototype (not both), alongside a supplementary team report. These team tasks are described below in part 1 with the key summary against mark weightings listed as User Acceptance Tests (UATs) in part 2. Teams must also attend a mandatory demonstration viva to attain marks, described in part 3. With all team assessments, members are expected to make fairly equal contributions. This can take different forms, i.e. not just volume of work, but also organisation and leadership. Some examples of different team roles for this assessment include project management, screen design or coding web pages, database management, user interface considerations and evaluations, etc. N.B. Where there are contribution problems, students should inform module tutors. If tutors deem there is evidence of an unequal contribution, the team mark may be reduced for individuals with a lower contribution. 1. Team Tasks 1.1. Design and Implementation Use the UATs in part 2 to implement your prototype in ONE of two ways, referring to class notes. In either case, refer to the case study and data model supplied in the separate document. i. Web-based prototype: Use the EasyPHP platform (a WAMP stack utilising Windows, Apache, MySQL, PHP) to implement dynamic screens. This entails creating the database (use of MySQL can be managed via phpMyAdmin within EasyPHP) and carrying out object-relational mapping (ORM) to tie the backend database to your frontend application. You will use both server-side (PHP framework) and client-side (HTML and CSS) technologies. Ensure the prototype includes sample data, e.g. fictional representative records in tables. For this part of your submission, include a zip of your completed EasyPHP stack from its root, and include a .SQL file of your database structure (within phpMyAdmin, click the root of your database and choose the ‘export’ tab. Check the SQL file has both ‘create’ and ‘insert’ statements reflecting your database tables and sample data records). N.B. Choosing this prototype, you MUST use the provided platform. You can use additional libraries to enhance usability, such as Bootstrap for styling, but must ensure this is integrated within EasyPHP. OR ii. Wireframe-based prototype: Use diagram software/online tool to implement static screen designs. Screens must be high-fidelity, e.g. colour scheme and real data/navigation labels, i.e. not placeholders. Ensure the prototype includes sample data, e.g. fictional represen