Tuesday 16 October 2007
Welcome
Hello, everyone, please be familar with this blog and know how to use it. Please put anything about our project here, even it is not important now, because it may be usefull later. I will go out this afternoon and evening, so any problem or suggestion, please just post here, I will fix later.
Liu Bo
I put the link of Liubo Game here, you can check:
Game Rules: http://history.chess.free.fr/liubo-rules.htm
Game history: http://history.chess.free.fr/liubo.htm
Info in Wikipedia: http://en.wikipedia.org/wiki/Liubo
Hope it will be internesting.
Game Rules: http://history.chess.free.fr/liubo-rules.htm
Game history: http://history.chess.free.fr/liubo.htm
Info in Wikipedia: http://en.wikipedia.org/wiki/Liubo
Hope it will be internesting.
Tuesday 9 October 2007
Notes of Student Handbook
Important Day
Equipment requests 26 October until 30 November 2007
Interim reports due Friday 7 December 2007
Final reports and software due Friday 25 April 2008
Open Day Wednesday 30 April 2008
Presentation Day Friday 2 May 2008
Groups
Select group leader
the project is "owned" by the group as a whole
Supervisors
the role of the supervisor is to monitor the group
Groups meet with their supervisor once a week
Project Descriptions
Lectures
Meetings
one formal meeting per week with their supervisor present: The weekly meetings with the supervisor will normally be held in his or her office, and should last 30 minutes. The purpose of these meetings is for the group to report on progress since the last meeting, discuss any problems that have arisen, and plan the work that will be carried out by each member prior to the next meeting. These meetings should be quite formal in nature, with a chairperson (who runs the meeting) and a secretary (who records the progress of the meeting and produces "minutes").
informal meeting
Equipment
need to complete an equipment request form detailing the hardware and software requirements for the project. To confirm that the requests are appropriate, this form must be signed by the project supervisor.
Assessment
Collective Group Mark:
Interim Group Report 20%
Final Group Report 30%
Software 20%
Open Day 15%
Presentation Day 15%
Peer assessment :
Individual Mark for Group Work 80%
Individual Report 20%
Most tasks are marked by the supervisor and a second marker. The exceptions are the Interim Report, which is marked by the supervisor only, the Open Day, where all members of academic staff are invited to mark the displays in addition to the supervisor and second marker, and the Presentation Day, where the presentations usually are marked by a third member of staff in addition to the supervisor and second marker.
Assessment Guidelines
Exceptional (90-100%) The reports and software should exhibit all the characteristics of an Excellent grade. Additionally, the project should have been carried out in an utmost systematic and professional manner, as evidenced by a problem analysis and subsequent requirements specification of stunning clarity and insight, a system design of highest possible quality that manifestly meets all requirements and given at a level of precision and detail that directly could be translated into an implementation, an implementation of highest possible quality and completeness whose conformance to the original specification has been verified rigorously, and impeccable project management in terms of planning, workload management, meeting deadlines, making the best possible use of each team-member's skills and strengths, and with absolutely minimal (technical or otherwise) guidance from the supervisor. .
The Open Day is marked primarily on the quality of the display itself and the professionalism of those manning the stands (attitude, ability to explain, demonstrate, answer questions etc.), not on the quality of the project itself. Similarly, the Presentation Day is marked primarily on the quality of the presentation and how the group handles questions and answers
The Individual Reports are primarily marked on the quality of the reflective statement and on the overall qualities as a report, such as writing, structure, typesetting. The contributions of an individual as such are is not what is being marked: peer assessment takes care of that. But showing a clear understanding of ones role in the project and the true value of ones contribution is important.
Peer Assessment
* Research and Information gathering
* Creative input
* Co-operation within group
* Communication within group
* Quality of individual contributions
* Attendance at meetings
Interim Group Report
4000-5000 words (around 12-15 pages; excluding any appendices)
* Updated and expanded description of the problem to be solved.
* Background information and research such as
o survey of any existing systems that address similar problems
o results of any market research conducted
o results of technical research into suitable platforms, tools, technologies, algorithms, data structures, etc.
* Requirements specification for the system to be built (agreed between the group and supervisor).
* Initial design of the proposed system and its user interface.
* Record of key implementation decisions, such as programming languages, operating systems, computers, and any additional software and hardware to be used, along with reasons for those decisions.
* Results of any initial implementation steps/prototyping.
* Discussion of any problems encountered so far.
* Time plan for the project.
submitted in PDF format
front page including:
* The text "G52GRP Interim Group Report"
* Project title
* Date
* Group Id
* Names and School of CS usernames of all group members
* Name of supervisor
Final Group Report
7000-8000 words (around 20-25 pages; excluding any appendices)
* Updated design of the system and its user interface.
* Discussion on the implementation and testing of the system. This must include a list of all major system components, which of these were written by the group and where the others come from, and an overview of the developed source code hierarchy.
* Summary of what was achieved, referring to the stated requirements.
* Reflective comments on the success of the project, both from a technical and a project management perspective.
* An appendix giving a description of how the developed system was tested (test cases, example outcomes, etc.)
A user-manual (if appropriate) should be included as an appendix.
front page
Software
source code
zip archive or a gzipped tar archive
All source code should be properly attributed
Assessed aspects:
* Functionality and features
* How well the developed software actually works
* The size and difficulty level of the addressed problem(s)
* The technical sophistication of the developed software
* How well the software is written (architecture, proper modularisation, proper abstractions, naming conventions, layout, documentation, etc.)
* Quality of the testing
Individual Report
2000-2500 words (around 6-8 pages
Submission of Reports and Software
Each deliverable should be handed in no later than 3:30 pm on the due date. Printed copies should be handed in to the School Office. Electronic copies are handed in using the School's CW coursework hand-in system.
Presentation Day
performed by the best speaker in the group
Golden Rules
Work consistently throughout the project
Make sure that you have enough to do.
Don't leave the programming until too late.
Don't think for a second that you can do the writeup in just a few days.
Keep track of everyone's progress.
Take the meetings seriously.
Keep good records of your meetings.
Equipment requests 26 October until 30 November 2007
Interim reports due Friday 7 December 2007
Final reports and software due Friday 25 April 2008
Open Day Wednesday 30 April 2008
Presentation Day Friday 2 May 2008
Groups
Select group leader
the project is "owned" by the group as a whole
Supervisors
the role of the supervisor is to monitor the group
Groups meet with their supervisor once a week
Project Descriptions
Lectures
Meetings
one formal meeting per week with their supervisor present: The weekly meetings with the supervisor will normally be held in his or her office, and should last 30 minutes. The purpose of these meetings is for the group to report on progress since the last meeting, discuss any problems that have arisen, and plan the work that will be carried out by each member prior to the next meeting. These meetings should be quite formal in nature, with a chairperson (who runs the meeting) and a secretary (who records the progress of the meeting and produces "minutes").
informal meeting
Equipment
need to complete an equipment request form detailing the hardware and software requirements for the project. To confirm that the requests are appropriate, this form must be signed by the project supervisor.
Assessment
Collective Group Mark:
Interim Group Report 20%
Final Group Report 30%
Software 20%
Open Day 15%
Presentation Day 15%
Peer assessment :
Individual Mark for Group Work 80%
Individual Report 20%
Most tasks are marked by the supervisor and a second marker. The exceptions are the Interim Report, which is marked by the supervisor only, the Open Day, where all members of academic staff are invited to mark the displays in addition to the supervisor and second marker, and the Presentation Day, where the presentations usually are marked by a third member of staff in addition to the supervisor and second marker.
Assessment Guidelines
Exceptional (90-100%) The reports and software should exhibit all the characteristics of an Excellent grade. Additionally, the project should have been carried out in an utmost systematic and professional manner, as evidenced by a problem analysis and subsequent requirements specification of stunning clarity and insight, a system design of highest possible quality that manifestly meets all requirements and given at a level of precision and detail that directly could be translated into an implementation, an implementation of highest possible quality and completeness whose conformance to the original specification has been verified rigorously, and impeccable project management in terms of planning, workload management, meeting deadlines, making the best possible use of each team-member's skills and strengths, and with absolutely minimal (technical or otherwise) guidance from the supervisor. .
The Open Day is marked primarily on the quality of the display itself and the professionalism of those manning the stands (attitude, ability to explain, demonstrate, answer questions etc.), not on the quality of the project itself. Similarly, the Presentation Day is marked primarily on the quality of the presentation and how the group handles questions and answers
The Individual Reports are primarily marked on the quality of the reflective statement and on the overall qualities as a report, such as writing, structure, typesetting. The contributions of an individual as such are is not what is being marked: peer assessment takes care of that. But showing a clear understanding of ones role in the project and the true value of ones contribution is important.
Peer Assessment
* Research and Information gathering
* Creative input
* Co-operation within group
* Communication within group
* Quality of individual contributions
* Attendance at meetings
Interim Group Report
4000-5000 words (around 12-15 pages; excluding any appendices)
* Updated and expanded description of the problem to be solved.
* Background information and research such as
o survey of any existing systems that address similar problems
o results of any market research conducted
o results of technical research into suitable platforms, tools, technologies, algorithms, data structures, etc.
* Requirements specification for the system to be built (agreed between the group and supervisor).
* Initial design of the proposed system and its user interface.
* Record of key implementation decisions, such as programming languages, operating systems, computers, and any additional software and hardware to be used, along with reasons for those decisions.
* Results of any initial implementation steps/prototyping.
* Discussion of any problems encountered so far.
* Time plan for the project.
submitted in PDF format
front page including:
* The text "G52GRP Interim Group Report"
* Project title
* Date
* Group Id
* Names and School of CS usernames of all group members
* Name of supervisor
Final Group Report
7000-8000 words (around 20-25 pages; excluding any appendices)
* Updated design of the system and its user interface.
* Discussion on the implementation and testing of the system. This must include a list of all major system components, which of these were written by the group and where the others come from, and an overview of the developed source code hierarchy.
* Summary of what was achieved, referring to the stated requirements.
* Reflective comments on the success of the project, both from a technical and a project management perspective.
* An appendix giving a description of how the developed system was tested (test cases, example outcomes, etc.)
A user-manual (if appropriate) should be included as an appendix.
front page
Software
source code
zip archive or a gzipped tar archive
All source code should be properly attributed
Assessed aspects:
* Functionality and features
* How well the developed software actually works
* The size and difficulty level of the addressed problem(s)
* The technical sophistication of the developed software
* How well the software is written (architecture, proper modularisation, proper abstractions, naming conventions, layout, documentation, etc.)
* Quality of the testing
Individual Report
2000-2500 words (around 6-8 pages
Submission of Reports and Software
Each deliverable should be handed in no later than 3:30 pm on the due date. Printed copies should be handed in to the School Office. Electronic copies are handed in using the School's CW coursework hand-in system.
Presentation Day
performed by the best speaker in the group
Golden Rules
Work consistently throughout the project
Make sure that you have enough to do.
Don't leave the programming until too late.
Don't think for a second that you can do the writeup in just a few days.
Keep track of everyone's progress.
Take the meetings seriously.
Keep good records of your meetings.
Monday 8 October 2007
G52GRP Software Engineering Group Project 2007-2008
Overview
TSG Group Project
Game Theory
- Module convenor: Dr N H Nilsson
- Syllabus: G52GRP
- Method and frequency of class:
- A number of support lectures, see below. Fridays 11.00-12.00, LT2, the Exchange
- Two group meetings per week, of which one is formal with the supervisor
- Project work
TSG Group Project
Game Theory
Subscribe to:
Posts (Atom)