Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

Eduqas a-level computer science > Systems analysis > Flashcards

Systems analysis Flashcards

(65 cards)

Start Studying
1
Q

Waterfall

A

sequential design process where developers drafts out all of the requirements for a system up front

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

waterfall pros

A

client knows what to expect (cost, time), strong documentation allows new team members to be added easily

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

waterfall cons

A

sequential so cannot go back to previous stage of development, if initial requirements are faulty project will likely fail, product only tested after completion so early bugs will impact large bits of code.

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

agile/scrum

A

incremental approach, start with simple project design and work on small modules in sprints - best suited when end goal not clearly defined

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

agile pros

A

changes can be made after initial phase, testing done throughout so bugs are found early, closer relationship between customer an developer

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

agile cons

A

can be hard to predict time needed/costs so can be easy to overrun/go overbudget

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

user documentation

A

targeted towards novice users so must be straightforward without technical terms. should help user perform any task on system

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

user documentation examples

A

instruction manual
installation guide
FAQs

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

technical/maintentance documentation

A

helps employees maintain system and ensure it runs smoothly once implemented

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

maintenance docs examples

A

data dictionary,
annotated code listings,
variable listing

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

feasability study

A

1st stage in systems analysis
aims to understand the problem and determine if it is worth proceeding
feasability report produced at the end

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

feasability study components

A

economic
time
technical
political
operational
legal

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

economic feasability

A

cost effectiveness
do benefits outweigh costs (wages, hardware etc)?

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

time feasability

A

can it be completed in desired time frame?

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

technical feasability

A

does technology needed exist?
can project be done with resources available?
does dev team have technical skills needed?

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

political feasability

A

is it politically motivated?
does it go against people’s beliefs?
eg government work

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

observations

A

analyst shadows employee in natural environment making notes on how they do their job

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

operational feasability

A

are current work practises and procedures enough to support new system?

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

investigation (analysis)

A

2nd stage of development
defines all the requirements of the project

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

main investigation methods

A

observations
questionaires
interviews
document collection

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

legal feasability

A

will project comply with laws in all countries it will be released in?

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

observation pro

A

picks up subtle aspects that may have been otherwise missed

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

observation con

A

people may feel intimidated being watched altering their behavior

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

questionaires pros

A

can be given to large num of people to get large num of opinions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
questionaire cons
creator must have knowledge of the system being built and the people it is being sent to not all sent out will be completed
21
document collection
analyst gathers documents relating to system eg invoices, orders etc to help see what new system needs
22
doc collection pros
documents are reliable doesn't interrupt workers
23
doc collection cons
may contain sensitive info causing viewing restrictions gives limited view of system
24
interviews
key stakeholders are asked targeted questions about current system
25
interview pros
can ask detailed questions with follow up questions
26
interview cons
people can lie so responses must be verified time consuming so only small num of people can be interviewed
27
abstraction
reduce to simplest set of characteristics most relevant to solving problem
28
control abstraction
hides actions and programming control (eg if statements)
29
data abstraction
hides how bits are organised for primitive data types ( eg floating points)
30
decomposition
break large problem into series of sub-problems that can be solved individually and merged to solve whole problem
31
systems implementation
the transfer of the completed project over to the user (4th stage after design)
32
changeover methods
parallel pilot big bang phased
33
parallel implementation
systems run parallel to each other for a time period to allow users to choose
34
parallel pros
users can learn at their own pace, if new system crashes can fall back on old one, can receive feedback
35
parallel cons
some processes are linear and need all using same system hardware may not be able to cope with 2 systems stubborn old system users will still face big bang eventually
36
phased changeover
a modular system implemented gradually with each old module being replaced with a new one
37
phased pros
users can get used to changes gradually
38
phased cons
can take long time and devs must be paid for all of it new system must be modular and fully integrated with old system users may get frustrated with combined system
39
big bang/ direct changeover
old system turned off and new system immediately installed
40
big bang pros
doesn't require additional resources users forces to use new system so can learn together and help each other only a temporary cut to productivity
41
big bang cons
if system fails there is nothing to revert back to training can be hard as everyone is new
42
pilot changeover
in large organisation with departments, several departments can change to new system and provide feedback
43
pilot pros
can receive feedback initial users can change other departments after full release
44
pilot cons
users can become isolated from rest of organisation can be expensive if changes are asked to be made
45
corrective maintenance
system developers called in to fix problems (eg bugs, logical errors) expensive to devs as they should have been spotted in testing
46
white box testing
focuses on program structure - program code is studied and tests are devised to test each possible path (control statement) at least once
47
black box testing
tests functions of the code - creates set of test data to cover all inputs, outputs and program function (valid, invalid and extreme data) does code do what it is supposed to do?
48
alpha testing
carried out by dev's in house testing team highlights errors and omissions in system requirements alpha builds often not stable and won't work fully as customers won't see it.
49
unit testing
ensures individual modules are working as intended
50
integration testing
tests interface between 2 or more software modules to ensure they work together seamlessly. can be done gradually or all together.
51
beta testing
done when product more stable product given to number of potential users who will test and report problems to devs. exposes product to real use.
52
acceptance/end user testing
final stage to ensure devs and client agree system meets the requirements so it can be signed off.
53
incremental backup
only backs up parts of system that have been changed since last backup requires processing to determines which files have been changed
54
full backup
complete backup of all files, software etc that is done regularly and held offsite for safety.
55
methods of storing backups
external hard drive/memory stick CD/DVD magnetic tapes dedicated backup server cloud
56
perfective maintenance
small changes made after system acceptance by devs to make system 'perfect' eg changing colour scheme for individual users
57
adaptive maintenance
changes made by client request after completion of the project at additional cost as they weren't in the original brief
58
backup
process of copying files from main storage to separate area so if file deleted the backup can be accessed to retrieve it
59
file recovery
copying file from backup to wherever file is needed
60
waterfall development stages
1. feasability study 2. analysis (investigation) 3. design 4. implementation 5. testing 6. installation 7. evaluation 8. maintenance

Eduqas a-level computer science (12 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions