ASSIGNMENT FRONT SHEET

Qualification

Edexcel BTEC Level 5 HND Diploma in Computing and Systems

Development

Unit number and

title

Unit 32: Quality systems in IT

Assignment due

Assignment submitted

Learners name

Lam Minh Khanh

Assessor name

Learner declaration:
I certify that the work submitted for this assignment is my own and research sources are fully acknowledged.
Learner signature

Date

Grading grid
P1.
1

P1.
2

P1.
3

P2.
1

P3.
1

P3.
2

M1

M2

M3

D1

D2

D3

Assignment title

Quality in Amazons IT System Software Development

In this assignment, you will have opportunities to provide evidence against the following criteria.
Indicate the page numbers where the evidence can be found.
Assessment criteria

Expected evidence

Task
no.

Assessors Feedback

LO1. Understand the need for quality assurance in IT systems

A Written document which:

1.1 discuss
appropriate standards
for the development of
an IT system

1.2 assess the risks

associated with the
development of an IT
system

1. Explains why a systematic

approach to quality
assurance, and quality
control is needed.
2. Discusses various SQA
standards.
A Written document

discusses the risks

associated with the
development of an IT
system which has a
database at its centre.

1.3 discuss quality

assurance practices at
all stages of the
systems development
lifecycle

A Written document
describes the systems
development life-cycle
(SDLC) as it applies to
database development, and
then go on to explain how
each phase of the life-cycle is
quality assured

LO2. Be able to employ standard quality control documentation

2.1 produce quality

control documentation
for each stage of the
systems development
lifecycle

- A software test plan (STP)

- A software test description
(STD)
- A software test report (STR)

LO3. Be able to use project management tools

3.1 apply project

planning and
management tools to
plan specific resources
and requirements for
an IT system
3.2 evaluate the
suitability of tools used
to manage the
development of an IT
system.

1. A Written document
explains the importance of
project management to
the production of high
quality IT systems.
3

b)
- a Work Breakdown
Structure
- a GANTT chart
- a Critical Path Method

Assessment criteria

Expected Evidence

M1 Identify and apply

strategies to find
appropriate solutions

1. Effective judgements
have been made.
2. An effective approach

Feedback
(note on Merit/Distinction if applicable)

M2 Select/design and
apply appropriate
methods/techniques

M3 Present and
communicate
appropriate findings

to study and research

has been applied
1. Relevant theories and
techniques have been
applied
2. The design of
methods/techniques
has been justified
1. An appropriate
structure and method
has been used and
technical language has
been accurately used to
present the findings.

D1 Use critical
reflection to evaluate
own work and justify
valid conclusions

2. Communication has
taken place in familiar
and unfamiliar contexts
1. Conclusions have been
arrived at through
synthesis of ideas and
have been justified

D2 Take responsibility
for managing and
organising activities

2. The validity of results

has been evaluated
using defined criteria
1. Substantial activities
have been planned,
managed and organized
2. Activities have been

managed
D3 Demonstrate
convergent/lateral/
creative thinking

1. Self-evaluation has
taken place
2. Problems have been
solved

Summative feedback

Assessors
Signature
IV Grading Check:

Date
Comments if any:

Agree
Disagree

IV Signature

Modify grade to

Date

Task 1
A quality management system (QMS) is a collection of business processes focused on consistently
meeting customer requirements and enhancing their satisfaction. It is aligned with company's purpose
and strategic direction (ISO9001:2015). It is expressed as the organizational goals and aspirations,
policies, processes, documented information and resources needed to implement and maintain it.
Early quality management systems emphasized predictable outcomes of an industrial product production
line, using simple statistics and random sampling. By the 20th century, labor inputs were typically the
costliest inputs in most industrialized societies, so focus shifted to team cooperation and dynamics,
especially the early signaling of problems via a continuous improvement cycle. In the 21st century, QMS
has tended to converge with sustainability and transparency initiatives, as both investor and customer
satisfaction and perceived quality is increasingly tied to these factors. Of QMS regimes, the ISO
9000 family of standards is probably the most widely implemented worldwide - the ISO
19011 audit regime applies to both, and deals with quality and sustainability and their integration.
1. Quality Assurance (QA):
a. The maintenance of a desired level of quality in a service or product, especially by means of
attention to every stage of the process of delivery or production.
b. QA is focused on planning, documenting and agreeing on a set of guidelines that are
necessary to assure quality. QA planning is undertaken at the beginning of a project, and
draws on both software specifications and industry or company standards. The typical
outcomes of the QA planning activities are quality plans, inspection and test plans, the

