Quality in Amazon’s IT System

Software Development

BÙI HUY HOÀNG

1|Page
Contents
Abstractions ............................................................................................................................... 4
Introduction ............................................................................................................................... 5
I. Quality assurance in IT systems .............................................................................................. 6
1. Quality Assurance and Quality Control: ............................................................................. 6
A. Quality Assurance .......................................................................................................... 6
B. Quality Control ............................................................................................................... 6
C. Connection between Quality Assurance (QA) and Quality Control (QC) ....................... 7
2. Software Quality Assurance standards in IT system .......................................................... 8
A. CMMI ............................................................................................................................. 9
B. ISO ................................................................................................................................ 11
3. Risk associated with developing a database centered IT system .................................... 13
4. System Development Life Cycle (SDLC) ............................................................................ 14
II. Software Testing ................................................................................................................... 17
1. Software test plan ............................................................................................................ 17
A. Scope............................................................................................................................ 17
B. Test environment ......................................................................................................... 17
C. Test identification ......................................................................................................... 17
D. Objective ...................................................................................................................... 18
E. Test level ....................................................................................................................... 19
F. Data recorded ............................................................................................................... 19
2. Software description ........................................................................................................ 19
A. Scope: .......................................................................................................................... 19
B. Testing environment .................................................................................................... 19
C. Testing process ............................................................................................................. 19
3. Software test report ......................................................................................................... 24
Test result ......................................................................................................................... 24
III. Project Management .......................................................................................................... 27
1. The importance of project management to the production of high quality IT systems. . 27
A. Organizing Chaos ......................................................................................................... 27
2|Page
 B. Managing Risk .............................................................................................................. 27
C. Managing Quality ......................................................................................................... 27
D. Managing Integration .................................................................................................. 28
E. Managing Change......................................................................................................... 28
F. Clearing Issues .............................................................................................................. 28
G. Retaining and Using Knowledge .................................................................................. 28
H. Learning From Failure .................................................................................................. 28
2. Produce for Amazon’s website development project...................................................... 29
A. Work Breakdown Structure ......................................................................................... 29
B. 2 GANTT Chat ............................................................................................................... 32
C. Critical Path Method .................................................................................................... 34
IV. Conclusion ........................................................................................................................... 35
V. References ............................................................................................................................ 36

3|Page
Abstractions

Amazon Inc. is an American international e- commerce company. It was started by Jeffrey P.

Bezos in the year 1994. Today, it is the world largest online retailer.

From a simple user’s point of view, Amazon is a Web-based application fulfilling three
purposes:

1. Find general information about available books

2. Check the prices of books

3. Purchase books to be sent home

Amazon makes use of the latest information technologies to maintain, and develop, its
competitiveness including “big data” and cloud-based e-commerce applications which are
web-browser accessible and database-center. It develops these in-house using its extensive
business analysis and computing expertise in these areas.

This report will act as the role of a senior systems analyst who also has particular
responsibility for ensuring that the company’s IT systems are developed, and evolved, to the
highest possible quality standards to ensure their cost-effective development and
maintenance.

4|Page
Introduction

- Understanding of the importance of the quality process as applied to IT-related systems

development is the key for all students who wish to work in computer science fields. This
report is a presentation which will provide readers with the knowledge necessary by
discussing quality in Amazon’s IT System Software Development.

- Readers will expect these topics:

 Discuss appropriate standards for the development of an IT system.

 Assess the risks associated with the development of an IT system.
 Discuss quality assurance practices at all stages of the systems development lifecycle.
 Produce quality control documentation for each stage of the systems development
lifecycle.
 Apply project planning and management tools to plan specific resources and
requirements for an IT system development.
 Evaluate the suitability of tools used to manage the development of an IT system.

- This report also satisfies the learning outcomes such as understanding how to formulate a
research specification:

 Formulate and record possible research project outline specifications

 Identify the factors that contribute to the process of research project selection.
 Undertake a critical review of key references.

5|Page
I. Quality assurance in IT systems
1. Quality Assurance and Quality Control:
- First of all, we have to understand what quality is:

General Definition: Fitness to use and conform to requirements

PMI Definition: Degree to which project fulfills requirements.

A. Quality Assurance

- The main objective of quality assurance is to prevent

error (defect) of the deliverables in the planning
process in order to avoid having to rework making
waste in financial.

- Quality assurance is a proactive process and it is early

