Embedded Files
Solutions should be verified using test data both at program and system level. Live testing of programs should take place so that potential problems can be identified and addressed. The project should also meet the original requirements and that there are no logic errors. All user interfaces should also be evaluated at this stage.
Outcome to be assessed:
Outcome to be assessed:
H3.1: identifies and evaluates legal, social and ethical issues in a number of contexts
H3.2: constructs software solutions that address legal, social and ethical issues
H4.2: applies appropriate development methods to solve software problems
H4.3: applies a modular approach to implement well structured software solutions and evaluates their effectiveness
H5.1: applies project management techniques to maximise the productivity of the software development
H5.2: creates and justifies the need for the various types of documentation required for a software solution
H5.3: selects and applies appropriate software to facilitate the design and development of software solutions
H6.1: assesses the skills required in the software development cycle
H6.2: communicates the processes involved in a software solution to an inexperienced user
H6.3: uses and describes a collaborative approach during the software development cycle
H6.4: develops and evaluates effective user interfaces, in consultation with appropriate people.
The following areas are considered in the testing and evaluating phases of software development (each links to a new page)
The presentation below is a 22 minute summary of this content. Below that is the parent presentation that was used to make the video. It has speaker notes in it if you want ot open that to a new window for the notes. Don't just copy these notes, it won't help. Make your own from these and other sources.
Page updated
Report abuse