FT2283 Team Software Development Project

1
FT228-3Team Software Development Project

• Ronan Bradley
• Brian Mac Namee

Module Web Page http//www.comp.dit.ie/bmacnamee/
tsdp.htm
2
Aims of this module

• This module offers the students the opportunity
  to use the knowledge and skills they have
  developed over the previous stages in the
  development of a software development
  application. The project is a team project
  requiring the students to collaborate and
  organise themselves in a group to achieve the
  module objectives.
• The module aims to familiarise students with a
  range of skills and knowledge necessary, to take
  a software application through its development
  life cycle.

3
Learning outcomes

• Demonstrate group interaction
• Implement a project design in an appropriate
  format from a requirements specification
• Demonstrate a choice of appropriate technology
• Determine roles within the project
• Implement role functionality
• Determine group integration.
• Develop presentation skills

4
Grading

• A students final mark will be composed of 40
  of their group mark and 60 of their individual
  mark.

5
Phase I

• The class will be split into groups of 3 or 4
  students.
• There are 8 projects
• Scrabble
• Monopoly
• Sopwith Redux
• Multi-User Calendar
• Hotel Booking System
• NCT Management System
• Uber-Vision DVD Rental Management System
• Surgery Appointment Management System

6
Phase I Win the business

• Each group can pick any project
• However only 1 group will be allocated a project
• Submit by end of 6th Feb a 1 page description of
  the approach you would take if allocated your
  requested project.
• Also submit a second choice.
• The lecturers will then allocate the project to
  groups on the basis of these descriptions.
• Allocations will be announced at the lab on the
  7th Feb.

7
Schedule

• Week 4 (starting 19/2/07)
• Group submission of a software design document
• Group presentation of the software design to the
  class and lecturers followed by questions from
  the lecturers (during lab session on Wednesday)
• Week 12 (starting 30/4/07)
• Group submission of final report detailing the
  application developed
• Individual submission of project journal
• Group presentation and demo of developed
  application to class and lecturers followed by
  questions from lecturers (during lab session on
  Wednesday)
• Individual interview of each student within a
  group by the lecturer (during week)

8
Points to note I

• We are your customer
• Deliver what the customer wants not necessarily
  what you want.
• If the project doesnt do what was agreed the
  project will be canned.
• You need to keep your customer happy
• Agree what you will deliver, communicate it to
  your customer, manage expectations!
• It is better to deliver a completed average
  project than not deliver a brilliant project.
• This project has an absolute deadline which
  cannot slip
• Unlike most commercial projects!

9
Points to note II

• This is a team based project
• Roles must be allocated across the team
• Be realistic about strengths not everybody has
  to be a superstar coder or design guru.
• Using the project plan document create a plan for
  the entire project.
• Track changes as you go through the project.
• Non-performers drag down the team.
• There is an individual component to the grading
• There are no extra marks for monopolising the
  project.
• Keep a Project Journal every week
• A list of tasks completed with brief description
  and comments on what has been learnt.

10
Open Source, design patterns

• It is normal practise in the software industry to
  use Open Source projects, design patterns etc.
• However, ensure that
• Verify it is available for use
• Just because it is on the web doesnt mean you
  can use it.
• You fully document both the components of the
  project that you have used and the components
  that you have written yourselves including
• Design Patterns
• Code
• User interfaces