Meetings Mintues - 27th, 29th August 2008

1. Meeting 6, 27th August 2008
1.1 Meeting Opened – 2.30PM
The meeting was initiated as our weekly meeting which we will have every week.
All team members are in attendance – Kevin, Andrew, Chinh, Chuong, Hai and Vivi.

1.2 Progress Report
· We have developed template for our requirement specification and devolvement plan.
· Further discussed the method we will design the database in and how it’s going to interact with the Vicnet system.
· We have collected extensive information about the company and have a clear vision for our website design.
1.3 General Business
· Our meeting today was the major meeting for the week.
· Our first assessment for our documentation is due on Monday 1st September.
· Need to discuss the areas we need to finish off.
· Confirm our Acceptance Criteria for the client to view and sign off.
· Major areas to finish are the functional requirements, user interaction with the system and use cases we need to develop.
· Create some ideas for our designing and developing of the software server, database and layout.
1.4 Actions to be taken
· Andrew – need to finish the requirements specification document (functional requirement)
· Kevin – to complete acceptance criteria, use cases, hand in assignments on Monday 1st Sep.
· John – to complete his part of the development plan (charts, gnat chart, timelines)
· Hai, Minh and Vivi to hand Kevin their completed use cases.
1.5 Next Meeting – Tuesday 29th August, 3.00PM
· Have our acceptance criteria complete for client
· Think of anymore questions to ask the client about the system
· Proof read through document to much sure all spelling and layout are correctly setup.
· Continue researching on our programming requirements needed to make our software for the project.
1.6 Meeting Adjourned – 5.30PM

2. Meeting 7, 29th August 2008
2.1 Meeting Opened – 3.00PM
The meeting was initiated as our weekly meeting which we will have every week.
Team members in attendance – Kevin, Andrew, Hai and Vivi.

2.2 Progress Report
· We have completed the requirements specification and development.
· Have now started developing the software for the client.
· Using a software tool called Joomla to make the project
· Our team is working well, all tasks are on track.
2.3 General Business
· This was our second meeting with the client.
· We discussed the requirements in further detail and layout of the site.
· Asked some questions about the database design concerns.
· Use common name as photo's title
· Only put common name beneath thumbnail
· Photo details include common name, scientific name, location, date, and description
· Observation log details include common name, scientific name, location, date, and description
· Member can post photo or observation log as anonymous, so that only admin knows who posted it
· Admin is able to edit photo details easily, eg. move photo to the correct album
2.4 Actions to be taken
· Kevin – hand in requirements specification and development on Monday 1st September
· Andrew and John to prepare power point presentation for Tuesday.
· Minh, Hai and Vivi to further develop the software.
· Ray would like to look at the blog that was setup for him, but he was unable to do so because of the "complex" procedure to setup a google account.
· John can you change the blog settings so that it is open to public? he said he wouldn’t mind, and there's nothing to hide anyway.
2.5 Next Meeting – Tuesday 1st September, 1.00PM
· Discuss our next step for the project.
· Andrew and John to go over their presentation.
· Group to get our testing document started and develop some testing requirements to test out.
2.6 Meeting Adjourned – 4.30PM

Beginning Joomla - From novice to professional

Hi guys

I have been digging around and found the book for joomla. It's exactly the same with the book Vivi's holding. It's ebook btw and i uploaded to file exchage already. So please download and read it.

Have fun reading book guys.

Blog for client update and meeting minute request

@Kevin: hi Kevin, can you update the blog for client with following things, thanks Kevin :

• The meeting minute (who took the meeting minute on friday would provide you this)
• Project progress (write something to say that we have finished the requirement specification and client has agree on Acceptance Criteria), post the project time line picture if you can (i put this PDF in file exchange in BB already)
  

