Topic 1 - System Fundamentals
No description yet. This curated deck is ready for daily study.
Card preview (24)
3 difficulties in changing software systems
• Users don’t like change • Expensive • Data loss
4 ways of changing to a new system
• Direct changeover • Parallel • Pilot • Phased
Direct changeover
When the old system is stopped and replaced completely by the new system
Parallel
When both the new and old system run simultaneously and data is entered into both
Pilot
New system tested with small part of the organization, bugs are fixed and then the system is expanded into the rest of the organization
Phased
When the new system is introduced in phases and the old system gradually phases out
2 pros and 1 con of Direct Changoeover
Pros: - Quick changeover - New system is available immediately Con: - There is no backup system in case of failure
2 pros and 1 con of parallel changeover
Pros: - There is a backup system in case of one system failing - Output from both systems can be compared to verify functionality of the new system • Expensive
2 pros and 1 con of pilot changeover
Pros: - Staff who are part of the pilot can train others - All features can be tested before it is implemented throughout the whole organization Con: - No backup for pilot group in case of failure
2 pros and 1 con about Phased Conversion
Pros: - Allows people to get used to new system - Training can be done in stages Cons: if system fails, no backup for that part of system
Data migration
Moving data from one system to another
3 possible problems with data migration
• Incompatible file formats • Validation rules • Different currencies
Legacy System and 1 example
Old technology, computer system or application that is no longer supported. E.g. Windows XP
3 characteristics of traditional software/local software
• One-time fee • Used on one computer • Free trial not available
3 characters of SAAS/Remote software
• Subscription fee • Use on any computer via internet • Free trial often available
2 cons and 2 pros of SAAS
• Software can be used from anywhere • Only need to pay for the time you use it • Security, your data is with the company behind the SAAS • Need an internet connection to use
Static Testing
VERIFYING documentation like planned specifications for the program and test plans to ensure that system is being built correctly for what it is intended for.
Dynamic testing
Code is executed and VALIDADED to ensure the code produces the required result and also to check for bugs.
Alpha Testing
Team behind the software tests each user journey and confirms they work as intended
Beta Testing
Testing of the software by end-users to see how it performs in real-world scenarios
Black box testing and who does it?
Testing for full functionality of a software without looking at the code behind it. Done generally by software testers
White Box Testing and who does it?
Testing the code and internal structure of the program to make sure it works. Done by the software developers.
User Acceptance Testing what is it and what is it AKA
AKA end-user testing Software tested by end users to see if it meets their expectations and whether it is right for them.
Usability
How easy is it to use a software