Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

System Analysis and Design > Finals > Flashcards

Finals Flashcards

1
Q

List the types of software piracy

A

Counterfeiting
Internet Piracy
End User Piracy
Keygen and serial piracy
Hard-Disk Loading

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

List and explain practices expected from an IT professional

A
  • Personal Development

stay up to date with new technologies, methodologies and knowledge

  • Organisation and Management

plan and track objectives of teams and allocate tasks according to ability, also communicate well

  • Contracting

use formal contracts to meet the needs and protect both parties

  • Privacy, Security and Integrity

able to identify and evaluate all risks relating to privacy, security and integrity, monitor and track all risk contentiously

  • Team Working skills

have team working skills to work with other people

  • Collaboration

IT often involves working in teams , being able to communicate well is essential for an IT professional

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

Professionalism

A

refers to having the knowledge, competence and skills needed, and behaving in such a way to allow a person to successfully complete specific work

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

Employment Equity

A

Concept that strives to eliminate discrimination and promote equal opportunity for all regardless of background, race, gender.

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

You need to be able to list and explain risks that can be expected (ICT-related)

A

Scope creep
Cyber security threats
Inside threats
Hardware and software failure

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

Scope creep

A

occurs when new features or requirements are continuously added to the project beyond the initial scope, leading to delays and increased cost

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

Cybersecurity threats

A

These include malware, ransomware, phishing. and hacking attacks that can be compromise the confidentiality, Integrity and availability (CIA) of data and systems

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

Inside threats

A

Insufficient training among employees can lead to Security lapses and increase to risks

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

Hardware and software failure

A

failure in software or hardware could result in loss of data and may be expensive to recover.

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

Principles of dialogs design as part of system.

A

Feedback -helps users to know that an action has been recognised and accepted by system

Consistent -The layout, design and behavior of dialog. Should be consistent through out the system.

Error handling-Error message should be shown when ever something. goes wrong in the system, be specific on cause of the problem and if possible, specify how to fix the problem

Clarity and simple - Dialogues should be clear and straight forward.

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

Concepts related to the system maintenance

A
  1. System changes
  2. System failure
  3. System crashes
  4. System backups
  5. Capacity planning
  6. System upgrades
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

List and explain types of tests

A

Unit testing
Integration testing
System testing
Usability testing

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

Unit testing

A

testing parts of the system in isolation

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

Integration testing

A

testing that parts of a system work together properly

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

System testing

A

testing that the system works property as a whole

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

Usability testing

A

testing that the system does what it is supposed to do and in the correct way

17
Q

Give reasons for reviewing a project after implementation

A

To determine whether the project met its objectives and achieved the desired outcomes
To identify any problems or issues that arose during the implementation phase
To evaluate the effectiveness of the system and identify areas for improvement
To ensure that the system is still meeting the needs of the end users and business, and to identify any new needs that may have emerged Since the system was implemented
To ensure that the system is being used in accordance with best practices and compliance standards.

18
Q

System analysts should be able to(role of SA in problem solving)

A

fully understand and define the problem
develop various possible ways of addressing or solving the problem
evaluate and propose the best approach
assist the team in designing, implementing and delivering the resulting system

19
Q

Types of Business source documents

A

Organisational: organisational charts, mission statements, business plans, strategies
Policy and procedure: invoices, receipts, application forms, reporting
Project related: Minutes of meeting, emails about problems or requested changes, customer complaints
System related: system specification, database designs, help desk logs, change requests

20
Q

Event

A

business related occurrence which can be clearly defined
occurs at a specific time and place
triggers a response from the system

21
Q

three types of events

A

External events - occurs externally to the system in the system environment

Temporal events - occur internally to the system and are triggered by time

State events - occur internally to the system and are triggered by changes in state due to another event

22
Q

List SIX data gathering techniques

A

interviews
questionnaires
business source documents
observation of people and processes
surveys

23
Q

FOUR types
of adoption/implementation strategies.

A

Big bang/Direct
Phased
Parallel
Hybrid

24
Q

Advantages of Big bang/Direct implementation

A

Simple
Saves time
Saves money

25
Q

Disadvantages of Big bang/Direct implementation

A

Risk of not finding the remaining errors in the new system before going live

No backup system is there to continue business operations

26
Q

Advantages of Phased implementation

A

Capitalises on the same advantages

Reduced risk because smaller pieces of the system are switched over

27
Q

Disadvantages of Phased implementation

A

involves more effort
logistical issues

28
Q

Advantages of Parallel implementation

A

compare every event done on the new system with the results of the old system to find errors faster

29
Q

Disadvantages of Parallel implementation

A

involves more effort
logistical issues

30
Q

Risk mitigation

A

analysis of the probability of a risk occurring and determining how severe it ‘s impact would be

31
Q

Risk management

A

the planning, identifying potential risks, assessing the risks, putting place a contingency plan to deal with any risks that occur

32
Q

Black-box testing

A

method of software testing that examines the functionality of an application without peering into its internal structures or workings

33
Q

White-box testing

A

method of software testing that provides the tester with complete knowledge of the application being tested, including access to source code and design documents

34
Q

SCRUM principles

A

Team focused
Responsive
Incremental

35
Q

main function of CASE tools

A

designed to support the the engineering environment

36
Q

CASE tools

A

Modelling tools
Documentation tools
Engineering tools
Construction

37
Q

examples of Agile software methodologies

A

eXtreme Programming
Unified Process
SCRUM

System Analysis and Design (1 decks)

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