1 / 34

CST Group Design Project Briefing 2010

CST Group Design Project Briefing 2010. Alan Blackwell. Overview. Each member of a group undertakes 30-60 hours of work over six weeks. Projects apply a broad range of academic knowledge. Intention is to experience a realistic professional environment.

judah-weber
Download Presentation

CST Group Design Project Briefing 2010

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CST Group Design ProjectBriefing 2010 Alan Blackwell

  2. Overview • Each member of a group undertakes 30-60 hours of work over six weeks. • Projects apply a broad range of academic knowledge. • Intention is to experience a realistic professional environment. • One practical credit for combined group product. • One credit for individual contribution.

  3. Scheduled events • This briefing lecture, with project topics • Students nominate preferences for topics • Assigned topics and group members are advised on first day of Lent term. • Progress reports, at three scheduled review meetings with project client • Presentation skills lecture 8 Feb • Demonstrations and presentations 9 Mar

  4. Syllabus • Appropriate data structures and algorithms are expected. • Concurrency, architectures, hardware and compiling may be required. • Software Design & Engineering essential: • professional design, quality and project management • careful planning and testing • cooperation with an imposed group • deal with external requirements, constraints and deadlines

  5. Computing facilities • Workstation room in Gates building • Development environment is PWF Linux • Filespaces will be created for each group: • ${CLTEACH}/grpproj/alpha, …/bravo, …/charlie … • There is a 1 Gbyte limit for working code, data, docs, backups etc

  6. Software tools • Selection and use of suitable tools is an important component. • Most will be implemented in Java. • May justify modules in a different language • Some open source software may be needed • Unix tools are as provided on PWF Linux • http://www-uxsup.csx.cam.ac.uk/pwf-linux/autodoc/

  7. Review meetings • Specifications are agreed, and progress reported, with an external client. • Three one-hour meetings held fortnightly: • 1. Requirements specification • 2. Implementation and test results • 3. Demo and final report • These are not supervisions, but an opportunity to work with professionals. • Sign up with student admin for slots.

  8. Project phases • Requirements definition • Functional specification and project plan • Module implementation and testing • System integration and testing • Personal report • Presentation

  9. Requirements definition • Start with the design brief provided. • Investigate problem and decide necessary features of the system. • Specify the acceptance criteria for completion. • Write a requirements specification of 3000-5000 words. • Deliver to client, agreeing adequacy and feasibility within time budget.

  10. Functional specification • Plan major components of the system • This may include some standard library modules, some public domain software. • Identify components to be implemented and specify their interfaces. • Java abstract classes with comments • Identify dependencies for planning the order in which work will be done.

  11. Planning • Choose overall management strategy and group roles • Include management, testing, etc. • Every member should do some programming. • Allocate development of modules to team. • Work to a budget of 60 hours per team member. • Set realistic targets and achieve them. • No extra marks for doing too much!

  12. Module implementation and testing • Write code for required modules • Mostly as Java classes • Test the modules in isolation • Construct test harnesses • Test and record results • Deliver • Progress report by the team manager • Code of the implementations • Description of testing procedures and results

  13. System integration and testing • Assemble the modules • Test the whole system • Final course assessment based on: • Source code ready for collection on March 7 • Final report by project manager on overall successes and failures. • Personal reports, giving details of individual contributions from each team member.

  14. Presentation of results • Public show on March 9. • Interactive demonstrations: • 2 hour session in workstation area. • Presentations in lecture theatre: • 5 minute talks by each group. • Project clients and CL staff voteon the best projects • Sponsored prizes for technical and professional achievement

  15. Project topics • There are 17 potential design briefs. • You may express personal preferences • Email preferences to group-project@cl.cam.ac.uk by Wednesday 1 December. • No guarantees! You will not necessarily be grouped with your friends. • Groups, and assigned design briefs, are announced at the start of next term.

  16. Design briefs

  17. 3D View Preview • What will the view be like from my hotel? • Crowd-source tourist models • Client @ LastMinute.com

  18. 2. African SMS Radio • Audience interaction for radio stations • Work with African users • Extend FrontlineSMS • Client @ FrontlineSMS

  19. 3. Crowd Control • Model flow of people in alarm/panic • Start with WGB openroommap • Then Olympics venue specifications

  20. 4. Digit[Ov]al cricket commentary • Wearable MeLock player tags • accelerometers • received signal strength • RSS, Twitter, animation • Client @ MeLock

  21. 5. Digital House Doctor • Decision tool: • upgrade building, or • use it more efficiently? • Client @ Cambridge Architectural Research

  22. 6. Energy Cloud • make people aware of energy use • control demand to smooth peaks • share information and hints

  23. 7. Global commerce • Purchase from Chinese websites • Use online translation tools • Support continuous ‘order journey’

  24. 8. Hand Wave, Hand Wave • Use digital gyroscopes for spatial input control • Control animated 3D objects • Change view direction • Modify objects • Gesture menus for lighting etc

  25. 9. iZoopraxiscope - Handheld Projector • Animated animal game using an Android pico projector • Client @ Disney Research

  26. 10. Lounge Star • App for business travellers • check-in, shopping, gate notification, frequent flyer clubs • via tilt and gestures only • Client @ Amadeus

  27. 11. Pimp my Fridge • Beyond the ‘Internet Fridge’ • Client @ ARM

  28. 12. The Energy Forecast • Estimate renewable energy and locations for new power plants. • Client @ Bloomberg

  29. 13. Top Tips • Analyse large sample of stock market tips to define a quality metric. • Test results against a corpus of over a million comments for use in online trading • (note confidentiality) • Client @ YouDevise

  30. 14. True Mobile Coverage • Network operators do not guarantee accuracy of signal maps • Allow customers to crowd-source surveys using Android phone with GPS • Client @ ARM

  31. 15. Twitter Dashboard • Track real-time public profile • Customisable widgets for public view • traffic volume • trend dynamics • tag clouds • ideas …

  32. 16. Walk out of the Underground • Help provincial academics in London • Smartphone app version of Vasco Pyjama's direction finding duck • Client @ CSR

  33. 17. Who is my Customer? • Analyse customer data to infer the internal structure of companies • Client @ Credit Suisse

  34. Next Step • Choose preferred projects. • Email 1st/2nd/3rd preferencesto <group-project@cl.cam.ac.uk>by noon on Wednesday 1 December. • (Specify projects by list number) • Wait for fun to start next term!

More Related