selection of defect tracking tools and the training of people in the selected methods and
processes.
c. The purpose of QA is to prevent defects from entering into the solution in the first place. In
other words, QA is a pro-active management practice that is used to assure a stated level of
quality for an IT initiative.
2. Quality Control (QC):
a. A system of maintaining standards in manufactured products by testing a sample of the
output against the specification.
b. QC includes all activities that are designed to determine the level of quality of the delivered
information and communications technology (ICT) solutions. QC is a reactive means by which
quality is gauged and monitored, and QC includes all operational techniques and activities
used to fulfil requirements for quality. These techniques and activities are agreed with
customers and/or stakeholders before project work is commenced.
c. QC involves verification of output conformance to desired quality levels. This means that the
ICT solution is checked against customer requirements, with various checks being conducted
at planned points in the development lifecycle.
d. Teams will use, amongst other techniques, structured walkthroughs, testing and code
inspections to ensure that the solution meets the agreed set of requirements.
3. Why quality control is needed:
a. Quality control is important because business owners must ensure they manufacture
products that customers want to buy over and over again. The goal of a quality control
system is to ensure that each product meets or exceeds a specific standard. A quality control
system can also help business owners identify weaknesses in products and come up with
solutions for improving them.

b. Some companies hire outside agencies to perform quality control checks, while others
designate staff members to perform this task. Some small business owners choose to
perform quality control inspections themselves to regularly compare their products to similar
ones in the marketplace. In service-based industries, quality control is generally performed
using customer surveys. Getting feedback directly from customers is a cost-effective way to
get up-to-date feedback on various aspects of a company from a customer's viewpoint. This
type of quality control also gives customers the perception that they are valuable to a
business.
4. SQA Standards:
ISO 9000
The ISO 9000 of quality management systems standards is designed to help
organizations ensure that they meet the needs of customers and other stakeholders while
meeting statutory and regulatory requirements related to a product. ISO 9000 deals with
the fundamentals of quality management systems, including the eight management
principles upon of standards is based. ISO 9001 deals with the requirements that
organizations wishing to meet the standard must fulfill.
Third-party certification bodies provide independent confirmation that organizations meet
the requirements of ISO 9001. Over one million organizations worldwide are independently
certified, making ISO 9001 one of the most widely used management tools in the world
today.
The ISO 9000 series are based on eight quality management principles.
- Customer focus
- Leadership
- Involvement of people
- Process approach
- System approach to management
- Continual improvement

- Factual approach to decision making

- Mutually supportive supplier relationships
Capability Maturity Model Integration (CMMI)
Capability Maturity Model Integration (CMMI) is a process improvement training and
appraisal program and service administered and marketed by Carnegie Mellon University
(CMU) and required by many DoD and U.S. Government contracts, especially in software
development. CMU claims CMMI can be used to guide process improvement across a
project, division, or an entire organization. CMMI defines the following maturity levels for
processes: Initial, Managed and Defined. Currently supported is CMMI Version 1.3. CMMI is
registered in the U.S. Patent and Trademark Office by CMU.
CMMI currently addresses three areas of interest:
- Product and service development CMMI for Development (CMMI-DEV),
- Service establishment, management, CMMI for Services (CMMI-SVC), and
- Product and service acquisition CMMI for Acquisition (CMMI-ACQ).
Organizations can receive CMM ratings by undergoing assessments by qualified auditors:
- Level 1 characterized by chaos, periodic panics, and heroic efforts required by
individuals to successfully complete projects. Few if any processes in place;
successes may not be repeatable.
- Level 2 software project tracking, requirements management, realistic planning,
and configuration management processes are in place; successful practices can be
repeated.
- Level 3 standard software development and maintenance processes are integrated
throughout an organization; a Software Engineering Process Group is in place to
oversee software processes, and training programs are used to ensure
understanding and compliance.
- Level 4 metrics are used to track productivity, processes, and products. Project
performance is predictable, and quality is consistently high.
- Level 5 the focus is on continuous process improvement. The impact of new
processes and technologies can be predicted and effectively implemented when
required.

 Institute of Electrical and Electronics Engineers Standards Association (IEEE-SA)

