Comp Sci Systems 2 Flashcards

1
Q

Legacy System

A

An old technology or computer system

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

Legacy System Compatibility

A

Operating systems. data formats. hardware

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

Legacy System (lack of) replacement

A

Still work well. too costly to develop new system. users are comfortable

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

In House hosting

A

+Low ongoing costs. full control. all data is kept within the organization -High initial cost. technical skills required to maintain

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

Outsourced hosting

A

+Low initial cost. no technical skill required -High ongoing cost. loss of full control. security risk

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

Installation Processes

A

Parallel running. pilot running. phased conversion. direct changeover

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

Data migration

A

The process of moving data from one system to another. usually an older system to a newer one.

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

Data migration issues

A

Incompatible file formats. data structures. validation rules Incomplete data transfer international conventions on dates. currencies and character sets

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

Testing

A

Debugging. alpha testing. beta testing. black-box testing. white box testing. unit testing. system testing. acceptance testing. automated testing

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

Debugging

A

Ongoing. happens during development

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

Alpha testing

A

the first stage of testing. done by the programmers themselves

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

Beta Testing

A

Later testing. done by future users when the system is almost finalised

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

Black-box testing

A

testing what the system is supposed to do. from the point of view of the user. with no knowledge of how the program does what it does

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

White-box testing

A

testing the system from the point of view of the programmer. with full knowledge of how it does what it does

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

Unit testing

A

testing the modules or components of the system separately

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

System testing

A

Testing the system as a whole

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

Acceptance testing

A

The last testing phase once the system is delivered to the user

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

Automated testing

A

Using software to test software

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

Importance of user documentation

A

Installation. operation. troubleshooting. sample data and screens. easing transition from legacy systems

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

Methods of providing user documentation

A

Paper manuals. online manuals. interactive tutorials. dedicated support teams

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

Paper manuals

A

Dont need to be near a computer need multiple copies

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

Online manuals

A

Can make use of rich media Can search Always available

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

Interactive Tutorials

A

Makes the learning process more interesting

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

Dedicated support teams

A

