CPT202

Assignment 2
Group Report

Group X
Members:

Name Student ID Role

SM

PO

DV1

DV2

DV3

DV4

DV5

Table of Contents
Introduction 1

Sprint Execution 1
System Implementation 1
Implementation Overview 1

Section 1 1

Section 2 1

Section 3 1

Test Reports 2
Test Plan Summary 2

Section 1 2

Section 2 2

Section 3 2

Justification and Evaluation 2

Distribution of Work 2

Strength and Limitations 3

Potential Risks 3

Conclusion 3
References 4

Appendix 5
Sprint 1 Epics, Features, PBIs and Tasks 5

Sprint 2 Epics, Features, PBIs and Tasks 5

Sprint 3 Epics, Features, PBIs and Tasks 5

Sprint 4 Epics, Features, PBIs and Tasks 5

Sprint 5 Epics, Features, PBIs and Tasks 5

Sprint 1 Meeting Minutes 5

Sprint 2 Meeting Minutes 5

Sprint 3 Meeting Minutes 5

Sprint 4 Meeting Minutes 5

Sprint 5 Meeting Minutes 5

Introduction
An introduction providing an overview of the report, as necessary, refinements and
modifications of the requirements. Provide justifications for any changes or your insights
into problems. Also state clearly what your solution to the problem does and justify that
your approach shows overall major progress towards addressing the problem.

ljr

Sprint Execution
Describe the work you have actually undertaken in your Sprints. Refer to the Sprint
framework cycle and use a timeline to describe your own progress. Provide a summary
of your requirements. Use figures and tables when appropriate.

jcx

System Implementation
Implementation Overview
Use suitable diagrams, based on appropriate standards such as UML, that clearly
expose the static structure of the system (e.g. class and component diagrams or ER
diagrams) and its dynamic behaviour (e.g. sequence or other interaction diagrams, use
cases) on various detail levels (from the high-level architecture to the detailed design).
The overall structure of your software must be clear from this.

Core implementation tasks may be described using pseudo code, activity or state
machine diagrams. The complete code implemented to solve the problem must be
provided in Git repository and the access to the repository must be provided.

Use subsections to present your work with more details.

page
1 of 15
Software Architecture
diagram + text

class uml

db uml

Core Functions & Their Implementations

use case + sequence + activity + state

pseudocode frontend + backend + diagrams

Login-lyx
Register-lyx
Display Product Details-gzh
Edit Product Details-ryx
Delete Products-ryx
Search Products-gzh
Filter Products-gzh
Instant Message-ryx

Github Access
ljr

Test Reports
Explain the approaches used to ensure good quality code has been developed. Clearly
describe how the software has been tested from a user's as well as a developer's
perspective. Include test reports and discuss what of the system is working and where
issues still exist.

jcx

page
2 of 15
Test Plan Summary
Describe how you have planned and implemented your testing, including the methods
and techniques you used, number of test cases related to your system features, and the
test pass rate, etc.

jcx

Use subsections to present your work with more details.

Sprint 1 Testing
jcx

Sprint 2 Testing
jcx

Sprint 3 Testing
jcx

Sprint 4 Testing
jcx

Sprint 5 Testing
jcx

Justification and Evaluation

A justification and evaluation of the presented software system. Ensure your report
contains justifications for your design and implementation decisions and evaluates the
resulting software system based on the data obtained in the tests. Clearly state any
choices and assumptions that were made.

Distribution of Work
Briefly summarise each group member’s contributions. Provide justification for uneven
distribution.

Provide your agreed contribution of each group member (the percentage should add up
to 100%):

page
3 of 15
 Name Contribution Percentage (%)

15

15

15

10

10

10

10

10

SUM = 100

Strength and Limitations

Identify strengths as well as limitations of your software system and the potential risk in
the software development. Discuss how well your solution meets the requirements and
realises the intended functionality.

Potential Risks
Your report should also highlight where you have considered or been influenced by
legal, social, ethical and professional issues.

potential risks
tzx

legal issues
tzx

page
4 of 15
social issues
myq

ethical issue
myq

professionals
myq

Conclusion
Complete your report with a clear set of conclusions and a statement on future work.
Furthermore, the code for the final software must be included in an archive with the
report.

page
5 of 15
References
Put all your reference here, including any open-source packages or frameworks that
you’ve used.
Appendix
Compile the Sprint Backlogs, the related PBIs, Tasks, and the capacity allocation here.

Sprint 1 Epics, Features, PBIs and Tasks

zxh

Sprint 2 Epics, Features, PBIs and Tasks

zxh

Sprint 3 Epics, Features, PBIs and Tasks

zxh

Sprint 4 Epics, Features, PBIs and Tasks

sprint summary - gzh

pbi 2/4/5 - lyx

pbi 3 - ryx

pbi 1 - gzh

Sprint 5 Epics, Features, PBIs and Tasks

sprint summary - gzh

pbi ½ - ryx
pbi ¾ - gzh

Sprint 1 Meeting Minutes

zxh
Sprint 2 Meeting Minutes
zxh

Sprint 3 Meeting Minutes

zxh

Sprint 4 Meeting Minutes

zxh

Sprint 5 Meeting Minutes

zxh

Sprint 1 Testing Report

ljq

Sprint 2 Testing Report

ljq

Sprint 3 Testing Report

ljq

Sprint 4 Testing Report

ljq

Sprint 5 Testing Report

ljq