AS11 Flashcards
1
Q
Feasibility
A
- Establishes whether or not a project can be completed given the scope laid out.
- Is it worth it?
2
Q
Economic Feasibility
A
- Can the project pay for the hardware, liscences, human wages and running costs in the given budget?
- What is the profit?
3
Q
Time Feasibility
A
- Will the project be done in time? (Risk of going over budget, making a negative impression)
4
Q
Technical Feasibility
A
- Can the project be done with the resources available?
- Is the project doable with current accessible technology?
5
Q
Political Feasibility
A
- Does the project go against the beliefs of certain people?
- Will the media report on it in a negative light?
6
Q
Legal Feasibility
A
- Does the project comply with the law?
- Any chance of being sued?
7
Q
Project Requirements Specification
A
- Produced at the end of analysis.
- Outline of how to create successful project.
- Poorly defined = delays/increased costs.
8
Q
Observation
A
- Analysts shadow employees, see how the business works.
ADVANTAGES: - Could pick up parts of system that are not obvious to customer.
- Confirms information gathered through other methods.
DISADVANTAGES:
* - Some people may feel threatened/uncomfortable.
* No guarantee that some subtle system parts will show during observation.
9
Q
Questionnaire
A
- A set of questions about the system, normally given to staff.
ADVANTAGES: - Can be given to big population.
- Can get a large number of responses.
DISADVANTAGES:
- Hard to design.
- Requires system knowledge.
- Not all questionnaires sent out will be completed.
10
Q
Existing Documentation
A
- Analyst gathers documents relating to new system to infer what data will need to be stored.
ADVANTAGES: - Analyst gains understanding.
- Reliable documents.
- Document trails help support the analyst’s picture of business processes.
DISADVANTAGES:
- Documents give limited view of system.
- Documents may contain sensitive information.
11
Q
Interview
A
- Analysts pick some key stakeholders and ask targeted questions about current system.
ADVANTAGES: - Large amounts of information can be gathered.
- Interviews produce detailed responses.
DISADVANTAGES:
- Time consuming.
- Interviewees may not be truthful. Reponses need to be verified.
12
Q
Requirements
A
- Help keep scope of project.
- Developers can be paid based on requirements.
13
Q
Types of Requirements
A
- Interface (Where is user interaction?)
- Functional (What will the system do?)
- Performance (e.g. response times.)
14
Q
Design
A
- Hardware/software choices.
- Data structure design.
- Input/Output design.
- Processing design.
15
Q
Flowcharts/Data Flow Diagrams
A
- Flowcharts represent an algorithm.
- DFDs represent how a system will process information. (Multiple levels, distinction between internal/external parts)
16
Q
Direct Changeover
A
- Swaps over all data at once/Switches off one system entirely.
- Only used when older system unavailable.
- Cheap, no duplication.
- Risky, have to transfer all data first.
17
Q
Phased Changeover
A
- Old system active, new one phased in chunks at a time.
- Used when a small company upgrading/implementing new system.
- Less risk of system going down, staff introduced to new system in small stages.
- Takes long time, difficult to integrate new system into old one.
18
Q
Pilot Changeover
A
- New system tested in small numbers of areas before fully implemented.
- Used by big brands.
- Only small part of business affected, new system staff can train old system staff.
- Extra work for IT staff, communication between systems harder.
19
Q
Parallel Changeover
A
- Both systems used, once new system is stable, the old one is discarded.
- Used when the system cannot afford to fail.
- Less risky, less stress.
- Time consuming, extra cost.
20
Q
White Box Testing
A
- Structure is tested.
- Knowledge of code required.
- Several paths created by control statements. Each path tested.
- Carried out by developers.
21
Q
Alpha Testing
A
- Unstable preliminary build.
- May not work.
- Carried out by developer/team.
22
Q
Beta Testing
A
- More stable than alpha builds.
- Still contains some errors.
- Carried out by customers in live models. Report faults.
23
Q
End User Testing
A
- Final phase.
- Uses real data.
- Tested by customers. They ensure developer has met requirements.
24
Q
Adaptive maintenance
A
- Companies fix bugs/add functionality to system.
- Customers can implement basic models, then upgrade.
- Helps businesses get running quickly.
25
Q
Corrective Maintenance
A
- Fixes problems as they arrive so system matches specification.
- Customers take out support contract that asks developer for this kind.
- No functionality updates.
26
Q
Perfective Maintenance
A
- Completely matches original system.
- Improves on performance and functionality at request of users.
27
Q
Black Box Testing
A
- No knowledge of code required.
- Tester provides input, observes output. Identifies how system responds to certain inputs.
28
Q
User Documentation
A
- For those who don’t understand complex technological ideas but work for the client/Employees that need training.
- Allows novice users to interact with the system/Needed for training.
29
Q
Technical Documentation
A
- For experienced users who have good understanding of technological concepts/Those who ensure system has been configured correctly and is running smoothly.
- Needed to know how database was set up/what hardware is required. Allow for greater understanding of system.
30
Q
5 Features of User Documentation
A
- Step by step getting started guide for main features.
- Installation guide.
- User guide.
- Reference manual.
- Error/Troubleshooting guide.
31
Q
5 Features of Technical Documentation
A
- Diagrams used in analysis/design.
- What data structure has been used.
- Hardware/Software requirements.
- Any relevant documents from design phase.
- Algorithm designs - flowcharts.
32
Q
Full Backup
A
- Copies all files/Provides complete set of the data.
- Everything is backed up at once, files can be restored quickly.
- Most files do not change/leads to redundancy, takes longer to carry out, security concerns.
33
Q
Differential Backup
A
- Copies only files that have been changed since last full backup.
- Faster than incremental/full, takes up less storage.
- Requires more storage space, longer time needed to restore files than with incremental.
34
Q
Incremental Backup
A
- Copies only files that have been changed since the last backup of any type.
- Faster backup time, less storage required.
- Recovery process takes longer, problems may occur if any backups corrupted.
35
Q
Disaster Recovery Plan
A
- An organisaton stores all of its data in a data centre, including sensitive data.
- A DRP is a document which details the steps that will be taken in the event of a man-made or natural disaster to protect/recover the data.