The Institute of Electrical and Electronics Engineers Standards Association (IEEE-SA) is an
organization within IEEE that develops global standards in a broad range of industries,
including: power and energy, biomedical and health care, information technology and
robotics, telecommunication and home automation, transportation, nanotechnology,
information assurance, and many more.
IEEE-SA has developed standards for over a century, through a program that offers
balance, openness, fair procedures, and consensus. Technical experts from all over the
world participate in the development of IEEE standards.
IEEE-SA is not a body formally authorized by any government, but rather a community.
Formally recognized international standards organizations (ISO, IEC, ITU, CEN) are
federations of national standards bodies (American ANSI, German DIN, Japanese JISC,
etc.).
Maturity levels in CMMI for services:
- Maturity Level 2 - Managed
- Maturity Level 3 - Defined
- Maturity Level 4 - Quantitatively Managed
- Maturity Level 5 Optimizing
The benefits of SQA standards:
The ability to apply methodologies and procedures of the highest professional level.
Better mutual understanding and coordination among development teams but especially
between development and maintenance teams.
Greater cooperation between the software developer and external participants in the
project.
Better understanding and cooperation between suppliers and customers, based on the
adoption of standards as part of the contract.
The project is executed in real environment with many changes, so risks will unavoidable. Or, no projects
without risks and Amazons IT System Software Development is no exception. Unless the project were
recognized and controlled well, it would be able to make the project failure, or rise a lot of troubles, waste

time and workforce, decrease profit and customers believe. Therefore, recognizing and having good
control risks is one of the most important aspects in management project.
If software quality assurance is a process that ensures that developed software meets and compiles with
defined standardized quality specification. In the development process, the risk development of an IT
system always be together which Amazon use database at it central for storing data. So here the list of
risk can cause when using database at central:
No.
1
2

Software risk class

Personnel Management
Risk
Scheduling and Timing

System Functionally

Software risk item

Personnel Shortfalls

Description
Lack and turnover or qualified personnel

Unrealistic schedules
budgets
Developing wrong
software functions

Incorrectly estimated (too low)

development time
Development of software functions that
are not
needed or are incorrectly specified

Developing wrong user

interface
Gold plating
4

Requirement
Management

Continuing stream of
requirement changes

Shortfalls in externally
furnished components
5

Subcontracting
Shortfalls in externally

Inadequate or difficult user interface

(GUI)
Addition of unnecessary features due to
professional interests, pride or user
demand
Uncontrolled and unpredictable changes
in system
functions and features
Poor quality of externally delivered
system
components

performed tasks

Real-time performance
shortfalls
6

Resource Usage
Performance

Straining computer
science capabilities

Virus attacking

Security

Unauthorized and
decryption database

Poor quality or unpredictable

accomplishment of
externally performed tasks
Poor system performance

Inability to implement the system due to

lack of
technical solutions and/or computing
power
Malware infections causing incidents such
as
unauthorized access, leakage or
disclosure of
personal or proprietary data, deletion of
or
damage to the data or programs,
interruption or
denial of authorized access to the
database, attacks
on other systems and the unanticipated
failure of
database services
Unauthorized or unintended activity or
misuse by
authorized database users, database
administrators, or network/systems

managers, or
by unauthorized users or hackers (e.g.
inappropriate access to sensitive data,
metadata or
functions within databases, or
inappropriate
changes to the database programs,
structures or
security configurations)

This is the risks I have planned for everything can caused in development process web site of Amazon. I
think with that list I
will ready and prepare the ways to cope with it before it coming. From that itll help us promote all the
tasks faster and not waste
time bring back the high efficiency. And certainly with customers one Amazon always be professions in all
situation.
System development is the process of defining, designing, testing and implementing a software
application. This includes the
internal development of customized systems as well as the acquisition of software developed by third
parties. A system
development project includes all the activities from the time a potential requirement has been identified
until the system has been
fully implemented.
The systems development life cycle, or SDLC, is the process of creating systems and the models used to
develop these systems. A

