Saturday, October 25, 2008

Final Update and project submission

As we met with Shiping for the final meeting (24/10)
We were asked to show what we had done.
The final application implementations on the C# version of iTester yielded these applications which were demoed by myself:
- An application GoogleTester (Googles web service technology)
utilising the framework.
- An application ATMclient/ATMserver, a client/server setup utilising the framework
- An application HTTPResponse, a query over the http protocol on a defined URL utilising the framework
The user and developer manual had been written and uploaded to sourceforge's cvs site.
The Java application implementations and extensions (getCL(), setCL(), getER(), setER()) on the framework had been completed.

After handing Shipnig the project clearance form to sign and after a brief
discussion on the future maintenance of the iTester website, this marked the end of the incredible journey.

Thursday, October 16, 2008


At this point:

Development updates:
- Implemented google webservice application with the C# implementation of the framework.
- Implemented an ATM Client / Server application with the C# implementation of the framework.

- Have started writing documentation, user guides and developer guides and how to run implemented sample applications with the framework

General updates:
- Resolved problem with initial running of the framework through config.xml file modification.

Monday, September 22, 2008


Work completed:
- Implementation of a basic ATM System application and interfaces to be tested by iTester.
- Conceptual diagram of ATM System drawn

CSIRO Meeting with Shiping 19/09/08 discussion points:
- Documentation of iTester on Sourceforge and structure.
- Team parts and which sections are worked on by who.
- Me working on C# documentation and web server application of iTester (C# implementation) - Shiping requires ATM System to be a web server application.
- Thesis requirements.

My planned actions:
- Management update of iTester project on Sourceforge
- Implementation of web server application using .net remoting.

Saturday, August 30, 2008

Current Updates and Group Discussion

Current updates to the framework:
- Implemented printReport() in to print out results into a file.
- Modified and cleaned up code in to increase readability.
- Lightweight example of Yahoo's search web service has been tested by the framework.

Meeting notes and development plans (
- Met with Shiping on 29/08/08, discussed further advancements and implementation of the framework.
- Applying the framework with large heavyweight applications in Java.
- C# integration and implementation of the framework to light and heavyweight applications to show high adaptability and versatility.
- Use of XML as the standard for file formatting and applying this to test.prop and the test results generated on file.
- Shiping strongly emphasised user friendlyness and a strong documentation base.
- Discussed getCL(), setCL(), getER(), setER() methods and how they function mathematically.
- Proposal of a graphing functions to portray average response time vs clients and latency vs occurance.

Friday, August 15, 2008

Group Meeting and Discussion

On the 12/8/08 we held a meeting regarding the deployment of the server. After much discussion and analysis of the pros and cons, we have decided to use Google as a web service as opposed to acquiring and deploying a web server.
Without much knowledge of web services and implementation of web services, we have tasked ourselves in reading and learning about Google's web service on the site.
Other results of this meeting included the creation and registration of the project on This was soon approved by the sourceforge admins and will be hosted on this site under the project name of "iTester" in my account.

Sunday, August 3, 2008

Submission of Project Plan

After receiving Shiping's feedback on the project plan. It was then revised and submitted on the 1st of August at the Uni

Saturday, August 2, 2008

Meeting at CSIRO / Final Draft

A final draft was produced and taken to the meeting with Shiping for feedback on the 30/7/08.

This draft consisted of the following changes:
- Feasible dates added to milestones
- New tasks of acquiring and setting up server added.
- Edited resource assignment matrix
- Edited task dependency matrix

Meeting discussion included the following issues:
- Giving the project a name. Something without "java" or the name of a programming language within it. Also the project name consisting of the words "performance" and "testing".
- Cleaning up existing code; formatting, commenting etc.
- Addition of 4 new functions: setCL, setER, getCL, getER. (where CL = confidence level , ER = error reading).
- Relationship between CL and ER.
- Building vs deployment of the application to be tested.
- Acquisition of a web service / web server.

Friday, August 1, 2008

Code from CSIRO

Testing framework from the CSIRO was received today. This will be implemented and used as a key component in testing the application at interest. If need be further functionalities will be added to the code as required.

Monday, July 21, 2008

Second draft plan produced

A second version of the draft project plan was produced and these were the changes:
- Resource assignment matrix was added.
- Task dependency matrix added.
- Thesis structure was refined and revised.
- Milestones added.
- Project aim added.
This copy was e-mailed to Shiping, David and Naimul.

Tuesday, July 15, 2008

Drafting A Project Plan

A group collaboration took place in the city as we sat down to discuss our project plan, in particular its scope and time management. One key problem included finding a template for the layout of the project plan. As there were none on the uni site, based on our internal supervisor's decision, we decided to encompass three sections in our project plan. Thesis structure (individual), thesis structure (collaborative) and a schedule. Dependencies and milestones of the project were also considered in the meeting. After a lengthy discussion we decided to go home and scribe thoughts to words.

Thursday, June 5, 2008 Account Setup

Recently setup an account with under the username "leonard_k".
As a requirement of the project this account will be used to contribute the project to the open source community.

Thursday, May 22, 2008

The Meeting with Dr Rafael Calvo

The next step of the journey was to select an internal EIE supervisor.
After deep contemplation we selected Dr Rafael Calvo as the EIE internal supervisor for our project, refer to A meeting was swiftly organised in his luxurious office the aim to discuss the expectations, monitoring and marking of the project. During this meeting we also met the other friendly students undertaking engineering projects under Rafael's control and a short self introduction took place.

As I pondered the structure my thesis, Rafael distributed a sheet of paper which saved what would look to be a couple of hours of reading. This informative sheet outlined how to write a thesis in a student friendly format.

We quickly learnt that with our project we would have to set distinctive work boundaries for each member so that each individuals part can be distinguished from one another.

CSIRO Project Acquisition and Description

The final semester is fast approaching and with it comes the last mountain to be climbed where some will fall along the way. Like all mountains sits the test of truth at the top that will make or break some, this final test is ELEC4707 (The Engineering Project)

After speaking to Dr Shiping Chen at the CSIRO ICT division, and sending in our resumes, David Ma (SID: 200414178), Naimul Khaled (SID: 200414172) and I (SID: 200419452) acquired a project labeled "Open Source of Software Performance Testing Framework"
This team project collectively involves:
1. Building/deployment of an enterprise system capable of simulating simple transactions using a Java and/or Microsoft .Net framework.
2. Subjecting this system to testing using a given framework by the CSIRO
3. Documentation of findings and results.
4. Publication of code as open source along with documentation to allow for further improvement by the community.