The OpenOffice.org specification process demystified
Download as ODP, PDF0 likes497 views
The document outlines the OpenOffice.org specification process, emphasizing the importance of clear and complete specifications for enhancing product quality and reducing errors. It provides a detailed framework for developing specifications, including tips for effective kickoff meetings, prioritization of features, and the creation of a specification template. Additionally, it highlights common pitfalls to avoid and encourages utilizing a structured approach to improve communication among stakeholders.
![Further Information and Feedback Specification Project on OOo Wiki http://wiki.services.openoffice.org/wiki/Category:Specification Specifaction Project Website http://specs.openoffice.org/ Specification Template http://specs.openoffice.org/collaterals/template/OpenOffice-org-Specification-Template.ott Feedback [email_address]](https://image.slidesharecdn.com/the-openofficeorg-specification-process-demystified4148/85/The-OpenOffice-org-specification-process-demystified-38-320.jpg)
The OpenOffice.org specification process demystified
- 1. The OpenOffice.org Specification Process Demystified Christian Jansen, Jörg Sievers Sun Microsystems The OpenOffice.org Specification Process Demistyfied Christian Jansen, Jörg Sievers Sun Microsystems
- 2. Why do we need specifications? Writing a specification A specification template - Why? Q&A Agenda
- 3. Why do we Need Specifications?
- 4. How many test cases have to be created after this change? Negative values can now be entered here
- 5. ... Way too many But...
- 6. At least 12 test case representatives are needed for methodical testing
- 7. Examplary Test Case Design To reduce the count of test cases some black-box methods (here: equivalence class partitioning with boundary value analysis ) are being used. Find for each equivalence class a representative test case. Combine all valid classes with one invalid class.
- 10. Errors & Costs Ebert C., Dumke R (Hrsg.), Software-Metriken in der Praxis, Springer, Berlin/Heidelberg, 1996
- 11. Errors & Efforts on OOo QA evaluates issue Program Management sets target Developer Evaluates issue Sets up workspace Fixes issue Builds workspaces Evaluates fix QA evaluates fix in installation set Release Engineering integrates workspace QA Evaluates fix on master workspace Closes issue Customer installs fixed version
- 12. Specifiying saves your time You increase the product quality You save others' time You can increase test coverage systematically if needed Conclusion
- 14. Todays Process Plan Do Review / Improve
- 17. These pre-requisites are needed A requirement (customer need).... ... and an i-Team Development starts with a kickoff chat (IRC #openoffice, GAIM, ...) How to Write a Specification?
- 18. Develop a common sense of the goal Introduce the feature Nail down the priorities Prioritize the sub-feature Kicking off a New Feature...
- 19. Nail down the responsibilities State clearly who is responsible for what Let the i-Team know who delivers what Always keep the customer in mind Wether an internal stakeholder or external client, the customers satisfaction must be top priority Kicking off a New Feature...
- 20. Don't: Design the feature: This chat is for planning only. If there's design to be done, schedule another chat for that. Try to solve technical problems Don't get bogged down in details at this first chat. No Agenda As this is a planning chat, this chat needs to be prepared. L ong, unproductive chats exhaust people. The Dont's in a Kickoff
- 21. I-Team Kickoff Detailed feature / sub-feature planning First design sessions Plan
- 22. Create prototypes Write specification Do
- 23. Review i-Team reviews specification Based on three essential rules R1: Complete R2: Clear R3: Simple
- 24. Specification Rules R1: Complete First and foremost a specification has to be complete. That means all relevant aspects of a feature have to be captured. R2: Clear Each statement has to be unambiguously clear to Development, QA, User Experience, Documentation. R3: Simple Each statement shall be as short and as simple as possible.
- 25. Reduction of defects in specification. Reduction of defects in implementation. Improve
- 26. Finish Specification and implementation must be identical Implementation Specification
- 27. A Specification Template - Why?
- 28. A Specification Template - Why? It simplifies writing specifications, It centralizes all information It gives you clear guidance on: “ What ” belongs to a specification, “ How ” to write a specification, and... ...It automates common tasks like specifying user interfaces
- 29. A Specification Template -Why? ...and thus it saves you and others time...
- 30. Issues of the Old Spec. Template Separation between specification template and specification guide No links to required companion documents Unnecessary sections Process related aspects (e.g. i-Team approvals) A motivation section, an user scenarios section, etc. Missing rules on how to write and read a specification Lack of examples
- 31. The New Specification Template
- 32. There is Lots More Stuff in it ... A Help which guides you through the template
- 33. There is Lots More Stuff in it ... Specification Status Section Abstract Section: The source for the “Guide to new features”
- 34. There is Lots More Stuff in it ... The i-Team
- 35. There is Lots More Stuff in it ... Links to important reference documents
- 36. There is Lots More Stuff in it ... Tooling for “automatic” User Interface specification
- 37. There is Lots More Stuff in it ... Concrete examples for junior specification writers
- 38. Further Information and Feedback Specification Project on OOo Wiki http://wiki.services.openoffice.org/wiki/Category:Specification Specifaction Project Website http://specs.openoffice.org/ Specification Template http://specs.openoffice.org/collaterals/template/OpenOffice-org-Specification-Template.ott Feedback [email_address]
- 39. The OpenOffice.org Specification Process Demystified Christian Jansen, Jörg Sievers Sun Microsystems Thank You! Christian Jansen, Jörg Sievers Sun Microsystems