5707952
Description
| Question | Answer |
| Identify | - No current system - Paper-based system -Inadequate system: does not meet user requirements - Problem limitation |
| Feasibility | - Cost/benefit analysis - Cost to change? - Is it worth it? - Who makes the decision |
| Analysis: Interview | Description: Talk specifically with key personnel Advantage: Very detailed knowledge of how system is used Disadvantage: Time consuming |
| Analysis: Questionnaires | Description: Asking people for opinions, series of questions. Advantage: Big sample, large target audience Disadvantage: Can only ask a limited number of questions, feedback is not detailed. |
| Analysis: Observations | Description: Watch how the system is currently used Advantage: Reliable first-hand data, detailed understanding of how system is used Disadvantage: Time consuming, having to know who to observe |
| Analysis: Using Existing Documentation | Description: Reading a manual to now about the system Advantage: Get to know about the system Disadvantage: Time consuming |
| Design | Pencil and Paper: Flow diagrams, input, process, output File Structure: File names, data types, table |
| Build | Programmer will build the system on a computer using the appropriate language SQL/Python/C++ or application access. |
| Test | - Use of text data to see if system works as expected |
| Test: Data Types | Normal: Data that should be accepted the system (85%) Abnormal: Data that should be rejected from the system (103%) Extreme: Data that is on the limits of what will be accepted by the system. (1% or 99%) Acceptance testing: How easy is it to use the system for the end user? |
| Design | Technical: Back end/ back office, error codes, installation guide, updates, system requirements, technical vocab/jargon Admin: Higher privileges (e.g. set changes)/read/work End User: Simple language: how to guides/video tutorials |
| Implement: Direct Changeover | Advantage: Avaliable immediately, costs are reduced because only one system is being used. Disadvantages: If the new system fails then there is the possibility of massive loss of data |
| Implement: Parallel running | Advantage: If something fails in the new system, the old one is running as a backup, employees have time to learn how the new system works Disadvantage: There are two systems running so costs are increased |
| Implement: Pilot running | Advantage: If the newly introduced module fails then there is only that area that needs attention, each area becomes fully functional before moving on the next Disadvantage: More expensive than direct changeover because there needs to be an evaluation period before moving to the next phase. |
| Maintenance | - updates - patches - archiving - import new data - export new data - ensure system operational |
| Evaluate | - Does system meet original stated requirements? - Is the system suitably user-friendly (acceptable)? - Have user-requirements changed? |
| Verification | Verification is testing that your product meets the specifications / requirements you have written. “Did I build what I said I would?”. |
| Types of verification | - Double Entry: Type data into system twice - Computer compares entries to check same values - Visual Check: Compare/Confirm entry in summary screen - Validation: Tries to ensure data being entered is of the right type, right format and is reasonable and sensible. - Validation checks - Range (0-100), Format (DD/MM/YY), Presence, Length |
| Validation | Validation tests how well you addressed the business needs that caused you to write those requirements. It is also sometimes called acceptance or business testing. “Did I build what I need?” |
0 comments
Want to create your own Flashcards for free with GoConqr? Learn more.