1 / 44

NOTICE!

NOTICE!.

abia
Download Presentation

NOTICE!

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. NOTICE! • These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer Science and Engineering, University of Mälardalen, Västerås, Sweden and at the Faculty of Electrical Engineering and Computing, University of Zagreb, Croatia (year 2009/2010). • For all other purposes, authors’ written permission is needed! • The purpose of these materials is to help students in better understanding of lectures in DSD and not their replacement!

  2. Distributed Software Development

  3. Progress Component Model ProCom@MdH Final Presentation

  4. Next ½ hour.. • Project Definitions • ProCom Requirements • Final Demo • Experiences and Challenges • Project Statistics

  5. Team Structure

  6. Project Definitions

  7. Procom@MdH? • A model-driven code generation utility for the embedded system, modeled using ProCom model. • Part of ongoing research in the University for the Progress project • Developed at MdH

  8. Why Procom Project? • Non existence of the code generation utility for the embedded system modeled using ProCom model. • Mapping the ProCom model to executable code.

  9. Procom Project Benefits? • An integrated platform to design & develop embedded-systems in a common IDE • Enables rapid application development

  10. Interaction with Progress-IDE? Interaction with Progress-IDE via XML files Final Product? A Plug-in integrated in Progress-IDE

  11. ProgressIDE

  12. Generated XML File

  13. Refine XML Schema

  14. Parse XML & store tags

  15. Identify individual elements

  16. Identify dependencies among components

  17. And then….

  18. Generate Java Code

  19. View Code

  20. Compile Code

  21. Execute Code

  22. Clean Code

  23. Requirements

  24. Fulfilled Requirements? • XML Parsing • Identifying Mapping Rules • Code Generation • Code Compilation • Code Execution • Plug-in for Progress-IDE • Investigated Glue Code Generation

  25. Additional Requirements? • XML Schema Dropped Requirements? • Compilation & Execution of Glue Code

  26. By: Edward V. Berard Image source: i.imgur.com/

  27. A Sample ProCom Model

  28. Experiences and Challenges

  29. Experiences and Challenges • Communication strategies • In face-to-face meetings • Slow Conversation speed • Team members availability • Online Meetings • Preferred text chat over voice chat • More online meetings rather than face-to-face meetings • Emphasis on use of latest communication technologies

  30. Experiences and Challenges • Skype • Google Groups • Online meetings @ www.gotomeeting.com

  31. Experiences and Challenges • Time Limitations • Because of exams and assignments of other courses • What we Like about the project • Team Work • Challenging Project • Opportunity to interact with knowledgeable Supervisors and Professors

  32. Cultural Differences (and Similarities)

  33. Spiral SDLC Model • Spiral helped incremental Product delivery • Customer feedback was taken after each delivery • Suggested changes were included in the next delivery • Continuous feedback ensured customer expected product

  34. Development Methodology Prototype 1 Prototype 2 Prototype 3 Final Release • Prototype1 : Code generation for PROSAVE Component • Prototype 2: Refinement of Code generation logic • Prototype 3: Code Generation for PROSYS and Progress IDE plug-in • Final release: Code Execution Framework and glue code investigation 10/13/2014 37

  35. Project Statistics

  36. Effort Distribution Cumulative Team Efforts (approx): 1200 hours

  37. SVN Statistics

  38. Communication Statistics • Team meetings: • Online Meetings: 6 • Campus Meetings: 5 • Meetings with the Supervisor: • Online Meetings: 3 • Campus Meetings: 3 • Informal team meetings: Countless

  39. Future Development • XML Schema Validation • Support For Multiple Languages • Class Diagram View Representation • Reverse Engineering (Code -> ProCom) • Improved Code Generation

  40. ADIOS!!! 

More Related