@Andrew: hi Andrew, can you update our blog with team meeting minute for last thursday, i will update the "things need to be done next after you post the minute" (leave a section called "things need to be done next" in the bottom of minute for me if you can). By the way, please save all the meeting minute documents in separate folder in your PC and for our blog only, you dont need to post the minute with formal structure, just say what we have done, what we have decided, who will do what and things need to be done next. And post the final Requirement and Development Plan to file exchange in BB. That would be great, thanks Andrew.

If you guys have any question (whatever it is - even dumbest one), feel free to speak it out and we all can answer it. Thanks guys

Quick summary of the 29/08/2008 meeting with client

• Use common name as photo's title
• only put common name beneath thumbnail
• photo details include common name, scientific name, location, date, and description
• observation log details include common name, scientific name, location, date, and description
  
• member can post photo or observation log as anonymous, so that only admin knows who posted it
  
• admin is able to edit photo details easily, eg. move photo to the correct album
• Ray would like to look at the blog that was setup for him, but he was unable to do so because of the "complex" procedure to setup a google account. John can you change the blog settings so that it is open to public? he said he wouldnt mind, and there's nothing to hide anyway.

please feel free to add if i have forgotten any

marinecare.org.au

it seems that they have got it up and running already
http://marinecare.org.au/

Meeting with client and the documentations

Time: Friday 3pm (Please try to arrive early and meet at the entrance of the building at around 2.45pm)
Address: please refer to First meeting with client
Attendant: Andrew Paton, Hai Minh, Kevin Chan, Vivi Lam
Note: Try to dress semi-formal, at least wear a shirt/polo shirt


In regards to the documentations (Requirements Specification, Development Plan and Acceptance Criteria), I have made some minor editing to them and uploaded them to BlackBoard. Please spend some time and proof read them.

In the requirements specification document, I noticed there are duplicate paragraphs and I have highlighted it in red. Should the text below the diagram be deleted or the one near the beginning?

For the use cases in the requirements specification, especially the ones for Administrator, I just kind of made them up because we really don't know how it operates yet. More use cases can be added before I submit them on Monday if needed.

BTW John can you send me the project timeline, without time elapsed, in a pdf file? since the one you sent me before has it.

Draft acceptance criteria added to BB

please take some time and read through it, tell me if you found anything wrong with it or if i have missed anything asap as i will send this to the client before this afternoon's meeting.

rough project timeline uploaded

hey guys, i upload the rough project timeline on BB already, you can download and have a look at it, i put more description in, the blue line is time elapsed

development plan template

The development Plan will look like this

Executive Summary

Background

Objectives

Scope

Constraints and Dependencies

Assumptions

Risks

Deliverables

Issues

Project team Structure

Roles and Responsibilities

Appendix A – Gantt Chart

The difference between this doc and requirement doc is Team structure, role, WBS and gantt chart, everything else is the same.

@Kevin: you can move on with the acceptance criteria without my part, but i send you a copy anyway

@Andrew: i will not write all the stuff like executive, backgound... I only write team structure, WBS and Gantt chart, can you copy other part from the requirement and put it here

Meeting minute request

Andrew, can you post the meeting minutes for the last 2 meeting (monday and tuesday) on here please, thanks

Use case 1

Scenarios

Preconditions for all Scenarios

• Mary is the Administrator of the database
  
• Joe has an active user account on the database
• They know their login name.
• They have a PC with a web browser installed and a working internet connection.
• They have basic skills in using a PC, a browser and how to access web sites.

Postconditions for all Scenarios

• Mary and Joe are successfully logged out and the web session between their PC and the marinecare.org.au web site is closed.
  

Name :
Posting an observation log and photos

Preconditions :
No further preconditions needed.

