1.1.1_to_1.1.7_Planning___System_Installation

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 21

PLANNING AND SYSTEM

INSTALLATION
1.1.1 TO 1.1.7
Life Cycles
The context for
which a new
system is planned.
 A new system is generally made
to replace and older system that
is inefficient, outdated,
redundant or no longer serves
its intended purpose.
 The purpose of the new system
can be to increase productivity
or quality or even to minimize
costs.
 The new system should reduce
or remove the errors/flaws of
the existing one.
The context for which a new system
is planned.
 How feasible is the new system?
 Change management involves the
change within organization with the
general goal of maximizing benefits and
minimizing negative impact. (especially
the change on individuals)
The need for  People can often feel uncomfortable with
change change management as they may feel
that their jobs are at risk. Unfortunately
management in some cases these does become true.
 Defined as
 “Change management is a systematic approach to
dealing with the transition or transformation of an
organization's goals, processes or technologies. The
purpose of change management is to implement strategies
for effecting change, controlling change and helping people to
adapt to change.”
 Legacy system – An old technology, hardware,
computer system or application
 Just because it is old it does not mean it does not
play an important role in an organization. It might
Compatibility be that its data cannot be converted to newer
formats.
issues resulting
from situations  Even NASA using legacy systems ! (what they need
does the job and so there is no need to change it)
including legacy
 It is clear that even with today’s technology
systems or combining legacy systems and newer systems can
business still be a big issue.
mergers
Compatibility issues resulting from
situations including legacy systems or
business mergers

 Business Merger - The


combining of more than one
entity (in this case Business)
 This is mainly done to
reduce costs
 An essential pat of this is the
consideration as to whether
or not the data from both
systems will be compatible.
Different systems
implementation
 What is SaaS? (also
known as on demand
software)
 Software is hosted and
managed from a central
data centre
 Resides on the cloud so
a broadband connection
and a web browser is
required
 Users pay a
subscription fee to
access services
 Any application hosted
on a remote server that
can be accessed over
the Internet is
considered a SaaS.
Activity

 What Saas Services do you use (Try to think of 2)?


 What are their pros and cons?

Service What is it used Pros Cons


for
 How does SaaS benefit its clients?
 Low start up costs and does not require large sums
of money for installation, maintenance and
upgrading.
 Only have to pay for the subscription required and
offer “scalable solutions” where clients can adjust
their subscription based on what is required.
 SaaS is supported within a wide range of devices
Different systems (mobile, desktop)
implementation  Few IT personnel are required as all updates are
managed away from the business location.
 There are however some drawbacks:
 If the SaaS company goes out of business data could
be inaccessible and result in data loss
 As the system requires an internet connection this
could result in slow response times or no connection
at all
 Integrating other Software into the system may be
difficult
Different systems implementation

 On premise software?
 On-premises software (sometimes abbreviated as "on-prem") is installed and runs on computers on
the premises (in the building) of the person or organization using the software, rather than at a remote
facility such as a server farm or cloud.
 Unlike the SaaS on premise software will be installed, upgraded and maintained within the organization
rather than at a remote facility.
 This means higher initial costs however could save in the long run as the organization would not have to pay
a subscription fee to maintain the system.
 The service would remain in house and so is not operational based on whether or not the internet is
available.
 This can prove costly when making upgrades, maintaining etc as hardware such as network & backup
equipment will have to be factored.
Alternative Installation Processes

 Installing a new system is pretty much something that every


business or organization will encounter at some point.
 This is the point where the old system is retired and the new
system takes its place
 This then poses one big question…….
 How do we implement the new conversion/changeover
method?
Direct – The old system is stopped and the
new system is started
• Advantages –
• New System is available immediately
• Minimal time and effort
• Disadvantages –
Alternative • If the new system fails there is no backup

Installation Parallel – The new system is run alongside


