Finals Flashcards
List the types of software piracy
Counterfeiting
Internet Piracy
End User Piracy
Keygen and serial piracy
Hard-Disk Loading
List and explain practices expected from an IT professional
- 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
Professionalism
refers to having the knowledge, competence and skills needed, and behaving in such a way to allow a person to successfully complete specific work
Employment Equity
Concept that strives to eliminate discrimination and promote equal opportunity for all regardless of background, race, gender.
You need to be able to list and explain risks that can be expected (ICT-related)
Scope creep
Cyber security threats
Inside threats
Hardware and software failure
Scope creep
occurs when new features or requirements are continuously added to the project beyond the initial scope, leading to delays and increased cost
Cybersecurity threats
These include malware, ransomware, phishing. and hacking attacks that can be compromise the confidentiality, Integrity and availability (CIA) of data and systems
Inside threats
Insufficient training among employees can lead to Security lapses and increase to risks
Hardware and software failure
failure in software or hardware could result in loss of data and may be expensive to recover.
Principles of dialogs design as part of system.
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.
Concepts related to the system maintenance
- System changes
- System failure
- System crashes
- System backups
- Capacity planning
- System upgrades
List and explain types of tests
Unit testing
Integration testing
System testing
Usability testing
Unit testing
testing parts of the system in isolation
Integration testing
testing that parts of a system work together properly
System testing
testing that the system works property as a whole
Usability testing
testing that the system does what it is supposed to do and in the correct way
Give reasons for reviewing a project after implementation
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.
System analysts should be able to(role of SA in problem solving)
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
Types of Business source documents
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
Event
business related occurrence which can be clearly defined
occurs at a specific time and place
triggers a response from the system
three types of events
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
List SIX data gathering techniques
interviews
questionnaires
business source documents
observation of people and processes
surveys
FOUR types
of adoption/implementation strategies.
Big bang/Direct
Phased
Parallel
Hybrid
Advantages of Big bang/Direct implementation
Simple
Saves time
Saves money
Disadvantages of Big bang/Direct implementation
Risk of not finding the remaining errors in the new system before going live
No backup system is there to continue business operations
Advantages of Phased implementation
Capitalises on the same advantages
Reduced risk because smaller pieces of the system are switched over
Disadvantages of Phased implementation
involves more effort
logistical issues
Advantages of Parallel implementation
compare every event done on the new system with the results of the old system to find errors faster
Disadvantages of Parallel implementation
involves more effort
logistical issues
Risk mitigation
analysis of the probability of a risk occurring and determining how severe it ‘s impact would be
Risk management
the planning, identifying potential risks, assessing the risks, putting place a contingency plan to deal with any risks that occur
Black-box testing
method of software testing that examines the functionality of an application without peering into its internal structures or workings
White-box testing
method of software testing that provides the tester with complete knowledge of the application being tested, including access to source code and design documents
SCRUM principles
Team focused
Responsive
Incremental
main function of CASE tools
designed to support the the engineering environment
CASE tools
Modelling tools
Documentation tools
Engineering tools
Construction
examples of Agile software methodologies
eXtreme Programming
Unified Process
SCRUM
