Outcome 3

Question 1

Archiving

Answer 1

Long term record of events.
Often compressed, and are placed in medium-to-long-term storage
Often required by local authorities

Question 2

Backups

Answer 2

A copy of a file(s) in case the original is lost or damaged

Question 3

Backups - Types

Answer 3

Differential Backups - takes a backup of all items that were changed since the last full backup
Incremental Backups - takes a backup of all items that were changed since the last incremental backup
Full Backups - complete backup of all data regardless of what has been backed up beforehand

Question 4

Reasons to store backups separate to main database

Answer 4

Regular backups will require less physical space
Regular backups will take less time
Retrieval of backups will take less time
Free space on the system
No confusion between the old and new data

Question 5

Disposing of Data

Answer 5

Process of deleting data so that it cant be accessed again

Requires data be scrubbed -> meaning data is overwritten by 0’s or 1’s three or more times

Question 6

Factors affecting the access of data (x5)

Answer 6

• Latency
• Reliability
• Cost
• Capacity
• Ease of Use

Question 7

Unit Tests

Answer 7

low level tests close to the source code that checks various different modules of the source code

Question 8

Integration Tests

Answer 8

verifies that different modules used by the application work together

Question 9

Functional Tests

Answer 9

tests if the solutions meet the SRS. Just the output is checked

Question 10

Acceptance Tests

Answer 10

formal test that verifies whether the SRS has been satisfied

Question 11

Performance Tests

Answer 11

observes response times, user behaviour

Question 12

User Acceptance Testing

Answer 12

checks if the end users are satisfied. Uses a combination of interviews, questionnaires and observations

Question 13

Examples of Appropriate Test Data x5

Answer 13

Valid Data
Valid but unusual data
Invalid data
Boundary condition data
Wrong Data

Question 14

Usability Testing

Answer 14

Testing that focuses on experience and any issues that arise with the clients use of the solution (i.e. can they use the solution easily

Question 15

Ways to document test results

Answer 15

• Testing Tables
• Subjective Reports
• Capturing screenshots of features that are not normally visible
• make handwritten calculations to verify
• capture screenshots of the solutions validations rules

Question 16

Annotations to Gantt Charts

Answer 16

handwritten or added as notes that give reasons to task schedules or resourcing priorities

Question 17

Evaluation

Answer 17

Final stage of the problem-solving methodology - checks how well the solution is satisfying the needs of the user it was created for.

Is not Testing - by the time evaluation has begun, the solution has been proven to work (in the testing phase) and its functionality is not in question

Question 18

Efficeincy

Answer 18

A measure of how much time cost and effort is applied to achieve intended results

Question 19

Effectiveness

Answer 19

A measure of how well a solution, information management strategy or network functions and whether each achieves its intended result

Question 20

Examples of Quantative Evaluation Methods

Answer 20

• task completion times
• survey
• number of successfully completed tasks

Question 21

When to Evaluate

Answer 21

after the solution has been ‘bedded in’ and the users are familiar and comfortable with it.
A few months of regular use is typical

Question 22

Purpose of Evaluating project Plans

Answer 22

help judge how your plan and the techniques used help you manage your project

Avoids the company making the same mistake as well

Question 23

Evaluation Criteria for Project Plans

Answer 23

Completeness - were any significant asks omitted from the project management plan? were resources included? was it annotated when required?

Maintainability - how easy was it to modify the Gantt chart to keep it up to date with reality:?

Accuracy - were tasks correctly identified and marked as dependent or concurrent, in the right sequence

Readability - was it easy to see the tasks and their dependencies? Was the Gantt chart and its text a readable size? were the colour choices appropriate?