Sequence of steps :
1. Joe opens a web browser and goes to marinecare.org.au.
2. Joe clicks on "Sightings" at the top of the page.
3. Joe types in his login credentials and selects "login".
4. If: login fails go to step 3 and show an error message.
5. Else: System message "You have been successfully logged in" and goes back to the first page.
6. Joe clicks on "Record Sightings".
7. Joe selects and enters the information about the sighting, which includes Category of sighting, Title, Scientific Name, Details, Location, Observed by whom, Time and Date.
8. Joe clicks on "Add photo".
9. A window pops up and allows Joe to browse for the photos.
10. Joe clicks submit and waits for the form and photos to be uploaded.
11. If: The fields are not correctly filled out, an error is displayed, fields that have errors are highlighted, and Joe has to go on with step10.
12. Else: System message "Sighting posted successfully." and goes to the summary page of the sighting.

Postconditions :
The sighting is added to the observation database.
The sighting can now be found by other users by using the Search function in "Sightings".
Photos are resized to under 500k.
Thumbnails of photos are created.
Photos uploaded are shown in the "Marine Galleries".
An alert is sent to Mary that new sighting and photos are uploaded by Joe.





bit of a rush :p

Communication channel with Greypath and Vicnet

Hi guys, i have just created a blog as a communication channel with our client and vicnet, they will be able to view and post any of their concern about the project. We can post our project result there for them to monitor and make sure everyone knows what's going on. Please make sure you dont post crap there, only formal stuffs because the client and Vicnet are gonna read them. Thanks guys.

Drafted email to Ray andJohn

Please check if it looks alright, and if I have missed anything.

Dear Ray and John,

We have spoken to Tania this morning and learned about the project's environment. They are in the process of setting the servers up. The servers should be up and running within next week, and access will be granted to us.

However, there is a problem with the limitation of webspace allocated to MarineCare.org.au. We were told that only 50MB is available for the whole website. That will leave VERY little space to store photos in the photo gallery. Considering each photo can take up to MBs, solutions to that can be:

- increase webspace to at least 300MB

- reduce photos size to (under) a MB

It is very likely that we will put our website up directly through Vicnet since access to the servers will be granted to us. In regards to the installation CD that you have asked for, after carefully analysing, it will be very hard to install the completed website and database with just a CD. Instead, we can provide a backup of the website, documentations and configurations on the CD for others to look at, in case of something happens to the server. Would you be happy with that?

We are in the process of producing an acceptance criteria document base on the requirements that you have stated. I will email it to you on Wednesday and get you to sign it on Thursday afternoon if it is ok for you.

Best Regards,

Kevin Chan

Joomla testing site

Hey guys, I just set up a website for testing:

https://unix-kernel.org/joomla

User: hit3061

Pass: t3st1ng

The user is assigned as manager, so he would be powerful enough :p

I manage this site, so let me know if you want to add/remove any feature

Questions for Tania tomorrow

- How much is disk space and monthly bandwidth?

- In case of exceeding monthly bandwidth, is it possible to purchase extra bandwidth block?

- If there is a need of contact the service provider, would be us or you (Tania) contact them?

- Is it a dedicated, VPS or shared hosting server?

- Is access to the server is ready yet?

- What does the installation disc do?

Meetings on Monday

• 10.30am at the State Library to meet Tania from Vicnet

let me know if you are coming.

• 1.30pm at the Atrium

John has listed what we will be doing in the post before this one.

Brief Requirement Uploaded

Hi guys, i have just uploaded the requirement document in file exchange (blackboard), which we collected from the meeting with client, you guys can have a look at it.
We will print this out and bring it to the meeting with Tanya on monday, 10.30am (is it?) and we can ask her more about the system.

@Andrew : can you prepare the requirement document template, we will be able to put all information in faster later on.

@Kevin: can you print this requirement doc out and bring to the meeting with Tanya.

Everyone wanna come to meet Tanya please confirm and make sure you have prepared some questions to ask her(excluding the information has been provided). Please meet up about half an hour before the meeting, we can arrange who will do what.

After we get the requirement from Tanya, we will make a brief formal requirement document and send it back to Tanya and Grey to confirm, they can add in more things they need, once they confirm, we will produce the requirement document (which will be submitted).

I will produce a draft development plan and bring it to the meeting to morrow on Monday.