the new system and data is input into both
Processes systems
• Advantages –
• If the new system fails the old one acts as a backup,
• The outputs from the systems can be compared to
determine If the new system is running correctly.
• Disadvantages –
• Running of the two systems is costly in terms of time
and money.
Pilot – The new system is piloted (trialled) in a small
part of the business. Once it is running correctly then
the new system is implemented across the
organization.
• Advantages –
• All features can be fully trialled
• If the system fails it only affects a small part of the organization

Alternative • Staff who were part of the pilot can be used to train other staff.
• Disadvantages –
• For the section that is piloting there is no backup
Installation Phased – The new system is introduced in phases as
Processes parts of the old system are gradually replaced with
the new system.
• Advantages –
• Allows other people to get used to the new system
• Training can be done in stages
• Disadvantages –
• If the new part of the system fails there is no back up for that
part of the area..
Activity – Change over Scenarios

 An Airport Ticketing system is now outdated and is replaced with a brand new cloud
based system.
 A school have been using Microsoft Teams but have trialled new even better software.
They are nervous about switching straight away.
 A company outsourced their services to a company who has gone bankrupt and are now
needing a new service.
 A high-end stock market company are considering a new type of AI trading software but
are a little unsure of how it will work in their company.
Problems that may arise as a part of data migration

 Data migration refers to the transfer of data between


different formats, storage types and computer
systems.
 This process is normally done automatically by
computers as the amount of data that needs to be
moved in most cases is far to big for human resources
 Possible problems include
 Incompatible file formats
 Data structure differences
 Validation rules
 Incomplete data transfers
 International conventions on dates,
 currencies & character sets
Testing is very important in developing a computerized
system, as it tries to ensure that the system works as
expected.

A system that does not work as expected (it is buggy)


greatly reduces productivity and end user satisfaction.

Various Normal data – entering standard data into the system


(example in a number system from 1 to 100 add numbers
35, 76,45)
Types of
Data at the limits - would involve add the numbers 0,100.
testing This can also be used to test if statements

Extreme Data – Would be adding data outside of the limits


-35, 105, 1160 -456. This should be rejected but test incase
the user accidently adds another digit

Abnormal Data – This would involves adding something


completely unexpected and out of character for example
adding the word “Hello” to the 1 to 100 numbering system
Activity - Temperature Checking

 Given a set of Temperatures for a set of Covid checks the following protocol is followed
 Any temperature lower than 30.0 is not accepted
 Any Temperature higher than 45.0 is not accepted
 Temperatures higher than 37.3,but below and including 45 mean that are infected
 Temperatures between 30 and 37.3 (including 37.3) are within the acceptable limits
 Now determine a range of test data to interrogate the system as best you can.
 With thousands of people using this system every day we cannot afford for this to be
wrong
 Please provide a suitable document to outline and provide details. Brief explanantions or
annotations are acceptable.
Various Types of testing

 Alpha testing - Alpha testing is done before the software product is made available to the
general public. Normally, Alpha testing will be carried out by the company that develops the
software in a laboratory type environment and not by the end users in their usual workplaces.
 Beta Testing – Beta testing includes comments and suggestions of the users. Unlike Alpha
testing, users outside the company are involved in the testing. In some cases, the Beta
version will be made available to the general public. This can provide vital real-world
information and feedback.
 Dry run testing - Dry-run testing is conducted using pen and paper by the programmer.
During dry run testing the programmer mentally runs the algorithm.
 Debugging - Debugging is a systematic process of finding and correcting the number of bugs
(errors) in a computer program.
Various Types of testing

 Validation and verification in relation to data input:


 Validation is the process of evaluating whether data input follows appropriate specifications and is
within reasonable limits.
 Verification is the process of ensuring that the data input is the same as the original source data. A
way of ensuring data verification is through double entry.
Various Types of testing

 Verification and validation in software testing


 Verification is the confirmation that a computer
product meets identified specifications, while
validation is the confirmation that a computer
product meets its design function or is appropriate
for its intended use.
 Validation :Are we developing the correct system?
 Verification: Are we developing the system
correctly?
 Validation: Does the product meet the customers
needs?
 Verification: Does the product comply with a
specific regulation or condition?

You might also like