程序代写案例-W4

9/20/2021 (simon_week four)l.md
file:///C:/Users/Eric Zhao/Documents/3888/2021/(simon_week four)l.md 1/12
Individual Contribution Report - W4
Front
page
Student Name: Ruilin Li
Preferred Name: Simon Li
SID: 490443594
Unikey: ruli3642
Group Name: SOFT3888_M17_06_Group5
Tutor Name: Ronald Noronha
Project Name: CP13 - Web app for facilitating the research to design and deploy surveys in different languages
Client Name: Professor Judy Kay
Clear statement of work done
Week 2
Roles: Customer*
Contributions:
Introduction email and meeting arrangement to the client. [1]
Initialising discussions with client during the meeting, and writing meeting minutes (See [Team Meeting Minutes
16.08.2021](https://bitbucket.org/ruli3642/soft3888_m17_06_group5/wiki/Team Meeting Minutes/Team Meeting
Minutes 16.08.2021.pdf))
*To deliver a better communication experience to the client, customer role does have role rotation. I am responsible
for the responsibilities of customer role for the duration of the project.
Weekly Plan
Expected: Arrange and have meeting with client, start drafting user stories
Actual: Arrange and having meeting with client
Week 3
Roles: Customer
Contributions:
Formulating the epic structure of the user stories [2]
Communicating with other teams on epic allocation [3]
Completion of first draft of user stories and project scope statement [4]
Writing client meeting minutes (See [Client Meeting Minutes 26.08.2021]
(https://bitbucket.org/ruli3642/soft3888_m17_06_group5/wiki/Client Meeting Minutes/Client Meeting Minutes
26.08.2021.pdf))
9/20/2021 (simon_week four)l.md
file:///C:/Users/Eric Zhao/Documents/3888/2021/(simon_week four)l.md 2/12
Communicating to the client about our user stories, and proactively seeking feedback. [4]
Weekly Plan
Expected: Complete user stories and finalise project scope statement
Result: Project scope statement complete, minor adjustment to user stories still in progress
Week 4
Roles: Customer, Manager, Programmer
Contributions:
Communicating to the client about our user stories, and proactively seeking feedback for second draft. [5]
Arranging team meetings and making meeting minutes (See [Team Meeting Minutes 30.08.2021]
(https://bitbucket.org/ruli3642/soft3888_m17_06_group5/wiki/Team Meeting Minutes/Team Meeting Minutes
30.08.2021.pdf), [Team Meeting Minutes 02.09.2021]
(https://bitbucket.org/ruli3642/soft3888_m17_06_group5/wiki/Team Meeting Minutes/Team Meeting Minutes
02.09.2021.pdf))
Writing client meeting minutes (See [Client Meeting Minutes 26.08.2021]
(https://bitbucket.org/ruli3642/soft3888_m17_06_group5/wiki/Client Meeting Minutes/Client Meeting Minutes
26.08.2021.pdf))
Confirming the first sprint (See [Team Meeting Minutes 02.09.2021]
(https://bitbucket.org/ruli3642/soft3888_m17_06_group5/wiki/Team Meeting Minutes/Team Meeting Minutes
02.09.2021.pdf))
Weekly Plan
Expected: Confirming all minor details to user stories, setting up web services in preparation of first sprint, ERD
planning
Result: Confirming all minor details to user stories, setting up web services in preparation of first sprint, ERD
planning
Extent of Work
Week 2
On Monday Week 2, we were informed the client's contact detail and I sent an introduction email as Customer. I was
able to arrange a meeting with the client on Thursday, giving the team opportunity to learn and be briefed on the
context, challenge, and requirements of the project. I was engaging with the client and asking questions in the
meeting to gain a better understanding of the project, while making meeting minutes and notes for future references.
We were originally planned to write user stories after the meeting, but it was later decided that the time would be
better spent reading background materials and conducting preliminary research. Formulation of user stories was
therefore delayed to next week to ensure our user stories are quality and fits the needs of our client.
Week 3
As Customer, I formulated the epic structure of the project, and populated many user stories that I have developed.
This structure was appreciated by other groups and is adapted to the starting point of all user stories development.
We were then able to quickly generate ideas for user stories and submit it to the client for feedback. The client was
9/20/2021 (simon_week four)l.md
file:///C:/Users/Eric Zhao/Documents/3888/2021/(simon_week four)l.md 3/12
happy with our scope statement but wished us to make some minor adjustments to some particular entries of user
stories [15]. Due to delays in email correspondence, adjustments of user stories was pushed to next week.
Week 4
As Customer, I followed up on the changes to user stories on Monday. After some more minor changes were made
after W4 meeting, our user stories were approved by the client and facilitator Waheeb. After that, as manager of the
week I set out the agenda for next two week towards our first demo in week 7. It was decided that the first weekly
sprint will be on the account subsystem and second weekly sprint will be on survey response subsystem. I also pushed
forward some technical work in preparation of these two sprints. In particular, I assigned and assisted Cheng Chen the
task of deploying a Jenkins instance to our server and it was successful and will aid future developments. I have also
done technical work myself, which is discussed later in the report.
As Manager, I also prepared this week's team meeting minutes.
Quality of technical work done
Week 2
No technical work carried out. Week 2 was mainly spent making contact with the client and understanding the project.
Week 3
No technical work carried out. Week 3 was mainly spent formulating project scopes and deciding user story details.
Week 4
ERD Diagram
Our group created ERD Diagrams to plan out the rational relationships between different entities for the first sprint. In
a meeting (See [Team Meeting Minutes 02.09.2021]
(https://bitbucket.org/ruli3642/soft3888_m17_06_group5/wiki/Team Meeting Minutes/Team Meeting Minutes
02.09.2021.pdf), and [6]), the team collaboratively drew the diagrams necessarily for the basic login and register
feature of the account subsystem.
Cloud Server
Due to the limited quota provided by Bitbucket for continuous integration and development, it was decided that a
dedicated server is needed to deploy our own Jenkins instance. The acquisition of cloud service is done by me and I
have decided to use Google Cloud Platform for having $300 free trail for 3 months. The use of cloud service is
approved by the client for data compliance. I created an instance with 2 AMD Epyc cores, 2G memory and 40G SSD[7],
as well as configured the appropriate firewall to ensure security. [8]
A sub-domain is also set up using one of my existing domains for better access (instead of typing the IP address to the
server) [9]
PostgreSQL
After the server is deployed, a PostgreSQL instance is also installed [8] to support subsequent development agenda.
Technical details of our PostgreSQL instance can be found at [PostgreSQL]
9/20/2021 (simon_week four)l.md
file:///C:/Users/Eric Zhao/Documents/3888/2021/(simon_week four)l.md 4/12
(https://bitbucket.org/ruli3642/soft3888_m17_06_group5/wiki/Technical Documentation/PostgreSQL.md).
Other contribution to group processes
Week 2
Group Contract
The group collectively contributed to the group contract. I helped explaining the XP roles to other team members and
volunteered for the role of Customer. The group contract is signed by everyone in the team. See Group Contract
[Week 2~4](https://bitbucket.org/ruli3642/soft3888_m17_06_group5/wiki/Group Contract/Group Contract W2-4.pdf).
Mega Group Arrangement
After introducing ourselves to the client, we were informed by facilitator Waheeb that we are to be working other two
groups collectively for this project. To deliver the best results to the client, we discussed the best communication plan
for our circumstances. I participated heavily in these discussion to represent our group's opinion [10] and deescalated
situations when one of other group's member became fastrauted to the arrangement [11].
It was ultimately decided that each group will have an representative for project requirements, technical details, and
user experience. I represent my group for project requirement issues due to my XP role of Customer and my
knowledge in the domain.
Week 3
Jira
I set up the mega team Jira board and Slack integration [12], and configure the notification setting to be more
appropriate after team member feedbacks [13]. We were able to much more quickly communicate user stories, epics,
and tickets with Jira-Slack integration.
Week 4
No contribution to group processes of note that's outside my XP's roles' responsibilities and not already discussed.
Appendix
[1] The introduction email sent on Monday Week 2.
[2] Edit history of the epic structure of the whole project (including epics that would later be assigned to other groups)
9/20/2021 (simon_week four)l.md
file:///C:/Users/Eric Zhao/Documents/3888/2021/(simon_week four)l.md 5/12
[3] Screenshot of Slack discussion on our proposal of user stories epic framework, and epic allocation
9/20/2021 (simon_week four)l.md
file:///C:/Users/Eric Zhao/Documents/3888/2021/(simon_week four)l.md 6/12
[4] Email attaching first draft of project scope statement and user stories to the client.
9/20/2021 (simon_week four)l.md
file:///C:/Users/Eric Zhao/Documents/3888/2021/(simon_week four)l.md 7/12
[5] Email attaching second draft of project scope statement and user stories to the client.
[6] Screenshot of the zoom meeting and ERD Diagram collaboration.
9/20/2021 (simon_week four)l.md
file:///C:/Users/Eric Zhao/Documents/3888/2021/(simon_week four)l.md 8/12
[7] Screenshot of GCP Computing instance
[8] Screenshot of GCP firewall configuration + Postgres working
9/20/2021 (simon_week four)l.md
file:///C:/Users/Eric Zhao/Documents/3888/2021/(simon_week four)l.md 9/12
[9] Cloudflare configuration
[10] Screenshot of Slack discussion on inter-team communication
9/20/2021 (simon_week four)l.md
file:///C:/Users/Eric Zhao/Documents/3888/2021/(simon_week four)l.md 10/12
[11] Deescalating situation
9/20/2021 (simon_week four)l.md
file:///C:/Users/Eric Zhao/Documents/3888/2021/(simon_week four)l.md 11/12
[12] Jira Integration working
[13] Jira notification changes
[14] Other group's response to our user stories
9/20/2021 (simon_week four)l.md
file:///C:/Users/Eric Zhao/Documents/3888/2021/(simon_week four)l.md 12/12
[15] Client's response to our first draft

欢迎咨询51作业君
51作业君 51作业君

Email:51zuoyejun

@gmail.com

添加客服微信: ITCSdaixie