Live Source - an Agile Toolkit
•Download as PPT, PDF•
1 like•717 views
- Live Source is a new technology that clarifies source code into an easy to read summary, allowing stakeholders and programmers to work together more effectively. - It integrates user stories and tasks more closely with the codebase, and allows source code to serve as documentation, communication, planning, and metrics. - The toolkit is available online for demonstration through a tic tac toe game, and allows viewing code summaries, editing documentation, and requesting features from programmers.
![Live Source an AGILE TOOLKIT Alline Watkins & June Clarke [email_address] [email_address]](https://image.slidesharecdn.com/livesourceagilewithvideos-110130231233-phpapp02/85/Live-Source-an-Agile-Toolkit-1-320.jpg)
![Getting the most of your source code ,[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (19)
Viewers also liked
Viewers also liked (17)
Similar to Live Source - an Agile Toolkit
Similar to Live Source - an Agile Toolkit (20)
More from Alline Oliveira
Recently uploaded
Recently uploaded (20)
Live Source - an Agile Toolkit
- 1. Live Source an AGILE TOOLKIT Alline Watkins & June Clarke [email_address] [email_address]
- 6. The advantages... Faster communication Less risk of miscommunication Knowledge of domain will reside in codebase Overhearing Code is easier to understand (maintainability, extensibility) Healthier code Better response to change
- 9. SNAPSHOTS & DEMO VIDEOS Ok, Now the Toolkit! DEMO VIDEO: http:// www.screencast.com/t/tO2yuhyZuVI
- 13. Editing the documentation of the source code In addition, stakeholders or a non-technical person can easily edit the documentation of a feature in the Toolkit. This documentation will not be stored in paper documents or outdated databases, but straight into the source code as a comment . VIDEO : http://www.screencast.com/t/VA1FCmzY4Gj
- 15. You can go further in your documentation and actually send messages to programmers very precisely straight inside the source code. This way they can more effectively identify bug reports and change requests. The Planning Tool VIDEO : http://www.screencast.com/t/wtGNmcDVO
- 16. Helping with Unit Testing The Toolkit can check if there are Unit Tests created in your source code. If they are not created yet, the Toolkit can help you create them. VIDEO : http://www.screencast.com/t/innoj1ydQ
- 17. Tagging and Filtering the source code The Toolkit can filter all the classes in the source code according to the tag that has been attributed to them at the Development phase; including Architecture, Main Feature and Entity Model. VIDEO : http://www.screencast.com/t/VUwtdMS6
- 18. The Specification Portal The Toolkit can automatically generated some documentation for your software totally based on the source code; like the Specification Portal and the User Manual. VIDEO : http:// www.screencast.com/t/xv1J98L35
- 19. Automatically generated User Manual http://helpagile.appspot.com/?project=TicTacToe VIDEO : http:// www.screencast.com/t/5UmiTLHD
- 20. Software Metrics
- 21. INSTRUCTIONS How the Toolkit works DEMO VIDEO: http://www.screencast.com/t/RwMporlpt
Editor's Notes
- Main problem in software is miscommunication
- New communication channel This New communication channel
- Maintainability – classes and packages are named/grouped in a way that makes sense in the real world Agility improve - Precise Communication
- c
- Edit class comments Helps managers to communicate with programmers Contextualize the conversation with the real code Helps
- Exposes the project classes If you write in Ubiquitous Language your code should be easy to read. Makes the managers familiarizes with what programmers are doing
- Exposes the project classes If you write in Ubiquitous Language your code should be easy to read. Makes the managers familiarizes with what programmers are doing
- Exposes the project classes If you write in Ubiquitous Language your code should be easy to read. Makes the managers familiarizes with what programmers are doing
- We understand each other Software development is by its nature a series of translations and compromises. What the end user wants, what the customer is willing to pay for, and what is technically feasible rarely combine to form a unified set of features. In this talk we will explore how an Agile team can work to understand each other better, in particular at the communication divide between stakeholders and developers. We will show you how to develop a domain-specific ubiquitous language, how to lessen the responsibility gap between managers and developers, and how to use your codebase as the central source for documentation.