typical SDLC includes a number of different phases, such as requirements analysis, software design,
software coding, testing and
debugging, installation and maintenance. This life cycle is implemented using a software development
process. There are a number
of models of software development, each with a somewhat different approach to implementing the
various phases of the life cycle.
The waterfall model of software development follows a very sequential design process. It is also referred
to as a linear-sequence lifecycle model. In this model progress is seen is flowing downwards through various phases, like a waterfall.
The phases include
initiation and conception, requirements analysis, software design, construction (or coding), testing and
debugging, installation and
maintenance. The basic premise of the waterfall model is that you only move to the next phase when the
preceding phase is
completed successfully.

Explain
1. System Planning
The Planning phase is the most crucial step in creating a successful system, during this phase you decide
exactly what you want to do and the problems youre trying to solve, by:

Defining the problems, the objectives and the resources such as personnel and costs.
Studying the ability of proposing alternative solutions after meeting with clients, suppliers,
consultants and employees.
Studying how to make your product better than your competitors.

After analyzing this data, you will have three choices: develop a new system, improve the current system
or leave the system as it is.
2. System Analysis
The end-users requirements should be determined and documented, what their expectations are for the
system, and how it will perform. A feasibility study will be made for the project as well, involving
determining whether its organizationally, economically, socially, technologically feasible. It is very
important to maintain strong communication level with the clients to make sure you have a clear vision
of the finished product and its function.
3. System Design
The design phase comes after a good understanding of customers requirements, this phase defines the
elements of a system, the components, the security level, modules, architecture and the different
interfaces and type of data that goes through the system.
A general system design can be done with a pen and a piece of paper to determine how the system will
look like and how it will function, and then a detailed and expanded system design is produced, and it will
meet all functional and technical requirements, logically and physically.
4. Implementation and Deployment
This phase comes after a complete understanding of system requirements and specifications, its the
actual construction process after having a complete and illustrated design for the requested system.

In the Software Development Life Cycle, the actual code is written here, and if the system contains
hardware, then the implementation phase will contain configuration and fine-tuning for the hardware to
meet certain requirements and functions.
In this phase, the system is ready to be deployed and installed in customers premises, ready to become
running, live and productive, training may be required for end users to make sure they know how to use
the system and to get familiar with it, the implementation phase may take a long time and that depends
on the complexity of the system and the solution it presents.
5. System Testing and Integration
Bringing different components and subsystems together to create the whole integrated system, and then
introducing the system to different inputs to obtain and analyze its outputs and behavior and the way it
functions. Testing is becoming more and more important to ensure customers satisfaction, and it
requires no knowledge in coding, hardware configuration or design.
Testing can be performed by real users, or by a team of specialized personnel, it can also be systematic
and automated to ensure that the actual outcomes are compared and equal to the predicted and desired
outcomes.
6. System Maintenance
In this phase, periodic maintenance for the system will be carried out to make sure that the system wont
become obsolete, this will include replacing the old hardware and continuously evaluating systems
performance, it also includes providing latest updates for certain components to make sure it meets the
right standards and the latest technologies to face current security threats.
SQA plays an important role in the SDLC as quality assurance is one of the most essential parts of the
software development process. SQA Manager is the person who involve with the planning activities and
Senior SQA engineers are involve with requirement or design validation task. Junior engineers are
engaged with testing and test script generation activities.
7. Requirement identification and Initiation Phase:
Project plan is delivered to QA department/team

QA Manager reviews the project plan and checks the process, procedures and the standards are
met.
QA Manager creates a team for the project and select team member.

8. Planning and Analysis Phase:

Senior QA/Manager ensure that the user/client requirements are captured correctly
Find out the risks in the requirement and decide how the system will be tested.
Properly expressed as functional, performance and interface requirements.
Review the requirement document and other deliverables meeting the standard
Prepare the formal test plan including the test tools are being used in the project.
9. Design Phase:
SQA Manager/Senior Engineer verifies the architectural design meets standards as designated in
the Project Plan
Verify all captured requirement are allocated to software components
Review the design documentation and ensuring that all action items are resolved
Verify all the design documents are completed on time according to the project plan and kept in
project repository (ER Diagram, Process diagram, Use Case, etc.).
Prepare the design test report and submit to the project manager.
Prepare the test objectives from the requirement and design document created.
Design a verification matrix or Check list and update on regular basis
Send the test documents to project manager for approval and keep them in repository
10.

