planning system and installation Flashcards

1
Q

what are the two important considerations when creating a new system?

A

the extent of it and the limitations of it

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

name at least three reasons why changing a system may be difficult.

A

– Users don’t like change (too often/at all)
– New systems might omit old features
– Old systems might be faster in certain circumstances
– People find change complex
– From a technology perspective, change might lead to incompatibility
– There might be data loss during migration
– It might be expensive (either in terms of money or time)
– basically almost any answer is okay just think abt it

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

what are the names of the four steps of changing a system?

A

plan
communicate
integrate
evaluate

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

explain the first step of changing a system.

A

plan - Before undertaking any change, a business needs to have a
clear and valid reason and mission for the change process.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

explain the second step of changing a system.

A

communicate - The most important factor in changing anything within a business, small or large, is to communicate the change, and
its many factors, to the key stakeholders within the
organisation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

explain the third step of changing a system.

A

integrate - If it’s possible for the change program of your
business to be adjusted, then open up your plans for
consultation with your stakeholder group

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

explain the last step of changing a system.

A

evaluate - It’s crucial that the organisation, its passage
through the change program, and the wider
organisation’s reactions to that change
program are evaluated at every feasible
opportunity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is legacy system

A

old method/computer/programme/app that can not be purchased anymore (because it is old)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

give at least three examples of legacy system as hardware.

A

– Floppy disks
– Parallel printer cables
– Connections like PS2
– basically any other.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

give at least three examples of legacy system as software.

A

– Windows XP
– Movie Maker
– Industry specific software
– basically any other

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

give at least three examples of legacy system as a computer system

A

– Apple II Series
– Amiga
– Commodore 64

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Whats a ,erger? Can you give three examples?

A

A combination of two entities or more, especially companies, into one.
Exxamples:
Disney and Pixar
Columbia and Sony pictures
Dream works and paramount

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Can you name at least three problems that may arise when merging systems?

A

– Issues of software compatibility
– Language differences
– Time zone differences
– Workforce cultural differences
– basically anything else

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Compare the implementation of systems using a client’s hardware with hosting systems remotely.

A

This looks like its a alot of things but actually you dont need to memorise this all you just need to be familiar with this.

  1. Location:
    Client’s Hardware (On-Premises): The system is installed and maintained on the client’s premises, requiring physical space, power, and cooling.
    Remote Hosting (Cloud): The system is hosted on infrastructure provided by a third-party cloud service provider, accessible over the internet.
  2. Infrastructure Ownership:
    Client’s Hardware (On-Premises): The client owns and is responsible for the hardware, networking equipment, and infrastructure.
    Remote Hosting (Cloud): The cloud service provider owns and maintains the underlying infrastructure; clients subscribe to services.
  3. Initial Setup and Deployment:
    Client’s Hardware (On-Premises): Implementation involves procuring hardware, software licenses, and configuring the system on-site. It may have a longer lead time.
    Remote Hosting (Cloud): Rapid deployment is possible, as infrastructure is provisioned by the cloud provider. Users can quickly scale resources up or down based on demand.
  4. Scalability:
    Client’s Hardware (On-Premises): Scaling may require additional hardware procurement and on-site adjustments, which can be time-consuming and expensive.
    Remote Hosting (Cloud): Scalability is often more flexible and can be achieved by adjusting subscription plans or configurations through the cloud provider’s interface.
  5. Maintenance and Upgrades:
    Client’s Hardware (On-Premises): The client is responsible for maintenance, updates, and ensuring hardware reliability. Downtime may be required for upgrades.
    Remote Hosting (Cloud): Maintenance and upgrades are typically managed by the cloud provider, reducing the client’s operational burden. Providers often ensure high availability during updates.
  6. Cost Structure:
    Client’s Hardware (On-Premises): Upfront costs for hardware and software licenses may be higher. Operational costs include maintenance, utilities, and staff.
    Remote Hosting (Cloud): Often follows a pay-as-you-go model, with lower upfront costs. Clients pay for the resources they use, and operational costs are managed by the cloud provider.
  7. Security and Compliance:
    Client’s Hardware (On-Premises): Clients have direct control over security measures and compliance but must manage and implement them.
    Remote Hosting (Cloud): Cloud providers invest heavily in security measures, but clients need to trust the provider. Compliance is often a shared responsibility between the client and the provider.
  8. Connectivity and Accessibility:
    Client’s Hardware (On-Premises): Local network infrastructure determines system accessibility, and remote access may require additional configurations.
    Remote Hosting (Cloud): Accessible from anywhere with an internet connection. Cloud services often provide global accessibility without additional configuration.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

