Topic 1 - System Fundamentals Flashcards

1
Q

3 difficulties in changing software systems

A
  • Users don’t like change
  • Expensive
  • Data loss
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

4 ways of changing to a new system

A
  • Direct changeover
  • Parallel
  • Pilot
  • Phased
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Direct changeover

A

When the old system is stopped and replaced completely by the new system

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

Parallel

A

When both the new and old system run simultaneously and data is entered into both

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

Pilot

A

New system tested with small part of the organization, bugs are fixed and then the system is expanded into the rest of the organization

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

Phased

A

When the new system is introduced in phases and the old system gradually phases out

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

2 pros and 1 con of Direct Changoeover

A

Pros:
- Quick changeover
- New system is available immediately

Con:
- There is no backup system in case of failure

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

2 pros and 1 con of parallel changeover

A

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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

2 pros and 1 con of pilot changeover

A

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

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

2 pros and 1 con about Phased Conversion

A

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

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

Data migration

A

Moving data from one system to another

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

3 possible problems with data migration

A
  • Incompatible file formats
  • Validation rules
  • Different currencies
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Legacy System and 1 example

A

Old technology, computer system or application that is no longer supported. E.g. Windows XP

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

3 characteristics of traditional software/local software

A
  • One-time fee
  • Used on one computer
  • Free trial not available
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

3 characters of SAAS/Remote software

A
  • Subscription fee
  • Use on any computer via internet
  • Free trial often available
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

2 cons and 2 pros of SAAS

A
  • 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
17
Q

Static Testing

A

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.

18
Q

Dynamic testing

A

Code is executed and VALIDADED to ensure the code produces the required result and also to check for bugs.

19
Q

Alpha Testing

A

Team behind the software tests each user journey and confirms they work as intended

20
Q

Beta Testing

A

Testing of the software by end-users to see how it performs in real-world scenarios

21
Q

Black box testing and who does it?

A

Testing for full functionality of a software without looking at the code behind it. Done generally by software testers

22
Q

White Box Testing and who does it?

A

Testing the code and internal structure of the program to make sure it works. Done by the software developers.

23
Q

User Acceptance Testing what is it and what is it AKA

A

AKA end-user testing

Software tested by end users to see if it meets their expectations and whether it is right for them.

24
Q

Usability

A

How easy is it to use a software

25
Q

User Documentation

A

These are documents that provide an explanation of how to use a particular software.

Some types include:
- Hard copy manuals/booklets
- Online PDFs
- Help Files

26
Q

2 types of user training

A
  • In-person classes
  • Online training
27
Q

Automated Testing

A

Uses automated testing software to rapidly execute tests for comparing outputs of a program to expected outputs.

28
Q

Dry Run

A

Using a trace table to test data

29
Q

3 ways to prevent data loss

A
  • Failover systems
  • Redundancy (having copies of the data that can be used in case the data in the main system is lost)
  • Online/offsite storage
30
Q

3 causes of data loss

A
  • Human error
  • Natural disasters
  • Hardware malfunction
31
Q

3 Social and ethical issues to consider with software design

A

Reliability - Does the program actually function as intended

Jobs - Does the software solution eliminate human jobs?

Security - Is the data in the program secure?

32
Q

Stakeholder

A

A person that has interest in a business and can affect/be affected by it

33
Q

Outline 2 types of getting requirements from stakeholders

A
  • Direct observations (observing the current/new system in use in the real-world)
  • Interviews (Ask selected individuals directly for feedback)
34
Q

Prototype

A

It is an unfinished version of the product that displays key functionality and is used to get feedback from stakeholders.

35
Q

Iteration (in software development)

A

A cycle that ends in a finished software solution by allowing for constant improvement based on user feedback.

It goes like this:

Prototyping –> testing –> analyzing test results –> refining

36
Q

Software deployment how is it done and 2 things to consider after a software has been deployed

A

Released

2 things to consider:
- Updates (software file that fixes a problem found after release)
- Patch (temporary fixes)

37
Q

3 usability problems

A

Screen size too small

Buttons too small

Battery life is too short

38
Q

Accessibility and 3 types to improve

A

How easily can people, especially those with uncommon challenges, use software?

  • Braille Keyboard
  • Voice recognition
  • Text to speech mode