Csit321 Fyp-21-S1-03 Progress Report

CSIT321
Progress Report
FYP-21-S1-03P
G-Buy
Written by
Van Phuong Thanh (6859598)
Ang Ding Xun (6744333)
Goh Elshender Ernest (6462054)
Lim Xin Rou (6650193)
Yang Haoxiong (6650387)
01st May 2021
1
Contents
Progress Report Week 1...................................................................................................................3
Progress Report Week 4..................................................................................................................11
Progress Report Week 10...............................................................................................................22
2
Progress Report Week 1
Progress Report Date: 10/01/2021

Team FYP-21-S1-03P
Project Name G-Buy
Reporting Period 04 January 2021 – 10 January 2021
Work completed
1. Formation of project team and familiarization of team members
2. Communication channels setup (WhatsApp, Teams)
3. Documentation repository setup (Sharepoint)
4. Common understanding of project requirements
5. Agreement to what the application needs to be like and what
technologies to be used
6. Agreement to platform to be used for versioning and development
Work targeted to complete
1. Draft templates for documentation submission
2. Draft Project Proposal
3. Self-reading on Laravel and Github
4. Setup of Github environment by Van
Items proceeding well
Majority of team members have already participated in IT projects
before and know what is required of them. There is also working
knowledge on the technologies required to make this project work.
Items of concern
Two members do not have coding experience and may
need significant guidance when writing the application.
Suggestions/Follow-up
Project Manager will delegate roles effectively that makes best use of
everyone’s skillsets.
3
Project Requirements
4
Communication channels setup (WhatsApp, Teams)
5
Documentation repository setup (Sharepoint)
6

Team FYP-21-S1-03P
Project Name G-Buy
Reporting Period 11 January 2021 to 17 January 2021
Work completed
1. Assignment of project portions out to team members.
2. Discussion of potential problems that could be faced and placed
in risk register.
3. Discussion on current industry players and their business
strategies.
4. 2nd discussion on draft of project proposal.
5. Agreement on meeting minutes template.
1. Team members to create their own GitHub account and
download GitHub desktop and Laravel installers.
2. Work on feedback provided on Project Proposal draft.
3. Staging code to be uploaded into GitHub.
Due to their prior experience in project participation, members were
quick to offer their insights on potential project risks and volunteer for
the different project roles.
Items of concern
As everyone else other than Van are not familiar with GitHub and
Laravel, installation and configuration of both software were found to be
complex and multiple team members experienced errors when trying to
configure onto their own separate local environments.
Van to provide private guiding sessions to guide members on steps of
installing GitHub and Laravel.
7

Team FYP-21-S1-03P
Project Name G-Buy
Work completed
1. All team members have created their GitHub accounts
and two team members have successfully installed and configured
both GitHub and Laravel onto their local environments.
2. 3rd discussion on draft of Project Proposal
3. Discussion on draft of Project Requirements Specifications
4. High level discussion and breakdown of Project timeline for all
members
5. Discussion on frontend wireframe
6. 1/3 of staging code uploaded into GitHub
1. Remaining two members to complete their Laravel installations
2. Remaining staging code to be uploaded into GitHub
3. Work on feedback provided on Project Proposal draft
4. Work on feedback provided on Project Requirements
Specifications
Work on both Project Proposal and Project Requirements
Specifications are on track.
Items of concern
Remaining two members who have yet to install Laravel have
highlighted that they have experienced errors and Van is aware and
currently assisting them.
Van to continue assisting to troubleshoot their installations.
8
 All team members have created their GitHub accounts and two
team members have successfully installed and configured both
GitHub and Laravel onto their local environments.
 3 discussion on draft of Project Proposal
rd
 Discussion on draft of Project Requirements Specifications
High level discussion and breakdown of Project timeline for all members
1/3 of staging code uploaded into GitHub
9
Discussion on frontend wireframe
10

Team FYP-21-S1-03P
Project Name G-Buy
Work completed
1. 2/3 of staging code uploaded into GitHub
2. Discussion on Project marketing website
3. Final discussion on Project Proposal and Project Requirements
Specifications
4. Discussion on prototype requirements
5. Final two members have completed installation and configuration
of Laravel onto their local environments
1. Prototype to be setup on proto.io platform
2. Marketing website to be setup on weebly.com
3. Changes to be made to Risks section in Project Proposal to
include appropriate colour coding
4. Work on feedback provided on Project Proposal and Project
Requirements Specifications
Project Proposal and Project Requirements Specifications are on
track. Team members also quickly came to an agreement to the
outlook of the marketing website and prototype.
Items of concern
Ernest highlighted that he might not have sufficient time to work on the
Project Proposal as he has other commitments this week that clash
with the project schedule. He will update again.
Project Manager will monitor progress on the Project Proposal
separately.
11
Final discussion on Project Proposal and Project Requirements
Specifications
Discussion on prototype requirements
12
Final two members have completed installation and configuration of
Laravel onto their local environments
13

