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;
31 Cards in this Set
- Front
- Back
|
System analysis uses |
Determine where problems are and how to improve |
|
|
4 methods of information collection |
Observation Questionaries Interview Document collection |
|
|
Observation advantages |
- reliable - overall view - inexpensive |
|
|
Observation disadvantage |
- uncomfortable being watcged - workers may fake hard work because of being watched |
|
|
Questionaries advantage |
- quick to answer - inexpensive - quick to analyze |
|
|
Questionaries disadvantage |
- response is less - infelixble - may get incomplete answer |
|
|
Interview advantage |
- more honest - more feedback (easier to extend a question) - interviewee can ask questions |
|
|
Interview disadvantage |
- time consuming - expensive - cant remain anonymous |
|
|
Document collection advantage |
- the only way to get some specific info - can see instantly |
|
|
Document collection disadvantage |
- time consuming = expensive |
|
|
What are the 2 things to consider in a design? |
Input and output |
|
|
Things to put in input and output |
-both input and output- Next and back button Maximize, minimize and close button -input- Submit -output- Confirm Edit |
|
|
What is verification |
A way to prevent errors when copying a data |
|
|
2 ways of verification |
Double entry - data entered twice with 2 people
Visual check - checking errors and comparing the original document |
|
|
8 validation |
- range check - data entered is within acceptable value
- lookup check - data entered stored in data
- leght check - check digit lenght
- character/type check - (name - must not contain number)
- format check - data is in specific format (student id, date)
- presence check - data is present - consistency check - check if it ties up - check digit - barcode/voucher |
|
|
Data type |
- text and alphanumeric - number - date - time - currency - logical/boolean - 2 option (f/m) - look up - more than 2 |
|
|
3 developement and texting |
Normal - acceptable Extreme - limits of acceptability Abnormal - out of range |
|
|
Implementation |
- direct - parallel - pilot - phased |
|
|
Direct advantages |
Minimal time and effort
Up immediately
Less cost |
|
|
Direct disadvantage |
No backup, if it fails data can be lost |
|
|
Parallel advantages |
Old system can be backed up Output can be compared to verify |
|
|
Parallel disadvantage |
2 system is run together, it takes alot of time and effort
Expensive |
|
|
Pilot advantage |
Can be fully trialed If error, only small part is affected Staff in pilot can train |
|
|
Pilot disadvantage |
Department using pilot will have no backup |
|
|
Phased adavatages |
Gtadually getting the user to get used to the new system If part of it fails, there is no backup |
|
|
User documentation |
• User documentation is designed to help users to learn how to use the software or system. • The users are usually non-technical people, who don't need to know how the system works. They just need to know how to use it • User documentation consist of : (from pp + textbook) 1. The purpose of the system/program/software package 2. How to log in/log out 3. How to load the software / how to install 4. How to do a search, to sort data, to do printouts 5. How to add, delete records 6. Screen layouts (input) 7. Print layouts (output) 8. Hardware & software requirements 9. Error handling, troubleshooting guide 10. Tutorials. 11. How to save files 12. limitations of the system 13. sample runs (with results and actual data used) 14. error messages 15. glossary terms |
|
|
Technical documentation |
• Technical Documentation is designed to help programmers and Analysts who need to make improvements to the system or repair/maintain the system. • Technical documentation consists of: (from ppt + textbook) 1. Program listing/coding 2. Programming language used 3. program flowcharts/algorithms 4. system flowchart 5. Purpose of the system/program/software 6. Details of the hardware and software required for the system 7. Details of data structures (data types, field names, etc.) 8. Details of expected inputs 9. Details of validation checks 10. Details of how data is processed 11. Diagrams showing how data moves through the system 12. Flowcharts describing how the system works 13. limitations of the system 14. input formats 15. hardware and software requirement 16. minimum memory requirement 17. known “bugs” in the system 18. list of variable used 19. file structure 20. sample runs 21. output formants 22. meaning of error messages |
|
|
Evaluation |
1. compare the final solution with the original requirement 2. identify any limitations in the system 3. identify any necessary improvements that need to be made 4. evaluate the user’s responses to using the new system 5. compare test results from the new system with results from the old system 6. compare the performance of the new system with the performance of the old system 7. observe users performing set tasks, comparing old with new 8. measure the time taken to complete tasks, comparing old with new 9. interview users to gather responses about how well the new system works 10. give out questionnaires to gather responses about the ease of use of the new system. |
|
|
2 result of evaluation |
Hardware updates Software update |
|
|
CLI |
|
|
|
CLI advantage |
Yk what just look at the last 2 page of the pdf summary. Im tired. |