Implementation and Deployment Phase:

Verify the results of coding and design activities including the schedule available in the project
plan
Check the status of all deliverable items and verify that all are maintaining the standard.
Getting updated with the tools and technologies used in the projects and provide the feedback
to the team if any better solution is available.
Complete writing the check list/ test cases to start testing.
Verify that the components are ready to start test or not

11.

12.

Integration and Test Phase:

Start testing individual module and stat reporting bugs
Verify that all tests are run according to test plans
Verify all the bugs available in the bug tracking system are resolved.
Compile the test reports and verify that the report is complete and correct
Certify that testing is complete according to the plan
Start creating the documentation and verify that all documents are ready for delivery
Participate in the Test Readiness Review and assure all action items are complete

Software Acceptance and Delivery Phase:

Run a Beta test session using the user data and create a report.
Ensuring the performance of a final configuration audit to demonstrate that all deliverable items
are ready for delivery
Against with each phases in waterfall model (system development life cycle(SDLC)). The ways we can
make their quality is assured by
applying The SQA System. The SQA System combines a range of SQA components, due to its difficulty, to
ensure that an acceptable
level of software quality is met. The SQA Components that are used by The SQA System can be classified
into six different categories,
each of which is necessary to guarantee maximum quality and ensure to compline with the standard and
procedures.
The six different components are broken down into the following categories:

With doing all the phase and including all the process of The SQA System. All the phase will always be
assured in high level. And
because this is the project of Amazon handling so its more important. In the problem is assured the
quality of the web site for
customer. Anyway, when see the SQA system of the web site it also makes a good relationship of
company with customer.
Task 2
Software Test Plan (STP)

1. Scope of The Tests

1.1 The web site develops by Amazon
1.2 The documents: Coding Document, Design Document, Database Document
2. Testing Environment:
2.1 Testing sites: All the site develop by Amazon
2.2 Required hardware and firmware configuration: Server hosting database
2.3 Participating organizations: Amazon
2.4 Manpower requirements: Coding team, Analysis team, Testing Team
2.5 Preparation and training required of the test team: Senior System Analyst
3. Test Detail (For Each Test):
3.1 Test identification: Test web site, test UI, test server
3.2 Test objective: All of the requirement function
3.3 Cross- reference to relevant design document and the requirement document: Coding Document,
Design Document,
Database Document
3.4 Test class: Book class, find class, rent class, delete class, update class
3.5 Test level (unit, integration or system tests)
3.5.1 Unit: States, transaction, data flow, functionally, UI
3.5.2 Integration: APIs, error handling, functionally, performance
3.5.3 System: States, Transaction, data flow coverage, functionally, UI, error handling, operation,
reliability,
date/time, localization, installation and configuration options

3.6 Test requirements: Find information about the books, check the price of books, purchase and sent
home
3.7 Special requirements: Measurements of response times, Security requirements: Fast response time
and good
performance, all the requirement met the standard of security
3.8 Data to be recorded: Yes
4. Test Schedule (For Each Test or Test Group) including time estimates for the following:
4.1 Preparation: 1 week
4.2 Testing: 3 weeks
4.3 Error correction: 2 weeks
4.4 Regression test: 1 week
Software Test Report (STR)
1. Test Identification Site Schedule and Participation
1.1 The web site develops by Amazon
1.2 The documents: Coding Document, Design Document, Database Document
1.3 Test site: All of the requirement function
1.4 Initiation: Coding Document (3 weeks), Design Document (3 weeks), Database Document (3 weeks)
1.5 Test team members: Coding team, Analysis team, Testing Team
1.6 Other participants: None
1.7 Hours invested in performing the tests: 3 weeks
2. Test Environment

2.1 Hardware and firmware configurations: Server hosting

