Skip to content

Latest commit

 

History

History
113 lines (71 loc) · 16 KB

README.md

File metadata and controls

113 lines (71 loc) · 16 KB

Radford college crest

Student name/ID: Will Pak Poy (0521858)
Course: Digital Technologies
Unit name, incl. point value: Year Eight Programming
Teacher(s): Mr Cook
Task & Seqta task #: Task 1 Programming
Big idea: How can we use computers to create solutions that improve our
lives?
Purpose of task: Assessment of knowledge and skills in Python programming
Skills needed to complete task: Python programming and logic.
Weighting: 100%
Maximum number of marks: 100
Date issued: 20th July 2020
Date due: 10th August 2020
Turnitin required: http://turnitin.com N/A
Submission method: Seqta submission by 5pm.
Limits (time, length, etc.): N/A
Last date drafts reviewed: N/A
Number of class lessons provided for completion: 6
Suggested amount of time for completion at home: 2
Conditions for task: Individual task.
Further information:

N/A (not applicable) is used for categories above that are not relevant for this task.

Task

Information and Requirements

Procedural

Information

  • You will be working individually.

  • Make sure you complete and include a Declaration of Own Work, available on the Radford Online page Sign in to your account.

Administrative Information

  • 6 lessons will be allocated to the completion of the task.

Assessment Criteria

Students will be assessed on the degree to which they demonstrate:

  • Develops algorithms with diagrams and / or texts to structure and plan programming solutions

  • Designs the user experience of a digital system

  • Implements and modifies programs with user interfaces in a general purpose programming language

  • Evaluate designed solutions and processes

Task:

People have problems. We write software to solve problems.”

Problem:

In this project you will be working to develop an application for a scientist to categorise observations of different amphibians. Using the Python programming language, you are to develop an application that:

  1. Has a clear user interface to allow data input

  2. Includes programming logic to categorise amphibians into their correct order of the species (see below).

  3. Outpts and allows for the storage of results

Program requirements:

Your program must be developed in Python. Source code must be supplied.

Documentation requirements:

You must include documentation based on the Design Process scaffold on SEQTA.

Program must include pseudocode to demonstrate knowledge of code being submitted.

Submission:

Your documentation and program files must be zipped and submitted on SEQTA by 5.00pm 10 August 2020.

Classfiying amphibians:

There are about 6,200 known species of living amphibians. They are placed in three different orders:

  1. Frog and toads

  2. Salamanders and newts

  3. Caecilians

Frogs and toads are adapted for jumping. Salamanders and newts may walk or swim. Caecilians live in the water or soil and are the only amphibians without legs.

You may want to do further research.

Learning or Reporting

Outcome
Mark Advanced
A student
who achieves
an A grade typically
Proficient
A
student who achieves
a B grade typically
Demonstrated
A
student who achieves
a C grade typically
Developing
A
student who achieves
a D grade typically
Experiencing
Difficulty
A student who achieves
an E grade
typically

Design



Designs
and implements a program that is highly modular and
appropriately applies algorithms and data structures. The
program includes a very high level of appropriate comments and
is very well structured. The
program uses well established techniques and design patterns
where appropriate.

Designs
and implements a program that is mostly modular and generally
applies algorithms and data structures. The
program includes a high level of appropriate comments and is
very well structured. The
program uses some established techniques and design patterns
where appropriate.

Designs
and implements a program that has some modules and generally
applies appropriate algorithms and data structures. The
program includes a good level of appropriate comments and is
very well structured. The
program uses few established techniques and design patterns
where appropriate.

Designs
and implements a program that is highly modular and
appropriately applies algorithms and data structures. The
program includes a high level of appropriate comments and is
very well structured. The
program uses very few established techniques and design
patterns.

Designs
and implements a program that is linear and applies a limited
range of algorithms and data structures. The
program includes a very low level of comments and is simply
structured. The
program does not utilize design patterns.

Planning


Plans
and manages the development process in an iterative way, mindful
of risks and project deliverables. Program
design strikes an excellent balance between functionality,
accessibility, usability and aesthetics. Documentation
includes excellent description of the design process and how the
program was developed.

Plans
and manages the development process in structured way, mostly
mindful of risks and project deliverables. Program
design strikes a very good balance between functionality,
accessibility, usability and aesthetics. Documentation
includes a very description of the design process and how the
program was developed.

Plans
and manages the development process in a post-hoc way, with some
mind paid to risks and ensuring project deliverables. Program
design strikes a good balance between functionality,
accessibility, usability and aesthetics. Documentation
includes good description of the design process and how the
program was developed.

Plans
and manages the development process in a completely post-hoc
way, with little management of risks. Program
design attempts to strike a balance between functionality,
accessibility, usability and aesthetics. Documentation
includes a limited description of the design process and how the
program was developed.

Provides
little evidence of planning and managing the development
process. Program
design does not strike a good balance functionality,
accessibility, usability and aesthetics. Documentation
is lacking or has a poor description of the design process and
how the program was developed.

Evaluate



Critically evaluates their
work with an eye to improving their knowledge and practice for
this and another work. Documentation
is very well written and reflects in a mature way on their
program development process.

Critically evaluates their
work with an eye to improving their knowledge and practice. Documentation is well
written and reflects in a mature way on their program
development process.

Critically evaluates their
work assessing their knowledge and practice as it applies to
this task. Documentation is well
written and reflects on their program development process.

Attempts a critical
evaluation of their work with an eye to improving their
knowledge and practice. Documentation is not well
written and has a very limited reflection on their program
development process.

Attempts little critical
evaluation of their work with an eye to improving their
knowledge and practice. Documentation is lacking
or poorly written and does not reflect on their program
development process.
Implementation



Develops
a program that is very responsive to the user experience and the
problem requirements. The
program is fully functional and is an excellent solution to the
programming problem.

Develops
a program that is responsive to the user experience and the
problem requirements. The
program is mostly functional and is a very good solution to the
programming problem.

Develops
a program that is mostly responsive to the user experience and
the problem requirements. The
program is generally functional and is a good solution to the
programming problem.

Develops
a program that is at times responsive to the user experience and
the problem requirements. The
program is not fully functional and or is a below standard
solution to the programming problem.

Develops a program that is
not responsive to the user experience and the problem
requirements. The
program is not functional and or is a poor solution to the
programming problem.

Comments: