CT079-3-M Software Quality Engineering Individual Assignment

INDIVIDUAL ASSIGNMENT
TECHNOLOGY PARK MALAYSIA

CT079-3-M-SQE

Software Quality Engineering

‘Hi-Tech Crop. Case study’

APUMP2105SE(PR)

HAND OUT DATE : 14th June-2021

HAND IN DATE : 4th September-2021

STUDENT ID : TP063111

STUDENT NAME : MD SAKHIRUJJAMAN SALIM

CT079-3-M Software Quality Engineering Individual Assignment

Contents Table
1.0 Introduction .................................................................................................................... 1

1.1 Background, Business Process, and Problem Statement ........................................... 1

1.2 Aims and objectives of Hi-Tech Crop ....................................................................... 2

1.2.1 Aims .................................................................................................................... 2

1.2.2 Objectives............................................................................................................ 2

1.2.3 Assumptions ........................................................................................................ 2

1.2.4 Constrain ......................................................................................................... 2

2.0 Testing Strategy for Hi-Tech Corp ................................................................................ 3

2.1 Testing Approach ....................................................................................................... 3

2.2 Responsibilities of test actors .................................................................................... 3

2.2.1 Stakeholder Responsibilities ............................................................................... 4

2.2.2 Project Manager Responsibilities........................................................................ 4

2.2.3 Quality Assurance Lead Responsibilities ........................................................... 4

2.2.4 Technical Lead Responsibilities ......................................................................... 5

2.2.4 Developer Responsibilities ................................................................................. 5

2.2.5 Tester Responsibilities ........................................................................................ 6

2.3 Testing Environments ................................................................................................ 6

2.4 Testing stage .............................................................................................................. 7

2.4.1 Unit Testing......................................................................................................... 7

2.4.2 Integration Testing .............................................................................................. 8

2.4.3 User Acceptance Testing .................................................................................... 9

2.4.4 Regression Testing ............................................................................................ 10

2.4.5 Production Deployment Testing ....................................................................... 10

2.4.6 Usability testing ................................................................................................ 11

2.5 Test Planning and Execution ................................................................................... 11

CT079-3-M Software Quality Engineering Individual Assignment

2.6 Risk analysis ............................................................................................................ 12

2.6.1 Risk Identification ............................................................................................. 12

2.6.2 Risk analysis and mitigation ............................................................................. 12

2.7 Review and Approvals ............................................................................................. 13

3.0 Software Quality Metrics ............................................................................................. 13

3.1 Process Metrics ........................................................................................................ 13

3.2 Product Metrics ........................................................................................................ 14

3.2.1 Reliability Metric .............................................................................................. 14

3.2.2 Portability Metrics............................................................................................. 14

3.2.3 Maintainability .................................................................................................. 15

4.0 Software Configuration Management.......................................................................... 16

4.1 Identification ............................................................................................................ 16

4.2 Version Control ........................................................................................................ 16

4.3 Changes Control....................................................................................................... 17

4.4 Status calculation ..................................................................................................... 17

4.5 Configuration Audit ................................................................................................. 18

5.0Conclusion .................................................................................................................... 19

6.0Reference ...................................................................................................................... 20
CT079-3-M Software Quality Engineering Individual Assignment

1.0 Introduction

1.1 Background, Business Process, and Problem Statement

Hi-Tech Crop is a company that provides and develops a generic software control.
system for a class of digital devices. The company is a leading company in this area
where, most of its clients use this product as a primary product. This system is considered
as a big system where there are around 20 developers, and maintenance staff is working
on this project. Additionally, customers usually receive the developed product in phased
releases which typically from 9 to 12 months, and it depends on the customer’s
requirements. Most of the time, these releases significantly contain chunks of new and
essential functionality to accommodate the new advanced technology.
Currently, the customers often report defects such as loss of availability, loss of
specific services, or erroneous services. Defects discovered in each of these phases are
expected (where relevant) to be traced to a specific module and fixed. An attempt must be
made to fix all defects in the subsequent release.

