Aveneu Park, Starling, Australia

1. quality within the project will cost

1.    
Introduction

Quality: the degree to which a set of inherent
characteristics satisfies the stated or implied needs of the customer. To
measure quality successfully, it is necessary to turn implied needs into stated
needs via project scope management.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

The
Quality management plan focuses on defining the objcetives for quality, how
they will be applied and how they will be meaasured.  Quality can planned in to each process and
controlled along the way, or it can verified and validated in the end.  The implementation of quality within the
project will cost time and money. 
Quality is the fourth component the the triple constraint of Cost, Time
and Scope, as any one of these change, so do the others, all of which impact
quality.  

 

2.     Scope

This SQP for ERP projects under Technical
Department responsibility in zoo Business solution.

 

2.1   About the Company

Zoo Business Solutions Co Ltd operates in the
field of business automation. It provides business applications and software
such as Odoo ERP that enables automation of business processes.

 

 

 

 

 

 

2.2   Structure

 

 

2.3   Quality
Stander

This SQP will follow the ISO 25010 stander to apply and
measure the quality in the software and software life cycle. The model have
eight characteristic we will use and measure three of them correctness and
completeness in requirement gathering phase, Integrity of
software component in development phase, and will measure the availability and
accessibility in testing phase and deployment phase.

 

2.4   Methodology

We use Scrum agile development methodology in
development lifecycle; scrum is an agile framework for completing complex
projects. The basic unit of development in scrum is sprint; the sprint is a
time boxed effort; it is restricted to a specific duration (2 weeks). Each
sprint start with sprint planning event that aimed to define the sprint backlog
and identify the work for the sprint and make estimated forecast for the sprint
goal. Each sprint end with sprint review that review progress to show to
stakeholders and identify lessons and improvement for the next sprint.

 

2.5   Roles &
Responsibilities

2.5.1         
Product Owner

2.5.1.1               
Elicit requirements (user story) using
interviews, document analysis, requirements workshops, surveys, site visits,
business process descriptions, use cases, scenarios, business analysis, task
and workflow analysis.

2.5.1.2               
Defines and documents customer business
functions and processes.

2.5.1.3               
Participates in user acceptance testing and
testing of new system functionality.

2.5.1.4               
Planning, estimating and retrospective across
development sprints.

2.5.1.5               
Maintain technical & Functional record
keeping

2.5.1.6               
Use analytical skills to resolve business
issues

 

2.5.2         
Scrum Master

2.5.2.1               
Prepare scrum tasks and divided it
to developers

2.5.2.2               
Develop the requirement
specification and cost estimation for the project

2.5.2.3               
Develop the design plan and test
plan for testing

2.5.2.4               
Planning, coordinating, testing and
assessing all aspects of quality issues.

2.5.3         
Development Team

2.5.3.1               
To ensure that the software
requirement and scope in the version document are clearly state.

 

2.5.4         
Quality Team

2.5.4.1               
Defines quality standards to be followed by
writing a quality assurance plan

2.5.4.2               
Review the requirement document

2.5.4.3               
Responsible for writing the Software Test Plan
(TP).

2.5.4.4               
Write UI test cases then going to
functional test cases.

2.5.4.5               
Managing the process of testing.

2.5.4.6               
Organizes usability test, this includes
gathering test group and preparation

2.5.4.7               
Classifies eventual usability errors and
together with GUI designer suggests improvement to GUI

 

3.       
Quality in Requirement
Gathering Phase

3.1   QA in
Requirement gathering

3.1.1         
Completeness : ensure  that requirement
are specified objectively and should provide criteria for validation

3.1.2         
Correctness: to ensure that the
requirements are correct and no conflict between them.

3.1.3         
To ensure that requirements
specifications are easily understandable not only by requirements analysts but
also other stakeholders, including software designers, users, and end users.

 

3.2  
Quality Activity in
Requirement gathering phase

3.2.1         
Gather the requirement through
technique (interviews, meetings, observation, etc.) that suitable with customer
filed and the nature of requirement.

3.2.2         
Record the requirement session to
ensure the access to session details any time during the system development.

3.2.3         
Write all the data that you
gathered in requirement document in clear statement

 

3.3  
QC in Requirement gathering
Phase

3.3.1         
Determine that the need have been
defined and documented

3.3.2         
Determine that the requirement
fairly represent what the user need

3.3.3         
Determine that the business problem
has been solved

 

4.    
Quality in Development phase

4.1   QA In
development phase

4.1.1         
Good use of descriptive comments for all
methods and relevant variables.

4.1.2         
Variables and method names should be chosen
that are short, unique and descriptive.

4.1.3         
Integrity: To ensure that the software able to
integrate with other component or another software.

4.1.4         
Develop the software
as several modules

4.2   Quality
activity in development phase

4.2.1         
Code inspection

4.2.2         
Naming convention

4.2.3         
Unit test individually

 

5.    
Quality in Testing Phase

5.1   QA In
testing Phase

5.1.1         
Identify types of test to be
performed

5.1.2         
Gathering details about testing
priorities and focus

5.1.3         
Identify test environment details
where testing is supposed to be carried out

5.1.4         
To ensure from the testability and
modularity of the software

 

5.2   Quality
activity in testing Phase

5.2.1         
Review requirement document

5.2.2         
Test case execution

5.2.3         
Integration test

5.2.4         
Non-functional testing

5.2.5         
Check the availability and accessibility
of the software

 

 

 

 

 

6.    
Quality in Deployment

6.1   QA In
deployment Phase

6.1.1         
To ensure the new system with the
old system in parallel for couple weeks

6.1.2         
To ensure that user training was
done before the deployment.

 

7.    
Quality Control for the
software

7.1   QC
Activity

7.1.1         
Check that assumptions and criteria
for the selection of data and different factors related to data are documented

7.1.2         
Check the transaction errors in
data input and reference

7.1.3         
Check the integrity  of database files

7.1.4         
Check for constancy in data

7.1.5         
Check that the movement of
inventory data among processing steps is correct

7.1.6         
Check for uncertain in data,
database files, etc.

7.1.7         
Undertake the review of internal
documentation

7.1.8         
Check the methodological and data
changes resulting in recalculations (if any)

7.1.9         
Undertake completeness check

7.1.10       Compare result to previous
result

x

Hi!
I'm Simon!

Would you like to get a custom essay? How about receiving a customized one?

Check it out