Implementation and Report - Individual

CW2: 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 representative records in tables. Some

suggested tools are given in class practical notes, though you are welcome to experiment and choose

any relevant tool you are able to utilise. Irrespective of the tool, please ensure all your screen designs

are compiled into one document, i.e. do not submit a set of individual image files, e.g. use your tool to

export each screen as image files, and compile these into one Word or PDF document for this part of

your submission.

1.2. Documentation: Team Report

For the report, there are TWO tasks to complete and compile into one document as follows:

2020-21

CW2: team tasks

Page 2 of 3

i. Discussion on project management

In around 500-1000 words (as a guide, not a strict word count), discuss how your team organised the

CW2 project work and distributed tasks in your team. Include details of specific tools/techniques

adopted with evidence (e.g. screenshots), for example some of these methods you may have chosen to

adopt: the use of Kanban, estimation with Planning Poker, working in sprint cycles, testing and

validation, file sharing and version control, etc.

ii. Written evaluation of the prototype

In around 500 words (as a guide, not a strict word count), critically evaluate your prototype’s interface

(with screenshots of drilled down aspects of the interface) by considering some (but not necessarily all)

of Nielsen’s 10 usability heuristics and WCAG (Web Content Accessibility Guidelines), referring to class

notes. Include both aspects of strength, and aspects which may need further improvements to meet a

heuristic(s) or WCAG constraint.

2. User Acceptance Tests (UATs) – Team Tasks

Team instructions: implement a prototype (either web-based using Section 1 OR wireframe using

Section 2 but NOT BOTH), alongside design factors and documentation in Sections 3 and 4 Mark

1 Web-based prototype - by choosing this, do NOT also complete Section 2

Implement using the web framework provided to demonstrate the following

a) i) Add new developer [1 mark], ii) Add new technology [2 marks],

iii) Associate a technology with its developer [4 marks] /7

b) Add new employee /3

c) Technology rating: add/associate a technology with an employee’s score and details /7

d) Edit data by changing the developer who owns a particular technology /3

e) Drill downs: search/filter the display of all technologies classified as ‘wearable’ /3

f) Drill downs: search/filter the display of highly rated technologies currently used, i.e. those rated

with “I have used this technology” and a score of 5 /7

g) Advanced: choose some, but NOT all of the below to implement [check weightings]:

• Data reporting: display a view (via custom SQL) that shows the results of all technologies that

employees are interested in (i.e. “I would like to use this technology”), ranked in order of the

highest to lowest scores. Ensure the name of and RRP of each technology is listed beside its

respective total score. [10 marks]

• System access rights: entry to interface via a login screen with restriction of pages in the

navigation and/or functionality (such as read/write) for different users [10 marks]

• Batch processing and restricting data: the ability to set availability for all technologies supplied

by a given developer. Include a custom form field box(es) with input criteria to select a

developer and alter their technologies to ‘available’ or ‘unavailable’. Technologies that are

unavailable should not be possible to rate (by restricting data) [10 marks]

• Other additional features chosen by you [10 marks]

/10

Section 2 subtotal /40

2 Wireframe-based prototype - by choosing this, do NOT also complete Section 1

Implement screens using any diagram software/online tool to demonstrate the following Mark

a) Home screen, which is relevant to the scenario, e.g. shows easy navigation, latest data updates,

etc. in relation to developers, technologies, employees, ratings /5

b) Display of data: screens with details recorded for developers, employees, AND technologies /5

c) Addition of data for ONE aspect: developers, employees, OR technologies, e.g. technologies:

screen(s) with a form to add a new technology with screen(s) for confirmation and user feedback /2

d) Screen(s) that demonstrate the process of an employee providing a rating for a technology /3

CW2: team tasks

Page 3 of 3

Final (raw) total out of 100 will be scaled to be worth 50% for the module overall. For example, a raw total of 60 out of 100

means accumulating 30% out of the possible 50% for the module overall (calculation: 60 x 0.50 = 30).

3. Demonstration Viva

After the hand-in, your team MUST attend a demonstration (demo) viva (Q&A), which will be scheduled with

module tutors (acting as the client). Whilst the nature of this is not overly formal in nature, it is a formal,

mandatory part of the assessment and should be treated like an exam.

For the demo, module tutors will consider some of the UATs in part 2 to direct you in showcasing your

prototype ‘live’. The prototype used for the demo, and what will be assessed, must only be what is submitted.

The demo may be followed by Q&A led by module tutors. These questions will be based on your prototype and

supplied documentation, and against team roles.

The slot (demo and Q&A) for each team is up to 20 minutes (plus a few minutes for set-up).

N.B. Every member of the team needs to attend. Marks cannot be awarded to members without this. If you

cannot attend and have extenuating circumstances, you should seek advice from module tutors. Following the

demo, any alterations to the team mark, or marks for individuals (if there are concerns over contributions), will

be at the discretion of module examiners and moderators.

e) Drill downs: screen(s) that show how a user can search/filter the display of highly rated

technologies currently used, i.e. those rated with “I have used this technology” and a score of 5 /5

f) Documentation: in 500 words, describe in your own words how object-relational mapping works.

Illustrate with specific examples from your wireframe both a one-to-many, and many-to-many

relationship, discussing how these wireframe objects would map to a relational database based

on the data model supplied

/10

g) Advanced: choose some, but NOT all of the below to implement screen(s) of:

• System access rights: entry to interface via a login screen with restriction of pages in the

navigation and/or functionality (such as read/write) shown for different users [5 marks]

• Technology gallery: enhanced display of technologies with images [5 marks]

• Developer showcase: profile page for a developer with technologies they offer [5 marks]

• Other additional features chosen by you [10 marks]

/10

Section 3 subtotal /40

3 Interface design and user experience of the prototype (web or wireframe) Mark

a) Choice of colour scheme, design and layout, including workflow, e.g. users can complete actions

in one place and do not need to refer to other tables/pages for IDs /15

b) Error and/or feedback messages that are meaningful after user actions /5

c) User help, e.g. context-sensitive prompts (attracts higher marks) or generalised FAQ/user guide /10

Section 4 subtotal /30

4 Documentation

a) Discussion on project and team management /15

b) Written evaluation of the prototype: 500 words against Nielsen’s and WCAG /15

Section 4 subtotal /30

FINAL TOTAL /100