We are in the course of drawing the big picture for the next Riena releases and would like to share your ideas and requirements. In this post I summarize Riena’s status of code and documentation quality, how we got there during the previous months and how we are trying to implement an ongoing improvement process. With your feedback we will be keeping on track, realizing the most painful quality issues and constantly going to hone our deliverables.
During the previous months we have been following the approach of consequently plan and spend a certain fraction of our sprints into quality improvements. We faced a couple of occasions when we deemed it best to follow the ‘code first’ rule, which (naturally?) turns out to harm Riena’s quality. But an overall retrospective now shows a remarkable push in the quality of different areas we have been touching:
- interface and parameter class documentation
- extension points documentation
- getting started tutorial
- efficient usage of memory and cpu resources
- eclipse-conform naming of extension points; injector handles both old and new names
which all took place under the hood of Riena’s public interfaces. Additionally we decided to let the Riena users pay an affordable price when we broke some of the APIs in order to improve
- consistent naming of interface methods
- cleanup of dead-end interface methods
- execution efficiency
We are and will be carrying on closing Riena’s documentation and resource consumption gaps. Simultaneously we undertake to deliver future enhancements and features together with a high level of quality that makes the Riena users’ life easier hopefully right from the start. Please share your thoughts on quality requirements that you have on Riena. Which grade of fulfillment do you experience? We also would be happy to compare notes on vision, ideas or processes to balance ‘code first’ and ‘non functional quality’ that you are following in your daily work.
I really appreciate the hight quality of riena code and the bunch of unit-tests.
I know, that we (at redView) have to do much to reach this level – but we’re working hard on this
in our work at first we went the ‘code first’ way to get the core functionality ready – now we’re working on quality, tests, documentations – hopefully in the future this will be balanced right.
for us it’s a real pleasure to use Riena API, Extensions etc.
ekke