OLE Development Cycle
...
FAQ: Using OLE Tools and understanding documents
The following are excerpted responsibilities to be used by OLE Spec and Tiger Teams for the creation of functional specs and ultimate coding of library processes in OLE. The tasks and responsibilities represent the portions of our renewed project approach specific to Spec Writing and Requirements Analysis, in support of coding and development in 2012-13 for the completion of OLE 1.0 and beyond.Please refer to detailed wiki pages for individual roles, tools to aid in your success, and templates for completing documentation.
Phase 1: Specs
Phase 2: Coding
...
some simple definitions and answers to Frequently-Asked-Questions the Core Team and OLE developers have been asked. Over time, we will continue to insert additional resources, tips and tricks to this list in response to SME's (Subject Matter Experts, i.e. OLE library staff members) requests. To make suggestions for additional content to the FAQ, please email the Core Team, or add comments through the link at the bottom of this page.
This page is under development and content is continuously being added and edited. Please click on any of the questions below to jump to the discussion thread. Many hyperlinks are also connected in the content, and where images are included, click on the image or illustration to see an enlarged view.
3. What do you include in a functional specification?
4. What is the schedule for completing Fspecs?
5. What about technical details? How do we account for system considerations?
6. How do I learn about the other Fspec teams? What other resources are available?
7. I have heard that OLE is being developed using Agile. What does that mean for OLE?
8. Is there training or help available for using Google Docs, Kuali email, and Google Calendars?
9. What tools are provided to help the spec team complete their work?
10. Are the specifications and terminology that have been defined by other teams available for review?
1. What is an "Fspec"?
| Anchor | ||||
|---|---|---|---|---|
|
An F-spec is a "functional specification", or a set of functional library requirements for a specific library process or set of related activities. In OLE, we are isolating our Fspecs per User Story in order to define a small, easily specified set of requirements.
2. What is a User Story?
| Anchor | ||||
|---|---|---|---|---|
|
A user story is a very small, succinct set of functionality written as "As a <role>, I want <action> so that <result>". Examples would be "As a library staff member I need to create a purchase order to order a book.", or, "As a budget officer, I need to modify the fund that is allocated to an account."
3. What do you include in a Functional Specification?
| Anchor | ||||
|---|---|---|---|---|
|
A functional specification can include many things, but focuses on a general description of the work to be done by library users, the data elements or documents affected, and any business rules for managing the work specified.
| Anchor | ||||
|---|---|---|---|---|
|