NOTICE!

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

7. Project Definitions

8. 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

9. 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.

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

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

13. ProgressIDE

14. Generated XML File

15. Refine XML Schema

16. Parse XML & store tags

17. Identify individual elements

18. Identify dependencies among components

19. And then….

20. Generate Java Code

21. View Code

22. Compile Code

23. Execute Code

24. Clean Code

25. Requirements

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

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

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

30. A Sample ProCom Model

31. Experiences and Challenges

32. 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

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

34. 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

35. Cultural Differences (and Similarities)

36. 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

37. 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

38. Project Statistics

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

40. SVN Statistics

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

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

44. ADIOS!!! 