2.2 Preparations and training prior to testing: Senior System Analyst
3. Test Results
3.1 Test identification:
3.2 Test case result (for each test case individually)
3.2.1 Test case identification: Testing web site
3.2.2 Tester identification: Coding team, Analysis team, Testing Team
3.2.3 Result:
Find general information about available book: OK
Check the prices of books: OK
Purchase books to be sent home: OK
Server: OK
UI: OK
Performance: OK
4. Summary Tables for Total Number of Error Their Distribution and Types
4.1 Summary of current tests: Whole the web site is good
4.2 Comparison with previous result (for regression test summaries): The same with previous test
5. Special Events and Testers proposals
5.1 Special events and unpredicted responses of the software during testing: none
5.2 Problems encountered during testing: none
5.3 Proposals for changes in the test environment, including test preparations: none
5.4 Proposals for changes or corrections in the test procedures and test case files: yes

Software Test Description (STD)

1. Scope of The Tests
1.1 The web site develops by Amazon
1.2 The documents: Coding Document, Design Document, Database Document
2. Test Environment (For Each Test)
2.1 Test identification: Software Test Plan (STP)
2.2 Detailed description of the operating system and hardware configuration and the required switch
setting for the
tests: Coding team, Analysis team, Testing Team
2.3 Instruction for the software loading: Coding team, Analysis team, Testing Team
3. Testing Process
3.1 Instruction for input, detailing every step of the input process: Coding team, Analysis team, Testing
Team
3.2 Data to be recorded during the tests: Yes
4. Test cases (For Each Case)
4.1 Test case identification details: Coding team, Analysis team, Testing Team
4.2 Input data and system settings: Coding team, Analysis team, Testing Team
4.3 Expected intermediate result (if applicable): message appear result
4.4 Expected result (numerical, message, activation of equipment, etc.); numerical and message result
5. Action to Be Taken in Case of Program Failure / Cessation
6. Procedures to Be Applied According to The Test Result Summary

Task 3

1. The important of project management to the production

of high quality IT system

Why Project Management to the production of high quality IT system is important? Because its reduce
the chance of a project falling, to ensure a minimum level of quality and that results meet requirement
and expectations, free up others staff members to get on with their area of work and increase efficiency
both on the project, make things simpler and easier for staff with a single point of contact running the
overall project, encourage consistent communications amongst staff and suppliers. Its also keep costs,
timeframes and resources to budget. Into IT aspect, project management to the production of high of
quality IT system also promote the quality of product to high level and make a good relationship with
customer. So project management to the product of high quality IT system isnt missed in IT company
against the Amazon company. So its really important and this also the compulsory step for each
company that have IT system.
2. Produce:
a. Work Breakdown Structure
b. GANTT Chart
Task Name
1. Initiation
1.1 Gather customer requirements
1.2 Submit and approve the Request for
Proposal
1.3 Prepare the Requirements Document

Durati
on
57
days
1 day
2 days
9 days

Start

End

01/25/20
16
01/25/20
16
01/26/20
16
01/28/20

03/21/20
16
01/25/20
16
01/27/20
16
02/05/20

16
02/08/20
16
02/08/20
16
02/08/20
16
02/17/20
16
02/17/20
16

16
02/08/20
16
03/10/20
16
03/17/20
16
03/21/20
16
03/21/20
16

31
days
27
days
28
days
24
days
23
days

02/17/20
16
02/17/20
16
02/17/20
16
02/24/20
16
02/25/20
16

03/18/20
16
03/14/20
16
03/15/20
16
03/18/20
16
03/18/20
16

42
days
3.1 Design data model
26
days
3.2 Write functional specifications
26
days
3.3 Design storyboards and/or prototypes 27

02/26/20
16
02/26/20
16
02/26/20
16
02/26/20

04/07/20
16
03/22/20
16
03/22/20
16
03/23/20

1.4 Conduct project kickoff meeting

1 day

1.5 Develop Statement of Scope

32
days
1.6 Build Work Breakdown Structure
39
(WBS)
days
1.7 Outline project plan
34
days
1.7 Assign resources to project plan tasks 34
days
2. Analysis
2.1 Create Entity Relationship Diagram
2.2 Create Data Flow Diagram
2.3 Define data dictionary
2.4 Perform object-oriented analysis

3. Design

3.4 Write detailed design specifications

