HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2008T2G4 Rojak/Minutes"

From IS480
Jump to navigation Jump to search
Line 34: Line 34:
 
##Wee Kee
 
##Wee Kee
 
### To make arrangements for the FYP server and lab access, and for SVN accounts.
 
### To make arrangements for the FYP server and lab access, and for SVN accounts.
 
+
<br />
 
=== Agenda - Meeting 2 (Group Meeting) ===
 
=== Agenda - Meeting 2 (Group Meeting) ===
 
Timing: Thursday 2PM, 15th Jan 2009<br />
 
Timing: Thursday 2PM, 15th Jan 2009<br />
Line 46: Line 46:
 
#Review and discussion of the Project Proposal and feedback provided
 
#Review and discussion of the Project Proposal and feedback provided
 
#Review and discussion of work plan for Week 3
 
#Review and discussion of work plan for Week 3
 +
<br />
  
 
=== Minutes - Meeting 2 (Group Meeting) ===
 
=== Minutes - Meeting 2 (Group Meeting) ===
Line 85: Line 86:
 
### Team logo, and project logo (Zixian)
 
### Team logo, and project logo (Zixian)
 
#### Project logo to follow client's colour scheme (burgundy)
 
#### Project logo to follow client's colour scheme (burgundy)
 +
<br />
  
 
=== Minutes - Meeting 3 (Group Meeting) ===
 
=== Minutes - Meeting 3 (Group Meeting) ===

Revision as of 12:52, 20 January 2009

Meeting Minutes

Meeting 1 (Client Meeting)

Meeting 1

DateJanuary 8, 2009 Thursday 6PM
VenueMeemo Pte Ltd, 59A Haji Lane
Duration 1 hr
Meeting AttendeesTeam Rojak
Wee Kee
Zuhairi
Ricky
Hafiz
Meemo Pte Ltd
Kevin Cheong
Toh Lay Ling
  1. Discussion on IP issues surrounding the project
    1. Meemo understood that the project will be built on Apache OFBiz, which is licensed under the Apache License, available at http://www.apache.org/licenses/LICENSE-2.0.html
    2. Meemo understood that it owns the rights only to Derivative Product (i.e. codes deriving from the project) and not OFBiz which the project is built on, subjected to terms in the below-mentioned MOU.
    3. Meemo was explained and understood the terms of the MOU regarding IP rights. The MOU will be prepared and signed at the next meeting.
  2. Administrative matters
    1. Meemo highlighted that it will liaise with only 1 member of the team to simplify communications.
    2. Meemo also hightlighted that both Layling and Kevin would be away on a business trip next Monday to Friday.
  3. Requirements and Process Flow
    1. Meemo was shown and accepted the list of requirements.
    2. Meemo made some slight changes to the process flow, but has given the go-ahead to work on the mock-up based on the process flow.
    3. Meemo will look through the mock-up of the website when they are back from their business trip.
  4. Work structure for the following week
    1. Ricky and Hafiz
      1. Deploy a working local copy of OFBiz.
      2. Provide recommendations on software tools for development.
    2. Wee Kee, Zixian and Zuhairi
      1. Complete the mock-up for presentation to Meemo.
    3. Wee Kee
      1. To make arrangements for the FYP server and lab access, and for SVN accounts.


Agenda - Meeting 2 (Group Meeting)

Timing: Thursday 2PM, 15th Jan 2009
Venue: SIS Level 3 Benches
Attendees: Wee Kee, Ricky, Hafiz, Zuhairi, Zixian

Agenda

  1. Review and status updates for Week 2
    1. Updates on the OFBiz deployment
    2. Updates on the mock-up and further discussion if required
  2. Review and discussion of the Project Proposal and feedback provided
  3. Review and discussion of work plan for Week 3


Minutes - Meeting 2 (Group Meeting)

Meeting 2

DateJanuary 15, 2009 Thursday 2PM
VenueSIS Level 3 Benches
Duration 1 hr
Meeting AttendeesTeam Rojak
Wee Kee
Zuhairi
Ricky
Hafiz
Zixian
  1. Review and status updates for Week 2
    1. Updates on the OFBiz deployment
      1. Some minor issues with deployment due to issues with SVN codes
      2. Resolved: We'll be using stable release instead of the SVN builds which was recommended by the book
      3. Work Required:A working copy to be up by next meeting (Monday)
    1. Updates on the mock-up and further discussion if required
      1. To check with meemo how they want the quotation to be sent to the client by reseller; whether direct, or sent to reseller, who will send it out-of-system. (email etc)
      2. Work Required:To have the softcopy sent by this weekend
  1. Review and discussion of the Project Proposal and feedback provided
    1. To add a page for Learning Outcomes, update it as we learn something to facilitate compilation in mid-term and final report
    2. Not to crash the project so early, but increasing meeting to twice weekly. Meeting for combined will be 10AM Monday, or Sunday. in Sub-teams, will be either monday or tuesday. This will improve the efficiency. If progress is good, the project timeline will be crashed and functionalities/scope increased. There is increased risk of delay if we commit to a larger project scope too early before we fully understand software development using OFBiz.
    3. WRT unclear scope, scope is clarfied in the other documents, i.e. mock-up and process flow which will be presented to the client. However, we do note that use-case would be a good supplementary to the stated list of requirements, and this would be presented to the client as well.
  1. Review and discussion of work plan for Week 3
    1. Meet on Mon morning 11AM for short updates
      1. Zixian will be away on sailing competition
      2. Discussion on the entities (attributes, ACL)
      3. Finalize on the IDE
    2. Work to be completed before that
      1. Working copy of OFBiz (Ricky and Hafiz)
      2. Softcopy of mockup to be completed (Zuhairi)
      3. Team logo, and project logo (Zixian)
        1. Project logo to follow client's colour scheme (burgundy)


Minutes - Meeting 3 (Group Meeting)

Meeting 3

DateJanuary 19, 2009 Monday 11AM
VenueSIS Level 3 Benches
Duration 1 hr
Meeting AttendeesTeam Rojak
Wee Kee
Zuhairi
Ricky
Hafiz
  1. Review and status updates for Week 2-2
    1. OFBiz deployment
      1. Deployment successful and running
      2. To be shifted to production machine instead of local computer once server access is provided
      3. Work Required: To configure the basic functionalities for Meemo
    2. Softcopy of Mockup
      1. Reviewed and accepted by team
      2. Work RequiredTo be presented to client in the next meeting with client
    3. Discussion on data entities
      1. Recognized the main entities of importance for current phase as Quotation, Items list in Quotation / Items, Users (Customer, Reseller, Meemo etc), Supplier, Payroll.
      2. To use a single list of items, with Access Control on individual items rather than 3 list of items, with AC on each list for Quotation
      3. Work Required;To review the various entities (depicted in OFBiz in XML), draw up the ER diagram and suggest required changes to the entities.
  1. Workplan for week 3
    1. Configure OFBiz's basic functionalities (Wee Kee)
    2. Discuss Mock-up with Client (Wee Kee)
    3. Supplier and Payroll Entities (Hafiz)
    4. Users (Zuhairi)
    5. Quotation and Items (Ricky)