Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Sanket 895 presentation


Published on

  • Be the first to comment

  • Be the first to like this

Sanket 895 presentation

  1. 1. Design and Development of Architecture and System Integration for Electronic Teamwork Assessment Tool e-TAT Masters Project Oral Defense by Sanket Parab Computer Science Graduate Student, SFSU Advisors/Committee Members Dr. Dragutin Petkovic Gary Thompson Prof. James Wong
  2. 2. Outline <ul><li>Background and Motivation </li></ul><ul><li>Problem Statement </li></ul><ul><li>Electronic Teamwork Assessment Tool (e-TAT) </li></ul><ul><li>Demo with Use-cases </li></ul><ul><li>Project Hosting Platform </li></ul><ul><li>Architecture </li></ul><ul><li>RSS/ATOM Feed Parser </li></ul><ul><li>Class Diagram and API </li></ul><ul><li>Testing </li></ul><ul><li>SE Methods Used </li></ul><ul><li>Contributions to e-TAT </li></ul><ul><li>Conclusion </li></ul>
  3. 3. Problem Statement <ul><li>Rapidly-evolving SW industry requires educational institutions to adopt innovative changes in their curriculums in order to provide students with the necessary competitive skills and experience required in today's job market. </li></ul><ul><li>Important for instructors to teach and evaluate students teamwork and soft skills, and know about how students apply it in real settings during team project development. </li></ul><ul><li>Manually collecting and analyzing team activity data is difficult and inefficient. </li></ul>
  4. 4. Background and Motivation <ul><li>SFSU is offering SE courses in collaboration with FAU, Florida & Fulda, Germany from past several years. </li></ul><ul><li>Instructors here developed composite method to evaluate and assess teamwork performance. </li></ul><ul><li>Team activity data was collected and analyzed manually. </li></ul><ul><li>No tool exists to automate the process of data collection and evaluation. </li></ul><ul><li>Proposed e-TAT to automate the process of metrics collection and analysis and started Project with 4 team members. </li></ul>
  5. 5. Electronic Teamwork Assessment Tool (e-TAT) <ul><li>Innovative Web Based Tool pioneered at SFSU with easy to use interface. </li></ul><ul><li>Developed by a team of 4 computer science graduate students. </li></ul><ul><li>Interfaces with Goggle Code and Google Groups collaboration platforms to collect team activity data. </li></ul><ul><li>Integrates fully functional customized Survey Tool and Data Mining tools to analyze data. </li></ul><ul><li>Stores data in centrally administered database for future use. </li></ul><ul><li>Generates reports based on collected data (in various formats) for reference by Instructors. </li></ul>
  6. 6. Demo with Use-cases <ul><li>Setup Google Code and Google Groups (overview). </li></ul><ul><li>Create new Course and add new Groups to that Course. </li></ul><ul><li>Use Google Code to make a project update (downloads, issues, etc.). </li></ul><ul><li>Update e-TAT feeds (through RSS/ATOM Feed Parser) and add Annotations. </li></ul>
  7. 7. Project Hosting Platform: Competitive Analysis
  8. 8. Project Hosting Platform: Google Code & Groups <ul><li>Advantages: </li></ul><ul><li>Availability </li></ul><ul><li>Performance </li></ul><ul><li>Quality of Service </li></ul><ul><li>Project Update Feed </li></ul><ul><li>Communication Tools </li></ul><ul><li>Collaboration Tools </li></ul>SVN Commits Wiki Updates Issue Tracking Mailing List Discussions Downloads ATOM Feed
  9. 9. Architecture
  10. 10. RSS/ATOM Feed Parser
  11. 11. Class Diagram
  12. 12. Internal Data Access API
  13. 13. Testing
  14. 14. Software Engineering <ul><li>AGILE / SCRUM engineering technique: </li></ul><ul><li>Highly iterative development. </li></ul><ul><li>Weekly updates (meetings). </li></ul><ul><li>Object Oriented API development: </li></ul><ul><li>Modular, and hence, flexible. </li></ul><ul><li>Highly maintainable and easy to extend. </li></ul><ul><li>User-centered Design method: </li></ul><ul><li>Focus on usability (rather than just functionality). </li></ul>
  15. 15. UI Iteration Example #1
  16. 16. UI Iteration Example #1
  17. 17. UI Iteration Example #2
  18. 18. UI Iteration Example #2
  19. 19. Contributions to e-TAT <ul><li>Design of the early Database Schema for the e-TAT application for easy and fast access of the data objects. </li></ul><ul><li>Design and implementation of e-TAT Architecture. </li></ul><ul><li>Design and implementation of RSS/ATOM feed parser for fetching relevant project data from two platforms (Google Code and Google Groups) into a single e-TAT database. </li></ul><ul><li>Integration of tools created by team members into the e-TAT application (survey, UI, reports, data mining). </li></ul><ul><li>Correctness (QA) and the Usability review of the software: Tested application for its correctness using various testing techniques and had a usability review of the software from the two instructors and an unbiased representative user. </li></ul>
  20. 20. Conclusion <ul><li>Designed and developed e-TAT as an automated teamwork assessment tool for use by Instructors teaching Software Engineering Practices. </li></ul><ul><li>Designed and developed Project Hosting Platform integration along with feed parsing functionality. </li></ul><ul><li>Integrated full functional customized Survey Tool and Data Mining Tools into e-TAT. </li></ul>
  21. 21. Acknowledgements The e-TAT development team would like to thank their project advisors, Dr. Dragutin Petkovic and Gary Thompson for their invaluable help, support and guidance in designing and developing the e-TAT from scratch. The author would especially like to thank the whole team for putting in several hours every week and brainstorming during the SCRUM meetings to help solidify the product features. Help from the Computer Science Department staff at San Francisco State University is much appreciated, for providing laboratory access and the ability to host the in-development prototypes of the e-TAT Application during semester terms.
  22. 22. References <ul><li>D. Petkovic, G. Thompson, R. Todtenhoefer, S. Huang, B. Levine, S. Parab, G. Singh, R. Soni, S. Shrestha : “Work in Progress – e-TAT: Online Tool for Teamwork and “Soft Skills” Assessment in Software Engineering Education”, submitted to Frontiers in Education FIE 2010 (undergoing final review) </li></ul><ul><li>Dragutin Petkovic, Rainer Todtenhoefer, Gary Thompson: “Assessment and Comparison of Local and Global SW Engineering Practices in a Classroom Setting”, ITiCSE’08, June 30-July02, Madrid, Spain </li></ul><ul><li>Collaborative Online Project Involvement Analysis [COPIA], Software Engineering (Dr. Dragutin Petkovic and Gary Thompson), Fall 2008 SFSU, / accessed on 07/15/2010 </li></ul><ul><li>M. Al-Yahya: “Using Wikis to Support teamwork Skills in Software Engineering Courses”, 22nd Conf. on Software Engineering Education and Training, 2009 </li></ul><ul><li>Orit Hazzan, Y. D. (2008). Agile Software Engineering. Springer. </li></ul>
  23. 23. References <ul><li>Project Kenai: We’re More Than Just a Forge, / accessed on: 09/12/2010. </li></ul><ul><li>Bulmer, M. (1979). Principles of Statistics. Oxford: Dover Publications, New York. </li></ul><ul><li>Pressman, R. (2005). Software Engineering: A Practitioner's Approach. Mc Graw Hill. </li></ul><ul><li>&quot;Software Engineering 2004&quot;: Curriculum Guidelines for Undergraduate Degree Programs in Software Engineering, The joint Task Force on computing Curricula, IEEE Computer Society, Association for Computing Machinery, August 2004. </li></ul><ul><li>Atlee, J.; leBlanc Jr., R.; Lethbridge, T.; Sobel, A.; Thompson, J.: “Reflections of Software Engineering 2004, the ACM/IEEE-CS Guidelines for Undergraduate Programs in Software Engineering”, P. Inverardi, M. Jazayeri (Eds.)., ICSE 2005 Educational Track, LNCS 4309, pp11-27, 2006, Springer Verlag, Berlin Heidelberg 2006 </li></ul>