COMP08097 2012 Project 400

General Details

Full Title
Project 400
Transcript Title
PRJ400
Code
COMP08097
Attendance
N/A %
Subject Area
COMP - Computing
Department
COMP - Computing & Creative Practices
Level
08 - NFQ Level 8
Credit
10 - 10 Credits
Duration
Stage
Fee
Start Term
2012 - Full Academic Year 2012-13
End Term
2017 - Full Academic Year 2017-18
Author(s)
Mr. John Kelleher
Programme Membership
SG_KSYSN_K08 201200 Bachelor of Science (Honours) in Systems & Networking L8 SG_KSDEV_K08 201200 Bachelor of Science (Honours) in Computing in Software Development SG_KCMPT_K08 201300 Bachelor of Science (Honours) in Computing SG_KSDEV_K08 201300 Bachelor of Science (Honours) in Computing in Software Development SG_KCOMP_H08 201500 Bachelor of Science (Honours) in Computing SG_JSCIE_X06 201400 Certificate SG_KCOMP_H08 201600 Bachelor of Science (Honours) in Computing
Description

In Project 400 individuals or teams (see note below) will undertake a significant piece of independent work under supervision. The module aims to encourage innovation, team-work, and exploratory learning. 

The actual deliverables will be tailored to the stream and background of the individual/group. For example, for those from a software development stream, the outcome will be set of software specifications probably underwritten by low-fidelity prototyping and implemented to a target platform. For other streams where a hardware based implementation may not be feasible, the presentation of a thesis (scoping the chosen domain, literary review, factual discovery, prototype/simulation/testbed and direction of future research) will be sought. In the case of students from a web design/development background, a typical submission will consist of task analysis, development of use cases/personas, contextual enquiry, iterative design sketches, evidence of wireframing process, low-fidelity prototypes, user evaluation, testing and implementation.

Particular to the Level 8 offering of this module, students will be expected to make a cogently argued submission and presentation of the facts/design/theories the support it. In reference to the justification of the thesis/deliverable, its applicability to research/industry will be scrutinised. When working in teams, students will be expected to form and manage a coherent team, assign roles/responsiblities, plan and direct to a high standard and provide evidence of same.

The objective is to prepare students for the demands of the workplace and/or further research. The deliverables expected will broadly reflect the content of the programme of study, a scientific approach to research and investigation, good time- (and team-, where selected) management as well as a strong appreciation of the industry view/role of the work undertaken. The intent is to provide students with a simulation of a real-world project along with the management issues (of time, people, resources and skills) and fixed deadlines that accompany it.

Team Size: In the case of B.Sc. in Computing Level 8 (Systems & Networking) Project 401 will typically be the work of an individual alone where a thesis submission is agreed, due to constraints surrounding hardware necessary for practical work.

Typically individuals will undertake a Project alone though consideration will be given to teams of up to three. In the case of B.Sc. in Computing Level 8 (Systems & Networking) Project 400 will typically be the work of an individual alone where a thesis submission is agreed, due to constraints around hardware necessary for practical work.

Learning Outcomes

On completion of this module the learner will/should be able to;

1.

be able to work either individually or in a small team to develop a major project to a deadline involving, inter alia, planning and coordination of design & development activities, setting realistic work objectives, and presenting and documenting of the work undertaken

2.

demonstrate practical and creative abilities when applied to a substantial body of work from the theoretical and practical aspects of the course programme

3.

have applied suitable research, computing resources, and written & verbal communication skills to the identification, analysis and implemented solution of an appropriate problem

4.

to integrate and evaluate the relevance, strengths and weaknesses of approaches developed throughout the course.

5.

demonstrate the attention to detail required of a full development effort and the need to rigorously manage both time and resources

6.

apply critical thinking to the exploration of the research area chosen, drawing conclusions, testing same and developing creative solutions or interpretations of the material examined

Module Assessment Strategies