In easy words explain what is local software and what is SaaS.

A

local - on premise, like buying a house - once and for all, but no one will clean it or protect it for you
saas (software as a servis) - like renting a house, but you get cleaned and safe

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

can you give three saas examples?

A
  • Microsoft Office 365
  • Google Apps
  • Amazon Web Services
  • Dropbox
17
Q

Pros and cons of Saas?

A

+ Reliable updates,
+ Cooperation,
+ Backed up by cloud,
+ Accessible on all devices,
+ Cheaper when switching,
+ Doesn’t use as much storage.
- More expensive,
- Requires internet connection,
- No updates - less secure,
- Usually doesn’t allow cooperation,
- Less secure, (data breaches)
- Still uses up space if you want to store the files.

(thank you Mitja for your notes for this.)

18
Q

Pros and cons of local?

A

+ One time payment,
+ Doesn’t equire internet connection,
+ More customizability,
+ Customer service.
- Uses up storage,
- Sometimes isn’t backed up by cloud,
- No updates - less secure,
- Usually doesn’t allow cooperation.

(again thank you Mitja)

19
Q

What are the foru ways of changing/installing a new system?

A

Direct changeover, Parallel running, Pilot running, Phased conversion

20
Q

whats a direct changover and what are pros and cons of it?

A

directly stoppping the old system and starting the new one.
pros: minimal time and effort, immediatly available new system
cons: if the new system failsm there is no way back.

21
Q

whats parallel running and what are pros and cons of it?

A

you start the new system with the old one and they both are available now.
pros: old system works as a backup and you canbe used as a way to see if the new one is running ok
cons: costly 😔

22
Q

whats pilot running and what are pros and cons of it?

A

the pilot system is being tested while the old one is still active, and when its all ready and (most) bugs are fixed a new system is applied.
pros: all features are fully trialled - if the new system fails, only a small part of the organisation suffers - staff who were part of the pilot can train other staff
cons: for the subset of users in the pilot group, there is no backup if the new system fails

23
Q

whats phased convertion and what are pros and cons of it?

A

The new system is introduced in phases as parts of the old
system are gradually replaced with the new system
pros: allows people to get used to the new system; training of staff
can be done in stages
cons: if the new system fails, there is no fall back for that part of
the system

24
Q

pick two and compare them.

A

or just read through your notes. just to make sure that you know that.

25
Q

what are the possible problems that may arise when the data migrates?

A
  • Incompatible file formats
  • Data structure differences
  • Validation rules
  • Incomplete data transfers
  • International conventions on dates,
    currencies & character sets
26
Q

What are some things that need to be tested?

A

functionality, user experience, performance, compatibility, security, managment.

27
Q

What are the types of testing?

A

Static and dynamic testing, alpha and beta testing and white-box black-box testing, user acceptance and automated testing.

28
Q

What is static testing? Give an example.

A

That is when you check the programme, requirements, possible errors.
An example would be a group of programmers checking each others work by reading the code.

29
Q

What is dynamic testing? Give an example please.

A

Dynamic testing is when the programme is being executed and through that finding bugs.
An example would be the group of programmers running their programme looking for glitches.

30
Q

What are the differences between the alpha and beta testing?

A

Alpha testing is performed at the developer’s site by the internal employees whereas beta testing is by performed by client at client’s location.

31
Q

What is white-box testing?

A

That is when the test team is aware of how does the programme work and specifically targets areas to display its capabilities or find a bug.

32
Q

What is black-box testing?

A

That would be when the tester team is not aware of the code and doesn’t specifically try to target it.

33
Q

What is user acceptance testing?

A

That is when you test how greatly have the programmers reached to the user’s expectation.

34
Q

What is automated testing?

A

That would be when the special software tools are being used to test the programme and the predicted results are then being compared to actual results.