1
System Changeover
System Changeover
March 6, 2017
System changeover
The system changeover affects a lot in the overall system. Some decisions about development, user training and data take on will be affected by the method of system transition the user has selected. The commonly available changeover techniques are phased installation, direct transition, and parallel running, and this will need to have been agreed on before the analysis phase is complete because it will affect the system design and will impact on the project planning.
The parallel changeover is the most expensive method, but also the most reliable, especially for new systems where users need adequate training to operate but the best choice when migrating from a manual to an automated system as in the case of HWE Accessories website. It requires that both the old system and the new run side by side over a given period. HWE Accessories Company in their changeover shall adopt this method due to the following reasons;
· The primary goal of a parallel changeover to HWE accessories is to validate the new system by checking the results it produces the effect generated by the old manual system. HWE Accessories need a way of trusting the new system in their daily production process. This option offers a better choice for HWE Accessories in their website system.
· Being a new system, user experience may hinder the performance of the company if it was changed directly. Online commerce systems require a high level of security. The only commerce systems are guaranteed over a period.
· The new system shall be staffed with less temporary workers, where they will be running a percent of the work, while the same transaction is recorded using the manual system until a certain level of trustworthiness is accredited to the new system.
· Most developers usually offer the first few months of a new system as a trial version for users to test and give feedback. At this period, the user can make a narrow decision regarding the system. They can be in a position to tell whether the system meets their requirement and needs or not. Therefore, the parallel changeover will be the best choice to offer this field testing moment for HWE Accessories before purchasing the system and as well as not having made a lot of changes to their current system.
In phased installation, one part of the system is installed first and go live for a period. A second part is then connected after a given period and go live. With direct changeover at given time on a specified date, one system must end while another takes over. It has significant alterations of the current system and policies and procedures of the company. It is the cheapest option, but in case it goes wrong leaves the client unable to carry out regular business. This is the reason why these changeover methods cannot be recommended for the new HWE Accessories system (Tanya, 2017).
The insertion and migration of data including the related tools and process ...
1. 1
System Changeover
System Changeover
March 6, 2017
System changeover
The system changeover affects a lot in the overall system. Some
decisions about development, user training and data take on will
be affected by the method of system transition the user has
selected. The commonly available changeover techniques are
phased installation, direct transition, and parallel running, and
this will need to have been agreed on before the analysis phase
is complete because it will affect the system design and will
impact on the project planning.
The parallel changeover is the most expensive method, but also
the most reliable, especially for new systems where users need
adequate training to operate but the best choice when migrating
from a manual to an automated system as in the case of HWE
Accessories website. It requires that both the old system and the
new run side by side over a given period. HWE Accessories
Company in their changeover shall adopt this method due to the
following reasons;
· The primary goal of a parallel changeover to HWE accessories
is to validate the new system by checking the results it produces
the effect generated by the old manual system. HWE
Accessories need a way of trusting the new system in their daily
production process. This option offers a better choice for HWE
Accessories in their website system.
· Being a new system, user experience may hinder the
2. performance of the company if it was changed directly. Online
commerce systems require a high level of security. The only
commerce systems are guaranteed over a period.
· The new system shall be staffed with less temporary workers,
where they will be running a percent of the work, while the
same transaction is recorded using the manual system until a
certain level of trustworthiness is accredited to the new system.
· Most developers usually offer the first few months of a new
system as a trial version for users to test and give feedback. At
this period, the user can make a narrow decision regarding the
system. They can be in a position to tell whether the system
meets their requirement and needs or not. Therefore, the parallel
changeover will be the best choice to offer this field testing
moment for HWE Accessories before purchasing the system and
as well as not having made a lot of changes to their current
system.
In phased installation, one part of the system is installed first
and go live for a period. A second part is then connected after a
given period and go live. With direct changeover at given time
on a specified date, one system must end while another takes
over. It has significant alterations of the current system and
policies and procedures of the company. It is the cheapest
option, but in case it goes wrong leaves the client unable to
carry out regular business. This is the reason why these
changeover methods cannot be recommended for the new HWE
Accessories system (Tanya, 2017).
The insertion and migration of data including the related tools
and processes
In the transition from the old manual system to the new
automated system, it is essential that the data the organization
already has is safely transferred to the new system. There are
several ways in which HWE Accessories data can be migrated
from their old manual system to the new automated system.
3. · One of these techniques is that HWE Accessories will employ
data entry clerks who will quickly enter quantities of data from
the hard copy file to soft format. This is a traditional method
but very powerful when migrating from a manual system to an
automated system. Errors can result in the process especially
when dealing with large data. HWE Accessories Company staffs
can also be used in entering the data as a way of familiarizing
them with the new system. Since this process is done early
enough before the system development, this data may be out of
date when the system goes live. Microsoft Excel is one of the
essential tools which will be used for the data entry.
· An approach to data take-on that is less prone to error is data
conversion. The data in old format is run through a program or a
series of programs which are not part the application under
development to convert it to a new format. Conversion can also
be from one hardware medium to another. Here HWE
Accessories will employ a bureau who are used in this kind of
conversion. It would be of important especially if HWE
Accessories Company were operating on tapes as a way of
archiving their data and this need to be migrated into modern
hard drives. After this, the structure and the format of data will
come clear to aid developers in the development process of the
website. After the system has been finished, the data will be
converted to a right format such as comma separated values
(CSV) to import to the system.
Configuration management including recommend tools
Configuration management is a system engineering process used
to establish and to maintain the consistency of the product
performance, physical and functional attributes as well as
design, and operational information throughout its life. HWE
Accessories Company will keep track and control changes in
their new automated website system by adopting the following
4. techniques:
· Revision control. A one-time delivery of a software product
never means it is over. Over time, HWE Accessories Company
will demand some changes as well improvement and
enhancement in the software product from the developers.
· The establishment of baselines. HWE Accessories Company
will set policies and procedures which will be used as a measure
of quality assurance of the delivered system.
Tools such as Chief which is an open source product and a paid
enterprise subscription is one of the configuration management
tools which can be used to provide some functionalities.
Another tool is puppet which is started as DevOps and is a very
popular configuration management tool. It’s written in Ruby
and available in both open source and paid version. Most of its
advanced feature are found in the paid version. Other tools
which can be used include Salt, Ansible, and others.
Release processes for updating the system
Once the system has been installed, and in operation, a
maintenance phase kicks off. Here, the HWE Accessories and
the developers will negotiate a warranty contract.
Once HWE Accessories request for an update either based on
security patches, performance tuning or advanced
functionalities and others, the developer shall improve the
existing system based on the HWE Accessories Company's
needs and arrange with them for the installation period and
process (Craig, 2009).
References
Craig, B. (Feb 12, 2009). Sample System Implementation
Guide. Retrieved from http://it.toolbox.com/blogs/enterprise-
solutions/sample-system-implementation-guide-29950
Tanya, R. (2017). Changeover Techniques. Retrieved from
http://smallbusiness.chron.com/changeover-techniques-
5. 34890.html
1
HWE Accessories Website: Contract Plan and System Testing
Document
HWE Accessories Website: Contract Plan and System Testing
Document
February 27, 2017
HWE Accessories Website: Contract Plan and System Testing
Document
HWE Accessories Contract Plan
BSA/515r3 - HWE Website
Contract Plan
Initiating Office: HWE Accessories
Project Title: HWE Website
Requiring Activity: HWE Website Development
Estimated Value: $30,000
Contract Type: Time Specific Contract
1. Evaluation and selection process is used to determine the best
responsive bid, as specified in the solicitation document. As per
HWE accessories, assessment and selection process should be
based on the following criteria:
· The proposals should entail all the necessary and required
accompanying information and documents
· Technical evaluation should be conducted to determine the
expertise or specialization of the contractor.
6. · Financial evaluation of the bid should be performed to detail
out the price of the contract.
· The financial status of the contractor as well plays an
important responsibility in determining their trustworthiness
(Software Evaluation, (n.d.).
2. Contract management is the process of managing contracts
from the point of creation, execution, and analysis with a goal
of maximizing operational and financial gain at an organization
while reducing financial risk. The following mechanism needs
to be employed:
· Quality Assurance Surveillance Plan. It manages contractor
performance assessment by ensuring that systematic quality
control methods are utilized to validate that the contractor's
quality control efforts are timely, efficient, and are delivering
the results specified in the contract or task order.
· Management Plan. It’s an assessment tool for accessing the
set goal and help in creating a realistic, detailed plan for
meeting those goals.
· Work Plan. It outlines the systematic procedure to be followed
to achieve the set goals during the contract period (Tinnirello,
2000).
3. Vendor risk and relationship management. Contract
agreement with an outside third party will subjects HWE
accessories to risks of financial and reputational harm, such as
from breach of contract, fraud, error, data loss, breach of
confidentiality, and so on. The risks associated with vendor
relationships for HWE accessoriesbasically lies on the data to
be handled during the contract period. The following measure
will be put into consideration during the process:
· Confidential and non-disclosure agreement will be drafted and
7. signed by both parties.
· Security policies such as insurance will be employed to take
care of any industrial risk (Gentle, 2002).
4. Software escrow. It is the depositing of software systems
source code with a third party escrow agent. By arranging a
software escrow agreement, you are taking responsibility for
your business continuity and ensuring that the systems you rely
on are always available.
· Enterprise escrow. HWE accessories shall enter into a
corporate escrow agreement with the contractor. The escrow
covers multiple user software systems, usually 6 or more, as
well as the arrangement, provides a cost-efficient solution to
managing a software escrow portfolio.
5. Software licensing. It is a contract between the licensing
party and the party purchasing the software product,
establishing the purchaser's right to use the software. HWE
shall retain the right to use and modify the software as well as
hosting to their local servers.
System Testing Document:
1. Black box testing. It concentrates on internal construction of
a program. This test will be carried out on the following:
· The loop testing – loops are crucial measurement point in a
program to get lead of thing such as infinite loops
· Cyclomatic complexity – which will measure the logical
complexity of the program
· Data flow testing – select paths of the program based on the
variable definition.
8. · Graph matrix – shall be used for testing conditions
2. White box testing. It focuses on functional requirements of
the software. It attempts to find errors in the following
categories:
· Missing or incorrect functions
· Performance errors such as memory exhaustion, overheating,
etc.
· Data structures errors such as stack overflowing
· Interfaces errors where two modules are unable to
communicate or misbehave after integration (Crawford, 2014).
3. Functional testing. Determine whether the stated requirement
are meet by the software product. It includes both functional
requirements and non-functional requirements.
4. Environment. A setup of hardware and software for
the testing teams to execute test cases. The website will be
tested in its working environment and subjected to equivalent
traffic as expected working traffic.
5. Security testing. It attempts to verify that protection
mechanism built into the system works. The site will be
subjected to penetration testing using various tools to reveal all
vulnerabilities that might pose a security risk.
6. User Acceptance Testing. The software is acceptable to the
users if they are to use it and also meet their functional
requirements. It can;
· Discover software errors not yet detected
· Determine whether any significant change need to be done to
the system
· Discover the actual and exact demands of the system
9. 7. Unit testing. Here the team shall test specific parts of the
software for specific functions. It emphasizes on the local data
structure, boundaries and interfaces among others (Singh,
2013).
References
Top of Form
Top of Form
Top of Form
Top of Form
Crawford, S. (2014). CompTIA CASP CAS-002: Black Box,
White Box, and Gray Box Testing.
Gentle, M. (2002). The CRM project management handbook:
Building realistic expectations and managing risk. London:
Kogan Page.
Singh, Y. (2013). Software testing.
Software evaluation. (n.d.). Montreal: SDM.
Top of Form
Tinnirello, P. C. (2000). Project management. Boca Raton:
Auerbach.
Bottom of Form
Bottom of Form
Bottom of Form
10. Bottom of Form
Bottom of Form
1
HWE Accessories Website: Project Plan, Risk Matrix, and Key
Factors
HWE Accessories Website: Project Plan, Risk Matrix, and Key
Factors
February 20, 2017
HWE Accessories Website: Project Plan, Risk Matrix, and Key
Factors
ProjectPlan
This project plan is based on System Development Life Cycle.
It is known as process driven or traditional system development
method. The technique requires analysts to follow some phases
in a sequential manner when developing and implementing an
information system. It involves people and is described as an
information system development project. There is clear project
objectives, stable project requirements, the progress of system
is measurable and strict sign-off requirements.
Risk Matrix
Essential Factors used to determine the success of the website
project
Smart Planning
Good and comprehensive planning sets up a project for success
from the start. Planning can assist the team members to meet the
11. deadlines and stay organized. Good plan not only keeps the
project team focused and on track, but also keeps stakeholders
aware of project progress. There many benefits of doing a
comprehensive planning among them being it allow realistic
time-scale to be created, project resources are managed with
minimal wastage, etc.
Open Communication
Keeping open communication within the team is essential and
determine the success of the project. When operating under a
given timetable, it is crucial that the team remains well-
informed of any undertaking going on. Communication should
be kept internally within the team as well as externally to the
end users of the website. This will allow the developers to
create user-friendly websites as well as maintain all
functionalities required.
Careful Risk Management
Not always thing goes as planned; sometimes thing rarely
happens as per the plan. During the planning process, it is vital
to produce a risk log and a risk assessment plan with an action
plan for the risks that the project could face along the way.
Maintaining things such as backups is an essential role during
the development process of the website. Unexpected risk can
cause the project to fail or take too long to finish.
Smart People
The right team will ensure the success of the project plans while
the wrong team will lead to a failure of any strategy which is
proposed. The right team mark a bright start and of the project.
All stakeholders; project manager, developers, software
engineers, designer and many other should be proficient in their
area of profession.
12. Strong Project Closure
If a project does not have strong and a determinable closure,
then it has the potential to continue to consume unplanned
resources. The team must be firm and agree with the customer
that all critical success factors have been met. The project
delivery and testing, as well as release, must be approved and
signed off as confirmatory measures. References such as
satisfaction surveys are critical methods of documentation
which can be used keep valuable information for future use.
5
HWE Accessories Company New Website
HWE Accessories Company New Website
February 13, 2017
HWE Accessories Company New Website
· The problem statement
The HWE Accessories Company experiences problems since its
current website is more manual as it just presents information to
the customers without allowing them to carry out any
transaction. In the present generation, the e-commerce is the
order of the day where the customers can use the Internet to
access various services on the net and do shopping without
having to move from one place to another. It is clear that the
current website the HWE Accessories Company is using is just
informational and thus users can just view a limited amount of
information without being in a position to browse inventory,
make comparisons for the items and as well make purchases.
The goal is to come up with a more computerized system which
will enable the HWE Accessories IT department and other
workers within the company as well as the customers to perform
transactions while using the company’s website. As well, the
13. new website will allow the customers to interact with the
company as to get assistance and clarification regarding the
company’s product and services.
· Analysis of the situation
It is clear that the current HWE Accessories website does not
fulfill the co-goals and objectives of the company which is to
market its products and services to many people. Even if the
customers happen to find the current website, they cannot be in
a position to fulfill their requirements since they cannot
purchase whatever they require. They might also come from far
and access the physical company's store becomes challenging.
Therefore, even after they find that the corporation has
whatever they require, they will end up exiting and looking for
other places (websites) to fulfill their demands. It is thus clear
that the company is not making any profit from the current
system and even if they make, it is minimal.
· Cost-benefit analysis
Computerizing the current HWE Accessories website will be
costly since it will require purchasing of various items such as
more powerful computers than the current ones. The company
will also incur a lot of money in paying the website designer,
introducing an internal IT department and training staff on how
to use the new system (website). These are just a few areas
where the company will require to use a lot of money. However,
we cannot compare these costs with the benefits the new
website will have to the enterprise. It will assist in marketing
the HWE Accessories products and services, increase sales and
profits which will be more than what the company has utilized
in the implementation of the website.
· Preliminary feasibility study
A feasibility study is important in determining whether the
system is worth developing. According to the feasibility study
carried out, it is evident that the current website is inefficient
while the proposed new system is viable. The feasibility study
showed that the capital, workforce, technology and time
required to build the new website are available, and nothing can
14. act as a controversy towards developing the new website.
· Total Cost of Ownership (TCO)
TCO is significant as it assists in determining the cost estimate
of the new system. The company will incur capital in
purchasing new computer programs and hardware, and as well it
will have operation expenses such as during training and testing
of the website. Last and not least, the company will incur long-
term expenses such as in the maintenance of the system.
According to this analysis, the estimated cost the company will
require is $4000 (Sandborn, 2013).
· Return on Investment (ROI)
ROI is significant as it helps in making decisions by comparing
the profits the system will yield with the cost of investment.
After the implementation of the new website, the company is
expected to make a profit of $1500 every month. Therefore, the
ROI will be; 1500/4000 * 100 = 37.5%. From the ROI above, it
is clear that the new website will bring more profits to the
company and it will just take around three months for the
company to cater for the cost of the implementation of the
website (Clarke, 2014).
·
Solution
options
There are various options in which the corporation can use to
come up and implement the new website. The company can
decide to employ a website designer who will come up and
implement the new website, monitor it and continue perfecting
15. it. As well, the company can choose to hire an IT expert or
another company to develop and implement the new website. It
means that every time the website has some problems or need
improvements, the company will have to contact the developer
as to be in a position to solve the issues.
· Recommendations-Teacher
According to the analysis of the advantages and the
disadvantages of the new HWE Accessories website, the website
is worth developing since the company will make a lot of profits
from it. As well, I recommend the company to employ a
permanent website designer who will continue working on the
system all the time and correcting any error rather than hiring a
person just to develop and implement the system since this will
cost the company a lot of money in the long run.
References
Top of Form
Clarke, G. E. (2014). CompTIA CASP CAS-002: Return on
Investment and Total Cost of Ownership.
16. Bottom of Form
Top of Form
Sandborn, P. (2013). Cost analysis of electronic systems.
Singapore: World Scientific.