Things need to be done next (in meeting on Monday)

• Decide the software development model
• Estimate the scope of the project
• Analyze our gap (knowledge gap, technology gap, skill gap).
• Arrange work for everyone.
• Decide milestone and time frame to finish project
• Prepare legal document
• Others...
  

Thanks guys. Any thought ?

meeting ??

Hi vin, how was the meeting with the client? and would you mind to tell me.. when is our next meeting? thanks...

1st meetup with client

How are things going guys? It was a big and long rain today, isnt it?

I just had a quick glance at the images Kevin sent. Looks like our client is interested in Drupal and WikiMedia. WikiMedia shouldnt be a problem to deal with, but I heard Drupal codes are quite complex.

by kevin

Requirements from Ray uploaded to File exchange in our group page in blackboard.

Printing questions for Wed meeting

If you don't have a printer at home (or if you only came up with a few questions and want to save paper) you can email me the questions before 12noon, I can add them to my list of questions and print them altogether. (since I didn't come up with many new ones either!)

PS. I will send you an email to confirm that I have added it. If you don't receive it, don't assume I have printed it for you.

Meeting Minutes

Marine Observation Database
Team 4
Meeting Minutes

Author(s): Andrew Paton
Reviewed By: Andrew Paton, Chuong Lam

Table of Contents
1. Meeting 1, 12th August 2008. 3
1.1 Meeting Opened – 9.45AM... 3
1.2 Progress Report.. 3
1.3 General Business. 3
1.4 Actions to be Taken.. 3
1.5 Next Meeting – Wednesday 13th August, 2:30PM... 3
1.6 Meeting Adjourned – 10.30AM... 3

2. Meeting 2, 13th August 2008. 4
2.1 Meeting Opened – 2.30PM... 4
2.2 Progress Report.. 4
2.3 General Business. 4
2.4 Actions to be Taken.. 4
2.5 Next Meeting – Monday 18th August, 1.00PM... 4
2.6 Meeting Adjourned – 4.00PM... 4

3. Meeting 3, 18th August 2008. 5
3.1 Meeting Opened – 1.00PM... 5
3.2 Progress Report.. 5
3.3 General Business. 5
3.4 Actions to be Taken.. 5
3.5 Next Meeting – Tuesday 19th August, 3.30PM... 5
3.6 Meeting Adjourned – 2.30PM... 5

1. Meeting 1, 12th August 2008

1.1 Meeting Opened – 9.45AM
The meeting was initiated as part of the Software Team Project unit tutorial.
All team members are in attendance – Kevin, Andrew, Chinh, Chuong, Hai, Vivi.
It has been decided that this will be a regular weekly occurrence for the duration of the project.

1.2 Progress Report
· All material under Blackboard links for the project has been reviewed.
· It was our first meeting in which we introduced ourselves.
· Decided the times in which our team will meet up each week.
· Gather members and client details.
· Informed our team members in what we need to do for our next meeting.

1.3 General Business
· Member's self-introductions, strengths and weaknesses
· Set up multiple communication channels
· distribute tasks to members

1.4 Actions to be Taken
· Prepare your own member skill assessment document, like how you do in your CVs.
· Research, get familiar with software management plans, software development models and work break down structure.
· Contact convenor and our client, which I already did. The convenor has replied and said we should contact our client ASAP. The client suggested to meet at a time which I couldn't make it. I have drafted an email and is going to suggest some other time slots.

1.5 Next Meeting – Wednesday 13th August, 2:30PM
Gather information including:
- Client detail
- Member detail
- Subject convenor detail
- Brief requirement from client
- All legal related documents
- Setup up communication channels including:
- cell phone
- email
- MSN
- Online tool (Blogger)
- Prepare software management plan
- Prepare member skill assessment document
- Analysing and choosing software development model
- Build work breakdown structure for project management
- Build brief work breakdown structure for software development
- Build detailed WBS for software development and follow that structure.

