Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
8 Cards in this Set
- Front
- Back
- 3rd side (hint)
|
Describe the purpose of analysis |
Research how previous systems work using interviews, observations, existing documentations, questionnaires and experience. Identify the main main requirements of the system set by the user. Identify hardware/software constraints. |
- Fact finding methods. - Limitations |
|
|
Fact-finding methods - Interviewing |
Allows you to get the views both strengths, weakness & possible improvements for the current system. Adv: Greater depth of information & personal contact allowing for more information transfer. Disadv: It is very time consuming and is often subject to bias. |
|
|
|
Fact-finding methods - Questionnaires |
Allows you to ask large groups of people a set of questions about the current system. Adv: Can get lots of information from a large pool of people easily. Disadv: It can be difficult to design a form that ensures all information is collect. Also some people may not want to fill in/return their forms. |
|
|
|
Fact-finding methods - Observation |
This gives useful information on how a company works by observing key users at work and recording daily activities. Adv: Information will be accurate as it is straight from the users using the system by seeing how daily activities are completed. Disadv: It can add stress and pressure on the on people being observed as well as some other jobs may be difficult to observe. |
|
|
|
Fact-finding methods - Document Sampling |
Allows for someone to see how data flows in an organisation. Typical documents include forms, orders and receipts. Adv: Able to see inputted, collated, processed and reported data telling you valuable information on the company. Disadv: If the system changes, the data may be unreliable or useless. |
|
|
|
Functional Requirements |
This specifies what a software must do. This is essential to the workings of the system. eg: Security of the system or that business requirements are met. |
Essential/Non-Essential |
|
|
Non-Functional Requirements |
This specifies additional criteria by which a system by which the system is judged. This is non-essential additions to the system that are not required for the system to work. eg: How efficient and effective the system is to the user. |
Essential/Non-Essential |
|
|
Data Flow Diagrams (DFD) |
A Data Flow Diagram is a process-orientated graphical representation of a system. This shows the flow of data through the system at each level. |
|