can give accurate focused assistance increases salary bill

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Methods of delivering user training
self-study. formal classes. online training. blogs. wikis. forums. FAQ's. getting feedback from users
26
Self-study
Slow. boring and inauthentic
27
Formal classes
Make users feel more secure and involved.
28
Online training
Reduce travel costs. but can cause time zone issues
29
Causes of data loss
virus. malware. nautral disasters. hardware failure. user error. physical damage. power failure. back-ups are essential to prevent data loss
30
Consequences of data loss
Business activities may have to be suspended. damages the organization's reputation. cost to replace data
31
How to prevent data loss
Back up. antivirus. failover and redundancy
32
Back up
removable media (USB). cheap simple to install. large capacity. easy to move offsite. Offsite: take back-ups in case of disasters Online: Always available. requires internet connection. possible security risk
33
Antivirus
Prevent malware from deleting/editing data
34
Failover and redundancy
Redundant system is a clone of an existing that is kept up-to-date in case the primary fails. Failover is the process of detecting a failure of the primary system and switching users to the redundant system.
35
Software life cycle
Continuous monitoring. testing. bug fixing and re-development.
36
Hardware
The machines. wiring. and other physical components of a computer or other electronic system
37
software
the instructions and data that can be stored electronically in a computer system
38
Peripheral
A computer device such as a CD-ROm drive that is not part of the main computer but which is added to provide some extra function
39
Network
A group of two or more computers linked
40
Human resources
the personnel of a business or organization. especially when regarded as a significant asset.
41
Networked world: Client
A computer on a network that makes requests to a server
42
Server
A computer on a network that listens to and responds to requests from clients
43
Email server
A computer on a network dedicated to sending and receiving email
44
DNS server
Domain name service. a computer on a network that translates between user-friendly names of network resources and their numerical IP address.
45
Router
A computer on a network that is responsible for sending network packets to the right host. subnet or network
46
Firewall
A computer on a network that limits the flow of data packets for a number of different reasons including: port number. application. content
47
Stakeholder
is any person or organization that is actively involved in a project. or whose interests may be affected by the execution of a project
48
Methods of obtaining requirements from stakeholders
surveys. interviews. direct observations
49
surveys
+get information from a lot of people quickly -may not ask the right questions
50
interviews
+Stakeholders can make you aware of things you hadn't thought of. unlike with survey in which their answers are restricted -Time consuming. might be biased
51
Direct observation
+avoids bias -time consuming
52
How to arrive at workable solution
Examine current system. competing products. consult experts within the organisation. literature search
53
Design notation
structure diagrams. systems flowcharts. data flow diagrams
54
Structure diagram
Just shows how something can be broken down. doesnt imply sequence
55
Data flow diagram
Very specific and takes a long time to construct them
56
Systems flowchart
Need to consider inputs. processing and outputs. often x shaped. inputs at the top. processing in the middle. outputs at the bottom
57
Purpose of prototypes
Allows user to give immediate feedback. gives a client a better sense of what the software will be as it is easier to understand a prototype than a written explanation. allows developer to verify that he understands the requirements. allows the client to change requirements before fully developing. reduces costs. saves time
58
Importance of iteration during the desing process
Users might find. bugs. unfulfilled requirements. new requirements and improvements
59
Consequences of failing to involve the user in the design process
Increased chance that the software is designed inappropriately. in this case the client might not end up using the software. wasted development cost and reduced productivity.
60
Usability
The notion of how easy a system is to learn and use
61
Learnability
How easy is it for users to accomplish basic tasks the first time they encounter the design?
62
Efficiency
Once users have learned the design. how quickly can they perform tasks?
63
Memorability
When users return to the design after a period of not using it. how easily can they reestablish proficiency?
64
Errors
How many errors do users make. how severe are these errors. and how easily can they recover from the errors?
65
Satisfaction
How pleasant is it to use the design?
66
Ergonomics
designing and arranging things people use so that the people and things interact most efficiently and safely
67
Accessibility
The ability of people to access and benefit from some system. Often people with disabilities or special needs
68
Range of usability problems
Confusing navigation Lack of help No search facility Small. fiddly buttons Too complex. too many functions
69
Measures to improve accessibily of systems
Touch screen Voice recognition Text-to-speech Braille keyboard Screen magnifier Font adjustment and zoom
70
Usability problems: Ticketing
Time zone issues
71
Usability problems: Online payroll
Internet downtime. currency dependant
72
Usability problems: Scheduling
time zone issues
73
Usability problems: Voice recognition
Can't understand accents/languages or speech-impaired users
74
Usability problems: Systems that provide feedback
Feedback not provided in a usable format. Compatibility.
75
SDLC
Asses needs. design specifications. Design/develop/test software. implement systems. support operations. evaluate performance
76
Linear search
examines each element in order until the desired element is found
77
Binary search
- examines the middle element and moves left if the desired element is less than the middle or right is the desired element is greater - more effective than linear search - the key is the value you are searching for
78
Dynamic data structures
memory is allocated dynamically there may be overflow or underflow if allocations are exceeded most efficient use of memory as it uses as much as it needs harder to program as program needs to keep track of data size
79
Static data structures
memory size is fixed no problems during run time with memory allocations might waste memory space easier to program
80
Singly linked list
- Contains a link element called first - Each link is linked with its next node using the next link - The last node carries a link to null to mark the end of the list - Traversal is only linear
81
Doubly linked list
- Contains a link element called first and last - Each link carries data fields to the next or previous link fields - Each link is linked with its next node using the next link - Each link is linked with previous node using the previous link - The last node carries a link to null to mark the end of the list - 2 way traversal
82
Doubly circular linked list
- The next pointer of the last node points to the first node - The previous pointer of the first node points to the last node making it circular in both directions
83
Pros of linked lists
- Flexible Size - Simple insertion and deletion of nodes - Easy to implement stacks and queues
84
Cons of linked lists
- Additional memory usage due to pointers - Sequential access only - Nodes are stored in an unconnected fashion. which slows down access speeds
85
binary tree traversal
- In order (LDR) - Pre Order (DLR) - Post Order (LRD)