1.6 Meeting Adjourned – 10.30AM

2. Meeting 2, 13th August 2008

2.1 Meeting Opened – 2.30PM
The meeting was initiated as our weekly meeting which we will have every week.
The team members in attendance were Kevin, Andrew, Chuong, Hai, Vivi, Chinh was unable to attend the meeting.

2.2 Progress Report
· Member's self-introductions, discuss strengths and weaknesses
· Set up multiple communication channels
· Distribute tasks to members

2.3 General Business
· Hold meetings often (Mon 13.00, Tue 15.30 we meet Anthony, Wed 14.30 we meet at the tutorial)
· Give warnings to those who don't contribute

2.4 Actions to be Taken
· Prepare your own part of the member skill assessment document, like how you do in your CVs, and post it up here.
· Research, get familiar with software management plans, software development models and work break down structure.
· Write your Personal Log.
· Prepare questions to ask the client.
· Contact convenor and our client, which I already did. The convenor has replied and said we should contact our client ASAP. The client suggested to meet at a time which I couldn't make it (Thur 10.00, he wanted us to meet him at his office in South Yarra. 2-3 of us can go.).

2.5 Next Meeting – Monday 18th August, 1.00PM
· We will decide role for everyone base on the skill assessment document
· Decide the software development model we should use (might be changed according to customer)
· Make questionnaire document for getting requirement
· Prepare all legal related documents.
· Build a brief WBS for project management and software development.
· Decide who will meet the client during the week.

2.6 Meeting Adjourned – 4.00PM

3. Meeting 3, 18th August 2008

3.1 Meeting Opened – 1.00PM
The meeting was initiated as our weekly meeting which we will have every week.
All team members are in attendance – Kevin, Andrew, Chinh, Chuong, Hai, Vivi.

3.2 Progress Report
· We decided on the roles for each team member to do.
· Discussed the questions in which we should ask the client at the interview.
· Complied some questions to ask Buzz about the issues we weren’t sure with.
· Discussed the best time to setup for the interview with client and then emailed him.
· Also further decide what software tool we are going to use for our project.

3.3 General Business
· It was our third meeting for the project and now we are slowing developing the project and gathering all the information together to complete the project.
· Looks like we will be having our first interview with the client this Thursday 21st August and Kevin, John and Myself will be attending the interview.
· We have sorted team responsibilities and requirements needed to have a successful project.

3.4 Actions to be Taken
· Kevin will email the client to confirm time and date for interview and type up questions to ask buzz about our project for Tuesday meeting.
· Hai will finalize our team responsibilities for each other and type it out in a word format.
· John will type up questions to ask the client at the interview
· Vivi will do further research on software and management tools to use.
· Gu to compile his skills assessment
· Andrew to print off the legal form for everyone to sign. Also to compile the minutes up together in a formal style.

3.5 Next Meeting – Tuesday 19th August, 3.30PM
· Finalize questions for interview
· Have the software model ready
· Decide task in meeting with client
· Build brief WBS for the project management
· Build brief WBS for software development

3.6 Meeting Adjourned – 2.30PM

Team member's role

Hey guys, this is the member role. I have drawn it by word so it's not really nice :-D

Download it here : http://docs.google.com/Doc?id=d7ns5ck_0ckwpswgc

Team member's role request

- Kevin, can you put the member's role graph on the blog, just like you put the google map, it would be very easy to view

- Andrew, when you do the main documents, not the meeting minutes, can you do it on google doc and share for everyone, just for everyone to have a look at it

Many thanks guys.

My personal skills & abilities

This is a short description of my skills and abilities relevant to the project:

I. Server deployment, configuration, administration and maintainance

The project will be likely hosted in server running Unix or Linux, which Im quite familiar with. Coming from Unix background, so managing Unix machine (especially FreeBSD), for me, shouldnt be an issue. Linux differs from Unix, but if the project server does run Linux, it shouldnt be problematic to me, either.

