ISSUES…

Professional Issues
Fall-2018

National College of Business Administration and Economics

 Issues
 Issue, synonym for a problem or a point in question

 Otherwise known as problems, gaps, inconsistencies, or

conflicts, and need to be recorded when they happen

 Issue(computers), a unit of work to accomplish an

improvement in a data system
 Planning

Execution

Monitoring

Control
SDLC!

The activities of the software

development process represented in
the waterfall model
 ITI’s

In computing, the term issue is a unit of work to

accomplish an improvement in a system

The word "issue" is popularly misused in lieu of

"problem". This usage is probably related
 ITI’s
An issue could be

Bug

Requested Feature

Missing Documentation

Task
 Issues as per Severity
Issues are often categorized in terms of severity
levels.
Different companies have different definitions of
severities. Two basic segmentations of issues as per
severity are:

CRITICAL COSMETIC
 Critical
 High:The bug or issue affects a crucial part of a system, and
must be fixed in order for it to resume normal operation.

 Medium: The bug or issue affects a minor part of a system, but has some
impact on its operation. This severity level is assigned when a non-central
requirement of a system is affected.

 Low: The bug or issue affects a minor part of a system, and has very little
impact on its operation. This severity level is assigned when a non-central
requirement of a system (and with lower importance) is affected.
 Cosmetic
 The system works correctly, but the
appearance does not match the expected
one.

 For example: wrong colors, too much or too

little spacing between contents, incorrect font
sizes, typos, etc. This is the lowest severity issue.
 ITI’s Investigation
 Inmany software companies, issues are often investigated by
Quality Assurance Analysts when they verify a system for
correctness, and then assigned to the developer(s) that are
responsible for resolving them.
 Theycan also be assigned by system users during the User
Acceptance Testing (UAT) phase.
 Issues
are commonly communicated using Issue or Defect
Tracking Systems. In some other cases, emails or instant
messengers are used.
 Common Causes

 Inaccurate estimates of needed resources

 Badly defined system requirements
 Poor reporting of the project's status
 Unmanaged risks
 Poor
communication among customers,
developers, and users
 Common Causes
 Unrealistic or unarticulated project goals
 Use of immature technology
 Inability to handle the project's complexity
 Sloppy development practices
 Poor project management
 Stakeholder politics
 Commercial pressures
 Issue types

 Define the categories of issues that the

organization or personnel are likely to encounter.

 This
helps to track issues and assign the right
people to resolve them.
 Issue types
1. Technical
Relating to a technological problem in the project

2. Business Process
Relating to the project's design

3. Change
Relating to business, customer, or environmental changes.

4. Third Party
Relating to issues with vendors, suppliers, or another outside
party
 Issues vs Risks
 The exact nature of both is largely unknown before
you begin.
 An issue tends to be less predictable; it can arise
with no warning.
 With risks, you usually have a general idea in
advance that there's a cause for concern.

 For example, being unable to find qualified staff is an

identifiable risk. However, when one of your staff is in a car
accident, and hospitalized for three weeks, that becomes an
issue!
 Issue Log
 Providing
a tool for reporting and communicating what's
happening with the project.

 Ensuring that issues are indeed raised, and then

investigated and resolved quickly and effectively.

 Withouta defined process, you risk ignoring issues, or not

taking them seriously enough – until it's too late to deal
with them successfully.
 Issue Priority
 Assign a priority rating to the issue

 High: A critical issue that will have a high impact on project

success, and has the potential to stop the project
completely.

 Medium: An issue that will have a noticeable impact, but

won't stop the project from proceeding.

 Low: An issue that doesn't affect activities on the critical

path, and probably won't have much impact if it's resolved
at some point.
Issue Development
Lifecycle Early Emerging

• As the issue moves through

the first four stages, it attracts
more attention and becomes Dormant Current
less manageable from the
organization’s point of view.

Crisis
 Issue Status
 Open– The issue has been identified, but no action
has yet been taken.
 Investigating–The issue, and possible solutions, are
being investigated.
 Implementing– The issue resolution is in process.
 Escalated– The issue has been raised to management
or the project sponsor/steering committee, and
directions or approval of a solution is pending.
 Resolved
 In other words, if the organization’s issues management process
detects an issue in the earliest stage, more response choices–such as
product modification, the introduction of new conduct codes or
anticipatory collaboration with key interest groups–are available to
decision-makers.
 As the issue matures, the number of engaged stakeholders, publics
and other influencers expands, positions on the issue become more
entrenched and the strategic choices available to the organization
shrink.

 If and when the issue becomes a crisis for the

organization, the only available responses are reactive
and are sometimes imposed by external parties, such
as government agencies. Not all issues reach the crisis
stage and many crises are not the result of an
underlying issue
Security

Reliability

Ethics

Privacy

Digital Piracy
Public Domain Software
Ergonomics

Environment
 Security & Security Breach
 Security is the means of safeguarding and
