Maximize benefits while making sure things go smoothy during a change from present state to desired state.
5
New cards
legacy system
an old system that is fast approaching or beyond the end of its useful life within an organization
6
New cards
Business Merger
The combining of two or more business entities.
7
New cards
Strategies for Integration
1. Keep both systems and develop them in parallel. 2. Replace both systems with a new one 3. Select the best systems from each company and combine them. 4. Select one company's system and drop the other
8
New cards
SaaS
Software as a Service; a subscription service where you purchase licenses for software that expire at a certain date.
9
New cards
On Premise Software
Software installed on buyer's computers
10
New cards
Change over
The process of putting the new system online and retiring the old one.
11
New cards
Types of Changeover (4)
Parallel Direct Pilot Phased
12
New cards
Parallel Changeover
a changeover approach that includes running the old system, then running both the old and new systems in parallel, and finally fully changing over to the new system after gaining confidence in the working of the new system
13
New cards
Direct Changeover
Immediate removal of an old system and complete replacement with a new IT system.
14
New cards
Pilot changeover
New system is trialed in a small part of business, once it's running correctly then new system is implemented across organisation
15
New cards
Phased changeover
a changeover approach where the older system is broken into deliverable modules; the first module of the older system is phased out using the first module of the new system, then the second module is replaced, and so on until the last module is replaced
16
New cards
Data migration
Transfer of data between different formats, storage types and computer systems.
17
New cards
Problems with Data Migration
Incompatible file formats Data structure differences Validation rules Incomplete data transfers International conventions on data, currencies & character sets (I [FF], DS, V, I, IC)
18
New cards
Fundamental Testing
Tests individual commands/text input to confirm that the program functions correctly according to design specs
19
New cards
alpha testing
the firm attempts to determine whether the product will perform according to its design and whether it satisfies the need for which it was intended, done before the product is released.
20
New cards
beta testing
A process that releases commercial software in development to a cross-section of typical users who evaluate the program's features and report any problems or "bugs" in the software before it is released to the public.
21
New cards
Dry Run Testing
Conducted with a pen-and-paper method by the programmer and he/she mentally runs the algorithm in the source code
22
New cards
Unit Testing
tests individual units of code
23
New cards
Integration Testing
The entire system is tested at the same time to verify that all components can work together.
24
New cards
User Acceptance Testing (UAT)
determine if the system satisfies the user and business requirements
25
New cards
Debugging
The process of figuring out why code doesn't behave as expected and eliminating bugs to make it work as desired.
26
New cards
Validation
The process of evaluating whether the data input is appropriate for the program.
27
New cards
verification
Ensuring that the data input is the same as the original source data. When reading from a source(file, db, etc) we make sure that we are reading the correct information.
28
New cards
Purpose of documentation
Providing users with information about how a system works. Informing other developers of reasons why code was included.