APPR6312POE

20; 21; 22; 23 2023
MODULE NAME: MODULE CODE:

APPLIED PROGRAMMING APPR6312
ASSESSMENT TYPE: POE (PAPER AND MARKING RUBRIC)
TOTAL MARK ALLOCATION: 300 MARKS
TOTAL HOURS: A minimum of 30 HOURS is suggested to complete this assessment
By submitting this assignment, you acknowledge that you have read and understood all the rules
as per the terms in the registration contract, in particular the assignment and assessment rules in
The IIE Assessment Strategy and Policy (IIE009), the intellectual integrity and plagiarism rules in
the Intellectual Integrity Policy (IIE023), as well as any rules and regulations published in the
student portal.
INSTRUCTIONS:
1. No material may be copied from original sources, even if referenced correctly, unless it is a
direct quote indicated with quotation marks. No more than 10% of the assignment may
consist of direct quotes.
2. Make a copy of your assignment before handing it in.
3. Assignments must be typed unless otherwise specified.
4. Begin each section on a new page.
5. Follow all instructions on the PoE cover sheet.
6. This is an individual assignment.
© The Independent Institute of Education (Pty) Ltd 2023

Page 1 of 21
20; 21; 22; 23 2023
Referencing Rubric
Providing evidence based on valid and referenced academic sources Markers are required to provide feedback to students by indicating
is a fundamental educational principle and the cornerstone of high- (circling/underlining) the information that best describes the
quality academic work. Hence, The IIE considers it essential to student’s work.
develop the referencing skills of our students in our commitment to
achieve high academic standards. Part of achieving these high Minor technical referencing errors: 5% deduction from the
standards is referencing in a way that is consistent, technically overall percentage. – the student’s work contains five or more
correct and congruent. This is not plagiarism, which is handled errors listed in the minor errors column in the table below.
differently.
Major technical referencing errors: 10% deduction from the
Poor quality formatting in your referencing will result in a penalty of overall percentage. – the student’s work contains five or more
according to the following guidelines a maximum of ten percent errors listed in the major errors column in the table below.
being deducted from the overall percentage. Please note, however,
that evidence of plagiarism in the form of copied or uncited work If both minor and major errors are indicated, then 10% only (and
(not referenced), absent reference lists, or exceptionally poor not 5% or 15%) is deducted from the overall percentage. The
referencing, may result in action being taken in accordance with examples provided below are not exhaustive but are provided to
The IIE’s Intellectual Integrity Policy (0023). illustrate the error.
Required: Minor errors in technical correctness of Major errors in technical correctness of
Technically correct referencing referencing style referencing style
style Deduct 5% from overall percentage. Deduct 10% from the overall percentage.
Example: if the response receives 70%, Example: if the response receives 70%, deduct
deduct 5%. The final mark is 65%. 10%. The final mark is 60%.
Consistency Minor inconsistencies. Major inconsistencies.
• The referencing style is generally • Poor and inconsistent referencing style used in-
• The same referencing format consistent, but there are one or two text and/or in the bibliography/ reference list.
has been used for all in-text changes in the format of in-text • Multiple formats for the same type of
references and in the referencing and/or in the bibliography. referencing have been used.
bibliography/reference list. • For example, page numbers for direct • For example, the format for direct quotes (in-
quotes (in-text) have been provided for text) and/or book chapters (bibliography/
one source, but not in another instance. reference list) is different across multiple
Two book chapters (bibliography) have instances.
been referenced in the bibliography in
two different formats.
Technical correctness Generally, technically correct with some Technically incorrect.
minor errors. • The referencing format is incorrect.
• Referencing format is • The correct referencing format has been • Concepts and ideas are typically referenced,
technically correct throughout consistently used, but there are one or but a reference is missing from small sections
the submission. two errors. of the work.
• Concepts and ideas are typically • Position of the references: references are only
• The correct referencing format referenced, but a reference is missing given at the beginning or end of large sections
for the discipline has been from one small section of the work. of work.
used, i.e., either APA, OR • Position of the references: references are • For example, incorrect author information is
Harvard OR Law only given at the beginning or end of provided, no year of publication is provided,
every paragraph. quotation marks and/or page numbers for
• Position of the reference: a • For example, the student has incorrectly direct quotes missing, page numbers are
reference is directly associated presented direct quotes (in-text) and/or provided for paraphrased material, the
with every concept or idea. book chapters (bibliography/reference incorrect punctuation is used (in-text); the
list). bibliography/reference list is not in
• For example, quotation marks, alphabetical order, the incorrect format for a
page numbers, years, etc. are book chapter/journal article is used,
applied correctly, sources in information is missing e.g. no place of
the bibliography/reference list publication had been provided (bibliography);
are correctly presented. repeated sources on the reference list.
Congruence between in-text Generally, congruence between the in-text A lack of congruence between the in-text
referencing and bibliography/ referencing and the bibliography/ referencing and the bibliography.
reference list reference list with one or two errors. • No relationship/several incongruencies
• There is largely a match between the between the in-text referencing and the
• All sources are accurately sources presented in-text and the bibliography/reference list.
reflected and are all accurately bibliography. • For example, sources are included in-text, but
included in the bibliography/ • For example, a source appears in the text, not in the bibliography and vice versa, a link,
reference list. but not in the bibliography/ reference list rather than the actual reference is provided in
or vice versa. the bibliography.
In summary: the recording of In summary, at least 80% of the sources are In summary, at least 60% of the sources are
references is accurate and correctly reflected and included in a incorrectly reflected and/or not included in
complete. reference list. reference list.
Overall Feedback about the consistency, technical correctness and congruence between in-text referencing and bibliography:

Page 2 of 21
20; 21; 22; 23 2023
Background
The Disaster Alleviation Foundation 1, a non-profit organisation, has approached you to build a
system for them. The foundation’s mission is to provide practical aid during disasters. They
receive donations from various sources and need a system to track what is available and what has
been dispatched to help with which disaster.
Donations can be made by individuals, companies, other organisations, and even governments.
Donations can be goods (clothes, non-perishable foods, etc.) or monetary. Donors can choose to
remain anonymous.
The Disaster Alleviation Foundation then needs to track what happens with the donations. For
example, goods can be dispatched to help with a disaster. And money can either be paid out (for
example, to a local community organisation) or used to purchase goods that are then dispatched
to a disaster area.
The Disaster Alleviation Foundation has transparency as one of its core values. It is important to
them that the collected data is accurate and always available to the right stakeholders. That is
why they want a web application with some pages visible to everyone, with summarised
information, and other pages accessible only to their employees (for editing data).
The requirements provided by the Disaster Alleviation Foundation are as follows:

1. The web application must use the colour scheme of the foundation – purple and orange.
2. Users must log in securely to the web application to be able to edit information.
3. The web application must allow authorised users to capture new monetary donations. The
date and amount are mandatory, but the donor may decide to remain anonymous.
4. The web application must allow authorised users to capture new goods donations. The
date, number of items, category, and description of each item are mandatory. But the
donor may decide to remain anonymous.
5. The web application must be pre-configured with the following categories of goods:
a. Clothes.
b. Non-perishable foods.
1
Fictional organisation. Any resemblance to a real organisation is purely coincidental.

Page 3 of 21
20; 21; 22; 23 2023
6. The web application must allow authorised users to define new categories of goods.
7. The web application must allow authorised users to capture a new disaster. The data for a
disaster includes the start date and end date, the location, and a description. It must also
be possible to specify the required aid types, such as water provision, clothing, food, etc.
8. The web application must allow authorised users to view the following lists:
a. All incoming monetary donations
b. All incoming goods donations
c. All disasters
9. The web application must allow authorised users to allocate money to an active disaster.
(Part 2 and PoE only)
10. The web application must allow authorised users to allocate goods to an active disaster.
(Part 2 and PoE only)
11. The web application must allow authorised users to capture the purchase of goods using
available money. This means that the available money decreases, and the goods are added
to the inventory of available goods and allocated to a specific disaster. (Part 2 and PoE only)
12. The web application must have a publicly accessible page that shows the following
information (PoE only):
a. Total monetary donations received.
b. Total number of goods received.
c. Currently active disasters, with the money and goods allocated to the disaster.
Instructions
In this Portfolio of Evidence (PoE), you will build a web application for the Disaster Alleviation
Foundation. You will use Azure DevOps and Azure Cloud services and complete various parts of
the application development life cycle.
The PoE consists of three parts that build on one another:

1. In part 1, you will plan the project using Azure Boards and implement a web application
prototype using Azure SQL Database and Azure App Services.
2. In part 2, you will set up a Git repository in Azure Repos and set up a build using Azure
Pipelines. And then, you will add a few features to the prototype.
3. In the final portfolio of evidence, you will add unit testing and automated deployments.
And you will add the finishing touches to the web application.

Page 4 of 21
20; 21; 22; 23 2023
The instructions below describe what you need to do and what you need to submit for each part.
Pay careful attention to the marking rubrics provided at the end of this document, using it as a
guideline for what is required and how much time to spend on each aspect.
Note that this portfolio of evidence does require working software. You will not receive marks for
web application features based on code that doesn’t compile and run.
Your lecturer will mark based on what you submit on Learn. So, ensure you include all the
required evidence in your submission. The evidence for each part must stand on its own, so it is
important that the change logs are comprehensive.
Tip: This portfolio of evidence will take some time to complete and may require additional
research to overcome any issues you encounter. Additionally, it requires internet access and
online systems. So, start early to avoid running into last-minute logistical issues such as loss of
internet connectivity.
Part 1 — Planning and Prototype (Marks: 100)

Learning Unit 1 – 2 (up to theme 3)
Create a project in Azure DevOps for this PoE and invite your lecturer as a team member.
Start by planning the project using Azure Boards. You have the full list of all the requirements that
will need to be met by the end of the project. You can use those requirements and break them
down further into specific work items that need to be completed.
Build an ASP.NET Core web application (using Azure SQL Server) that satisfies the following
requirements:
1. The web application must use the colour scheme of the foundation – purple and orange.
2. Users must log in securely to the web application to be able to edit information.
3. The web application must allow authorised users to capture new monetary donations. The
date and amount are mandatory, but the donor may decide to remain anonymous.
4. The web application must allow authorised users to capture new goods donations. The
date, number of items, category, and description of each item are mandatory. But the
donor may decide to remain anonymous.