protecting an enterprise’s information technology
assets, that is by keeping away from criminals,
natural hazards, and other threats, while a breach
is a breakdown in security.
 Site Security
 Resource Security
 Network Security
 Service Security
 Types of Security Breach

 Intrusion: Forced and unauthorized entry into a

system.

 Interception:Aimed at preventing the capture of

data and information transmitted over an
enterprise network or other communications link.
 Results of Security Breach

 Destruction of Resources
 Corruption of Data and Applications
 Denial of Services
 Theft of Services
 Theft of Resources
 Denial-of-Services Attack

 Depriving, usually intentionally and temporarily, an

enterprise or its users of the services they would
normally expect to have.

 Involving a network service (such as e-mail) or

access to a location on the network (such as a
Web site).
 Internet Scam
Fraudulent or deceptive acts or operations
designed to trick individuals into spending
their time and money with little or no return.

Common scams include identity theft, chain

letters, auction fraud, vacation prizes, and
advance free loans. Almost all Internet
scams initiated by mass e-mails.
 Malicious Programs
 Also known as malware (malicious software),
include viruses, worms, and Trojan horse.
 Viruses migrate through networks and operating
systems and most attached to programs and
databases.
 Worms are special viruses that self replicate to slow or
stop a computer’s operation
 TrojanHorses are programs that come into a computer
system disguised as something else. While not a virus,
Trojan horses deposit viruses onto unsuspecting
computer systems.
 Sources
of
Security Breach

• Employees
• Computer Viruses
• Hackers & Crackers
• Organized Crime
• Terrorists
 Sources of Security Breach
 Employees: This is the largest category of
computer and enterprise criminals where an
employee (insider) who gain access to certain
records or files without prior permission in order
to tamper (manipulate figures, steal records or
damage files).
 Organized Crime: including imitating and fake.
Identify Theft: Loss of personal identity through a security
breach.
 Sources of Security Breach

Hackers and Crackers

White Hat Hackers
Black Hat Hackers
 Sources of Security Breach
 Terrorist: Someone who conducts a
“premeditated, politically motivated attack
against information, computer systems, computer
programs, and data, which results in violence
against non-combatant targets by sub-national
groups or undercover agent.” A terrorist usually
cause potential crime to satellites and wage
economic warfare.
 Cyberterrorism: Terrorist attack on computer facilities in
companies that rely on IT to produce their services.
 Security Measures

 Security
involves keeping enterprise hardware,
software, data and programs safe.

 Some measures are encrypting messages,

restricting access through passwords and
firewalls, backing up data and storing the data
in a safe remote location.
 General Security
 Change access passwords frequently
Policies &
 Restrict system use
Procedures
 Limit access to data
 Set up physical access controls
 Partition responsibilities
 Encrypt data
 Establish procedural controls
 Institute educational programs
 Audit system activities
 Log all transactions and user activities
 Virus Protection
Norton Software/Antivirus
Bit defender

Kaspersky

Avast

Panda

PC Cillin
 Encryption

 Digital Signature Encryption: Relies on a

mathematical coding scheme designed to foil
a virus’s attempt to attack programs and data.

 Encryption
 Firewall
Proxy Server
Firewall: A special-purpose software program
located at a network gateway server.

Proxy Server: Act as an intermediary between

a PC and the Internet, separating an enterprise
network from an outside network
 Reliability

 The assurance that computers and

communication systems will do what they
should when they should.
 Ensuring Reliability
 Fault-tolerant
Computer: A computer designed with
duplicate components to ensure reliability.

 Uninterruptible Power Supply (UPS) System

 Disaster Recovery Plan: A procedure for restoring data

 Off-siteBackup Facility: A backup computer center

located away from a company’s main facility.
 Ergonomics
 Ergonomics is the study of human factors related
to things people use, including computers

 Eyestrain and headache – take frequent breaks; avoid glare

on the monitor.
 Back and neck pain – use adjustable chairs, tables, monitor
stands, keyboards, and footrests.
 Repetitive Strain Injury (RSI), also known as repetitive motion
industry, includes carpal tunnel syndrome – take frequent
breaks, use good posture; adopt healthy lifestyle; use
ergonomic keyboards.
There are few constraints provided to you for two
different venues, create a separate issue log for the given
constraints.
1. Multimedia dysfunctional at Lab 1.
2. Slide visibility low at Lab 2.
3. Lab 1, row # 1: systems not working, power supply cut off.
4. Lab 2, sitting capacity is lesser than the student count.
5. Lab 2, multimedia pin broken, pin available, administrator not available.
6. Lab 1, GIS software not working on systems in row # 3, rest working, no power supply or hardware issues.
7. Lab 2, office 2013, partially functional throughout the systems in the lab.
8. AC’s not working in Lab 1.
9. Lab 2, professional training courses to be conducted, day 1, RA’s conducting the class.
10. Lab 1, instructor system’s mouse dysfunctional.
11. Lab 2, instructor system windows corrupt.
12. Lab 1, software packages require update.
13. Lab 2, instructor system, ERP prototype not deployable.
14. Lab 1, instructor system LCD display out.
15. Lab 2, printer ink finished.