Tutorial 2: To Identify the main stakeholders for the tutorial task 1
1. Users
2. Client Management
3. Trainers
4. Technical Support
5. Premises Management
6. Catering Service
7. Document Services
In the meeting, we have reviewed the draft copies of our software project plan. We have also look at our various deliverables like ER-diagram and data dictionary. We have also discussed on the use cases and functional/non-functional requirements. During the meeting, tasks has been allocated to each team member for the coming 2 weeks as we will not be having our weekly meeting during chinece new year.
Below is the minutes for the meeting:
http://www.freewebs.com/holtz311/meeting20080131v02.pdf
Thursday, January 31, 2008
Tutorial 2 and 3rd meeting
Thursday, January 24, 2008
Tutorial 1 and 2nd Meeting on 24 Jan 08
Tutorial 1: In this tutorial we discussed on the various Software Project Plan, below are our findings.
Rspa
Pros
1. Simple and generic style
Cons
1. No example to follow
2. Too generic and vague description
Dsdm
Pros
1. Professional style
2. Examples given
Cons
1. Too detail and complex
2. Takes time to understand and comprehend
UPEDU
Pros
1. Easy to understand and comprehend
Cons
1. Moderate detail
Software Project Plan from Chair of Software Engineering at ETH Zurich, Switzerland
Pros
1. Covers all managerial aspects of a project
2. Easy to understand
3. Useful help given
Cons
1. Too much detail
Conclusion: After some discussion, we have decide to adopt the last option which is the project plan from Chair of Software Engineering at ETH Zurich, Switzerland. Main reason is that it allows us to generate a comprehensive report in a short time constraint.
In the meeting, we have reviewed the draft copies of our software project plan and software requirement spec. We have also started discussion on our design specs.
Below is the minutes for the meeting:
http://www.freewebs.com/holtz311/meeting20080124v02.pdf
Rspa
Pros
1. Simple and generic style
Cons
1. No example to follow
2. Too generic and vague description
Dsdm
Pros
1. Professional style
2. Examples given
Cons
1. Too detail and complex
2. Takes time to understand and comprehend
UPEDU
Pros
1. Easy to understand and comprehend
Cons
1. Moderate detail
Software Project Plan from Chair of Software Engineering at ETH Zurich, Switzerland
Pros
1. Covers all managerial aspects of a project
2. Easy to understand
3. Useful help given
Cons
1. Too much detail
Conclusion: After some discussion, we have decide to adopt the last option which is the project plan from Chair of Software Engineering at ETH Zurich, Switzerland. Main reason is that it allows us to generate a comprehensive report in a short time constraint.
In the meeting, we have reviewed the draft copies of our software project plan and software requirement spec. We have also started discussion on our design specs.
Below is the minutes for the meeting:
http://www.freewebs.com/holtz311/meeting20080124v02.pdf
First Meeting on 19 Jan 2008
Team Members:
S8539305G Ho Wei Zhe
S8337246Z Lim Yong Keong
S8437490C Zhuo Senxian
S8321012E Oh Chin Hock
S8530018J Tan Boon Chin
Our first meeting was conducted on 19 Jan 2008, we first formed our group and sit down to get to know each other. HOLTZ was agreed as our company name, it was formed using the first letter of all our sir names (Ho, Oh, Lim, Tan & Zhuo) .
Our discussed on the roles of each member and came out with the below team.
Project Manager : Ho Wei Zhe
System Requirement/Change Management Lead: Lim Yong Keong
Technical Development/System Architect Design/Quality Assurance Lead : Zhuo Senxian
Graphical Interface/Configuration Lead: Oh Chin Hock
System Testing/Validation Lead: Tan Boon Chin
During the meeting, we went through the case scenario together and came out with a project strategy.
Below file is our minutes of meeting for 19 Jan 2008
http://www.freewebs.com/holtz311/meeting20080119v02.pdf
S8539305G Ho Wei Zhe
S8337246Z Lim Yong Keong
S8437490C Zhuo Senxian
S8321012E Oh Chin Hock
S8530018J Tan Boon Chin
Our first meeting was conducted on 19 Jan 2008, we first formed our group and sit down to get to know each other. HOLTZ was agreed as our company name, it was formed using the first letter of all our sir names (Ho, Oh, Lim, Tan & Zhuo) .
Our discussed on the roles of each member and came out with the below team.
Project Manager : Ho Wei Zhe
System Requirement/Change Management Lead: Lim Yong Keong
Technical Development/System Architect Design/Quality Assurance Lead : Zhuo Senxian
Graphical Interface/Configuration Lead: Oh Chin Hock
System Testing/Validation Lead: Tan Boon Chin
During the meeting, we went through the case scenario together and came out with a project strategy.
Below file is our minutes of meeting for 19 Jan 2008
http://www.freewebs.com/holtz311/meeting20080119v02.pdf
Subscribe to:
Posts (Atom)