So far, the current methods of Hi-Tech Crop have been able to achieve its core
goals with various problems, but this rapid growth of the market and its high demand, the
current development and methodologies have not met the quality standards. Customers
have received an overwhelming number of errors, which are causing the company to find
itself in a bad position. Therefore, the top product has recently been identified as
unreliable and has gained a bad reputation and is starting to get off track. Because of
these big problems, high-tech crop management has started to go downhill. As a result,
management plans to focus on quickly reporting all errors. Thus, the company wants to
study and analyze the incredible things that have earned a bad reputation as well as
establish a quality system in the company to ensure the quality of all future publishing.
So, the Hi-Tech Crop has faced some big problems, and their business is falling.

In this down moment, Hi-Tech Corp management is making plans to focus on as

soon as possible fixing all the reported errors. Now, Hi-Tech Corp wants to improve their
product by taking an appropriate testing strategy and methodology. Also, Hi-Tech Corp
company wants the evaluation of the products documents that explains software metric.

1
CT079-3-M Software Quality Engineering Individual Assignment

In addition, the company wants the product management software control documentation
that explains the software configuration strategy.

1.2 Aims and objectives of Hi-Tech Crop

1.2.1 Aims
The main aim of this paper is to establish a production-quality system that
maintains a high-quality standard and it will not be facing issues with all future versions.
The second aim is to regain their market reputation by providing their customers with a
high-quality system that fulfills customers' all requirements. In addition, the paper's aim is
to remove all the detected problems and regain their loss of availability and services.

1.2.2 Objectives

• Hi-Tech Corp needs a proposal to appropriate testing strategy and

methodology that boost their quality.
• Interpretation of software quality metrics for critical high-tech
corporation product evaluation.
• Explains the software configuration strategy to maintain their
software.
1.2.3 Assumptions

• Hi-Tech Corp.'s main product is a generic software control system

for a class of digital devices.
• Improve their availability, services, and security issues based on
customer reports.
1.2.4 Constrain

• Time constraints are related to the project schedule or plan,

including the duration of each phase of the project and much more.
• Cost constraint mention that the project’s budget which includes
required financial resources to complete and finish the main task
and project in time. For example, cost constraints for materials,
quality control, vendors, and more factors.

2
CT079-3-M Software Quality Engineering Individual Assignment

• The economic issue can affect software quality and the company.
For example, the customers do not buy the product due to unstable
economic.

2.0 Testing Strategy for Hi-Tech Corp

Software testing is the most important method of software engineering, and a
defined testing strategy is required for the test process. By using a testing strategy, the
software product can be enough tested and verified. The testing strategy is the method
which is analysing and verifying all the requirements and confirms customer satisfaction.
The testing strategy is the documentation of the software testing method that is provided
to all testing relevant teams, as it declares all testing methodology. This document
describes clear the testing Strategy and gives an overview of the test team, also includes
required testing activities and how testing should be performed. It is a very helpful
document of all responsible testing teams. This section will be proposed and discussed the
Hi-Tech Corp testing strategy.

2.1 Testing Approach

The test approach defines the testing method, testing level, roles, and
responsibilities of every relevant team. Basically, the Test approach is described which
components when and how they will be testing, who will be responsible for it. It also
gives the instruction of how error discovered was tracked and managed during the test. It
also gives the instruction of how error discovered was tracked and managed during the
test. For example, Hi-Tech Corp should be performed in each sprint feature testing a final
user acceptance testing “UAT. before software going live, the company should take this
test. This test result gives a clear passed result or has defects and also illustrates who will
be responsible for this detects.

2.2 Responsibilities of test actors

For Hi-Tech Corp., there are several actors required in this testing process.
All actors have specific responsibilities for their testing process.

3
CT079-3-M Software Quality Engineering Individual Assignment

2.2.1 Stakeholder Responsibilities