0. Web Server:

Definitely the project requires web server to publish the content. I have been having a few chances to manage some web servers, running Apache of course. One website that Im currently administering is:

https://unix-kernel.org

1. Database Server:

It has been 3 years since I took the database subject, and I assume all my database knowledge have gone now. Still, long time ago I managed to install, config a MySQL server and now I still maintain it. Not the best database admin though, but if there is a need for database server admin, it shouldnt be a big problem.

2. DNS Server:

The client may need to create some sub domain names for better management. Im currently managing a BIND server, so Im quite familiar with DNS.

3. SSH & Command Line Interface

If access to the server given to us, the chance is we will need to use SSH. Its a complicated world and if you know CLI, probably I have nothing to say further here.

II. Programming

I study C and I should have mastered it by now, but reality isnt always as good as you expected. Im not quite confident if the application is big (also because Im quite busy), but small one is fine to me. I also have experience with shell script, which is a must for an sys admin, especially in *nix environment. The client may need some applications processing a number of tasks, then return the output to the web interface. This is where C and shell script come, as back-end application, the front-end application, is the website.

III. Security

For non-technical minded people, security is normally overlooked, and it would be the case of our situation. Not quite sure if Im qualified to be security guy here, but it shouldnt be any problem for me to handle this job.

IV. Documentation

The heading says it all.

First meeting with client

Time: Thursday 3pm (we can arrive 5 mins early, meet at the entrance and walk in together)
Address: 302/ 9 Claremont St, South Yarra, VIC 3141, Australia
Attendant: Andrew (asking questions), Kevin (asking questions), John (note taking)
Dress code: semi-formal

Questions for Buzz

1. Which software model to use? Royce's Waterfall? Agile Software Development? Extreme Programming?
   
2. Can the project's requirements be changed once the project has started (after week3)?
3. Check if the questions we have for the client is appropriate. Did we miss anything?
   
4. Check our members' roles
   

Proposed questions for the first meeting with Client

Following are some question chosen for the first meeting with client; we will consult with Buzz to choose the most appropriate one only: (questions might be changed)

• Do you mind if we make a recording of this interview?
• Can you tell us a little bit more about your organization which could relate to the project?
• The system developed from this project will be use for internal purpose or external purpose (will it be used by public) combined with next question
• Who are users of the new system? Internal? External? Both?
• Tell us briefly what do you want us to build? (website? application?)
• How does the current system work?
• Are there parts of the system that you wish to keep?
• What part(s) of the current system do you find obsolete?
• What type of improvements you would like to see in the system?
• Specify the basic functions the new system should have (manage data, search data, manage user...)
• Specify all the extra functions the new system should have (run fastly, simple interface...)
• Do you have any technical document of the current system that we can inspect?
• What is the scope of the new system, what you do not want in the new system? (what we don’t have to build?)
• How long do you expect the system to be completed Time frame is already set. I think we should be advising him the time frame not him.
• Can we contact you in case we need more information or do you have any dedicated person to work with us in case we need?

Please note that all other questions will not be thrown away, we still keep them for second meeting with client.

edited by Kevin

Meeting time and location (18/08/2008)

We have regular meeting on 18/08/2008

Time: 13.00pm
Location: meet at Attrium --> then choose other place to sit

Please be there on time.

some questions for our client (brief questions)

hi guys, here is some questions that pop up in my mind. they're all about the design

- What do you want your site layout to look like?
- What color pattern do you want ? (the marine style or any fancy style :-)
- Do you want your database to be public? or visitors must register before they can looking for data.

Kevin's Questions
- Is there a SQL server running? If so, which one?
- Do you want a complete redesign of the homepage as well as the database?
- Do you want something like this database form?
http://www.cisanctuary.org/mammals/index.html


