Daily Report 18/05/05

- Started on Prototype Beta (interface)
- Finished up to 70% of prototype Beta

This prototype will evolve as the project progresses and give an indication of the functionality and 'look and feel' that the final system would offer.

- Went to the InnoGram Computer Expo at Brisbane Convention Centre

13/05/05 Daily Report

Dropped in to help Willy with the improvements on the MS Access Database. Created 1 Form and 1 sub-form to handle Parts Order and Usage.

Installation and setup of MySQL server, PHP and Apache Web Server.
Configured Apache Web Server to work with PHP.

12/05/05 Daily Report

Upgraded current MS Access Database with 5 forms and 3 sub forms in order for better efficiency.

11/05/05 Daily Report

A lot of NB service jobs today.

Worked on categorising data of Order books to be imported into the database.
Worked on 3 order books.

Daily Report 14/4

- Identified processes within the workflow that will modify the data
- Created Data Flow Diagram in MS Visio 2003
- Compiled Database Proposal Documentation

- Received & Analysed 2 external data sources from Kenny
- Installation of MySQL, MySQL Administrator, MySQL Query Builder


Things to be done:
- Create ER Diagram
- Compile User Requirement report
(Consolidate User Requirements, Workflow, Dataflow, UoD, DFD and ER)
- Map ER to Table
- Create Extreme Programming Story Cards (Function Testing)

Daily Report 13/4

- Tested Notebook for display problems (No Error Found)
- General Receiption Work
- Database Project Proposal created
- Estimated Costs
- Estimated Milestones
- Outline of work and processes to be done
- Analysis on Current Database Table
- Kenny advised of Data Import capability requirement
- able to import from "Order Book"
- able to import from Third party repair centres
- Universe of Discourse created

The Universe of Discourse
Asus Notebook Service Centre, Brisbane

Customer has First Name
Customer has Last Name
Customer has Phone Number
Customer has Mobile Number
Customer has Fax Number
Customer has E-mail address
Customer has company name
Customer has Address

Address has Street
Address has Post Code
Address has City
Address has State

Street has Street Number
Street has Street Name

Customer owns a Notebook

Notebook has a Serial Number
Notebook has a Model
Notebook has a Specification
Notebook has a Purchase Date
Notebook has a Warranty Expiry Date (2 yrs from purchase date or 2 yrs from Serial Number, whichever is later)
Notebook has a Service Job

Service Job is fixed by Staff
Service Job is delivered by Staff
Service Job is received by Staff
Service Job has failure symptoms…
Service Job has Service Charge of ($)
Service Job has diagnosis description
Service Job has Action Taken
Service Job uses Parts
Service Job is serviced at Location (def: Brisbane)
Service Job was received on (Time)
Service Job was started on (Time)
Service Job was ended on (Time)
Service Job was delivered on (Time)

Parts has Part Number
Parts has Serial
Parts has Description
Parts has Status (New/Used)
Parts has Price

Staff has FirstName
Staff has LastName
Staff has StaffID

Call is taken by Staff
Call is calling from a Customer
Call is related to Notebook
Call maybe about Service Job
Call has Inquiry Detail
Call has Advise Given
Call has start time
Call has finish time
Call has call_type (in/out)

Daily Report 7/4

1st Meeting on Database Project was held- Brief on project scope:
- obtained current DB table structure
- current DB structure contains data redundency
- DB Project divided into two stages, warehouse data and service data
- Project Proposal to be submitted outlining milestones and development technologies and process.

Current Workflow of Asus Notebook Service Centre
There are three categories of work that will be using the DB:
- Walk-in Service (Stage 1)
- Telephone Enquiries (Stage 1)
- Parts Replacement (Stage 1 & 2)
- Warehousing (Stage 2)

Daily Report 6/4

- Learnt normal business operations tasks such as: mailing, parcel delivery, work flow within the service centre.
- Observed data flow and work flow
- Investigated into the original DB structure

Daily Report 31/3

Back Office Operations
- All phone calls are logged in database


NB Servicing
- NB stacked into a FIFO queue
- NB Engineer to inspect for technical problem
- Software / Hardware testing to identify problem
- Replace hardware with spare parts (if under warranty)
- Contact customer if not under warranty with quoted price
- Record old and new spare parts serial/product code
- Contact customer for collection
- Place NB in 'ready for collection box'

* Never place staples near LCD Panel
* Never place metal objects on top of NB to prevent scratches


Existing database analysis
- Data Redundancy exists
- Tables for each 'function' - phone call, NB details, Warehousing, Job details etc.

* Started UoD creation from existing DB details
* Started ER mapping