• Stakeholders shall do Requirements Review, check to validate

description of business requirements
• For the urgent purposes, Stakeholders can be assisting on Design
Review for requested requirements are filled or not.
• Stakeholders can join in User Acceptance Test and approve
implementation.
2.2.2 Project Manager Responsibilities
Regarding testing process, the Release Manager shall

• The resources (staff, environment, equipment) that are available in

the confirmed project mentioned in the approved test plan.
• Include specific testing tasks in the test plan in the overall project
plan.
• Associated with Technical Lead and Quality Assurance Lead in the
implementation of Test Plan.
• associate with all the team of User Acceptance Tests and request
stakeholders to approve the implementation of their requirements
and overall preparation of the application for release.
2.2.3 Quality Assurance Lead Responsibilities

• Build the test plan based on each test stage.

• Can be Requested to Technical Lead for parts of each Test Plan
review.
• The quality Assurance Lead can supervise the Functional Testing
and System Integration Testing phase by testers, also report to the
project manager about test progress.
• The quality Assurance Lead can communicate errors found in those
test stages, associate error management in the error tracking system.
• The quality Assurance Lead ensures that the tester of the software
who have all the skills and all the required components which are
needed in his assigned tests.

4
CT079-3-M Software Quality Engineering Individual Assignment

• Can taking reviews of the product quality risk in each test stage and
inform upper-level staff.
• Monitor all the testing stages process based on their acceptance
criteria.
• Can provide a contribution to all test strategies and testing
processes.

2.2.4 Technical Lead Responsibilities

• Technical Lead defines all the test strategies and targets for their
testing stages.
• Technical Lead can contribute to the test plan with the Upper-level
staff.
• Performs and inspects on the design reviews.
• Technical Lead can perform and inspects the design reviews.
• Can inspect all the test stages and report to the projecting manager
on their test’s stages process.
• The Technical Lead ensures that the tester of the software who have
all the skills and all the required components which are needed in
his assigned tests.
• The technical lead ensures that all test equipment is supplied to the
team and that they meet the criteria for entry into this testing phase.
• The Technical Lead gets involved in the Quality Risks reviews.
• Technical Lead can collaborate with Quality Assurance Lead on
making testable and on test automation.
• The technical Lead team can provide environments for testing by
the testing stage team.
2.2.4 Developer Responsibilities

• Developers of the company develop the testing code of the

application and deliver it to a specified Test Plan.

5
CT079-3-M Software Quality Engineering Individual Assignment

• Developers are performing on the stakeholder requirement

implementation and error fixing.
• Developers ensure that their implementing code is committed to an
integration build that does not break the building, passes all the
testing stages.
• As per the Technical lead, Developers get involved in the design
reviews.
• Developers working with the tester for bug fixing and analysis of
the error.
2.2.5 Tester Responsibilities

• Tester will apply black-box and Gray-box testing methods for

application tests.
• Implements the test stages, including automating the test.
• Prepare the application test data for testing.
• Creating testing framework.
• Tester working with Developers the tester for bug fixing and
analysis of the error.
• Provide approximately scheduled experimental actions and their
process report.

2.3 Testing Environments

Any environment is not perfect for test, if we select an environment and
test is pass, so this is the well-defined environment. So, well-defined environment can't
pass the test because of incorrect configuration and testing team will waste their time to
why this is not worked. That description of a test environment should specify features
like:

• Organize of a pure environment

• Comparison of the test environment to the target Production
environment
• Required hardware setup for running tests, virtualization solutions,
networking setup.

6
CT079-3-M Software Quality Engineering Individual Assignment

• Software environment setup where applications will be placed:

operating system, application server and database server version,
browser type and client machine version and others.
• Collaboration with other connection applications
• Configuration options for application installations
• Tests need to use data sets and data feeds.
For Hi-Tech crop., below list showing testing type and their specific environment.

• Development environment -- Unit testing, integration testing.