started in the beginning of the project in order to
develop plans to achieve the requirements and
expectations of the product.

B. Quality Control

- If Quality Assurance approaches in process then Quality Control approaches in terms of

products. Quality Control interested in operating activities and techniques to fulfill the
requirements in terms of quality.

- Quality Control procedures include operations to ensure high-quality products. These

activities are focused on the identification of defective products (Identifying Defect) during
project implementation.

6|Page
- The feature of Quality Control is reactive, which means only after detecting the error the
process will act and repair the product, unlike the proactivity in Quality Assurance. Quality
Control helps detecting errors in deliverables.

- Objectives of Quality Control are to ensure the deliverables are defect-free and are
accepted in the quality requirements set out. In case deliverables is not good as required,
the Quality Control will have to fix the problem.

C. Connection between Quality Assurance (QA) and Quality Control

(QC)

- QA and QC are two completely different processes, but related to each other. The
relationship between QA and QC: QC Process receives input from QA, QA QC receives
feedback from QC and performs editing (validate) operating procedures (operational
processes).

- For example, if the project team to find errors in the process of implementation of the
project, they will fix (QC) and send feedback to the QA team. QA team will have to find out
the cause of the error and offer solutions to prevent errors for this error so it will not occur
in the future. Once this process has been updated, QC Team will follow the new process.

- The general objective of the QA and QC is to deliver a defect-free product. And they bring
these benefits:

+ High quality output.

+ Increase operational efficiency.

+ Enhance customer satisfaction and strengthen your brand.

+ Less rework, saving money for the project.

+ High level confidence and motivate teamwork.

7|Page
2. Software Quality Assurance standards in IT system

- Software Quality Assurance (SQA) is a set of activities to ensure quality in developed

software which meets and complies with defined or standardized quality specifications

- One of the most commonly used definitions of software quality assurance is offered by the
IEEE Glossary (IEEE, 1991) [1] :

Software quality assurance is:

1. A planned and systematic pattern of all actions necessary to provide adequate confidence that an
item or product conforms to established technical requirements.

2. A set of activities designed to evaluate the process by which the products are developed or
manufactured. Contrast with quality control.

- The quality management normally based on one or more of the following

models/standards:

+ CMMI

+ ISO 9000

Note: There are many models/standards for quality management but the ones mentioned
above are the most popular so this report will discuss both of them.

- The benefits of use of standards:

+ Apply methodologies and procedures of the highest professional level.

+ Gain understanding and coordination among development teams and maintenance

teams.

+ Greater connection between the software developer and external participants,

suppliers and customers.

8|Page
A. CMMI

- CMMI is a Process Model Framework for process-improvement developed by Software

Engineering Institute (SEI), Carnegie Mellon University (CMU), Pittsburgh, USA.

- CMMI, standing for Capability Maturity Model Integration, is a structured and systematic
collection of best practices for process-improvement.

-CMMI describes best practices in managing, measuring and monitoring software

development processes. The CMMI model does not describe the processes themselves; it
describes the characteristics of good processes, thus providing guidelines for companies
developing or honing their own sets of processes. [2]

- It is described on the official CMMI website thusly:

The Capability Maturity Model Integration (CMMI) project is a collaborative effort to provide
models for achieving product and process improvement. The primary focus of the project is to build
tools to support improvement of processes used to develop and sustain systems and products. The
output of the CMMI project is a suite of products, which provides an integrated approach across the
enterprise for improving processes, while reducing the redundancy, complexity and cost resulting
from the use of separate and multiple capability maturity models (CMMs).

- Following are obvious objectives of CMMI: [3]

+ Produce quality products or services

+ Create value for the stockholders

9|Page
 + Enhance customer satisfaction

+ Increase market share

+ Gain an industry-wide recognition for excellence

- The model identifies five levels of process maturity for an organization:[3]

+ Level 1 - Initial: Performance may not be stable and may not meet specific
objectives such as quality, cost, and schedule, but useful work can be done. This is only a
start in process improvement, which means that you are doing something but you cannot
prove that it is really working for you.

+ Level 2 - Repeatable: A managed process is planned, performed, monitored, and

controlled for individual projects, groups, or stand-alone processes to achieve a given
purpose. As the title of this level indicates, you are actively managing the way things are
done in your organization.

+ Level 3 - Defined: The process is defined/confirmed as a standard business process;

organization is proactive which contributes work products, measures, and other process-
improvement information to the organizational process assets.

