Software Quality Engineering for Hi-Tech Corp

SOFTWARE QUALITY ENGINEERING 1
SOFTWARE QUALITY ENGINEERING FOR A HIGH TECH CORP
Student's name:
Code +course name
Professor's name
University name
City, state
Date

SOFTWARE QUALITY ENGINEERING 2
Executive summary
Software projects for all hi-tech companies across the world have become complex
than ever before. With many teams across the world working on the same programs, test
methods are quickly changing. Therefore a culture of quality is necessary for the success of
this Hi-tech company.
In this paper, we will look at a Hi-Tech corp which concentrates more on selling
generic software control system for various classes of digital services. The company has a
good number of customers who purchase this product. In this Hi-Tech company, customers
are said to report defects such as erroneous services, loss of availability and loss of some
specific services in their products; these seem to be a big irony concerning quality. Thus in
this paper, we will be advising the company on the best testing strategy, software quality
metrics and software configuration management it can implement to help solve the issues
being experienced
The company should consider test automation because it helps to run tests suites
easily thus saving human capital. I would also recommend the company to try software
product metrics because it will help in coming up with the best control process which is
greatly beneficial when offering the high-quality product to customers. Lastly, the company
should adopt agile configuration management.

SOFTWARE QUALITY ENGINEERING 3
TABLE OF CONTENTS
Introduction................................................................................................................................4
PART A......................................................................................................................................5
SUITABLE TESTING STRATEGY AND PROCEDURE FOR HI-TECH CORP.................5
Benefits of Automation..............................................................................................................6
PART B......................................................................................................................................8
SOFTWARE QUALITY METRICS.........................................................................................8
Product Quality Metrics.............................................................................................................9
PART C....................................................................................................................................12
SOFTWARE CONFIGURATION MANAGEMENT............................................................12
Software configuration best practices......................................................................................13
Configuration management......................................................................................................14
Agile Configuration Management Practices............................................................................15
References................................................................................................................................17
APPENDICES..........................................................................................................................20
Appendix I: Introduction Letter............................................................................................20
Appendix II: Questionnaires.................................................................................................21

SOFTWARE QUALITY ENGINEERING 4
Introduction
Programme software examination is a significant activity and happens to be one of the
important processes when developing software (Fujita & Guizzi, 2015). Hi-Tech companies
that do not adhere to this process, together with the quality control processes can easily
destroy their reputation together with the reputation of other companies which depend on
them (Desai,2016). Customers also waste a lot of their money trying to deal with such a
company (Homs, 2013). Having a test schedule is also very critical when it comes to
developing software. Specific programs of software plan cover the different objectives and
needs of a particular program application (Rhett, 2015). Test documentation is also needed to
create test issues that assist in determining how best the user copes in various categories and
different working fields.
The Hi-tech company needs to understand that the development team is the one
responsible for ensuring quality rather than the quality assurance team (Black, 2011). Each
line of the code can make the customer experience good or bad. Developers have a quality
relationship with the customers (Black, 2011). The quality assurance team is only responsible
for informing the organization about risks. This is important for the Hi-tech Corporation so
that it will not place the responsibility of quality on tests and not have value in the
development process (Schmidt, 2016). The absence of developers in the quality makes
problems to deteriorate in the code base thus becoming expensive to fix. Software teams must
comprise of executive stakeholders, designers, product managers, testers, and developers. All
play a major role in ensuring quality.
Developers are very important in software projects (Hanmer, 2015). They greatly determine
the experience that a customer will have at the realization of a product (Sommerville, 2015).
Many are the times that developers do not have a chance to own the whole of their feature

SOFTWARE QUALITY ENGINEERING 5
lifecycle. Traditional test methodology considers testing as a separate process that does not
require developers. However, testing should be a collaborative process that must involve a
team of developer and customers (Stephens, 2015). Developers that can own and prove the
quality of feature have fewer round trips with QA, fewer bugs and are faster to get into the
market. A series of tests owned by test teams and developers greatly assist in protecting the
code from incoming bugs. Developers who write tests greatly keep their quality up. Hi-tech
company's need to empower their Developers.
Secondly is that Hi-tech company need to engage its users (Sommerville, 2015). A
regular release to the customer's base gives the customers a chance to give feedback on the
software necessary for future development (Desai, 2016). Test and development teams that
easily respond to the customers' feedback are said to be more effective and successful. Hi-
Tech Company also needs to make sure that customers find it easy to give their feedback
(Staron, 2017). Test engineers are also very Important in a software project because of their
ability to check on some quality issues across a given product (Schmidt, 2016). Test
engineers should be able to enable the larger team to run faster, inspire creativity, give
feedback early, engage with the outside and test flexibility.
PART A
SUITABLE TESTING STRATEGY AND PROCEDURE FOR HI-TECH CORP
Another way that Hi-Tech Company can ensure quality is by building a solid software
test strategy (Basu, 2015). A good test strategy may include manual, explanatory and
automated tests to tighten the release cycle and effectively reduce risk (Loope, 2011). Tests
may inform of unit tests, functional tests or integration tests. For Hi-Tech Company I would
recommend it to consider the automated software method.

SOFTWARE QUALITY ENGINEERING 6
Benefits of Automation
The major changes taking place in software projects makes it hard for test teams to
validate changes manually. Therefore computers are necessary and can easily be able to run
repetitive tasks easily (Graham& Fewster, 2012). This makes them the most necessary
gadgets for testing. Tests automation helps computers to run tests suites easily thus saving
human capital for some other engaging work in the organization. Since tests are frequently
run it is easier to detect issues earlier and fix them
 Features and Test Code: 2 Hearts That Beat as 1
Developers usually know how the product they are implementing is supposed to work. The
QA specialists become like the user to be able to detect the various issues the product may be
subjected to (Desai, 2016). Both the QA specialists and developers become the testing
powerhouse (Pressman, 2010). Engineers who take part in maintenance and coding of their
won test usually find bugs earlier on before committing the code. The QA helps in ensuring
that developers can write the right tests specifically in functional and integration test level.
Bugs can waste a lot of time and resources (Stephens, 2015). Finding them and being able to
fix them much early makes a program efficient.
 Test Efficiently
As automation tests continue to grow some problems that come from manual testing may
arise. For example, the test may begin to take time to run. Engineers can help to solve these
issues in three ways which are horizontal scaling; faster performance and more focused
testing (Basu, 2015). For every test carried out in the system must use minimum resources.
Equivalence partitioning is also necessary to make tests more efficient when they are
performed against different configurations(Fujita & Guizzi, 2015). Test that does not rely on
each other can be run in parallel by use of multiple build agents.