• Testing and Training Environment -- User acceptance test,
Regression tests.
• Production Environment -- production validation.

2.4 Testing stage

For Hi-Tech Corp., there must be different types of tests guideline at the
different ends in developing the software development life cycle. There are different
types of tests for different purposes, so all the tests finish with customer satisfaction. In
this section, a detailed discussion of the required tests.

2.4.1 Unit Testing

The main goal of unit testing is to provide that each unit performs well as
its task. The unit test is working on a single input, that's why the unit test is the small test
part of any software. Unit testing is required whenever new software components are
created in any environment. So, the team of Hi-Tech Corp. will be responsible for
controlling unit tests on the environment, below table shows full testing details and who

7
CT079-3-M Software Quality Engineering Individual Assignment

are involve in this test.

Table1: Unit testing table (Screenshot from other assignment).

2.4.2 Integration Testing

Integration testing is a test where the testing team integrated all the
software modules into a group for testing purposes. Hi-Tech Crop. the testing team
integrated several software groups from the assigned project developer's codes. This test
is mainly focused on data communication validation and check flow between created
modules. This test is performing on new software development which is develop the
generic software control system (Services, C. A. and Practice, L, 2018). Below table
shows full testing details and who are involve in this test.

8
CT079-3-M Software Quality Engineering Individual Assignment

Table2: Integration testing table (Screenshot from other assignment).

2.4.3 User Acceptance Testing

User acceptance testing is testing user satisfaction who are using
this application after release. This test is performing by the customers because they are
trying to achieve the best performance of a product and when the product is ready then
the product will be certified. After this test, Hi-Tech Corp can give representative clients
brief training on how to use and how to navigate the features.

9
CT079-3-M Software Quality Engineering Individual Assignment

Table3: User acceptance testing table (Screenshot from other assignment).

2.4.4 Regression Testing

Basically, Regression Testing is working on a new feature added to
the old product of Hi-Tech Corp. This test ensures that the older software version is still
working after the upgrade. Also, this test also working on various testing stages like unit
and integration testing, its main focus on after software upgrade all the main functions
working properly or not. To maintain good regression testing, all testing team should do
this test. Selenium Web Driver is Automated Regression tests tool, which is a browser
work with open source APIS.

2.4.5 Production Deployment Testing

In the production environment, Hi-Tech Corp. is releasing their
product, now need to check product validation testing to confirm all functionality are
deploying properly or not. The production validation testing is doing by the tester and
representative customers. Skilled testers are required for this validation who have some

10
CT079-3-M Software Quality Engineering Individual Assignment

experience of this type of product build. If the skilled tester faces any problem during
recruitment, they can roll back immediately. Also, the skilled tester must remove test data
sets after completing the test in the environment.

Table4: Production deployment testing table (Screenshot from other assignment).

2.4.6 Usability testing

Usability Validation, Basic usability check is a process that has been verified
when testing a feature or an application. this can be a separate stage test. The Usability
testing result provide several improvement lists, also give information about which
features are users liked or disliked. For Hi-Tech Corp., usability testing will provide
proper improvement guideline for the project team and found out which acceptance
criteria are not cleared.

2.5 Test Planning and Execution

A test plan is a guideline of Test strategy. A test plan template is a
document of the full project schedule. Every project team member follows this template
in the processes, and they can confirm which test stage schedule is running now. By
following these processes, Hi-Tech Corp will be developed properly to maintain short-
term organizational objectives. Test plan must include

11
CT079-3-M Software Quality Engineering Individual Assignment

• The test plan is followed by an application team in the testing stage

mapping software development process mentioned in this document
• Specification of implementation of the test stage
• Teat plan should have all schedule information of the testing stage
or staff.
• Includes all the millstones.

2.6 Risk analysis

Risk management is the complementary component of the software testing
process since the risk is the potential issue. Risk identification, analysis, and response on
risk are the risk management main stages.