Team FYP-21-S1-03P
Project Name G-Buy
Reporting Period 01 February 2021 to 07 February 2021
Work completed
1. Remainder of staging code has been uploaded into GitHub.
2. Draft of Project marketing website completed.
3. Draft of wireframe completed.
1. Typesetting and formatting of Project Proposal.
2. Typesetting and formatting of Project Requirements
Specifications.
Work on both marketing website and wireframe are on track and work
continues.
Items of concern
Project Proposal and Project Requirements Specifications
have slightly overrun allotted time due to oversight.
1. Ernest has assured the team that Project Proposal will meet
targeted submission date on Chinese New Year
(13/02/2021) despite being behind on time as only some content
changes are due to be made.
2. Van has assured the team that Project Requirements
Specifications will meet targeted submission
date (13/02/2021) despite being behind on time as only some
content changes are due to be made.
14
15

Team FYP-21-S1-03P
Project Name G-Buy
Work completed
1. Completed and submitted Project Proposal
2. Completed and submitted Project Requirements Specifications
3. Marketing website pages (Home, About, Contact Us) completed
4. Initial look of wireframe completed
1. Marketing website (Project Documentation) to be worked on
2. Wireframe (page navigation and page description)
1. Marketing website is mostly complete and team members are
satisfied with the look and feel of the site.
2. Team members are satisfied with the look and feel of the
wireframe
Items of concern
The Lunar New Year public holidays 13/02/2021 and 14/02/2021 fall
in this week and work will likely slow down or not be done during these
two days.
Project Manager to monitor progress of both items separately with
members responsible.
16
 Completed and submitted Project Proposal
 Completed and submitted Project Requirements Specifications
Initial look of wireframe completed
17

Team FYP-21-S1-03P
Project Name G-Buy
Reporting Period 15 February 2021 to 21 Februay 2021
Work completed
1. Marketing website (Project Proposal and Project Requirements
Specifications uploaded)
2. Discussion on prototype requirements
1. Marketing website (upload meeting minutes, Project Progress
Report and Project Schedule)
1. Prototyping is largely completed. Several cosmetic changes to be
implemented.
Items of concern
1. Ernest report slight delay in completing marketing website due to
other commitments, he will put in more time this week to catch up.
2. Ding Xun reported slight delay to be expected in
providing Project Schedule as original one needs to be amended
but should be on track for marketing website to be completed by
end of Week 8.
Nil
18
 Discussion on prototype requirements
 Marketing website (Project Proposal and Project Requirements
Specifications uploaded)
19

Team FYP-21-S1-03P
Project Name G-Buy
Work completed
1. Marketing website (meeting minutes and Project Schedule
uploaded)
1. Marketing website (upload Project Progress Report)
2. Team members to peruse prototype and feedback on changes
needed
Marketing website is on track so far.
Items of concern
1. Ernest reported that he is experiencing some difficulties with a
particular section of HTML code for the marketing website.
2. Xin Rou and Haoxiong report changes highlighted in prototyping
have experienced some issues.
Ding Xun and Van will assist Ernest and Xin Rou/Haoxiong in
troubleshooting.
Marketing website (meeting minutes and Project Schedule uploaded)
20
21

Team FYP-21-S1-03P
Project Name G-Buy
Reporting Period 01 March 2021 to 07 March 2021
Work completed
1. Marketing site completed.
2. Issues with prototype highlighted last week have been ironed out.
1. Final touches on prototype for demo.
2. Presentation slides for prototype demo.
1. Market website was completed with expert assistance from Ding
Xun and Van.
2. Prototype issues highlighted last week were ironed out with expert
assistance from Ding Xun and Van.
Items of concern
The team members each have a busy schedule this week and may not
be able to commit the time required to complete the targets for this
week.
As the project is well before schedule, some work can be postponed till
the next work week.
22

Team FYP-21-S1-03P
Project Name G-Buy
Work completed
Prototype for demo.

2. Checking of documentation, prototype and marketing website
by team members.
The prototype was completed despite the team having little to no time
for tasks last week.
Items of concern
The team will need to ensure that the presentation slides are done in
time and also review all documents and source code.
The team will work closely together next week to ensure all potential
issues have been addressed.
23
24
Prototype for demo and created our logo.
25

