It has to precede a technical development because it objectionally and rationally covers the strengths and weaknesses of an existing system.
Systems life cycle
An examination of a system, which contains different stages - analysis, design, development and testing, implementation, documentation and evaluation. It is a cycle, because once the system is established, further improvements can be made
Scenarios
Another name of situation - hypothetical situation on which we made decisions about how ICT should be applied.
Systems analysis
Examining the existing system in detail. Information about it is collected by observation, examination of documents, interviews and questionnaires.
Examination of documents
All documents involved in the system are examined. This helps the analyst identify the input and output of the existing system and assess the processing.
Interviews
They are done face to face with users of the system, most importantly representatives of workers and owners because personal needs are discovered. They are flexible, as follow up questions can be asked, but take a lot of time to conduct and organize.
Observation
This method gives information about how the processes overlap, how the workers interact and if the adopted methods are efficient.
Questionnaires
Most common way of collecting information. Questions have to be created carefully to avoid bias. Used in large companies where employees can not be all interviewed. Even though they are impersonal, once they are made, it is easy to create a lot of copies and distribute them to the users.
Processing
The processing would be the way the input information is used in order to create an output. If we have an example with a payroll system, this is the calculation of the payrolls until the payslip is created.
Data flow diagram
A graphical method of recording the inputs, outputs and processing that have been identified in the current system.
Terminator
This is the process when data flows to or from somebody/somewhere outside the company
Process box
When information is processed, the process order is put in a process box.
Store
The outputs are not kept on the computer but the data can still be viewed, as it is being stored and therefore, called a store.
Data flow
These are the arrows in a data flow diagram. Each arrow have to be in an accurate direction, appropriately recorded and labelled to show what data is flowing at what point in the diagram.
System flowchart
This is an alternative way to the data flow diagram, which can represent the data flow for processing customer orders. This is generally a method of designing a systems solution.
Storage medium
The orders that are considered to be a store in the data flow diagram have to be represented as being stored on a storage medium in a computerised system. This can be different data storage devices.
Requirements specification
A list of the features of the system that are required. It will contain general requirements such as what the user wants the overall system to do as well as very specific requirements of the users.
Programmer
This is the person who would write a software, if a new software has to be written and an already existing one is not sufficient for the needs of the system. The programmer designs the inputs and outputs to the system, the files and databases needed to store the data, the processing required, the validation checks and the needed data to test the system.
Data collection forms
They can be hard copies or screen based. They must be easy for users to fill and for the secratary to read the information afterwards. A common method of ensuring that mistakes will be as few as possible is to put boxes in each section to be completed, each box representing a character, required to be filled.
Screen layouts
Their design accoring to the user requirements.
Input screens
Input screens have to be easy to use, attractive to look at and limit the possibility for inaccurate data to be filled. The screen designs should not be over-elaborative because they tend to be distractive.
Input devices
The decision of input devides depends largely on the amount of data the system is likely to produce.
Report layouts
The design of report layouts is heaviy influenced by the users' specifications. The people who are likely to see them need to be considered, because good impression is important.
Screen displays
They should have instructions on how to move from screen to screen, as well as being pleasant to look at and not too distracting.
Master file
This is a file which contains relatevely permanent information, usually updated periodically. Examples of data on a master are name, address, hourly rate, department, etc.
Transaction file Validation Range checks Length checks Format check Picture check Off-the-shelf software Purpose-built software Expected results Actual results Normal data Extreme data Abnormal data Single stepping Parallel running Direct changeover Phased implementation Pilot running Technical documentation User documentation Systems documentation Program documentation Troubleshooting guide Frequently Asked Questions
- It has to precede a technical development because it objectionally and rationally covers the strengths and weaknesses of an existing system.
Systems life cycle- An examination of a system, which contains different stages - analysis, design, development and testing, implementation, documentation and evaluation. It is a cycle, because once the system is established, further improvements can be made
Scenarios- Another name of situation - hypothetical situation on which we made decisions about how ICT should be applied.
Systems analysis- Examining the existing system in detail. Information about it is collected by observation, examination of documents, interviews and questionnaires.
Examination of documents- All documents involved in the system are examined. This helps the analyst identify the input and output of the existing system and assess the processing.
Interviews- They are done face to face with users of the system, most importantly representatives of workers and owners because personal needs are discovered. They are flexible, as follow up questions can be asked, but take a lot of time to conduct and organize.
Observation- This method gives information about how the processes overlap, how the workers interact and if the adopted methods are efficient.
Questionnaires- Most common way of collecting information. Questions have to be created carefully to avoid bias. Used in large companies where employees can not be all interviewed. Even though they are impersonal, once they are made, it is easy to create a lot of copies and distribute them to the users.
Processing- The processing would be the way the input information is used in order to create an output. If we have an example with a payroll system, this is the calculation of the payrolls until the payslip is created.
Data flow diagram- A graphical method of recording the inputs, outputs and processing that have been identified in the current system.
Terminator- This is the process when data flows to or from somebody/somewhere outside the company
Process box- When information is processed, the process order is put in a process box.
Store- The outputs are not kept on the computer but the data can still be viewed, as it is being stored and therefore, called a store.
Data flow- These are the arrows in a data flow diagram. Each arrow have to be in an accurate direction, appropriately recorded and labelled to show what data is flowing at what point in the diagram.
System flowchart- This is an alternative way to the data flow diagram, which can represent the data flow for processing customer orders. This is generally a method of designing a systems solution.
Storage medium- The orders that are considered to be a store in the data flow diagram have to be represented as being stored on a storage medium in a computerised system. This can be different data storage devices.
Requirements specification- A list of the features of the system that are required. It will contain general requirements such as what the user wants the overall system to do as well as very specific requirements of the users.
Programmer- This is the person who would write a software, if a new software has to be written and an already existing one is not sufficient for the needs of the system. The programmer designs the inputs and outputs to the system, the files and databases needed to store the data, the processing required, the validation checks and the needed data to test the system.
Data collection forms- They can be hard copies or screen based. They must be easy for users to fill and for the secratary to read the information afterwards. A common method of ensuring that mistakes will be as few as possible is to put boxes in each section to be completed, each box representing a character, required to be filled.
Screen layouts- Their design accoring to the user requirements.
Input screens- Input screens have to be easy to use, attractive to look at and limit the possibility for inaccurate data to be filled. The screen designs should not be over-elaborative because they tend to be distractive.
Input devices- The decision of input devides depends largely on the amount of data the system is likely to produce.
Report layouts- The design of report layouts is heaviy influenced by the users' specifications. The people who are likely to see them need to be considered, because good impression is important.
Screen displays- They should have instructions on how to move from screen to screen, as well as being pleasant to look at and not too distracting.
Master file- This is a file which contains relatevely permanent information, usually updated periodically. Examples of data on a master are name, address, hourly rate, department, etc.
Transaction fileValidation
Range checks
Length checks
Format check
Picture check
Off-the-shelf software
Purpose-built software
Expected results
Actual results
Normal data
Extreme data
Abnormal data
Single stepping
Parallel running
Direct changeover
Phased implementation
Pilot running
Technical documentation
User documentation
Systems documentation
Program documentation
Troubleshooting guide
Frequently Asked Questions