2.6.1 Risk Identification

Usually, risk identification is preferred at the product level. Risk
identification depends on the list of products producing processes or releasing time or
after release which unknown risks can face.

2.6.2 Risk analysis and mitigation

Every project has some positive risks and negative risks. Hi-Tech Crop.
also have both types of risk. Below describes risks probabilities and impacts.

1. Organization financial problems like budget issue (Low, Medium)

2. Skilled or key employees are ill in the critical time. (Low, Medium)
3. The time required to develop the software is underestimated.
(Medium, Medium)
4. Customers fails to understand the software features. (Low, Low)
5. Required training staff is not available. (Medium, Medium)

Mitigation Action:

Risk1: Prepare a brief document of the project. Before starting a project,

the project manager should clear all the budget issues.

12
CT079-3-M Software Quality Engineering Individual Assignment

Risk2,5: Reorganize the team, so that they can understand each and other
work.

Risk3: Recruit serious experience employees, so they can understand the

project value and don't waste time.

2.7 Review and Approvals

• The Project Manager is responsible for verifying and approving all

technical test lead and tester lead test results.
• The customer representative must sign the user acceptance test as
well as the product validity results.
• The team leader is responsible for signing the outcome of the
integration process.

3.0 Software Quality Metrics

3.1 Process Metrics

There are groups of processes that are closely related to collection or
activity software. To Hi-Tech Corp process metric measurement, there are three main
features that should be

▪ Process duration
▪ Requested attempts will be includes in the process.
▪ Events that may occur in the process.
In addition, there are a few external characteristics that will be deliberated such as
quality, cost, durability, and controllability. The world's most popular is the Constructive
Cost Model “COCMO II" which calculated software cost estimation. Constructive Cost
Mode is divided into four characteristics which are:

1. Product Features Which take on the application size, product

complexity, and reliability required for the software.

13
CT079-3-M Software Quality Engineering Individual Assignment

2. Personal Features Which take on application and programming

virtual machine experience, analytics ability, and language
experience.
3. Hardware Features which is a limitation of memory, a limitation of
performance while running.
4. Characteristics of the project that determine the necessary
development.

Hence, Hi-Tech Crop will be using this tool for their process measurement.

3.2 Product Metrics

3.2.1 Reliability Metric
System reliability measurement is a type whose shows system capabilities
provide an excellent operation. System reliability can identify the failure rate and provide
the issue of system function. System reliability has two factors, which are the whole
number of current issues and how users use this system. Basically, this testing helps to
ensure the software-related issue.

3.2.2 Portability Metrics

Portability is one of the quality factors that helps determine the level of
comfort and inconvenience of a component. it finds out the possibility of one software
component transfers to another software. For example, a web application has been created
to work with all the available browsers. So, users visit those browsers, the application
should work properly.

For measuring software portability, there are four main characteristics that
should be combined through measurement. According to (ISO 29119 (2013)), these
characteristics are adaptability, install-ability, replaceability, inter-operability, and
localization.

• Adaptability: To adaptability testing, this type of test provides that

application is work within the different environment like HTML
language helps any software gain their desired adaptability.
• Install ability: To install ability testing, this type of test taken
measurement of environment that this environment has the ability
for application install or not.
14
CT079-3-M Software Quality Engineering Individual Assignment

• Compatibility: To compatibility testing, this type of test taken

measurement of the environment that the same environment can run
multiple applications without creating any issue. For example, two
applications share their memory. If one application provides an
error in the system, this error should affect the full system and the
system will be down.
• Replicability: To replicability testing, it works by replacing one
component with another component of the ability test in a single
system.
To Hi-Tech Corp., they need to follow about five steps when measuring the portability of
their software. those steps are:

