- To provide students with hands on experience testing, developing, and maintaining a backend server in
- To develop students’ problem solving skills in relation to the software development lifecycle.
- Learn to work effectively as part of a team by managing your project, planning, and allocation of
responsibilities among the members of your team.
- Gain experience in collaborating through the use of a source control and other associated modern team-based
- Apply appropriate design practices and methodologies in the development of their solution
- Develop an appreciation for product design and an intuition of how a typical customer will use a product.
To manage the transition from trimesters to hexamesters in 2021, UNSW has established a new focus on building
an in-house digital collaboration and communication tool for groups and teams to support the high intensity
Rather than re-invent the wheel, UNSW has decided that it finds the functionality of Microsoft Teams to be nearly
exactly what it needs. For this reason, UNSW has contracted out Penguin Pty Ltd (a small software business run
by Hayden) to build the new product. In UNSW’s attempt to try and add a lighter note to the generally fatigued and
cynical student body, they have named their UNSW-based product UNSW Streams (or just Streams for short).
Penguin Pty Ltd has sub-contracted two software firms:
BlueBottle Pty Ltd (two software developers, Andrea and Andrew, who will build the initial web-based GUI)
YourTeam Pty Ltd (a team of talented misfits completing COMP1531 in 21T3), who will build the backend
In summary, UNSW contracts Penguin Pty Ltd, who sub contracts:
BlueBottle (Andrea and Andrew) for frontend work
YourTeam (you and others) for backend work
Penguin Pty Ltd met with Andrea and Andrew (the frontend development team) 2 weeks ago to brief them on this
project. While you are still trying to get up to speed on the requirements of this project, Andrea and Andrew
understand the requirements of the project very well.
Because of this they have already specified a common interface for the frontend and backend to operate on. This
allows both parties to go off and do their own development and testing under the assumption that both parties will
comply with the common interface. This is the interface you are required to use.
The specific capabilities that need to be built for this project are described in the interface at the bottom. This is
clearly a lot of features, but not all of them are to be implemented at once.
3. Iteration 1: Basic Functionality and Tests
4. Iteration 2: Building a Web Server
NOTE: In merging the instructions for this iteration into your repo, you may get a failed pipeline. This is most likely
because your code is not pylint compliant. If this is the case, that is the first thing you should address for this
iteration. It is important you have a stable master branch before proceeding to add additional features.
In this iteration, more features were added to the specification, and the focus has been changed to HTTP
endpoints. Many of the theory surrounding iteration 2 will be covered in week 4-5 lectures. Note that there will still
be some features of the frontend that will not work because the routes will not appear until iteration 3.
In this iteration, you are expected to:
- Make adjustments to your existing code as per any feedback given by your tutor for iteration 1.
- Implement and test the HTTP Flask server according to the entire interface provided in the specification.
本网站支持淘宝 支付宝 微信支付 paypal等等交易。如果不放心可以用淘宝交易！
E-mail: email@example.com 微信:itcsdx