10 | P a g e
 + Level 4 - Managed: Process management and measurement take place;
Quantitative objectives for quality and process performance are established and used as
criteria in managing the process. Quality and process performance is understood in
statistical terms and is managed throughout the life of the process.

+ Level 5 - Optimizing: Process management includes deliberate process

optimization/improvement; Focus on process improvement.

B. ISO

- ISO 9000 is a series of standards, developed and published by the International

Organization for Standardization (ISO). The ISO standards define, establish, and maintain an
effective quality assurance system for manufacturing and service industries. The ISO 9000
standard is the most popular and makes the most impact over 13,000 standards published
by the ISO. Many different industries and organizations are served as a guide to quality
products, service, and management. [4]

- An organization can be ISO 9000-certified if it successfully follows the ISO 9000 standards
for its industry: [5]

11 | P a g e
 + Principle 1 – Customer focus.

Organizations depend on their customers and therefore should understand current and
future customer needs, should meet customer requirements and strive to exceed customer
expectations.

+ Principle 2 – Leadership.

Leaders establish unity of purpose and direction of the organization. They should create and
maintain the internal environment in which people can become fully involved in achieving
the organization’s objectives.

+ Principle 3 – Involvement of people.

People at all levels are the essence of an organization and their full involvement enables
their abilities to be used for the organization’s benefit.

+ Principle 4 – Process approach

A desired result is achieved more efficiently when activities and related resources are
managed as a process.

+ Principle 5 – System approach to management

Identifying, understanding and managing interrelated processes contribute to the

organization’s effectiveness and efficiency in achieving its objectives.

+ Principle 6 – Continual improvement

Continual improvement of the organization’s overall performance should be a permanent

objective of the organization.

+ Principle 7 – Factual approach to decision making

Effective decisions are based on the analysis of data and information.

+ Principle 8 – Mutually beneficial supplier relationships

An organization and its suppliers are interdependent and a mutually beneficial relationship
enhances the ability of both to create value.

12 | P a g e
3. Risk associated with developing a database centered IT system
- The success of a software development project depends quite heavily on the amount of
risk. Because risks are painfully real and quite prevalent on all software projects, it’s critically
necessary to work hard to identify, understand, and mitigate any risks that might threaten in
developing process.

- The risk associated with development and how they affect a database is noted below:

+ Scheduling and timing risks: When an organization develops a project, there may
happen some problems in computing incorrectly estimated time and budget. It may cause a
waste in financial.

+ System functionality risks: If company’s developers build software whose functions

are not needed or are incorrectly specified, they are making risk in system functionality. Also
it can happen when developing wrong user interface which make difficulty for the person
who uses software.

+ Subcontracting risks: This means shortfall in externally furnished components. So

the product has poor quality and not met the requirement in quantity of components.
Shortfall in externally performed tasks is also counted in this kind of risk.

+ Requirement management risks: There is a word to describe the first cause of this
risk which is “Gold plating” - Addition of unnecessary features due to professional interests,
pride, or user demands. The second cause is uncontrolled and unpredictable changes in
system functions and features.

+ Resource usage and performance risks: Poor system performance is the way to
easily understand this risk. It also occur problems in computer science capabilities.

+ Personnel management risks: A company which has a few qualified personnel

often meets this risk.

13 | P a g e
4. System Development Life Cycle (SDLC)

- One of the essential knowledge of every professional software engineering that is

knowledgeable and familiar with SDLC. SDLC, standing for System Development Life Cycle, is
a classic model displays development process of a company’s software through phases. The
most common illustration of the SDLC model is the waterfall model:

- Depending on the type of software development pattern, which makes different sorting
(arranging) stages in different organizations. The model has 7 phases and they will be
discussed below:

14 | P a g e
 + Phase 1 - Requirements definition: The most important task in building a software
product is planning to meet the requirements. These requirements need to be
acknowledged / confirmed by the software engineers who have the skills and experience to
understand and identify any unclear requirements that customer desired.

+ Phase 2 - Analysis: Once the requirements are collected from customers, the next
step is precisely describing, identifying the task, the benefit for the company, computing
risks and financial, then clearly stating in paper.

+ Phase 3 - Design: Detailed definition of the outputs, inputs and processing

procedures, including data structures and databases ensuring that the software system will
meet all the requirements of the product, as well as ensuring that future requirements can
be addressed.

