Goal of this presentation is to bring the specification process closer to the OpenOffice.org community. Specifications are an essential and central part of the OpenOffice.org development process. They serve as working base for Development, User Experience, Quality Assurance and Documentation.

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

8. Test Case Representatives

9. More Impacts...

10. Errors & Costs Ebert C., Dumke R (Hrsg.), Software-Metriken in der Praxis, Springer, Berlin/Heidelberg, 1996

13. Writing a Specification

14. Todays Process Plan Do Review / Improve

15. Tomorrows Process

16. No Waterfall Model

27. A Specification Template - Why?

29. A Specification Template -Why? ...and thus it saves you and others time...

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