Microsoft Word - ProjectMarkingScheme.docx
Team Project Marking Scheme
Your API should include at least 2 controllers, and each controller needs to implement all 4
methods (GET, POST, PUT and DELETE). In the real world, some methods (e.g., post) may only
e available for internal user(s). In this project, you don’t need to wo
y about them.
The due date for source code and project report is November 28, 2021 (Sunday). One group
member submits the package to the dropbox on behalf of the whole group. The project needs
to be demonstrated lively, pre-record video is not acceptable.
Mark Weighted
Mark
1. Proposal 10 5
2. Implementation 50 20
XXXXXXXXXXData model and rational XXXXXXXXXX
XXXXXXXXXXData is in the cloud XXXXXXXXXX
XXXXXXXXXXUse Parameter stores to store the credentials XXXXXXXXXX
XXXXXXXXXXUse the repository pattern XXXXXXXXXX
XXXXXXXXXXUse AutoMapper XXXXXXXXXX
XXXXXXXXXXHttp Get method, GetAll & GetByID XXXXXXXXXX*1
XXXXXXXXXXHttp Post method XXXXXXXXXX
XXXXXXXXXXHttp Put method XXXXXXXXXX
XXXXXXXXXXHttp Delete method XXXXXXXXXX
XXXXXXXXXXContainerize your Web API and publish to AWS XXXXXXXXXX
XXXXXXXXXXUse Apigee to manage your published API XXXXXXXXXX
XXXXXXXXXXYour API proxy policy should include “Verify API key” XXXXXXXXXX
XXXXXXXXXXGenerate portal to support your potential API client(s XXXXXXXXXX
XXXXXXXXXXImplement a client to consume your published API, the
client can be Web app, mobile app or WPF app
XXXXXXXXXX15.1 Instantiate HttpClient object XXXXXXXXXX
XXXXXXXXXX15.2 invoke all 5 methods provided in your API, each
method invocation is 1 mark
XXXXXXXXXX*2
XXXXXXXXXXNon functional requirements XXXXXXXXXX
2 Presentation
10 5
XXXXXXXXXX.1 Functionalities XXXXXXXXXX
XXXXXXXXXX.2 Answer questions XXXXXXXXXX
ISDG is a core programming group that supports
939 Progress Avenue, Sca
orough, Ontario, Canada M1G 3T8
IT Project Proposal:
Submission date:
Submitted by:
Project Name and Description:
Briefly introduce the project.
Project Purpose/Goal(s): (be
ief)
Why do you like to undertake this project? What problem will be solved? Who will be the beneficiary of this project? What is the impact of not initiating this project?
Assumptions:
Describe the assumptions (resources, policies, schedules, technologies, etc.) upon which this plan is based.
Success Factors:
Describe the outcomes to be realized – distinguish between “must haves” and “nice to haves”. What will success look like / be measured once the project is complete?
Risk Factors:
Are there identifiable risks related to either the completion or non-completion of this project? These might include items such as security issues, regulatory concerns, public relations or institutional image factors, or academic potentials?
Projected Project Resources:
(outline what you know at this point in time)
Project Needs
Hardware
Software
Other (Please specify)
Group Project Proposal Template - Page 1 of 3
Group Project Proposal Template - Page 3 of 3