+ Phase 4 - Coding: In this phase, the design is translated into a code which is a form
the computer can read / understand. If the design is made in detail, the coding can be done
without a lot of fuss, trouble. Coding involves quality assurance activities such as inspection,
unit tests and integration tests.

+ Phase 5 - System test: After generating code, the software testing begins. The
different test methods can be used to clarify the error has been committed in the previous
period to achieve an acceptable level of software quality. System tests are carried out by the
software developer before the software is supplied to the customer. In many cases the
customer take acceptance tests to make sure that the developer has fulfilled all the
commitments.

15 | P a g e
 + Phase 6 - Installation and conversion: Once the code is approved and checked in
an appropriate manner, it will be used in practice. The System is installed to serve as
firmware, if the new information system is to replace an existing one, a software conversion
process has to be initiated to make sure that the company’s activities continue
uninterrupted during the conversion phase.

+ Phase 7 - Operation and maintenance: Throughout the regular operation period,

which usually lasts for several years or until a new software generation invented,
maintenance is surely needed. This phase begins when installation is completed, which
sustain and maintain software and cope with newly discovered problems or new
requirements can take longer than the initial development of the software.

16 | P a g e
II. Software Testing

This report contains information regarding testing of Amazon Inc. website development
project, it describes how the various components of the website and how they function.

1. Software test plan

A. Scope
The amazon’s website based application

+ Site: http//:www.amazon.com

+ Functions test: search, login, purchase.

B. Test environment
Testing sites Amazon.com

Computer hardware Intel Core i7

Computer Operating
Windows 10
System

Web Browsers Chrome (latest version)

Internet Connection 3.5 Mb/sec

+ Manpower: 2 years studying website development and technologies.

+ Requirement: Studying and training in website development field to understand the

procedure and complexity of the website and making test plan

C. Test identification

17 | P a g e
Test ID Objectives Test level Input Output

TED1 Test the LOGIN UNIT TEST Enter username Retrieves

details for errors and password. information,
process log in.

TED2 Test the SEARCH UNIT TEST Enter data Retrieves

button information.
Show searched
data

TED3 Test for ADD TO FUNCTION TEST Add item to Cart increment
CART cart. items.

TED4 Test for MAKING FUNCTION TEST Click on Make Credit card
PAYMENT payment details is read.

D. Objective
- Amazon will ensure if given user exists in
the database, and then process.

- Amazon will search and display the correct

given searched data.
Positive
- If user adds an item into cart, it should
increment items in the cart.

- The final payment button when clicked

should authorize the payment.

- Non matching username and password will

Negative displays incorrect message.

- Search function will have problem and

18 | P a g e
 displays incorrect output.

- Items in cart doesn’t increase when added

- Card is not read while making final payment

to checkout.

E. Test level
This report describes unit test and function test.

F. Data recorded
Data given from each test case will be recorded and executed when the program process has
no occurred error and meet the requirement to run.

2. Software description

A. Scope:
- A test description for Amazon Inc. web development project is described below. This
section contains formal test list in software test plan from section II.1, testis personnel
tasked with the installation, verification and performance of Amazon Inc. website.

B. Testing environment
(Mentioned in section II.1)

C. Testing process

19 | P a g e
Test ID: TED1

Test Checked Test case Steps to Expected

Input
Case Items Objectives execute output

TEDDY- Login Click the Click login Leave all fields A message
001 login button. empty. appears saying
button please provide
without email address
inserting. or mobile
number and
enter
TEDDY- Username Enter Fill in the Username: Error message:
password.
002 and invalid username “blah69” invalid email or
password. username and Password: phone
and password “nullnull”. number.
password fields,
. Then click

TEDDY- Username Enter login

Fill in the Username: User logs in.
003 and correct button.
username “teddyhbui”
password. username and Password:
and password. “Teddy123”.
password Then click
. login
button.

20 | P a g e
Test ID: TED2

Test Checked Test case Steps to Expected

Input
Case Items Objectives execute output

TEDDY- Search Click the Click Leave empty. Reloading the

004 search search web page,
button button. nothing
without happens.
inserting.

TEDDY- Product Enter Fill in the Search: “sdfsdaf”. Load to new

005 non- search page with
existed field. error message:
product. And click “Did not match
search any products”.
button.

TEDDY- Product Enter Fill in the Search: “toilet Load to new

006 existed search paper holder”. page with a list
product. field. of various
And click product.
search
button.

21 | P a g e
Test ID: TED3

