OLE FAQs

FAQ: Using OLE Tools and understanding documents

The following are 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.

">1. I just joined a spec team - what does that mean?

There are several steps you need to take:

1. Sign up for a KIS account
2. Become familiar with your team's KIS page and bookmark it. It has useful links, calendar events, team members and the email list serve (listed under the team admins).
3. Read through [OLE:Getting Started with OLE - OLE 101] - this page has links to great OLE introductory materials.
4. Learn about the process: [OLE:OLE Spec Writing & Requirements Analysis] and Spec Team- Roles in Spec Writing

">2. What is an "Fspec"?

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.

">3. What is a User Story?

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."

">4. What do you include in a Functional Specification?

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.

See our spec templates page for templates (that include explanations) and samples.

">5. What is the schedule for completing Fspecs?

Functional specifications are completed in several phases by the designated Fspec team. While teams are encouraged to be self-organizing, each team will be given deadlines for completing a group of specifications. Upon completion of the final documentation, teams will be requested to be available for some ongoing Q&A with the core team and developers, and then a subset of volunteers will be requested to participate in future testing.

• See Spec Team- Roles in Spec Writing for sample spec timelines
• See OLE Development Cycle to review the entire process

6. Tools of OLE

">KIS

Tip: Bookmark your team's KIS page

To guarantee access to all OLE materials (Wiki, Jira, Google Docs, KIS Calendars & Team pages), it is recommended you be logged into KIS.

• Link to
  Unknown macro: {link-window}

  Create a KIS account

• How to create a KIS account wiki page

">Kuali Email

Everyone in Kuali that has KIS credentials will also have a Kuali email address (_____@kuali.org). You may synch your Kuali email with your primary email client by using the help center for your specific application. Please note: some scheduling notifications or calendar reminders that originate in your Kuali calendar and email may not forward to your primary email client. Be aware of this and check your Kuali email periodically. Please refer to the

">Jira

Be sure to log in to Jira using your KIS account. If you know the Jira number, just do a quick search.

If you do not know the Jira number, choose Search for Issues from the Issues menu (see image at right). This will allow you to do a simple search using the left side panel. Choose OLE as the project, otherwise you will search all of Kuali.

• For more in depth searching of Jira, including advanced searching, see the
  Unknown macro: {link-window}

  Guide to Searching Issues on Jira

• If you are having troubles accessing Jira, see
  Unknown macro: {link-window}

  How to Access Jira

">Google Docs

• Introduction to Google Docs is a wiki page we have created that contains basic Google how-to's.
• Google Docs's
  Unknown macro: {link-window}

  Help Center

  offers video tutorials, formatting assistance and discussion threads to answer common questions.
  A few things to note about Google Docs are:
  • Page Refresh: Google Docs will sometimes show only partial lists of documents. It's particularly frustrating when you know a document is in the file. Please click on your browser's refresh button to see a full folder view.
  • KIS: You must be logged into KIS to access documents stored in Google (See KIS for instructions). You can also access your team's Google Docs folder through the KIS page.
  • Mapping "My Collections": When you first open Google Docs, your left menu will not display any OLE file folders - only those owned by you. In order to map OLE folders into your "My Collections", please use these
    Unknown macro: {link-window}

    Instrustions

    to map the OLE project folders. You only have to do this once, and then Google Docs navigation will be much easier.

">Google Calendar

Please refer to the online

for tutorials and discussion threads.
You may create additional calendars, or access other Kuali OLE Team calendars. Open one of the linked OLE calendars, and click on the +Google Calendar button in its lower right corner to add it to your "Other Calendars" view.

[OLE:OLE Meeting, Conference Resources & Calendars]

• The OLE Scheduling Calendar is the master schedule for OLE
• The OLE Demo Calendar is new - this is to communicate when demos are to occur and also when the demo environment is down.

">Webex

OLE uses Webex for team calls:

We have a limited number of accounts so if you need to set up a meeting, please contact Carla North (cnorth@indiana.edu) or Nora Roggeveen-Sams (nroggeve@indiana.edu).
To find out more about connecting and a link to the Webex user's manual, see [OLE:OLE Meeting, Conference Resources & Calendars].

For more tools used by spec teams, see [OLE:OLE Tools & Working Teams]

">7. What does this word mean? or that acronym?

We are compiling a [Glossary of Terms] for use by and between all functional and specification teams, so that we share common understanding of terms, and can share those with developers.
See the link to the full Google Spreadsheet for the most current version as well as tabs to additional information.

">8. What about testers?

Spec Teams, Tiger Teams and SA's will be called upon to participate in the testing of OLE. This begins during the documentation of User Requirements (Acceptance Criteria), continues as coding is begun to formulate Test Scripts, and culminates in user testing/executing Test Scripts. There is more information about testers on the Acceptance Criteria, Test Scripts & Testing page.

">9. How do I find out what has been done and what's in the future plans of OLE?