This project will differ with respect to a Level 7 project in several respects. While the core features of the module are similar, the Level 8 project will exhibit greater mastery in the following areas:

  • project scope (e.g. choosing a topic not previously encountered or one involving multiple un-familiar disciplines)
  • research (greater depth and thoroughness of literary discovery) 
  • greater industry awareness (project must relate to the demands/needs of industry/research)
  • evaluation (e.g. heuristic evaluation of prototypes, hierarchical task analysis or the choice of a more appropriate design methodology) 
  • defence (that is, the student(s) will be expected to provide a coherent, composed and informed response to questions regarding the project, his/her research, literary findings as well as technical details of implementation. 
  • documentation will be scrutinised to verify readability, thoroughness and completeness. 

Submissions will be rigorously scrutinised for possible plagiarism. Sources will be randomly verified and the oral presentation will be used to confirm competency with the material.

The group/individual will:

  • agree a project proposal with the group supervisor and form an initial specification/scoping document for the Project
  • hold regular weekly meetings to assign tasks and review progress
  • adopt an agile methodology (scrum, lean, XP) to support product delivery (group-dependant)
  • rapidly prepare mock-ups of designs, document such design decisions and prepare and review lo-fidelity prototypes
  • maintain a project blog to record progress, decisions debated/decided, individual contributions, reflections on work undertaken, downloads of prototypes/deliverables
  • make presentations to other selected peer groups and take questions
  • submit a group/individual report at module-end to encapsulate work undertaken
  • make presentation to lecturer review panel for assessment

Assessment is through a number of individual deliverables and/or team deliverables (as applicable), emphasising the practical nature of the module. In groupwork, individual deliverables are designed to allow students to demonstrate their understanding of the problem to be solved, what their role within the group has been and to provide a reflection of what they personally have learnt from the module.

Project deliverables require the student(s) to produce software prototypes or web-site mockups or body of documented research. In groups, the students must demonstrate that they have worked collectively to produce the end product. Also for groups, peer assessment is employed to identify each individual's contribution to the team.

Teams/Individual will be assigned a supervisor knowledgeable in the cognate area of the Project. The group will meet with the supervisor for 1.5hrs each week (30min for individuals) during which problems or needs related to the work are discussed and progress reviewed. The supervisor is drawn from a supervisor panel:

  • familiar with the operation of project work and regularly assigned to such work
  • have competencies in underlying technologies employed by project teams in the various cognate areas, both technically and in project management methodologies
  • on the programme board for Level 7 or Level 8 for whom he/she is supervising 

In accordance with agile development methodologies (e.g. Scrum), at the end of each sprint (every 4 weeks) a 'Sprint Review Meeting' is called to present progress (among other things) to the other groups, and to solicit opinion/critique.

Indicative Syllabus

Problem Formulation                                                                

  • Identify project
  • Document project proposal
  • Assemble facts regarding users and tasks
  • Outline specification of project
  • Prepare a project plan
  • Identify appropriate implementation platform, development tools and other aids.

Analysis & Design

  • Select appropriate design methodology
  • Produce supporting diagrams/ design documentation
  • Develop low-fidelity prototype(s)
  • Submit evidence of end-user evaluation where possible

Implementation

  • Employ appropriate tools/resources to realise product
  • Apply software quality standards
  • Show evidence of project planning and scheduling

Testing & Evaluation

  • Develop, deploy and analyse test plan
  • Iterate user evaluation of interface
  • Test for program completeness

Documentation

  • Articulate project rationale
  • Identify target audience and skills base
  • Document personas and goals
  • Describe scenarios of use
  • Outline specification
  • Specify hardware/software requirements
  • Document design process
  • Provide program listing
  • Provide testing documentation
  • Provide user evaluation reports
  • Produce User Manual
  • Product purpose and role
  • Tutorials and ‘How-to' sections
  • Troubleshooting section
  • Maintain project log book/web site
  • Bibliography

Coursework & Assessment Breakdown

Coursework & Continuous Assessment
100 %

Coursework Assessment

Title Type Form Percent Week Learning Outcomes Assessed
1 Interview Interim Presentation Continuous Assessment UNKNOWN 10 % End of Term 1,2,3,4,5,6
2 Project Project Submission/Assessment Continuous Assessment UNKNOWN 90 % End of Year 1,2,3,4,5,6
             

Full Time Mode Workload


Type Location Description Hours Frequency Avg Workload
Directed Learning Not Specified Supervisor Meeting 1 Weekly 1.00
Independent Learning UNKNOWN Independent Work 13 Weekly 13.00
Total Full Time Average Weekly Learner Contact Time 1.00 Hours

Module Resources

Non ISBN Literary Resources

Projects in Computing and Information Systems: A Student's Guide
Dr Christian Dawson (Author)
Addison Wesley (2009)
ISBN-13: 978-0273721314

 

Computer Science Project Work: Principles and Pragmatics
Sally Fincher (Editor), Marian Petre (Editor), Martyn Clark (Editor)
Springer; 1st Edition. edition (6 Mar 2011)
ISBN-13: 978-1849968652

Successful teamwork! For Undergraduates and Taught Postgraduates Working on Group Projects
Peter Levin (Author)
Open University Press; illustrated edition edition (1 Sep 2004)
ISBN-13: 978-0335215782

Version Control with Subversion
C. Michael Pilato (Author), Ben Collins-Sussman (Author), Brian W. Fitzpatrick (Author)
O'Reilly Media; 2 edition (23 Sep 2008)
ISBN-13: 978-0596510336


Other Resources
  1. A designated room or lab for duration of project. Lockable and with necessary IT infrastructure required for such projects. This demands, inter alia, white boards, ample table-top space, presentation space, shared work-stations and data projector, wireless network and printing facilities
  2. Hardware budget for equipment
  3. Use of old IT equipment such as servers etc which may become available from time to time.
  4. Easy access to the college at weekends for such students.
Additional Information
None