Test Checked Test case Steps to Expected

Input
Case Items Objectives execute output

TEDDY- Add to Check Select No input Cart does not

007 Cart adding to quantity increment, the
cart and add to function is not
response. the cart working

TEDDY- Add to Check Select No input Cart

008 Cart items are quantity increment.
added and add to
the cart

22 | P a g e
Test ID: TED4

Test Checked Test case Steps to Expected

Input
Case Items Objectives execute output

TEDDY- Making Payment Fill in all Enter the user Credit card
009 payment is not details info, credit card details not
made about info. read by the
delivery and web server
credit card and payment is
details and not made.
click “Make
payment”
button

TEDDY- Making Payment Fill in all Enter the user User’s card
010 payment function is details info, credit card information
successful about info. are secured
delivery and and verified.
credit card Orders has
details and been made.
click “Make
payment”
button

23 | P a g e
3. Software test report

Software ID Amazon website System

Test site Amazon.com

Tester Bùi Huy Hoàng

Other participants

Hours invested in performing the tests 6 hrs

Test result

S/N Test Data Recorded during

test case execution.
1 No of requirements 4

2 Average no of test cases per requirements 25

3 Total no of Test Cases written for all requirement 90

4 Total no of test cases executed 55

5 No of test cases passed 35

6 No of test cases Failed 30

7 No of test cases blocked 9

8 Total Number of defects 40

9 Critical Defects 11

24 | P a g e
 10 High Defects 15

11 Medium Defects 3

12 Low Defects 5

Sales
No of requirements
Low Defects 1%
Medium Defects
2%
1%
Critical Defects
3% High
Defects Average no of
5% test cases per
requirements
8%

No of test cases
blocked Total Number of
3% defects
12%

Total no of Test Cases

written for all
requirement
28%
No of test cases failed
9%

No of test cases
passed
11% Total no of test cases
executed
17%

25 | P a g e
 Sales
100
90
80
70
Axis Title

60
50
40
30
20
10
0
Total
Averag
no of
e no of Total
Test No of Total
No of test no of No of No of Mediu
Cases test Numb Critical High Low
requir cases test test test m
writte cases er of Defect Defect Defect
ement per cases cases cases Defect
n for blocke defect s s s
s requir execut passed failed s
all d s
ement ed
requir
s
ement
Sales 4 25 90 55 35 30 9 40 11 15 3 5

Test Result
Sales

Low Defects 5
Medium Defects 3
High Defects 15
Critical Defects 11
Total Number of defects 40
No of test cases blocked 9
No of test cases failed 30
No of test cases passed 35
Total no of test cases executed 55
Total no of Test Cases written for all requirement 90
Average no of test cases per requirements 25
No of requirements 4

26 | P a g e
III. Project Management
1. The importance of project management to the production of high
quality IT systems.

- The development of software for an improved business process is considered as a project.

The project must be expertly managed to deliver the on-time, on-budget results, learning
and integration that organizations need. That’s why Project management is born, which is
the application of knowledge, skills, tools, and techniques to project activities to develop a
high quality system meeting the project requirements. Overall, Project management is the
organization, planning and control of projects.

- Project management is essential for several reasons:

A. Organizing Chaos
- Projects often happen chaotic in every way. The primary objective of project management
is to organize and make plans for projects carefully to tame and avoid chaos.

- It is impossible for any IT system project that achieved success without organizing chaos.
Imagine the big lost after a project has run and has not prepared to deal with chaos.

B. Managing Risk
- Risks in developing an IT system have been mentioned in this report, and they naturally
occur in many industries included software development, so they need to be handled well.

- Risk is all about happening negative event or loss to the company. Uncontrolled risk leads
to the destruction and compliance issues. Risks must be avoided and controlled if the
company wants to continue surviving.

C. Managing Quality
- We all understand the definition of quality and its importance. So it do not make sense to
build something that has no value.

- Leaving quality to chance is analogous to producing something of random value.

27 | P a g e
D. Managing Integration
- A project needs to be integrated with business processes, systems and organizations that
have the same system designed.

- It is not possible to build a hospital system that doesn't integrate with your management
process and hospital organization. It wouldn't add much value.

E. Managing Change
- There always are changes in any environment; projects are also always a moving target. It is
important to note that if environment is shaking, the project has to upgrade to survive.

- Managing change is a complex and difficult task which must be frequently concerned. If the
project does not manage well, it will permanently pause or totally disabled

