Internal DT211 Module Descriptor

 
DT211 Home
Stage 1
Stage 2 
Stage 3
 Full-time 
Stage 3
 Internship
Stage 4
 Full-time 
Stage 4 
Internship  
School of 
Computing 
DIT
   
 

Stage 3 Project

Pre-Requisite Modules Co-Requisite Modules ECTS Credits Module Code

PROG2101

SENG2201

SENG2101

TECH2401

TECH2101

BUSN1501

PROG3101

TECH3301

SENG3201

TECH3302
10 PROJ3501

Author:

Damian Bourke

Description:

Previously students will have separately demonstrated an understanding and proficiency in the development of software using a variety of development tools, languages, technologies and development methodologies and techniques.  This module is intended to allow the student to demonstrate this understanding and proficiency in a single body of work.  It is an important piece of work that is essential for students intending to graduate after stage three.

Aim:

The aim of this module is to produce an individual piece of work comprising a substantial software system using the skills they have developed from previous modules to research, design and implement software systems.

Learning Outcomes:

On completion of this module the student will be able to demonstrate an ability to:

  • Produce a detailed project proposal.
  • Undertake research to determine the most appropriate technologies, platforms and methodology for developing their proposed system.
  • Review existing systems and to produce end-user specifications/requirements.
  • Fully design and implement a complete software system.
  • Formally document the entire process from inception to completion.
  • Present their solution and research findings to a select group of staff members.
  • Critically analyze their work.

Learning and Teaching Methods

Each student is required to define their project area and to produce a formal project proposal at the outset.  If the proposal is deemed to be of a sufficient standard the student will be allocated a supervisor whom they will meet for an allocated period of time each week.

An Interim Report is required to be submitted by the student upon completion of the research/analysis and design phases of the project.  The findings of this Interim Report must be presented to a panel of internal examiners.  Likewise upon completion of the project the student is required to submit a finalised project manual documenting the entire project process including relevant research findings and the main project conclusions.  The student is also required to submit the final system software.  The findings of this Final Project Manual and the implementation of the software solution must be presented to a panel of internal examiners.

The students are provided with on-line access to detailed guidelines on the project process.  These guidelines detail the requirements of the project in terms of the project content and deliverables and they also provide guidance on the content and format of the Interim Report and Final Project Manual.  The guidelines also explain the roles of the key stakeholders including the student, the supervisor etc. 

The submission requirements and submission dates of key project deliverables will be outlined on the relevant projects webpage together with the associated penalties.

 

Module Content

As prescribed by the student’s chosen project topic.

Module Assessment

The progress of the student is monitored throughout the year by the supervisor. Students are expected to maintain a diary of their meetings with the supervisor and to submit reports on their progress on a weekly basis.

The Interim Report will be assessed during Semester I in accordance with the following criteria:

  1. The Report Style  - The quality of the Interim Report in terms of its lay-out, structure, writing style, correctness and referencing.
  2. Research and Understanding - The extent of the student’s background research and overall understanding of the project subject area and their ability to choose appropriate technologies for the final implementation.  
  3. Design Quality - The quality of the design of the system to be implemented.
  4. Complexity and Difficulty – The complexity of the proposed final system in terms of its functionality, the technologies to be used and whether the student has had previous experience with the proposed technologies. 
  5. Student Approach - The conduct of the student during the project, including project management skills, effort, taking responsibility for completing work etc.

 

The Final Project Manual and the Final System Deliverable will be assessed during Semester II in accordance with the following criteria:

    • Presentation – The quality of the student’s Project Presentation/Demonstration.
    • Project Manual  - The quality of the Final Project Manual in terms of its lay-out, structure, writing style, correctness and referencing.
    • Research and Understanding – The quality of any additional background research undertaken during the implementation phase and the alignment of the final system deliverable to the original background research findings. 
    • Design Quality - The alignment of the final system deliverable to the original system design specification.  
    • Software Quality - The quality of the software produced for the final system deliverable in relation to its structure/architecture, layout, comments, code re-use etc.
    • Completeness and Complexity - The completeness of the final system deliverable in terms of its functionality, the end-user interface, the system inputs and outputs etc. Students are expected to exceed the standard of all previously submitted coursework.  In particular recognition will be given to students that produce complex and complete work and those that successfully address difficult issues. 
    • Project Management - The conduct of the student throughout the project in relation to their approach to the project, their project management skills, independent effort etc.
    • Value and Usability - The value of the final system deliverable in terms of the problem area it addresses and the likelihood of it being adopted.

Essential Reading

As prescribed by the student’s chosen project topic.  In addition the student is expected to continually monitor the appropriate project webpage for information on all aspects of the project including key delivery dates, the project guidelines, demonstration schedules etc.

Supplemental Reading

Web references, journals and other:

Further Details:

40 minute weekly contact to be delivered across two semesters.

Date of Academic Council Approval:

June 2010