Team FYP-21-S1-03P
Project Name G-Buy
Work completed
2. Checking of project documentation, prototype and marketing
website.
Discussion on Phase 2 of project implementation
Nil
Items of concern
Nil
Nil
26
Presentation slides for prototype demo.
Checking of project documentation, prototype and marketing website.
27

Team FYP-21-S1-03P
Project Name G-Buy
Reporting Period 22 March 2021 to 28 March 2021 
Work completed
Presentation (Slides and wireframe demonstration).
General discussion on Phase 2 of project implementation.
What is proceeding well
The presentation went well generally without a hitch.
What needs attention

As the team agreed to take a one-week hiatus until the start of Week
13, we will need to eyeball development from then on to ensure that
documentation and testing can begin as soon as possible.
Suggestions/Followup
The team will need to work more closely than ever before and
overcommunicate due to the fast-approaching deadline. Ad-hoc and
off-channel communications will be more frequent.
28

Team FYP-21-S1-03P
Project Name G-Buy
Reporting Period 29 March 2021 to 04 April 2021 
Work completed

1. Discussion on configuration of VM in Azure.
2. Discussion on system integration.
3. Begin to build UI of platform.
4. Restoration of staging environment in backend
tech’s replacement machine.
Nil

Backend tech’s harddisk crashed, resulting to a loss of all data. A
backup of application source code is fortunately saved online. The
backup is slightly dated, thus, development has been set back by
3 man days.
Project manager and front-end tech will work closely with the backend
tech to align his environment to the team’s and help rebuild the lost
code as soon as possible to cut down the 3 days lost down to 1.
29

Team FYP-21-S1-03P
Project Name G-Buy
Reporting Period 05 April 2021 to 11 April 2021 
Work completed
1. Discussion on configuration of VM in Azure.
2. Discussion on system integration.
3. Restoration of staging environment in backend tech’s new
machine.
4. Front end tech has finished setting up the skeleton UI of the
platform’s homepage, profile page and product page.
1. Configuration of Windows VM in Azure.
2. Draft of Test Plan, Technical Manual, Technical Report and User
Manual.
3. Populating buttons, icons and placeholder images and
hardcode so that the backend can integrate the frontend with the
backend.
While the backend tech suffered severe data loss last week, he was
able to restore most of his lost code with help from the frontend
tech and was able to cut down the lost man days down from 3 to 2 and
start development again.
Delay of 2 days in development.
30
The coding team will continue to work closely together and ensure
development can catch up to the original timeline.
31
Front end tech has finished setting up the skeleton UI of the platform’s
homepage, profile page and product page.
32
 Discussion on configuration of VM in Azure.
 Discussion on system integration
33

Team FYP-21-S1-03P
Project Name G-Buy
Work completed
1. Test plan, Technical Manual, Technical Report and User
Manual have been drafted.
2. Work on platform buttons, icons and placeholder images and
hardcode has been completed.
Project manager to vet through drafts and give the go-ahead if
documents can be used by the team for updating.
Development is now up to speed and in accordance to our
internal high-level timeline.
Billing issues surfaced when trying to create a VM in Azure.
Contact Microsoft support and create a service request for assistance.
Test plan, Technical Manual, Technical Report and User Manual have
been drafted.
34
35

Team FYP-21-S1-03P
Project Name G-Buy
Work completed
Vetting of draft documents for the team to work on.

1. Test plan, Technical Manual, Technical Report and User Manual.
2. Provisioning of VM in Azure.
3. UI/UX of platform.
4. Backend logic to integrate the homepage, profile page and
product page.
The technical report is on track for completion and should be ready for
vetting by the end of next week.
1. Microsoft support has not resolved the billing issues in Azure and
the provision of the VM remains on limbo.
2. User manual and test plan will need to be expedited when the
platform is ready for initial testing.
Further communication with Microsoft support to iron out the
Azure billing issues and have the VM up and running by the mid next
week.
36
Vetting of draft documents for the team to work on.
37

Team FYP-21-S1-03P
Project Name G-Buy
Reporting Period 26 April 2021 to 02 May 2021 
Work completed
1. VM successfully provisioned in Azure.
2. Technical report ready for vetting.
3. Backend logic for home, profile and product pages are done.
4. UI for above 3 pages has been further enhanced.
1. Setup OS and required tools in VM.
2. UI for remaining pages.
3. Logic for remaining pages.
4. Begin testing of platform.
With the VM provisioned, it should be relatively easy and fast to put it
into commission due to the team’s experience in setting up Windows
Server.
1. Testing of platform needs to start as the soonest to allow time for
bug fixes.
2. Backend has reported difficulties in implementing Stripe API that
is necessary for payments.
1. Tester will work closely together with coding team to allow for
expedited testing as and when possible.
2. Stripe FAQ and guides to be referred to and technical support to
be contacted if needed.
38
 VM successfully provisioned in Azure.
 Technical report ready for vetting.
 Backend logic for home, profile and product pages are done.
 UI for above 3 pages has been further enhanced