1- In the 1st step, the testing team needs to identify the necessary and get
an environment that will have different components.
2- In the 2nd step, the testing team must define all the tests that will be
tested while taking their required measurements.
3- In the 3rd step, the tester needs to run all the test cases.
4- In the 4th step, the tester should take a record of all the test results and
established errors.
5- In the 5th step, the tester should verify all the errors are fixed by the
project team.
Here, Hi-Tech Corp has a probability problem. Customers are reported several times
about the software errors. Their software is not user-friendly, their software does not
support all devices. So, software design implementation is not doing correctly. Hi-Tech
Corp. needs to check their whole software design and fix it.

3.2.3 Maintainability
To Hi-Tech Corp products, maintainability measurement is very
important, because it helps engineers know the maintenance rate accurately and if the
system got any maintainability issues it will help to increase maintainability. There are

15
CT079-3-M Software Quality Engineering Individual Assignment

various tools available in the market which help the developers calculate maintainability.
The world's most famous tool is Oman and Hagemeister called the Maintenance Index.
This tool has used many factors to calculate application maintainability which Cyclomatic
Complexity, Halsted Volume, and line of codes (SEI, 2018).

4.0 Software Configuration Management

Software configuration management is the process of managing and maintain the
activities of product making. Software configuration management is very important for
Hi-Tech Corp which bits helps to monitors all the activities and tasks in the development
process. It also eliminates all the clashes in maintenance that all processes will be
documented. This section discussed five processes of configuration management and
explaining how Hi-Tech Corp. can manage the configuration process.

4.1 Identification
Identification is the item called Software configuration items that are used
in project stages that are some documents, folders, and testing files. After identifying
items, the manager should be announcing the relation between various types of items. All
the items that must be reviewed, corrected, and approved become the last items. The
below table shows stage items.

Table: Identification Items.

4.2 Version Control

Version control works as a tool to organize different versions of software
configuration items as well as to integrate methods. Version control is bounden for

16
CT079-3-M Software Quality Engineering Individual Assignment

detecting versions of SCI to ensure searchability with different versions. Version control
is very important for Hi-Tech Corp., because this is the way how can manage their old
version and a new version. Hi-Tech Corp. version changes can follow a systematic way to
manage their version. Below example showing the version look.

4.3 Changes Control

Change control is a method that is primarily created for applied software
changes can control. Change control processes basically work on maintaining software
changing processes items. In addition, there are two types of change control, first one is
access control which working with the country governing committee access, and the
second one is synchronization control which makes sure that common changes don't clash
with each other. Hi-Tech Corp can be taking help from those controllers to monitor the
software critical changes.

• The Software Design Board is always provided with a change to

determine changing impact of the system.
• After the approved change, a software change request "SCR" should
be received from the product manager.
• A project manager is present their changes at a board meeting, after
that they decide those changes are approved or rejected.

4.4 Status calculation

Status accounting is the tracking record and provides a report of changing
processes. Also, Status accounting can help Hi-Tech Corp to monitor their change data.
The focus of status accounting is making reports if required, tracking changes in item
status or full system status after applied changes, and generate reports for those changes.
Status accounting reports are helping the software development team of Hi-Tech Corp to
monitor the changes. In this process, a configuration status report must be submitted to

17
CT079-3-M Software Quality Engineering Individual Assignment

the High-Tech Corporation development team. This report has all data of version
changes, a list of items specifications, and all the requested changes history.

4.5 Configuration Audit

Project audit is the type of review process that is designed to review project
working status and confirm that the project all documents follow the standard and fulfill
all requirements. This process is very important for Hi-Tech Crop. Because, Project audit
is based on a separate team and their responsibilities are very important which decide
software quality. The audit team has separate working schedules, they have managed
some objectives checklist where they are taking reviews from all the team members. Here
below present the general process of audit.

Set 1: Project Criteria Development

• Conduct interviews with Hi-Tech Crop. members and managers to

