The Software Engineering process in Everyware Technologies
0 likes440 views
The document discusses best practices for software engineering projects with customers. It recommends (1) understanding the customer's needs through open communication, (2) providing clear estimates and budgets, (3) collaborating on design and prototypes to ensure customer satisfaction, and (4) maintaining the relationship after a project is completed through support and potential new features. The overall message is that software development requires an ongoing, collaborative process between engineers and customers.
The Software Engineering process in Everyware Technologies
- 1. Software Engineering on Everyware Carlos RodrĂguez DomĂnguez Everyware Technologies S.L. TomĂĄs Ruiz LĂłpez /everywaretech @everywaretech {tomas, carlos}@everywaretech.es
- 2. 1. Letâs talk with the costumer
- 3. 1a. Our ïŹrst meeting
- 4. 1b. We need to understand your work/ service/product
- 5. 1c. Whatâs our portfolio in your area
- 6. 1d. Is a mobile app suitable for you? Maybe notâŠ
- 7. 2. What? When? How much?
- 8. 2a. Estimate when, taking into account what
- 9. 2b. How much = Days x People x 100 âŹ
- 10. 2c. Donât discuss the price, discuss what to do
- 11. 2d. Deliver a clear, but simple budget > 80% acceptance rate But is not enough for us⊠;D
- 12. 3. The âfaceâ of the code: Design + Storyboard
- 13. 3a. The graphical design needs to be clear
- 14. 3b. The storyboard is key for customer satisfaction
- 15. 3c. Do not impose, explain
- 16. 4. First prototype: Is the app already ïŹnished?
- 17. 4a. Your ïŹrst prototype must include most of your storyboard But not all the functionalities, of course!
- 18. 4b. Iterate over the design again! But explain!
- 19. 5. Letâs code together
- 20. 5a. One person-One project = FAIL! But some times inevitable!
- 21. 5b. Coordination tools! Extra work=Less work Code + TODOs + Communication NOW LATER
- 22. 5c. Modeling team and Viewing team And exchange the people! And make them work together! Leaders? Yes, but carefully chosen and not always the same people!
- 23. 5d. Everyone is on the controller team! Strictly Model-View-Controller
- 25. 6a. The customer is the most important member of the development team! A prototype is not a surprise! is programmed!
- 26. 6b. Provide a date for the next prototype - Why on that date? Explain! Explain! Explain! Explain!
- 27. 6c. TIC! TOC!
- 28. 7. Your app is ready! Letâs start the projectâŠ
- 29. 7a. We donât provide products, we provide software Software Product = Software + Infrastructure + Marketing + Manuals + Economical model + CRM + âŠ
- 30. 7b. âŠBut we need to help! Our experience is a great value for the customer! Give your opinion and⊠explain!
- 31. 8. We are here!
- 32. 8a. A customer is always a customer The relationship should never end
- 33. 8b. Maintainability! Suggest it! New features? Technological changes? New knowledge? Detected bugs?
- 34. 8c. Comeback to the beginning if you need it If you failed: Accept it, take actions and continue
- 35. 8d. Train! Demo!
- 36. We need to learn and change a lot! ! Software Engineering is the new Never-ending Story! ! Questions? Feedback?