LEVEL 6 - PRODUCTION

PROJECT
Engineering Customer Relationship Management
Database
Robert Gaskin 77087494

PROJECT PLAN

Contents
1. Project Aim...........................................................................2
2. Objectives............................................................................3
3. Product Specification............................................................4
3.1. Product Rationale.............................................................4
3.2 MoSCoW Analysis..............................................................4
3.2.1 Must Have...................................................................4
3.2.2 Should Have...................................................................5
3.2.3 Could Have....................................................................6
3.2.4 Wont Have..................................................................6
3.3. Research Aims.................................................................7
4. Physical Resources...............................................................8
4.1 Software Requirements....................................................8
6. Human Resources.................................................................9

1 | Page

1.

Project Aim

The Aim of this project is to create anout of the box Customer

Relationship Management Database System for use by
potential Engineering Firms to manage sales made by the
companyand services offered.

2 | Page

2.

Objectives

Identify a methodology for this project.

Manage the project via Gantt Charts created in Microsoft
Excel to track the progress of each individual phase of the
project and document all meetings.
Specify a set of succinct requirements based from existing
engineering business documentation and interview the
client to analyse requirements using the MoSCoW
Technique.
Perform research to understand what is meant by high
quality data, which areas are most relevant to this project
and issues others have encountered with data quality.
Decide on tools and techniques based off the research
that can be used to improve the quality of the Database.
Createa design document torepresent how and what the
system will display using appropriate design techniques
such as Normalisation.
Using CASE toolscreate an ERD for the system to establish
the structure for the Database and forward engineer the
code.
Implement a Database Management System using SQL
with the aid of application software such as Oracle APEX to
ensure that our project makes use of excellent queries,
triggers, LOV, PL-SQL, challenges, Reports, Charts and
Navigation.
o Implement a web-based front end application which
allows end users of the system to successfully
interact through the database using a web-browser.
Test the final product to ensure that all functional
requirements that have been specified are met using
dummy data.
o Deploy a successfulrelease of the complete product
with a unique configuration to a test site.
Critically evaluate the implementation, design and testing
of the project.
3 | Page

4 | Page

3.

Product Specification

3.1. Product Rationale

This project is being developed as a Customer relationship

management databasefor engineering companies that will have
to it will be used by them to track sales of products and
services and also manage customer feedback.
The major Goal of the project is to develop a system that could
be sold on to these companies however marketing the product
will not be a part of this project.
3.2MoSCoW Analysis.

MoSCoW will be used to breakdown the requirements into

fourdifferent groups;Must, Should, Could and Wont. This is
being done to establish priorities for the project.
3.2.1 Must Have.
The database will need to store information about the products
that the engineering company supplies the following.
Information on productsthey are selling such as:
o Products Name
o Attributes
o UN-Hazard Code (As needed.)
o Product Current Location.
Information on the Customers They are selling to such as:
o Name
o Address
o The Company they belong to.
o Contact Details
Information on any services offered such as:
o The Engineer Performing Service.
o Total cost for the Service

5 | Page

Information of the engineer providing the service such as;

o Name
o Contact number
o Where they are located

6 | Page

Queries to support;
Creating a new order on the system and adding a new
customer if required for this orderinterfaced with via a
GUI.
Add, edit or remove any information held on Products,
Services, Engineers or Customers, interfaced with via a
GUI.
For customer orders that require a service, create a new
service, specify which products are required and choose
who will perform the service.
Find and list all current ongoing services that do not have
any Engineers assigned to them and assign them
appropriately.
Orders andservice statusmarkersto track the current
progress of orders.
Reports to display:
Display the most profitable customers for the year
including options that limit by Orders + Services, Just
Orders or only Services.
3.2.2 Should Have.

The database couldalso store information on;

Engineer Qualifications, Which products require specific
qualifications and which Engineer has these qualifications.
Customer Feedback on specific products.
The following queries could then be implemented:
The ability to view any feedback for a specific product or
engineer on the system.
7 | Page

 The ability to add, invalidate or edit existing Engineer

Qualifications.
Appropriate Messages or Warning to inform that an
engineeris already working on another project.
The following report should be included:
Reports that display all engineers who are currently not
working on another project.
Reports that display how many engineers have a specific
qualification.
3.2.3 Could Have.

The ability to keep track of customer messages sent via Email tracking, highlighting them initially as service
requests and dealing with them appropriately.
Dashboard for engineers managed by separate user logins
to display current services that are assigned to them and
reject or accept them also allowing them to update their
own information.
The ability to manage these users removing or adding
access for them.
The ability to upload a set of services or products to the
system via a .CSV file or Excel spreadsheets. Potentially
this could lead to the ability to upload product lists for
Individual services.
Substitutes or Alternatives products to maintain available
services so that if a product is removed a replacement
takes its place or as recommendations for a regular order.
The ability to switch on or off certain pieces of
functionality such as product feedback or engineer
feedback using administrator controls.
Logic to display or assign available engineers to a service
when a service request is made.
8 | Page

 Web integration with the feedback system allowing users

to write up reviews on a website and this appearing on the
system.
A calendar system allowing services to be booked on an
Engineers diary.
Tracking of engineers currently studying a qualification
including estimated completed dates.
3.2.4 Wont Have.
Marketing the end product for sale as this is not the field of
study for the developer of the project.
3.3. Research Aims

The need for high quality data in engineering companies

stretches beyond financial incentives as they will often store
information on;
Hazardous Products, such as chemicals or adhesives which
may be a risk to health if misused or used inappropriately.
Engineers who may pose a risk to others or themselves if
they are poorly trained.
Some accidents could be prevented with better understanding
on how dangerous a product was or making sure that an
engineer can safely complete a piece of work. High quality data
helps with both of these by providing the necessary information
accurately of the product or engineer.
The Aim of the research is tounderstand what is meant by
quality data, why it is so important and analyse tools and
techniques others have used in the past to come up with an
appropriate solution to address data quality for the system.

9 | Page

10 | P a g e

4.

Physical Resources

4.1 Software Requirements

Item
QSEE SuperLite version 1.1.2

Oracle Application
Express 4.1.0.00.32

EndNote X7

Microsoft Office
2010
Notepad++ 6.6.9

11 | P a g e

Purpose
ERD Creation
Forward
Engineering
SQL.
Project
Development,
Design and
Testing.
Referencing Tool
For Research
Report
Documentation
Reviewing
Forward
Engineered
Code.

Source
Leeds Beckett
University

Leeds Beckett
University

Leeds Beckett
University
Leeds Beckett
University
Open Source Tool,
available from :
http://notepad-plusplus.org/

5.

Human Resources

Robert Gaskin

Student I.D.: C7087494

Course: Computing
Role
Role:
Project Manager/Development/Design/Implementation/Unit
Testing/Functional Testing
Experience
QSEE SuperLite, Oracle APEX, Microsoft Access, SQL.

Jackie Campbell

Role
Project Supervisor

Leeds Beckett Staff Member

Margaret Chawawa

Leeds Beckett Staff Member

12 | P a g e

Role
Project Client/User-Acceptance
Testing.