John's question (might be changed)
- Tell us briefly what do you want us to build?
- Specify all the basic functions the system should have (manage data, search data, manage user...)
- Specify all the extra functions the system should have (run fastly, simple interface...)
- Will the new system have to work with current system?
- Can you give us some more information about the current system?
- Do you have any technical document of the current system that we can inspect
- What is the scope of the new system, what you do not want in the new system (what we dont have to build).
- How long do you expect the system to be completed
- During the development process, we might need to corporate with you or your people in order to build a more reliable and accurate system, we might need to create some sort of communication between us such as exchanging Email, meeting, blog. We hope you can keep in touch with us.

Chinh's Questions (added by kevin)

- Questions
# Comments


- To ensure we are on the right track, could you spare some time each week to have a look at our weekly work?

# "Must be compatible with Vicnet resources"
- Could you elaborate a little bit more on that?

# when asking, give a few words about the terms static and dynamic
- Will the website be static or dynamic content?

# The size of the database has a impact on the server and the database application's performance.
- As far as the database concerned, do you have a rough number of users in mind?

# Not a fan of web editor, but if we are too busy with other things, web editor would be an option
- Does the website has to be hand coded, or could be built with a web editor like Dreamweaver?

# The client is likely to be interested in rich web content, e.g. flash (not an advocate, though)
- Within the web site, do you require any special element/effect?

# He might have a fav website in mind, and it would give us a clear idea what he really wants, no harm to ask
- Do you have any website that you wish to show us as an example?

- Where would be the server hosted? Do we have access to that server or all work will be submitted to you?

# Now, stuff for the paranoid people
- In term of security, do you have any particular requirement? (viewable for user only, password authentication, sensitive info must be transmitted over secure channel)

Wednesday Weekly Meeting - 13-8-2008 @ 14.30-16.00

Members who did not attend:

• Chinh Pham

What we did:

• Member's self-introductions, discuss strengths and weaknesses
• Set up multiple communication channels
• Distribute tasks to members

Decisions made:

• Hold meetings often (Mon 13.00, Tue 15.30 we meet Anthony, Wed 14.30 we meet at the tutorial)
• Give warnings to those who don't contribute
  

Tasks:

• Prepare your own part of the member skill assessment document, like how you do in your CVs, and post it up here.
  
• Research, get familiar with software management plans, software development models and work break down structure.
• Write your Personal Log.
  
• Prepare questions to ask the client.
  
• Contact convenor and our client, which I already did. The convenor has replied and said we should contact our client ASAP. The client suggested to meet at a time which I couldn't make it (Thur 10.00, he wanted us to meet him at his office in South Yarra. 2-3 of us can go.). I have drafted an email and is going to suggest some other time slots as follows:

I am delighted to have the chance of meeting you next week. However due to my lecture on Thursday morning, I wonder if our meeting could be changed to either Wednesday morning, Thursday afternoon, or any time on Friday at your kind preference.

Please comment if I left out anything, or you have any concern :D

Next meeting (Mon 13.00) we will do following task:

• We will decide role for everyone base on the skill assessment document
• Decide the software development model we should use (might be changed according to customer)
• Make questionaire document for getting requirement
  
• Prepare all legal related documents.
• Build a brief WBS for project management and software development.
• Decide who will meet the client during the week.
  

useful websites for writing meeting minutes:
http://www.effectivemeetings.com/meetingbasics/minutes.asp
http://careerplanning.about.com/cs/communication/a/minutes.htm
http://en.wikipedia.org/wiki/Minutes

Meeting minute request

Kevin, can you put the meeting minute on the blog for everyone to see it, and the task list as well so everyone will know what have to be prepared before next meeting

Opening ceremony - Welcome all team members

Hi guys, welcome to private blog of Swinburne Team 4 - Final Project

- This blog will mainly host meeting minute and task list for all members in the team.
- You can subscribed to this blog feed in order to get latest update information
- Everyone Please keep in touch with other members, if we do not receive any response from any particular member for 5 straight days, we need explanation or you shall be out.

Hope the project will go on well. Thanks
Chuong Lam (John)