decide and admit on the success criteria.
• Make sure that the criteria are fulfilled the business requirements.
• Create a questions checklist based on success criteria.
• Send the list of all the members who are involved in the project
team.
• Take interviews of all team members and collect their responses.
• Call a meeting team with the team to discuss their responses and
current project status.
• During this meeting, try to identify major issues and challenges.
• Before close the meeting, the audit team must ensure that the first
step checklist is done.
Set 2: Analysis

• Run single research interviews with the Hi-Tech Crop. members to

discuss project background, problem and identify challenges.
• Create a complete summarizes report based on the discussions and
find out the problem.
• Set a probability of the problem impact and create a list.

18
CT079-3-M Software Quality Engineering Individual Assignment

• Check each problem to acknowledge which assumption has been

done and which is not done.
• Check quality plans to determine which solutions can be applied
and which opportunities can be implemented
• Define and taking a record of the process.
• Make sure the second step of the audit checklist is completed
Set 3: Reporting

• Collect all the interviewing and meeting records, also previous step
records.
• Collect all data from other audit members and combine it like
project documentation.
• Identify all the possible problem solutions, that problems are found
in the project running time.
• Ensure that all the listed problems are successfully solved.
• Create a fully detailed audit report where all the details of the audit
process are mentioned.
• forward this audit report to the Hi-Tech Crop. management.
• At the last, confirm that audit process is complete.

5.0Conclusion
To summarize, Hi-Tech Crop is a software development company, that develops
the software control system for digital devices. The company produces big and complex
software, so they have 20 developers and maintenance staff. Hi-Tech Crop releases any
software within 9-12 months and depends on requirements. Currently, Hi-Tech Corp
faces some difficulties in that their release product is not meet the standard quality. So,
Hi-Tech Corp losing their marketplace because customers found out numerous detects in
the new systems. So, the Hi-Tech Corp. management committee decided to make a
testing strategy and improve their product. This paper proposed a testing strategy that
provides bugs and errors-free products for Hi-Tech Corp. Also, reliability, portability,
and maintainability are introduced in the software to demonstrate how relevant metrics

19
CT079-3-M Software Quality Engineering Individual Assignment

can measure quality metrics. The last section is discussed in detail by five processes of
software configuration management like version control, audit, and more. In a closing
thought, honesty is the best policy, so Hi-Tech Crop will be going back with their high
reputation in the market if Hi-Tech Crop followed their product testing processes
honestly.

6.0Reference
Abdullah, M. Khan and R. Srivastava, "Flexibility: A Key Factor to Testability", International
Journal of Software Engineering & Applications, vol. 6, no. 1, pp. 89-99, 2015.

Saraswat, S. & Yadava, G. (2008). An overview on reliability, availability, maintainability, and

supportability (RAMS) engineering. International Journal of Quality & Reliability Management.
25 (3). pp. 330-344.

Project Management Institute (2013). A guide to the project management body of knowledge
(PMBOK® guide). 5th Ed. Newtown Square, Pennsylvania: Project Management Institute, Inc.

Carlson, C., Sarakakis, G., Groebel, D. & Mettas, A. (2010). Best practices for effective
reliability program plans. 2010 Proceedings - Annual Reliability and Maintainability Symposium
(RAMS).

Services, C. A. and Practice, L. (2018) ‘Leading Practice: Test Strategy and Approach in Agile
Projects’, pp. 1–6.

Pinciroli, F. (2016) ‘Improving Software Applications Quality by Considering the Contribution

Relationship among Quality Attributes’, Procedia Computer Science. Elsevier Masson SAS,
83(Antifragile), pp. 970–975. doi: 10.1016/j.procs.2016.04.194.

Supaartagorn, C. (2011) ‘Php F Ramework F or D Atabase M Anagement’, International Journal

of Computer Science $ Information Technology (IICSIT), Vol3, No 2, 3(2), pp. 251–258.

Yang, C., Liang, P. and Avgeriou, P. (2018) ‘Evaluation of a process for architectural assumption
management in software development’, Science of Computer Programming. Elsevier B.V., 168,
pp. 38–70.

20