F. Clearing Issues
- Even the finest project is imperfect, it obviously causes issues sometime. Problem must be
managed to achieve objectives. A project manager will identify and solve to continue the
project.

G. Retaining and Using Knowledge

- Projects generate knowledge. Knowledge represents a significant asset for most
businesses. Left unmanaged, knowledge tends to quickly fade.

H. Learning From Failure

- Project build on failure. Project use it as a stepping stone.

28 | P a g e
2. Produce for Amazon’s website development project
A. Work Breakdown Structure

Amazon Web site

Preparation Planning Deploy Conclusion Building system

Market Document Archive

Fix bug Code Design
analysts requirement Files/Documents
Evaluation & Calculute Install
Recommenda financial Update Login fuction Background
tions System
Build project Files/Records
Sponsors plan and Run
schucle Search fuction Login layout
Document Lessons
Manpower Learned
required Purschase
Search layout
fuction
Review and
approve
Purschase
Testing
layout

Peview and
Database
approve design

29 | P a g e
 Level Element name Definition

1 Amazon website All work to development

2 Preparation Preparation phase

Analyzing market demand and customer’s

3 Market analyzing
requirement

Evaluation &
Recommendations Evaluate solutions and make
3
recommendations

3 Sponsors Calling sponsors

2 Planning Planning phase

Document Document necessary for planning build

3
requirement project

3 Calculate financial Calculate cost for implement project

Build project plan

3 Build project plan and schedule
and schedule

3 Manpower require Workers are assigned for the project

3 Review and Approve Review and close the planning phase

2 Building system Developing phase

3 Design Build website display

4 Background Build Background display

4 Login layout Build Login display

4 Search layout Build Search display

4 Purchase layout Build Purchase display

30 | P a g e
 Review and approve
4 Reviewing and closing the designing phase.
design

3 Coding Code Function

4 Login Program Login Function

4 Search Program Search Function

4 Purchase Program Buy Function

4 Database Build database for store data

4 Running test Test to find bugs, errors to fix

2 Deploy Deploying phase

3 Install System Install a development system

3 Run The system runs

3 Fix bug Fix problems and maintain the process

2 Conclusion Final phase

Document Lessons
3 Lessons learned is noted
Learned

Update
3 All files and records are updated
Files/Records

Archive
3 Documents is formally archived
Files/Documents

31 | P a g e
B. 2 GANTT Chat

32 | P a g e
33 | P a g e
C. Critical Path Method

Activities Immediate Predecessor Time (Days)

Preparation(PRE) 2
Planning (PLA) PRE 4
Designing (D) PLA 7
Coding (C) D 6
Database (DATA) D 1
Installation (INS) C 2
Testing(T) C 2
Documentation (DOC) INS ; T 2

Early Late Early Late LS – ES Critical

Activities start Start Finish Finish path
Preparation(PRE) 1 1 2 2 0 yes
Planning (PLA) 3 8 5 10 5 no
Designing (D) 10 10 18 18 0 yes
Coding (C) 21 21 28 28 0 yes
Database (DATA) 24 25 24 25 1 no
Installation (INS) 29 29 30 30 0 yes
Testing(T) 25 27 28 30 2 no
Documentation (DOC) 36 36 37 37 0 yes

34 | P a g e
IV. Conclusion

- So we have reached the final part of the report. Overall, we have understood of the
importance of the quality process as applied to IT-related systems development.

- This report has discussed through several of topic:

 Standards for the development of an IT system.

 Risks associated with the development of an IT system.
 Quality assurance practices at all stages of the systems development lifecycle.
 Quality control documentation for each stage of the systems development lifecycle.
 Project planning and management tools to plan specific resources and requirements
for an IT system development.
 The suitability of tools used to manage the development of an IT system.

35 | P a g e
V. References
[1] IEEE Glossary (IEEE, 1991)

[2] Lynn Greiner - CIO.com - Capability Maturity Model Integration (CMMI) Definition and
Solutions

[3] http://www.tutorialspoint.com - SEI CMMI Overview

[4] http://searchdatacenter.techtarget.com/definition/ISO-9000

[5] http://isoconsultantpune.com/the-eight-principles-of-quality-management/

[6] Galin D - Software Quality Assurance From Theory to Implementation. Harlow, England:
Pearson Education Limited ( 2004)

[7] http://management.simplicable.com/management/new/why-project-management-is-
important

36 | P a g e