3.5 Write documentation plan
3.6 Write SQA test plan, test cases
3.7 Write customer support plan
3.8 Write risk management plan

4. Development
4.1 Code application components
4.2 Unit test
4.3 Integration test
4.4 Write documentation
4.5 Write training courseware

5. Software Quality Assurance

(SQA)
5.1 System test

days
28
days
28
days
30
days
30
days
32
days

16
02/26/20
16
03/03/20
16
07/03/20
16
07/03/20
16
07/03/20
16

16
03/24/20
16
03/30/20
16
04/05/20
16
04/05/20
16
04/07/20
16

32
days
29
days
30
days
30
days
30
days
31
days

03/15/20
16
03/15/20
16
03/16/20
16
03/16/20
16
03/16/20
16
03/16/20
16

04/15/20
16
04/12/20
16
04/14/20
16
04/14/20
16
04/14/20
16
04/15/20
16

34
days
20
days

03/23/20
16
03/23/20
16

04/25/20
16
04/21/20
16

5.2 Track defects

5.3 Regression test

6. Manage Release and Change

6.1 Configuration management
6.2 Maintenance releases
6.3 Defect and enhancement tracking

7. Implementation
7.1 Install beta test system and Conduct
beta tests
7.2 Track defects and report to customer
support
7.3 Gather requirements for
customizations
7.4 Install development system (GA
release)
7.5 Implement/adapt system
7.6 Integration test (Implementation)
7.7 Execute customer acceptance test
procedure

30
days
27
days

03/23/20
16
03/30/20
16

04/21/20
16
04/25/20
16

34
days
27
days
29
days
27
days

03/30/20
16
03/30/20
16
03/30/20
16
04/06/20
16

05/02/20
16
04/25/20
16
05/27/20
16
05/02/20
16

36
days
27
days
27
days
28
days
24
days
25
days
25
days
25
days

04/08/20
16
04/08/20
16
04/08/20
16
04/08/20
16
04/18/20
16
04/19/20
16
04/19/20
16
04/19/20
16

05/13/20
16
05/04/20
16
05/04/20
16
05/05/20
16
05/11/20
16
05/13/20
16
05/13/20
16
05/13/20
16

c. Critical Path Method

EST: Earliest Start Time

LST: Latest Start Time
(1): Initiation
(5): Software Quality Assurance (SQA)
(2): Analysis
(6): Manage Release and Change
(3): Design
(7): Implementation
(4): Development

Initiation

Critical Path: Start (1) (2) (4) (5) (7) Finish

(1): Gather customer requirements

Scope
(2): Submit and approve the Request for Proposal
Breakdown Structure (WBS)
(3): Prepare the Requirements Document
project plan tasks
(4): Conduct project kickoff meeting

(5): Develop Statement of

(6): Build Work
(7): Assign resources to
(8): Outline project plan

Critical Path: Start (1) (2) (3) (4) (8) (7) Finish
Analysis

(1):
(2):
(3):
(4):

Create Entity Relationship Diagram

Create Data Flow Diagram
Define data dictionary
Perform object-oriented analysis

Critical Path: Start (2) (3) (4) Finish

Design

(1): Design data model

(5):
(2): Write functional specifications
cases
(3): Design storyboards and/or prototypes
plan
(4): Write detailed design specifications
plan

Write documentation plan

(6): Write SQA test plan, test
(7): Write customer support
(8): Write risk management

Critical Path: Start (4) (5) (8) Finish

Development

(1): Code application components

(2): Unit test
(3): Integration test

(4): Write documentation

(5): Write training courseware

Critical Path: Start (1) (5) Finish

Software Quality Assurance (SQA)

(1): System test

(2): Track defects

(3): Regression test

Critical Path: Start (1), (2) (3) Finish

Manage Release and Change

(1): Configuration management

(2): Maintenance releases
(3): Defect and enhancement tracking
Critical Path: Start (2) (3) Finish
Implementation

o (1): Install beta test system and Conduct beta tests (5): Implement/adapt system
o (2): Track defects and report to customer support
(6): Integration test
(Implementation)
o (3): Gather requirements for customizations
(7): Execute customer
acceptance test procedure
o (4): Install development system (GA release)
o
o Path Critical: Start (3) (4) (5), (6), (7) Finish