Assessment &
Grading
How will I be assessed?
You will individually write, test and document a series of
programs which satisfy the requirements of a given specification.
Assessment will be by means of a set of assignments, collected into a
portfolio of work. This portfolio will be internally and externally assessed.
The
class activities are designed to cover the grading
criteria. This means that you should attend all classes unless you have
a VALID reason for not attending.
How
will I be graded?
Pass
To achieve a pass grade, you must achieve the six pass criteria listed in the grading grid provided below.
P1 requires you to describe the software development process. For P2, you will need to describe one programming language. You will also need to describe simple data structures such as array and how constructs such as loops may be used to create structured programs.
For P3, you will need to provide a design that meets a user need. The evidence for this criteria may be any or a combination of storyboards, pseudo code, narratives, action lists and graphical tools such as flowcharts or structure diagrams. For P4, you must produce a software component for the defined user need. The component must include at least one pre-defined function.
For P5 you must show that you tested and debugged your program code. For P6, you must produce documentation for their component, which could include screen shots and clear instructions on how to start and use the program. There also needs to be some internal and maintenance documentation. The evidence for internal documentation may be a print out that shows meaningful identifiers, comments or indentation. The maintenance documentation should include at least a technical description or data dictionary for the software component.
Merit
To achieve a merit you will need to achieve all the pass and merit criteria.
M1 requires you to justify the choice of programming language for a given user need. For M2 you must provide evidence demonstrating you have complied with organisational standards during development of the software component. This may include naming conventions for variables, procedures and functions, indentation and coding annotations. It is also appropriate to define standards for documentation including contents page and page footer content. For M3, you will need to show an understanding of debugging facilities; you wil be expected to link together testing software with types of error and the tools provided to debug components.
Distinction
To achieve a distinction you will need to achieve all the pass, merit and distinction criteria.
For D1 the maintenance documentation will be complete with technical description, data dictionary, evaluation of solution and future development for the software component identified. The learner will consistently make correct usage of specialist terminology. For D2, documentation will evaluate how development procedures were applied to produce the software component. To do this, you will need to directly relate your work with how it progressed from user need to investigation, design, implementation, testing and documentation. This evidence may be in the form of a written report or presentation with accompanying notes. You should consider the different stages of the development procedures separately.
Grading
Criteria
The table below shows
the grading criteria. A printer
friendly version is available.
|
Grading Criteria |
|
To
achieve a pass your
work must show: |
To
achieve a merit your
work must show: |
To
achieve a distinction your
work must show: |
|
P1 describe the software development procedures and the need for organisational standards
P2 describe one programming language
P3 select and use an appropriate design tool to address a defined user need
P4 produce a software component for a defined user need
P5 demonstrate appropriate debugging and testing has taken place during the development period
P6 internally document the solution and produce user instructions |
M1 justify the choice of the programming language used to address a given need
M2 demonstrate compliance with organisational standards during development of a software component
M3 demonstrate an understanding of debugging facilities in the chosen development environment |
D1 produce complete technical documentation and a troubleshooting guide for one software component
D2 evaluate how development procedures were applied to produce a software component |
