1 / 22

Student Companion - Project Current State – Achievements

This update highlights the current state of the Student Companion Project, including achievements, member contributions, design changes, source code structure, modularity, communication, synchronization, and user interface developments.

cristobale
Download Presentation

Student Companion - Project Current State – Achievements

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. Student Companion-Project Current State – Achievements Members in Croatia: Ante Radman Bruno Samardžić Gabrijel Smoljkić Members in Sweden: Andreas Drake Asad Saleem Muhammad Usman Ghani Robert Lundquist Vasilis Odontidis

  2. Agenda • Milestones fulfilled • Current project phase • Workload and cost • Roles for development • Design changes • Detailed design • Source code structure • Modularity demo • Communication • Synchronization • GUI

  3. Milestones DONE DONE DONE ALMOST ON TRACK LATER ON TRACK LATER LATER LATER

  4. Current project phase • First version of all initial documents done – continue revising through entire project • Defined structure for the CVS • Some problems with WinCVS • TortoiseCVS works great  • Defined structure for the development solution • Made a prototype for modularity • The implementation phase started • Everyone working on their ”own” component • Had some problems with the Bluetooth connection • Solved with another method • Have presented some GUI proposals for the customer • The latest approved

  5. Workload

  6. Cost

  7. Roles • For the implementation we have defined some new responsibilities • Almanac (Usman) • Backup (Robert) • ConnectionHandler (Gabrijel, Ante) • Courses (Asad) • FileHandler (Andreas) • InformationHandler (Bruno) • Installer (Robert) • Language (Andreas) • Search (Vasilis) • Sync (Gabrijel, Ante) • Integration - Andreas and Robert

  8. Design changes • Decided to skip the SQL Server Express • Will use XML instead • Makes it possible to reuse code on both PC and PDA • ConnectionHandler – new component • Will abstract the connection with other devices • Divided some components • One core part, several GUI parts

  9. Detailed PC Design

  10. Detailed PDA Design

  11. Source code structureand modularity prototype • Time for some demo…

  12. File structure – er diagram

  13. File Courses.xml <courses> <course ID="" name=""> <note ID="" datetime=""> here goes text </note> <description> here goes description </description> <file ID="" location=""> here goes file comment </file> </course> </courses> File events.xml <events> <event ID="" date="" time="" courseID="" reccurence="yes/no"> <activity ID="" /> </event> </events> File activities.xml <activities> <activity ID="" courseID="" grade="" updated=""> <note ID="" datetime=""> here goes text <file ID=""> here goes pageComment </file> </activity> </activities> File notes.xml <notes> <note ID="" datetime=""> here goes text </note> </notes> File structure - xml

  14. Communication • Primary task: connecting to PDAs • Successfully started Bluetooth connectivity • Supporting both one-to-one and one-to-many topology • ConnectionHandler component

  15. Communication - continued • Underlying protocol: TCP/IP (WindowsSockets) • working on a familiar and reliable technology • made the system easy to expand • Special testing version for simulating PC-PDA communication

  16. Synchronization • Exchanging XML messages • Three synchronization steps: • devices send their data to master • master synchronizes it’s database and sends necessary data to others • exchanging files where necessary • Made a separate component for synchronizing — SyncComponent

  17. User Interface • We started with a research in user interaction principles, mainly within: • User Experience Guide from Microsoft • Human Interface Guidelines from Apple • Principles of Interaction Designfrom Nielsen-Norman Group • The main resource: • Our own Requirements definition

  18. User interface • Main issue: information architecture • What is displayed to the user • How it is displayed and how it works • The initial UI draft was very large and complex • What we did: • Removed all elements and actions that weren’t needed • Bring information that is important to user to the first plane • Conformed all elements and behaviours to most common practices • Made the system as simple and efficient as possible

  19. User interface • The blueprints

  20. User interface • The blueprints

  21. References • Microsoft User Experience Guidelineshttp://msdn.microsoft.com/library/en-us/dnanchor/html/anch_UIDesignDev.asp • Apple Human Interface Guidelineshttp://developer.apple.com/documentation/UserExperience/Conceptual/OSXHIGuidelines/ • NN/g First Principles of Interaction Designhttp://www.asktog.com/basics/firstPrinciples.html

  22. Thank you Now your questions, please.

More Related