1.1 System Organizations Flashcards
1.1.1- Identify the context for which a new system is planned
Before a new system is designed. The analyst reviews previous systems using primary and secondary research to figure out the advantages and disadvantages of the old system. This is done to improve efficiency with a new system
1.1.2 - Describe the need for change management
–> If there is a change in employees might need training on how to use it.
–> Will the current system have to shut down while the new system is being implemented? Or will it be parallel running?
1.1.3 Outline compatibility issues resulting from situations including legacy systems or business mergers
It is rare the 2 companies use the same system. So, there will be a surprise for one of the companies. There could be language barriers.
Unit Barriers (ft. and cm)
1.1.4 Compare the implementation of systems using a client’s hardware with hosting remotely (SaaS)
Software as a System (SaaS)
–> delivery methods that allows software and data to be hosted and managed centrally on a remote datacenter
–> users pay on a subscription basis
Advantages
–> cheaper in the short term
–> SaaS applications are designed to integrate easily with other software and applications
Disadvantages
–> users entrust their sensitive data to a third-party provider, which can raise security concerns.
–> SaaS applications are designed to be used by a large number of users, which can limit customization options.
1.1.5 Evaluate alternative installation processes
- Parallel Running
- Pilot Running
- Phased Implementation
- Direct Changeover
Parallel Running
When the new system operates simultaneously during the implementation process
Benefits –> No data loss, if the new system fails
Limitations –> Cost inefficient as two systems are running
Pilot Running
running a system in only one part of the business
Benefit –> If the system fails only one part of the business is affected
Limitations –> Data loss when implementing the new system
Phased Implementation
the old system is being replaced part by part of the new system
Benefit –> Each component can be tested individually. Staff training can be done step by step
Limitations –> sometimes if the system is too complex it might be hard to do it step by step
Direct Changeover
When the old system is unplugged and the new system is plugged in at the same time.
Benefits –> Cheap, doesn’t require parallel running
Limitations –> There is no back if the new system fails
- 1.1.6 Discuss problems that may arise as a part of data migration
- incompatible file formats
- incompatible data structures
- errors while transferring
1.1.7 Suggest various types of testing
- Alpha Testing
- Beta Testing
- White Box testing
- Debugging
Alpha Testing
Testing before the system has been implemented
‘A’ comes before ‘B’
Beta Testing
Testing after the system has been implemented
‘B’ comes after ‘A’
Dry- Running Testing
Testing that occurs when someone traces data on paper with a pen while the algorithms run
Debugging
Finding and correcting the number of bugs in a program. Other programs do this automatically
Faster and Cheaper in the LONG TERM
