Scribd
Upload
78 views

Computer Science Notes HL

This document discusses computer systems and the process of installing new systems. It covers computer hardware, software, planning system installation, legacy systems, business mergers, compatibility issues, different implementation methods like SAAS, alternative installation processes like parallel running and phased changeover. It also discusses issues in data migration like changes in language, timezone etc. and different types of testing like alpha, beta, unit, integration and user acceptance testing.

Uploaded by

jay soni
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
78 views

Computer Science Notes HL

This document discusses computer systems and the process of installing new systems. It covers computer hardware, software, planning system installation, legacy systems, business mergers, compatibility issues, different implementation methods like SAAS, alternative installation processes like parallel running and phased changeover. It also discusses issues in data migration like changes in language, timezone etc. and different types of testing like alpha, beta, unit, integration and user acceptance testing.

Uploaded by

jay soni
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Chapter 1

1System fundamental
1.1 system in organization
1.1.1Computing system
A computing system is a dynamic entity, used to solve
problems and interact with its environment.
1.1.2Computer hardware
Computer hardware is a Collection of physical elements that
make up a machine and its related pieces; the casing, circuit
boards, electronic chips, wires, disks, keyboard, monitors,
etc.
1.1.3Computer software
Computer software is the collection of program that provide
the instruction that a computer can carry out. At the very
heart of a computer system is the information that manages
it.
1.1.4 Planning and system installation
Installing a new system
Unpacking of files in a computer
The system environment
It is the limit of a system and its use the environment of a
system is decided by its creator it consist of how a system or
software will work. When a new is planned its environment is
decided and to change environment of an out-dated system
it is updated and installation of new system is done.
Changes in environment
Changes in environment of a system are done when the old
system is creating problem so it can be upgraded to solve the
existing problems.
Problems with change
There are many chances of problem during changing of
environment of a system
1 legacy system
Legacy system refers to out-dated computer system that
need a change in its environment as it is not able to fulfil the
needs of a client.
And it is costly to change and opt for a new system
But it is important because problems for the out-dated
system are
1 cost for maintaining old system can be very high
2 old systems can fail frequently which can lead to data loss
3 technical supports for out-dated system may not be
available
4 legacy system can have security threats.

Business mergers
Business mergers refer to the combing of two or more
entities using different system. During that they all need a
common system environment for all the entities
Ways of integration
1 keep both information system and develop them to have
same functionality problem is high maintenance cost
2 replace both systems with a new system problems are high
initial cost for developing a new system and cost and time for
training employees.
3 keeping the best system for both the entity employees will
face a problem working with unfamiliar working with other
entities system
Compatibility issues
When a system changes, consequences can occur for a
person operating new system day to day. So a developer
should keep these consequences in mind during developing
the software and should test software for errors and bugs. As
new system can have greater effect on an entity which is
totally based on system.
Different system implementation
1 saas (software as a service)
Saas is an software which is totally installed on cloud and can
be used anywhere and data is accessible by an authorized
person with the help of internet and a web browser.
Developer develop a system according to need of a client and
post it on cloud and all the work is saved on cloud it is easy to
access and cost effective and time saving and also save space
as now we don’t need big storage device to save dataAnd
powerful computers to access it
Example –netflix

Alternative installation processes


The installation of a new system which is faced by an entity
one of more times which causes problems as old sytem get
retired and new system takes its place so problem come is
choosing a right way of change over.
Types of changeover
1. parallel running- it is a changeover technique in which
new system runs parallel to old system and as client get
satisfy with the new system the old system can be
terminated and retired and if new system fails entity can
continue with old till the time new system get perfect
this method is popular because it has very limited risk.
But problem with this changeover method is that it has
high cost of maintenance as entity have to maintain two
system parallel.
2. Big band or direct- this method is very risky as entity
directly shut down the old system and install new
system
3. Pilot- it is a method mostly used by large organization as
it is a way to try out the new system on a small scale
before implementing is done on whole organization.
4. Phased changeover in this method the new system is
implemented in several stages. A phased conversion
requires a long time to be put in place and a significantly higher
amount of work

Problems with data migration


Issues during data migration
1. Change in language can be a problem
2. Change in timezone and currency
3. Change in date formate
4. File formate

Testing
Testing is investigating a computer system to find flaws,
discrepancies or errors
Types of testing
1. Alpha testing- testing done during developing process
done by third paytry to get feedback and make changes
accordingly
2. Beta testing- after alpha testing , the developer provide
a version to public for testing and have feedback.
3. Dry run testing Is a check to ensure there are no errors in the
algorithm or the logic of the system. Is conducted by engineer
on pen and paper.
4. Unit testing- test involve small, individual tests for sun
modules of the system can be done automatic by a
different system.
5. Integration testing- all components are tested together to
ensure that system work as a whole
6. User acceptance test- done at client place as a final
product to get feedback by clients.
7. Debugging – finding logically bugs are making change to
debug mostly done by automated by different system
which make it easier.

User focus
User documentation helps user to operate new system
Types of documentation

You might also like