39

Team FYP-21-S1-03P
Project Name G-Buy
Reporting Period 03 May 2021 to 09 May 2021 
Work completed
1. VM OS has been configured and required tools have been
installed.
2. Initial ad-hoc testing of platform.
1. Upload backend logic to VM.
2. Amendments to Technical Report.
3. Continue work on Technical Manual.
4. Continue work on Test Plan.
5. Logic for remaining pages.
Testing has been reported to be well underway with the team working
closely and assisting each other.
1. Backend has reported that implementation of Stripe API has been
completed but minor bugs that affect useability of payment
method needs to be addressed before the platform can start
accepting electronic payments.
2. Frontend has reported that UI for remaining pages needs more
time.
3. User manual needs a lot of work.
1. Stripe FAQ and guides to be referred to and technical support to
be contacted if needed.
2. User manual to be expedited on.
40
41

Team FYP-21-S1-03P
Project Name G-Buy
Reporting Period 10 May 2021 to 16 May 2021 
Work completed
1. Backend logic uploaded to VM.
2. Amendments to Technical Report completed.
3. UI for the rest of the pages
1. Test Plan.
2. Technical Manual.
3. Preliminary check on Technical Report.
4. Minor bugfixes on UI for remaining pages.
5. Begin work on User Manual
UI is largely done for the platform and the frontend can spare more
time to assist the backend in the logic.
Work on the Test Plan, Technical Manual and User Manual is slow.
Project manager, platform manager and product manager will work
closely together and help each other in each of the three documents.
42
Some issues solved and back-end logic uploaded to VM.
Class diagram added then Technical Report completed
43

Team FYP-21-S1-03P
Project Name G-Buy
Reporting Period 17 May 2021 to 23 May 2021
Work completed
1. Test Plan.
2. Technical Manual.
3. User Manual.
4. Backend logic for platform.
1. Presentation slides.
2. Preliminary rechecking of all required project documentation.
3. Uploading of all necessary documentation to marketing site.
Development work is mostly done, with the coding team working on
bugs reported by testing.
Documentation needs to be thoroughly checked through to ensure no
lapse in deliverables.
Project manager to hold frequent ad-hoc meetings with all or several
members to ensure no document has been left out.
44
Test Plan completed on 22/05
Technical Manual completed on 22/05
User Manual completed on 22/05
45
Backend logic for platform.
46

Csit321 Fyp-21-S1-03 Progress Report

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Csit321 Fyp-21-S1-03 Progress Report

Uploaded by

Copyright:

Available Formats

CSIT321

01st May 2021

Progress Report Date: 10/01/2021

Progress Report Date: 17/01/2021

Progress Report Date: 24/01/2021

Van to continue assisting to troubleshoot their installations.

 Discussion on draft of Project Requirements Specifications

1/3 of staging code uploaded into GitHub

Progress Report Date: 31/01/2021

Discussion on prototype requirements

Progress Report Date: 07/02/2021

Progress Report Date: 14/02/2021

Initial look of wireframe completed

Progress Report Date: 21/02/2021

Progress Report Date: 28/02/2021

Marketing website is on track so far.

Marketing website (meeting minutes and Project Schedule uploaded)

Progress Report Date: 07/03/2021

Progress Report Date: 14/03/2021

Work targeted to complete

Progress Report Date: 21/03/2021

Discussion on Phase 2 of project implementation

Checking of project documentation, prototype and marketing website.

Progress Report Date: 29/03/2021

Presentation (Slides and wireframe demonstration).

Work targeted to complete

General discussion on Phase 2 of project implementation.

What is proceeding well

The presentation went well generally without a hitch.

What needs attention

Progress Report Date: 04/04/2021

General discussion on Phase 2 of project implementation.

Work targeted to complete

What needs attention

General discussion on Phase 2 of project implementation.

Progress Report Date: 11/04/2021

Delay of 2 days in development.

Progress Report Date: 18/04/2021

Billing issues surfaced when trying to create a VM in Azure.

Contact Microsoft support and create a service request for assistance.

Progress Report Date: 25/04/2021

Vetting of draft documents for the team to work on.

Work targeted to complete

Progress Report Date: 02/05/2021

Progress Report Date: 09/05/2021

Progress Report Date: 16/05/2021

Work on the Test Plan, Technical Manual and User Manual is slow.

Class diagram added then Technical Report completed

Progress Report Date: 23/05/2021

Technical Manual completed on 22/05

User Manual completed on 22/05

You might also like