Page 5 of 21
20; 21; 22; 23 2023
5. The web application must be pre-configured with the following categories of goods:
a. Clothes
b. Non-perishable foods
6. The web application must allow authorised users to define new categories of goods.
7. The web application must allow authorised users to capture a new disaster. The data for a
disaster includes the start date and end date, the location, and a description. It must also
be possible to specify the required aid types, for example, water provision, clothing, food,
etc.
8. The web application must allow authorised users to view the following lists:
a. All incoming monetary donations.
b. All incoming goods donations.
c. All disasters.
As you build the various features, update the work items in Azure Boards to reflect your progress.
Publish the web app to the Azure Cloud. You are not required to do this using Pipelines for this
part. A manual deployment is perfect.
Create a screen recording video of you demonstrating the features of the web application running
in the Azure Cloud. You may use an online screen recording service (such as Loom -
https://www.loom.com/) if you can make the video private but accessible via a link.
To submit for part 1:

• A Word or PDF document containing:
o The URL to the Azure DevOps project;
o Screenshots of everything that you created in Azure Boards. Show all the items that
you created and edited;
o Screenshots of all the pages in your web application;
o Screenshots of the configuration of the web app in the Azure Portal; and
o The URL to the deployed web application and credentials that your lecturer can use
to log in.
• A screen recording video (or link) of you demonstrating all the features of the web
application.
• A zip file containing all your source code.

Page 6 of 21
20; 21; 22; 23 2023
Part 2 — Continuous Integration and More Features (Marks: 100)

Learning Unit 1 – 3
In this second part, you will continue working on the code from part 1. But now, you will be
working in a Git repository.
Start by recreating a repository and committing your code from part 1. Then create a branch that
you will use to add the part 2 features. Next, make sure you are working on that branch.
First, implement any feedback you received from your lecturer on part 1. If you got full marks,
make improvements to your code or improvements to the user interface. Keep a list of the
changes you are making – you will need this for the change log you submit. And remember to
commit and push your changes frequently to the repository.
Add the following features to the web application:

1. The web application must allow authorised users to allocate money to an active disaster.
(Part 2 and PoE only).
2. The web application must allow authorised users to allocate goods to an active disaster.
(Part 2 and PoE only).
3. The web application must allow authorised users to capture the purchase of goods using
available money. This means that the available money decreases, and the goods are added
to the inventory of available goods and allocated to a specific disaster. (Part 2 and PoE
only).
Once you are satisfied with the code for this part, merge the branch.
Keep updating the items in Azure Boards as you complete the work.
Set up a build in Azure Pipelines to build the project every time a change is pushed to the
repository.
Create a screen recording video of you demonstrating the new features of the web application
running in the Azure Cloud. You may use an online screen recording service (such as Loom -
https://www.loom.com/) if you can make the video private but accessible via a link.

Page 7 of 21
20; 21; 22; 23 2023
To submit for part 2:

o Screenshots of the files in the Git repository;
o Screenshots of the commit history of the repository, including the branch and merge;
o Screenshots of the all the new pages in the web application;
o Screenshots of the updated items in Azure Boards;
o Screenshots of the Pipeline configuration and a successful build;
to log in; and
o A change log describing what was changed from part 1.
• A screen recording video (or link) of you demonstrating the new features of the web
application.

Page 8 of 21
20; 21; 22; 23 2023
Portfolio of Evidence — Continuous Testing and Deployment (Marks: 100)

All Learning Units
The web application is nearly complete (just one feature to add), but we still need to reach a point
where we can confidently automatically test and deploy the web app.
Create a branch for the PoE. Implement any feedback from part 2. If you got full marks, make
improvements to your code or improvements to the user interface. Keep a list of the changes you
are making – you will need this for the change log that you need to submit. And remember to
commit and push your changes frequently to the repository.
Add the following feature to the web application:
1. The web application must have a publicly accessible page that shows the following
information (PoE only):
a. Total monetary donations received
b. Total number of goods received
c. Currently active disasters, with the money and goods allocated to the disaster
Add unit tests to test any logic in the code, for example, to check that you cannot allocate more
goods than are available. Remember to commit and push frequently.
Merge the branch. Then change the build-in Azure Pipelines to also unit test and deploy your web
application to the Azure Cloud.
Remember to update your work items in Azure Boards as you complete them. Everything should
be done by the end of the PoE. You will need to submit evidence of that here.

Page 9 of 21
20; 21; 22; 23 2023
To submit for the PoE:

o Screenshot of all the items in Azure Boards;
o Screenshot of the files in the Git repository;
o Screenshot of the commit history of the repository, including the branch and merge;
o Screenshot of the all the pages in the web application;
o Screenshots of all the added unit tests;
o Screenshot of the unit tests results in Visual Studio;
to log in;
o Screenshots of the Azure Pipelines build configuration; and
o A change log describing what was changed from part 2.
• A screen recording video (or link) of you demonstrating all the features of the web
application.

Page 10 of 21
21; 22; 23 2023
Assessment Sheet (Marking Rubric)
Please note: Tear off this section and attach it to your work when you submit it/ If this is an online submission, then this information needs to be included
in the online submission.
MODULE NAME: MODULE CODE:

APPLIED PROGRAMMING APPR6312
STUDENT NAME:
STUDENT NUMBER:
PART 1 – PLANNING AND PROTOTYPE

Marking Criteria Does not meet the Meets the required Partially exceeds the Greatly exceeds the Feedback
required standard standard required standard required standard
(0% - 49%) (50% - 64%) (65% - 74%) (75% - 100%)
Skill: Creating a • No evidence was • All the requirements • All requirements and • All requirements and
plan in Azure submitted. are captured in Azure tasks are captured tasks are captured
Boards • No work items Boards. with sufficient detail. with a lot of detail.
created in Azure • All tasks are captured
[20 Marks] Boards. with minimal detail.
0 – 9 Marks 10 – 12 Marks 13 – 14 Marks 15 – 20 Marks
Skill: Updating work • No evidence was • All tasks are updated • All tasks are updated • All tasks are updated
items in Azure submitted. but with minimal detail but with some with a lot of additional
Boards as work is • No updates made in provided. additional detail detail provided.
completed Azure Boards. provided.
0 – 4 Marks 5 Marks 6 – 7 Marks 8 – 10 Marks

[10 Marks]

Page 11 of 21
21; 22; 23 2023

(0% - 49%) (50% - 64%) (65% - 74%) (75% - 100%)
Skill: Application • The feature is not • The feature is • The feature is well • The feature works
feature: Users can implemented or does implemented with implemented with perfectly without any
log in and only have not work at all. some bugs. only one or two bugs. errors.
access to restricted • The feature is
areas after logging implemented but
in there are lots of bugs.

[10 Marks]
feature: Monetary implemented or does implemented with implemented with perfectly without any
and goods not work at all. some bugs. only one or two bugs. errors.
donations can be • The feature is
captured implemented, but
there are lots of bugs.
[10 Marks] 0 – 4 Marks 5 Marks 6 – 7 Marks 8 – 10 Marks
Skill: Application • No pre-configured • The minimum required • Some additional • A comprehensive list
feature: categories are categories are included. categories are of categories is
Preconfigured included. included. included.
categories of goods
are available
0 – 1 Marks 2 – 3 Marks 4 Marks 5 Marks
[5 Marks]

Page 12 of 21
21; 22; 23 2023

(0% - 49%) (50% - 64%) (65% - 74%) (75% - 100%)
feature: New implemented or does implemented with implemented with perfectly without any
categories can be not work at all. some bugs. only one or two bugs. errors.
added • The feature is
implemented, but
[5 Marks] there are lots of bugs.
0 – 1 Marks 2 – 3 Marks 4 Marks 5 Marks
feature: A new implemented or does implemented with implemented with perfectly without any
disaster can be not work at all. some bugs. only one or two bugs. errors.
captured • The feature is
implemented, but
feature: The lists of implemented or does implemented with implemented with perfectly without any
items as per the not work at all. some bugs. only one or two bugs. errors.
requirements can • The feature is
be viewed implemented, but
[10 Marks] 0 – 4 Marks 5 Marks 6 – 7 Marks 8 – 10 Marks
published to Azure implemented or does implemented with implemented with perfectly without any
Cloud not work at all. some bugs. only one or two bugs. errors.
• The feature is
[10 Marks] implemented but

Page 13 of 21
21; 22; 23 2023

(0% - 49%) (50% - 64%) (65% - 74%) (75% - 100%)
Skill: Quality of • No video included. • Video demonstrates • The video goes • A comprehensive
video • The video does not just the basic features. somewhat beyond just video that
demonstration demonstrate most of demonstrating the demonstrates the
the functionality. basic features. features in an
[10 Marks] • Technical quality is so engaging way.
bad that it is
impossible to follow.

Page 14 of 21
21; 22; 23 2023
PART 2 – CONTINUOUS INTEGRATION AND MORE FEATURES

(0% - 49%) (50% - 64%) (65% - 74%) (75% - 100%)
Skill: Updates to • No change log was • The most significant • All feedback was • All feedback was
the application submitted. changes have been implemented, but no implemented, and
after part 1 • No changes have been made, but not all additional additional
made since part 1. feedback has been improvements were improvements were
[10 Marks] implemented. made. made.

Skill: Create a • No evidence was • Repository created and • Repository created • Repository created
repository and submitted. initial code committed and initial code and initial code
commit the initial • No repository was with very basic commit committed with some committed with a
code created. comment. useful information in comprehensive
• The repository exists, the commit comment. commit comment.
[10 Marks] but no code has been
committed.

Skill: Branch and • No evidence was • Branch created and • Branch created and • Branch created and
merge in the submitted. merged with minimal merged with some merged with
repository • No branch was comments. information in the comprehensive
created. commit comment. commit comment.
[10 Marks] • Branch created but not
merged.

Page 15 of 21
21; 22; 23 2023

(0% - 49%) (50% - 64%) (65% - 74%) (75% - 100%)
Skill: Regular • No evidence was • More than 5 commits • Commits with commit • Fully detailed commit
commits to the submitted. • Commits with very comments that are comments, including
repository • No further commits brief commit sufficiently detailed to Azure Board links to
made after the initial comments. know what is included. tasks.
[10 Marks] commit. • No Azure Board links.
• Less than 5 commits
with no useful commit
comments.
Skill: Work items in • No evidence was • All tasks are updated • All tasks are updated • All tasks are updated
Azure Boards are submitted. but with minimal detail but with some with a lot of additional
updated when • No updates made in provided. additional detail detail provided.
work is done Azure Boards. provided.
[10 Marks]

feature: Allocate implemented or does implemented with implemented with perfectly without any
money to a disaster not work at all. some bugs. only one or two bugs. errors.
• The feature is
[10 Marks] implemented but

Page 16 of 21
21; 22; 23 2023

(0% - 49%) (50% - 64%) (65% - 74%) (75% - 100%)
feature: Allocate implemented or does implemented with implemented with perfectly without any
goods to a disaster not work at all. some bugs. only one or two bugs. errors.
• The feature is
[10 Marks] implemented, but
feature: Capture implemented or does implemented with implemented with perfectly without any
the purchase of not work at all. some bugs. only one or two bugs. errors.
goods • The feature is
implemented, but
Skill: Pipeline • No evidence was • The pipeline build has • The pipeline build has • The pipeline build has
configured and submitted. been configured. been configured. been configured.
build successful • Pipeline build doesn’t • A configuration file can • The build has been run • Configuration is clearly
succeed. be structured better. successfully. structured.
[10 Marks] • The build has been run
successfully.

Page 17 of 21
21; 22; 23 2023

(0% - 49%) (50% - 64%) (65% - 74%) (75% - 100%)
bad that it is

Page 18 of 21
21; 22; 23 2023
PORTFOLIO OF EVIDENCE – CONTINUOUS TESTING AND DEPLOYMENT

(0% - 49%) (50% - 64%) (65% - 74%) (75% - 100%)
Skill: Updates to • No change log was • The most important • All feedback was • All feedback was
the application submitted. changes have been implemented, but no implemented, and
after part 2 • No changes made made, but not all additional additional
since part 2. feedback has been improvements were improvements were
[10 Marks] implemented. made. made.

Skill: Azure Boards • No evidence was • All tasks are updated • All tasks are updated • All tasks are updated
fully up to date submitted. but with minimal detail but with some with a lot of additional
with project status • No updates were provided. additional detail detail provided.
made in Azure Boards. provided.
[10 Marks]

Skill: Repository up • No evidence was • Branch and merge • Branch and merge • Branch and merge
to date with new submitted. done. done. done.
branch, changes, • No further commits • Commits are made on • Commits are made on • Commits are made on
and merge were made after the the branch with basic the branch with the branch with fully
initial commit. commit comments. commit comments detailed commit
[10 Marks] • No branch and merge. with some detail. comments.

Page 19 of 21
21; 22; 23 2023

(0% - 49%) (50% - 64%) (65% - 74%) (75% - 100%)
feature: public implemented or does implemented with implemented with perfectly without any
statistics page not work at all. some bugs. only one or two bugs. errors.
implemented • The feature is
according to implemented, but
requirements there are lots of bugs.

[20 Marks]
Skill: Unit tests • No evidence was • Working unit tests have • Working unit tests • Comprehensive unit
added to the code submitted. been implemented for have been tests have been
base • No unit tests were the most important implemented for most implemented for all
added. functionality. logic. logic.
[20 Marks] • Unit tests don’t
compile.
• Unit tests don’t test
anything useful.
Skill: A configured • No evidence was • The pipeline runs unit • The pipeline runs unit • The pipeline runs unit
pipeline to test and submitted. tests. tests. tests.
deploy, and build • No changes made to • The pipeline doesn’t • Pipeline successfully • Pipeline successfully
succeeds the pipeline. deploy the app. deploys the web app. deploys the web app.
• The pipeline doesn’t • Pipeline makes use of
[20 Marks] build. advanced features.

Page 20 of 21
21; 22; 23 2023

(0% - 49%) (50% - 64%) (65% - 74%) (75% - 100%)
bad that it is
[TOTAL MARKS: 100]

Page 21 of 21

APPR6312POE

Uploaded by

Document Information

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

APPR6312POE

Uploaded by

Copyright:

Available Formats

20; 21; 22; 23 2023

MODULE NAME: MODULE CODE:

ASSESSMENT TYPE: POE (PAPER AND MARKING RUBRIC)

TOTAL MARK ALLOCATION: 300 MARKS

TOTAL HOURS: A minimum of 30 HOURS is suggested to complete this assessment

© The Independent Institute of Education (Pty) Ltd 2023

© The Independent Institute of Education (Pty) Ltd 2023

The requirements provided by the Disaster Alleviation Foundation are as follows:

© The Independent Institute of Education (Pty) Ltd 2023

The PoE consists of three parts that build on one another:

© The Independent Institute of Education (Pty) Ltd 2023

Part 1 — Planning and Prototype (Marks: 100)

© The Independent Institute of Education (Pty) Ltd 2023

To submit for part 1:

© The Independent Institute of Education (Pty) Ltd 2023

Part 2 — Continuous Integration and More Features (Marks: 100)

Add the following features to the web application:

© The Independent Institute of Education (Pty) Ltd 2023

To submit for part 2:

© The Independent Institute of Education (Pty) Ltd 2023

Portfolio of Evidence — Continuous Testing and Deployment (Marks: 100)

Add the following feature to the web application:

© The Independent Institute of Education (Pty) Ltd 2023

To submit for the PoE:

© The Independent Institute of Education (Pty) Ltd 2023

Assessment Sheet (Marking Rubric)

MODULE NAME: MODULE CODE:

PART 1 – PLANNING AND PROTOTYPE

0 – 4 Marks 5 Marks 6 – 7 Marks 8 – 10 Marks

© The Independent Institute of Education (Pty) Ltd 2023

PART 1 – PLANNING AND PROTOTYPE

0 – 4 Marks 5 Marks 6 – 7 Marks 8 – 10 Marks

© The Independent Institute of Education (Pty) Ltd 2023

PART 1 – PLANNING AND PROTOTYPE

© The Independent Institute of Education (Pty) Ltd 2023

PART 1 – PLANNING AND PROTOTYPE

© The Independent Institute of Education (Pty) Ltd 2023

PART 2 – CONTINUOUS INTEGRATION AND MORE FEATURES

0 – 4 Marks 5 Marks 6 – 7 Marks 8 – 10 Marks

0 – 4 Marks 5 Marks 6 – 7 Marks 8 – 10 Marks

0 – 4 Marks 5 Marks 6 – 7 Marks 8 – 10 Marks

© The Independent Institute of Education (Pty) Ltd 2023

PART 2 – CONTINUOUS INTEGRATION AND MORE FEATURES

0 – 4 Marks 5 Marks 6 – 7 Marks 8 – 10 Marks

© The Independent Institute of Education (Pty) Ltd 2023

PART 2 – CONTINUOUS INTEGRATION AND MORE FEATURES

© The Independent Institute of Education (Pty) Ltd 2023

PART 2 – CONTINUOUS INTEGRATION AND MORE FEATURES

© The Independent Institute of Education (Pty) Ltd 2023

PORTFOLIO OF EVIDENCE – CONTINUOUS TESTING AND DEPLOYMENT

0 – 4 Marks 5 Marks 6 – 7 Marks 8 – 10 Marks

0 – 4 Marks 5 Marks 6 – 7 Marks 8 – 10 Marks

0 – 4 Marks 5 Marks 6 – 7 Marks 8 – 10 Marks

© The Independent Institute of Education (Pty) Ltd 2023

PORTFOLIO OF EVIDENCE – CONTINUOUS TESTING AND DEPLOYMENT

0 – 9 Marks 10 – 12 Marks 13 – 14 Marks 15 – 20 Marks

© The Independent Institute of Education (Pty) Ltd 2023

PORTFOLIO OF EVIDENCE – CONTINUOUS TESTING AND DEPLOYMENT

[TOTAL MARKS: 100]

© The Independent Institute of Education (Pty) Ltd 2023

You might also like