Pachyderm Requirements Document (version 1 by qor17644

VIEWS: 35 PAGES: 102

									Requirements Specification
             version 1.5




                      May 19, 2004
Pachyderm Requirements Document (version 1.5)
Contents
1. Introduction .....................................................................................................3
   1.1 Purpose of This Document ................................................................................................ 3
   1.2 How to Use This Document................................................................................................ 3
   1.4 Overview of the Requirements Document........................................................................ 4
2. General Description........................................................................................6
   2.1 About the Project ................................................................................................................ 6
   2.2 Project Goals ....................................................................................................................... 7
   2.3 User Characteristics ........................................................................................................... 7
   2.4 General Constraints............................................................................................................ 8
3. Core Requirements Listing ............................................................................9
   3.1 Essential Requirements ................................................................................................... 10
      3.1.1 System, Database & Security Requirements .............................................................. 10
      3.1.2 User Interface & Usability Requirements..................................................................... 18
      3.1.3 Metadata Requirements .............................................................................................. 25
      3.1.4 Template Requirements .............................................................................................. 28
      3.1.5 Help & Documentation Requirements ......................................................................... 37
   3.2 Useful Requirements ........................................................................................................ 38
      3.2.1 System, Database & Security Requirements .............................................................. 38
      3.2.2 User Interface & Usability Requirements..................................................................... 45
      3.2.3 Metadata Requirements .............................................................................................. 50
      3.2.4 Template Requirements .............................................................................................. 52
      3.2.5 Help & Documentation Requirements ......................................................................... 56
   3.3 Desirable Requirements ................................................................................................... 58
      3.3.1 System, Database & Security Requirements .............................................................. 58
      3.3.2 User Interface & Usability Requirements..................................................................... 66
      3.3.3 Metadata Requirements .............................................................................................. 69
      3.3.4 Template Requirements .............................................................................................. 70
      3.3.5 Help & Documentation Requirements ......................................................................... 71
4. Gap Requirements (Placeholder) ................................................................73
5. Wishlist Requirements .................................................................................74
      5.1 System, Database & Security Wishlist............................................................................ 74
      5.2 User Interface & Usability Wishlist.................................................................................. 81
      5.3 Metadata Wishlist............................................................................................................ 82
      5.4 Template Wishlist............................................................................................................ 83
      5.5 Help & Documentation Wishlist ...................................................................................... 84
6. Process Requirements .................................................................................86
7. Out of Scope Requirements.........................................................................89
8. Assumptions ...............................................................................................100
9. Issues...........................................................................................................102




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                                                               2
Table of Contents
1. Introduction
This document contains the system requirements for this project.

Date(s): May 5, 2004; revised May 19, 2004
Prepared by: Rachel S. Smith & Pachyderm Requirements Team

Document status:           Draft   X Proposed          Validated   Approved

1.1 Purpose of This Document
This document is intended to guide development of this project. It will go through several stages
during the course of the project:
    1. Draft: The first version, or draft version, is compiled after requirements have been
        discovered, recorded, classified, and prioritized.
    2. Proposed: The draft document is then proposed as a potential requirements
        specification for the project. The proposed document should be reviewed by several
        parties, who may comment on any requirements and any priorities, either to agree, to
        disagree, or to identify missing requirements. Readers include end-users, developers,
        project managers, and any other stakeholders. The document may be amended and re-
        proposed several times before moving to the next stage.
    3. Validated: Once the various stakeholders have agreed to the requirements in the
        document, it is considered validated.
    4. Approved: The validated document is accepted by representatives of each party of
        stakeholders as an appropriate statement of requirements for the project. The developers
        then use the requirements document as a guide to implementation and to check the
        progress of the project as it develops.

1.2 How to Use This Document
We expect that this document will be used by people with different skill sets. This section explains
which parts of this document should be reviewed by various types of readers.

Types of Reader
System developer. You are working on the team that is building the project, or you are a
consultant who has been requested to review this document. Sections 2 and 3 will be of most
interest to you. You may also wish to review sections 8 and 9.

User interface designer. You are working on the team that is building the project, or you are a
consultant who has been requested to review this document. Sections 2 and 3 will be of most
interest to you. You may also wish to review sections 8 and 9.

End-user. You are a student, museum or educational institution staff person, or faculty member
who will create learning objects with Pachyderm, use such learning objects, or both. Section 2 will
give you a general overview of the project. In Section 3, subsections 3.1 and 3.2 are likely to be
of most interest to you.

Other readers. Section 2 will give you a general overview of the project. In Section 3, subsections
3.1 and 3.2 are likely to be of most interest to you.

Technical Background Required
Section 2 requires no special technical background. For Section 3, some familiarity with the
concept of using authoring tools to create learning objects is helpful. Especially for Sections 3.1.3,
3.2.3, 3.3.3, and 5.3, an understanding of the idea of attaching metadata to assets or objects is
helpful.




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                       3
Section 1: Introduction
1.4 Overview of the Requirements Document
This section (Section 1) serves as an introduction to the document.

Section 2: General Description
Section 2 contains an overview of the product in general terms, including major product functions
and expected user characteristics.

Section 3: Core Requirements Listing
This section comprises the bulk of the requirements specification. The requirements have been
sorted in priority order:

Essential Requirements will be included in the October 2004 release.

Useful Requirements may be included in the October 2004 release as time permits. These
requirements will have the highest priority for the next version of Pachyderm.

Desirable Requirements will probably not be included in the October 2004. These requirements
will have a lower priority for the second release, but may have a higher priority in subsequent
releases.

Requirements in each of the above categories have been further divided according to system
component:

System, Database, and Security: These are requirements which relate to how the system is built
(including the authoring tool, the assets database, the publishing process, and
authentication/security procedures).

Usability and User Interface Design: Requirements that deal with the interface and with the user's
interactions with the system (both authoring tool and end product, or templates) fall into this
category.

Metadata: These requirements have to do with what types of metadata will be collected, how and
where metadata will be stored, and any special steps the system will take to collect, store, or
organize metadata.

Templates: Requirements which are specific to the end product, the final published modules, fall
into this category.

Help and Documentation: Requirements relating to the help system, user manuals, and other
types of documentation are collected in this category.

Section 4: Gap Requirements Listing
This section will contain requirements that were identified late in the process. It is empty at
present.

Section 5: Wishlist
These are requirements which may be implemented in some future version of Pachyderm.

Section 6: Process Requirements
These generally describe actions we think users might take while creating or using Pachyderm
modules. Process requirements were captured during the requirements gathering effort but are
not directly relevant to development.

Section 7: Out of Scope Requirements


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                      4
Section 1: Introduction
Requirements that have been determined to be beyond the scope of the Pachyderm project are
noted here. These were captured during the requirements gathering effort and are noted for the
sake of completeness.

Section 8: Assumptions
Basic facts or constraints that we expect to work with are listed here.

Section 9: Issues
Open questions which we need to discuss or resolve are included in this section.




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                    5
Section 1: Introduction
2. General Description
This section contains an overview of the project, including why it was conceived, what it will do
when complete, and the types of people we expect will use it. We also list constraints that were
faced during development and assumptions we made about how we would proceed.

2.1 About the Project
The Pachyderm 2.0 Project is a partnership led by NMC: The New Media Consortium and the
San Francisco Museum of Modern Art (SFMOMA), and funded by the Institute for Museum and
Library Services (IMLS). The project brings software development teams and digital library
experts from five NMC universities together with counterparts from five major museums to create
a new, open source authoring environment for creators of web-based and multimedia learning
experiences. The new tool will be based on Pachyderm, the authoring and publishing tool
developed by SFMOMA to author its successful series, Making Sense of Modern Art.

Developed by SFMOMA to make the publication of modular and updateable rich media an easy
task, Pachyderm has allowed non-programmers to create a variety of engaging resources that
draw from the digital collections of SFMOMA. The result has been detailed interactive learning
programs such as Ansel Adams at 100, and Eva Hesse. To date, literally millions of online and in-
museum users have used the interactive learning programs authored using Pachyderm at
SFMOMA.

The Pachyderm 2.0 Project is creating an interoperable, robust, easily distributable version of
Pachyderm that will be open-source and include a wide range of pedagogical templates.
Pachyderm 2.0 will be piloted by leading museums and universities across North America in an
extensive series of field tests. The learning materials created with Pachyderm 2.0 will be
optimized for Internet delivery, easily reusable, and conformant with key search, archival, and
cataloging standards. The final product will be made available to the field at no charge as an
explicit goal of the project.

The effort brings together the metadata and other expertise of the NMC’s library community, the
technological expertise in infrastructure and programming of key university members, and the
expertise of a team of experienced interactive producers from five museums and several NMC
schools advising on interface design, audience needs, and the technological capacities of future
students, faculty, curatorial staff, and museum users.

                                         Project Leads
                                  NMC: New Media Consortium
                            SFMOMA: San Francisco Museum of Modern Art

                       University Partners                 Museum Partners
           Case Western Reserve University                 Berkeley Art Museum
                 California State University               Cleveland Museum of Art
                      University of Calgary                Fine Arts Museums of San Francisco
                   Northwestern University                 Metropolitan Museum of Art
                       University of Arizona               San Francisco Museum of Modern Art


Central to the project is the development of at least 20 richly interactive learning experiences by
the project’s museum and university partners using the new environment. These will constitute a
comprehensive test of the software in at least 10 different settings, and prove its worth as an
authoring environment — as well as provide exemplars for the range of ways in which the tool
might be used.

The Pachyderm project is supported by a grant from the Institute of Museum and Library Services (IMLS)




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                            6
Section 2: General Description
2.2 Project Goals
The project has two goals related to the development of the Pachyderm 2.0 authoring
environment. The first is to move the software to an “open platform” model in which the tool could
be installed on any server, with Linux, Window, and Mac servers to be tested. The second is to
redesign the authoring interface's look and feel, moving it to a completely open-source approach,
and putting the code into place that will enable a future shift to a component-based rather than a
template-based system.

Activities related to the first goal primarily involve rewriting the original Pachyderm code to
incorporate open-source components such as MySQL rather than the original FileMaker Pro
database, and rewriting scripts and other components now in Visual Basic in the more open PHP.

To accomplish the second goal, Pachyderm is conceptualized as having two major parts. The
first is the “Authoring Interface,” which includes the web pages into which authors enter the
content for their modules and the logic required to make those pages functional. Users can use a
web browser on any machine to access the authoring interface. This half of Pachyderm is being
completely moved to open-source in the IMLS-funded Pachyderm project.

The “Publishing Component” resides on a server and runs commands issued by the Authoring
Interface to turn data from the database into a finished Pachyderm module (Flash & media files
ready to run on a web server or CDROM). Because this part of Pachyderm works well in its
current form, it is not being rebuilt under the IMLS-funded project, but its related code base is
being released with the other components of Pachyderm 2.0 as part of the project’s “open-
source” philosophy.

2.3 User Characteristics
There are 4 major groups of users for Pachyderm: students, faculty, museum personnel, and
museum visitors. We have also identified two secondary groups: support staff and librarians.
Other types of users exist but these are the primary groups.

The "typical" Pachyderm user may have a lot of computer experience, or none at all. The
expected age range is anywhere from a grade school student to a retiree. Note that there are two
ways to "use" Pachyderm: authoring a module or viewing a completed module. We envision
authoring not as belonging only to faculty or museum staff, but potentially to students and visitors
as well.

Sample personae, or descriptions of imaginary people, are included below for each of the four
major user groups. These descriptions, and others, were used to help generate scenarios about
how Pachyderm could be used. Potential requirements were then drawn from the scenarios.
These personae are ficitional and bear no intentional resemblance to any individual person.

Students
Liam C., Freshman
Liam is a freshman at a small liberal arts college. He has not decided on a major yet, though he
loves music and is an accomplished pianist. Liam is visually impaired and cannot read normal
text on a computer screen. He can distinguish large shapes and can read if the type is very
large. He learns easily through auditory means and has a roommate who will describe diagrams
on the white board to him when they are in the same class.

Sharon T., High School Freshman
Sharon is a high school freshman, with strong creative writing and multimedia skills, and very
tech-savvy. She was a key member of her middle school yearbook team, and loves learning and
using many multimedia tools. She loves AIM (Instant Messaging), plays several musical
instruments, and loves being part of a social group or team.. She loves to play around with all
kinds of visual presentation ideas and features of multimedia tools she learns—and often knows


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                       7
Section 2: General Description
more about how to use these tools than other students or her teachers. She loves visual arts and
has considered being an animator, movie-maker or script writer for TV. She is actually very
knowledgeable about math and science, but has less interest in these areas.

Faculty
Chris F., Marketing Professor – Early Adopter
Chris is a professor of Marketing and an early adopter of technology. She has taught for seven
years and is up for tenure at the end of the year. She is always looking for better ways to teach
and often uses her weekends to go online to see what new learning objects are available. She
often uses MERLOT as a resource. She wants to pull together a strong syllabus this year, using a
variety of media, and really wants to author her own presentation available online for others to
use. (Giving back to MERLOT.)

Shayla W., Chemistry Professor
Shayla is a Chemistry professor at Oceanview University. Shayla teaches courses mainly for
undergraduates. She keeps a laptop at home and uses her university provided machine in her
office. Shayla generally uses her computers for communication with her undergraduate students
via email, chemistry-specific data analysis tools for her experiments, and Microsoft Word for
generating grants, reports, and recommendations. Shayla is faced with the challenge of teaching
large lecture hall classes for undergraduates and is always looking for ways to motivate and
entice students to prepare for the course, collaborate with their peers, and participate in the class.

Museum Personnel
Charles H., New Media Director
Charles is responsible for new media and works with curators who do not want to be Pachyderm
authors but want to have him make projects for them. He needs to interpret the content delivered
by the curator and convert it into something that will be easily understood and appreciated by the
visitors. His technical skill level is high.

Jen T., Docent Trainer
Jen presents information about the museum's exhibits to her docents prior to the exhibitions. She
is familiar with the museum's kiosks (from an end-user perspective) but does not use computers
on a regular basis otherwise.

Museum Visitors
Carl M., Retiree
Carl is a sixty-eight year-old visitor who is retired and looking for ways to use his time that
stimulate and interest him. He has an Internet account at the local library and does some limited
e-shopping.

Marjorie R., Stay-at-home Mom
Marjorie drops her kids off in the art classes and likes to do something in the Museum while she
waits for the classes to be finished. She believes in the arts and wants to have more information
about the permanent collection. She has limited technical skills and does not use a computer at
home.

2.4 General Constraints
Software projects are generally constrained by time, budget, available resources, and technical
feasibility. In the case of Pachyderm 2.0, both time and budget are limited by the terms attached
to the grant which funds the project. Available resources are less constrained as the Pachyderm
Project partner institutions have all made significant commitments to the success of the project
above and beyond the resources provided by the funding agency. The technical feasibility of the
project is also less constrained, as a working prototype (Pachyderm 1.0) already exists and a
structured process has been built that will ensure all new feature requests are carefully evaluated
for technical feasibility.


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                        8
Section 2: General Description
3. Core Requirements Listing
This section lists specific requirements for Pachyderm 2.0. Requirements are divided according to
priority:

Essential Requirements will be included in the October 2004 release.

Useful Requirements may be included in the October 2004 release as time permits. These
requirements will have the highest priority for the next version of Pachyderm.

Desirable Requirements will probably not be included in the October 2004. These requirements
will have a lower priority for the second release, but may have a higher priority in subsequent
releases.

Wishlist Requirements will not be included in the October 2004 release. These requirements
will be re-examined before each release to see if new technologies or techniques may allow them
to be re-prioritized. See Section 5 for Wishlist Requirements.

Section 3 is organized as follows:

3.1 Essential Requirements
       3.1.1 System, Database & Security Requirements
       3.1.2 User Interface & Usability Requirements
       3.1.3 Metadata Requirements
       3.1.4 Template Requirements
       3.1.5 Help & Documentation Requirements

3.2 Useful Requirements
       3.2.1 System, Database & Security Requirements
       3.2.2 User Interface & Usability Requirements
       3.2.3 Metadata Requirements
       3.2.4 Template Requirements
       3.2.5 Help & Documentation Requirements

3.1 Desirable Requirements
       3.3.1 System, Database & Security Requirements
       3.3.2 User Interface & Usability Requirements
       3.3.3 Metadata Requirements
       3.3.4 Template Requirements
       3.3.5 Help & Documentation Requirements




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                   9
Section 3: Core Requirements Listing
3.1 Essential Requirements

3.1.1 System, Database & Security Requirements
    3.1.1.1 Persistent user accounts (#29)
          The system must support persistent user accounts, allowing users to log in (and out as
          needed) to access data tied to their account.
          Rationale: Users will have basic data that should be "remembered" by the system so
          users don't have to look it up or enter it by hand each time they use Pachyderm.
          Notes: This refers to users of the Authoring Tool (not to users of completed modules).
          Volatility: stable
          Clarity: refine (We need a good definition of what data would be tied to their accounts.)
          Recorded by: Rachel Smith
          System Components: Authoring Tool
          Stakeholders
                      Developers: Programmers, User Interface Designers
                      End Users: Authors (Education), Authors (Museum)
          Official Priority: essential
          Desired Priority: useful

    3.1.1.2 Admin accounts (#117)
          A login procedure is required for administrators to enter the system.
          Rationale:
          Notes:
          Volatility: stable
          Clarity: refine (Not sure if there is a definition anywhere about what an admin can do on
          the system. Partial list: user accounts, privilege granting)
          Recorded by: Wendy Shapiro
          System Components: Authoring Tool
          Stakeholders
                      Developers: Programmers, Pedagogy Experts (templates), User Interface
                      Designers, Metadata Experts
                      End Users: Maintenance Staff, Authors (Education), System Administrators,
                      Production Staff, Authors (Museum), Project Managers
          Official Priority: essential
          Desired Priority: essential

    3.1.1.3 Automated password retrieval (#294, revised)
          Users who forget their passwords should be able to log in.
          Rationale: It may not be convenient or possible for users to make a physical visit to
          change or retrieve a forgotten password.
          Notes:
          Volatility: medium-term change likely
          Clarity: refine (Not sure that "challenge questions" should be part of this requirement.)
          Recorded by: Claire Stewart
          System Components: Authoring Tool
          Stakeholders
                      Developers: Programmers
                      End Users: Authors (Education), Authors (Museum), System Administrators
          Official Priority: essential
          Desired Priority: useful

    3.1.1.4 Listing Digital Assets (#30, revised)
          Users should be able to see at a glance what resources are available for them to use.


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                         10
Section 3.1.1: System Essential Requirements
          Rationale:
          Notes:
          Volatility: stable
          Clarity: refine (I think this is referring to assets, but what type of "collections" do you
          mean? Priority might change if this is not a simple list of assets.)
          Recorded by: Rachel Smith
          System Components: Authoring Tool, Assets (Database)
          Stakeholders
                      Developers: User Interface Designers, Programmers
                      End Users: Authors (Education), Production Staff, Authors (Museum)
          Official Priority: essential
          Desired Priority: useful

    3.1.1.5 Persistent archive of assets (#32)
          The system should maintain an archive or database of created assets so they may be
          reused by authors.
          Rationale: We already have such a database. It saves time for users.
          Notes: Already exists.
          Volatility: medium-term change likely
          Clarity: refine (I'm not sure what a "created asset" is and what "appropriate authors"
          implies. )
          Recorded by: Rachel Smith
          System Components: Assets (Database)
          Stakeholders
                      Developers: User Interface Designers, Programmers
                      End Users: Authors (Education), Production Staff, Authors (Museum)
          Official Priority: essential
          Desired Priority: essential
          Comments
          Rachel Smith: Includes #120 (formerly 3.1.1.7, System Essential).

    3.1.1.6 Database to store XML (#272)
          Pachydatabase should be able to store (or at least accept and spit out) XML as defined
          by the mythical metadata & interoperability standards
          Rationale: need to store stuff
          Notes:
          Volatility: stable
          Clarity: clear
          Recorded by: D'Arcy Norman
          System Components: Assets (Database)
          Stakeholders
                      Developers: Programmers, Metadata Experts
          Official Priority: essential
          Desired Priority: essential

    3.1.1.7 Online Accessibility (#111, revised)
          Allow users to use the authoring system via Internet
          Rationale:
          Notes:
          Volatility: stable
          Clarity: refine (Do different browsers need supporting? Different versions?)
          Recorded by: Wendy Shapiro
          System Components: Authoring Tool, Assets (Database)
          Stakeholders
                      Global Concern: Global Concern (all stakeholders)

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                           11
Section 3.1.1: System Essential Requirements
          Official Priority: essential
          Desired Priority: essential

    3.1.1.8 Pachyderm is optimized for internet delivery (#177, revised)
          Pachyderm productions can be accessed over the internet.
          Rationale: The user scenarios all assume that users are getting to both the authoring
          environment and the published units via a network in 99.8% of the cases. Off-line kiosk
          use in a museum or university environment will be the exception, not the rule.
          Notes: We have generally assumed Pachyderm only needs to produce broadband
          content. We might want to officially state this assumption.
          Volatility: stable
          Clarity: refine (See 111)
          Recorded by: John Weber
          System Components: Assets (Database)
          Stakeholders
                      End Users: Other End Users, Authors (Education), Production Staff, Viewers
                      (Museum), Authors (Museum), Viewers (Education)
          Official Priority: essential
          Desired Priority: essential
          Duplicates: Online Accessibility (#111)

    3.1.1.9 Performance (#174)
         Authoring tool must run rapidly enough so as not to be an impediment to progress
         Rationale: Frustrated authors will not use this tool
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Michelle LaMar
         System Components: Authoring Tool
         Stakeholders
                     Developers: Programmers
                     End Users: Authors (Education), Production Staff, System Administrators,
                     Authors (Museum)
         Official Priority: essential
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 4.1.20 (Process).
         Usability Group, Spring Meeting: System has to respond to user input within 3 seconds or
         display some indication of the progress. Validate through user testing.

    3.1.1.10      The authoring environment should be easy to install. (new)
         Individual departments, schools, or other organizations must be able to download and
         install their own Pachyderm authoring system. It should be possible to install a
         Pachyderm server on computers other than Tim's.
         Rationale: Lots of people will need to install it with minimal help.
         Volatility: stable
         Clarity: clear
         Recorded by: Rachel Smith
         System Components: Authoring Tool, Assets (Database)
         Stakeholders
                   Developers: Programmers
                   End Users: System Administrators
         Official Priority: essential
         Desired Priority: essential
         Comments

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                   12
Section 3.1.1: System Essential Requirements
         Rachel Smith: Combines System Essential requirements #121 (formerly 3.1.1.14), #130
         (formerly 3.1.1.13) and #286 (formerly 3.1.1.18).

    3.1.1.11      The authoring environment should be platform independent (#169)
         Pachyderm operates in and across more than one set of software,hardware and
         operating system configurations, giving institutions some leeway in how to install and
         support it.
         Rationale: We need this feature in order to make Pachyderm accessible to its core
         audience of institutions of higher education and museums.
         Notes: We need to define how interoperable we can afford to make Pachyderm in this
         iteration, balancing what is possible with what is desirable.
         Volatility: medium-term change likely
         Clarity: refine (Need to define exact platforms on which Pachyderm must operate.)
         Recorded by: John Weber
         System Components: Authoring Tool, Assets (Database), Other
         Stakeholders
                  Developers: Metadata Experts, Programmers, User Interface Designers
                  End Users: Project Managers, Maintenance Staff, System Administrators,
                  Production Staff
         Official Priority: essential
         Desired Priority: essential
         Duplicates: A downloadable installation of Pachyderm (#121), Pachyderm is *easily
         distributable* (#130)

    3.1.1.12      The Pachyderm Project should be open source (#214, revised).
         The authoring environment will be open source. Definition pending. The software
         environment, tools, and supporting code developed in this project, all to be created as
         “open source,” will be provided royalty-free to every not-for-profit museum, university, and
         library in the U.S.
         Rationale: We promised.
         Notes: I suspect that IMLS will want access to Pachyderm to be "open," but I doubt that
         they will argue that it needs to be open source from a purely programming point of view.
         Volatility: stable
         Clarity: refine (We need a tighter definition of what we mean by open source.)
         Recorded by: Michelle LaMar, et al.
         System Components: Authoring Tool, Assets (Database), Templates, Other
         Stakeholders
                   Global Concern: Global Concern (all stakeholders)
         Official Priority: essential
         Desired Priority: essential
         Duplicates: Pachyderm is Open Source (#158)
         Comments
         Mike Mattson: needs to be "Open Source License" who writes the license, NMC,
         SFMOMA?
         Rachel Smith: Combines System Essential requirements #214 (formerly 3.1.1.17) and
         #158 (formerly 3.1.1.15).

    3.1.1.13    The authoring environment will be implemented on a free, open-source
        platform (#88, revised).
         Make Pachyderm work on a free, open source server platform (e.g. .jsp, apache/tomcat,
         php, etc.)
         Rationale: So that it can be run on a wider variety of systems, reduce the cost of
         installation, and avoid Windows server security vulnerabilities.
         Notes: Strategies for this could include: Porting the existing code base to a new
         technology (.jsp) Completely re-implementing the design spec

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                      13
Section 3.1.1: System Essential Requirements
         Volatility: stable
         Clarity: clear
         Recorded by: Lou Zweier
         System Components: Authoring Tool, Assets (Database)
         Stakeholders
             Developers: Programmers
             End Users: System Administrators
         Official Priority: essential
         Desired Priority: essential
         Duplicates: Server Platform Independence (#269), Portability of server stuff (#286)

    3.1.1.14      Pachyderm is robust (#147, revised)
          The authoring tool does not crash routinely.
          Rationale: this requirement is in the "About the Project" document. If the authoring
          environment is too touchy, people will not want to stick with it.
          Notes: We need to define "robust."
          Volatility: stable
          Clarity: refine (Performance issues on various machines/OS's. Testing procedures.
          Definitions of "robust" and "satisfactory.")
          Recorded by: John Weber
          System Components: Authoring Tool
          Stakeholders
                      Developers: User Interface Designers, Metadata Experts, Pedagogy Experts
                      (templates)
                      End Users: Authors (Education), Production Staff, Maintenance Staff, Authors
                      (Museum), Project Managers
          Official Priority: essential
          Desired Priority: useful

    3.1.1.15      Delivery in multi-modes (#235)
          Authored presentations should be deliverable as online, CD-ROM and kiosk.
          Rationale:
          Notes:
          Volatility: stable
          Clarity: clear
          Recorded by: Michelle LaMar, et al.
          System Components: Authoring Tool, Templates
          Stakeholders
                      End Users: System Administrators, Project Managers, Viewers (Education),
                      Viewers (Museum), Production Staff, Maintenance Staff
          Official Priority: essential
          Desired Priority: essential
          Duplicates: Kiosk/Live Web Editions (#73)

    3.1.1.16      Can return to a saved work-in-progress (#195)
          Authors can come back later to work previously begun.
          Rationale: No one works in one sitting.
          Notes:
          Volatility: stable
          Clarity: clear
          Recorded by: Jared Bendis and Claire Stewart
          System Components: Authoring Tool
          Stakeholders




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                    14
Section 3.1.1: System Essential Requirements
                     Developers: User Interface Designers, Programmers
                     End Users: Authors (Education), Project Managers, System Administrators,
                     Authors (Museum), Production Staff
          Official Priority: essential
          Desired Priority: essential

    3.1.1.17      Sequence of Pachyderm Screens (#207, revised)
         The authoring tool should allow any screen type to be the first screen in a pachyderm
         presentation, and should allow any type to screen to link to any other type of screen.
         Rationale: Support flexibility in designing and modifying the structure of pachyderm
         presentations.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Lou Zweier
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Programmers, Pedagogy Experts (templates), User Interface
                  Designers
                  End Users: Authors (Education), Production Staff, Authors (Museum), Project
                  Managers
         Official Priority: essential
         Desired Priority: useful
         Comments
         Template Team: After using Pachyderm for years, SFMOMA staff would very much like
         to be able to do this.
         Rachel Smith: Formerly 3.2.1.12 (UI Essential). Includes #215 (formerly 3.4.2.2) and
         #282 (formerly 3.1.1.23).

    3.1.1.18      Publish multiple projects simultaneously (#211, revised)
         Authors can publish more than one project at the same time. Multiple authors should be
         able to publish their different projects from a single server at the same time.
         Rationale: Authors may author over time and publish at once.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Jared Bendis and Claire Stewart
         System Components: Authoring Tool, Other
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: essential
         Desired Priority: desirable
         Comments
         Rachel Smith: Formerly 3.2.1.16 (UI Essential)

    3.1.1.19      Asset regeneration - optimize (#316)
         Currently when new assets are regenerated, the database is queried and **every single
         asset** is regenerated, even if it already exists and hasn't changed. Not only does this
         take a long time (4-5 hours at SFMOMA) and produce an ungodly error log, but it is not at
         all user-friendly. One should be able to regenerate new and changed assets only, by
         selecting them in front.
         Rationale: If one needs, say, just one more asset one should be able to have it available
         in a reasonable timeframe.
         Notes:

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                     15
Section 3.1.1: System Essential Requirements
         Volatility: stable
         Clarity: clear
         Recorded by: Mark
         System Components: Authoring Tool, Assets (Database)
         Stakeholders
                  Developers: Programmers
                  End Users: Authors (Education), Production Staff, Authors (Museum)
         Official Priority: essential
         Desired Priority: useful
         Comments
         Michelle LaMar: This is almost a bug.
         Rachel Smith: Formerly 3.1.2.15 (System Useful).

    3.1.1.20 Metadata can be batch-imported (1 or more at a time) as a delimited (tab- or
        comma-) text file (#255, revised).
         Two options for handling the mapping: prepare the text exactly according to what
         Pachyderm will understand, AND/OR, map on the fly. We suggest: on the fly, with some
         kind of a visual tool to match incoming data (fields) to available Pachyderm Dublin Core
         elements.
         Rationale: Reduce redundant data entry and assure consistency with source data.
         Remove barrier to entry for potential authors, via this centralized, automated functionality.
         Notes: Especially important for any media file requiring an Object ID
         Volatility: stable
         Clarity: clear
         Recorded by: Peter Samis
         System Components: Assets (Database), Other
         Stakeholders
                  Developers: Programmers, Metadata Experts
                  End Users: Authors (Education), System Administrators, Authors (Museum)
         Official Priority: essential
         Desired Priority: essential
         Comments
         Metadata Team: Includes requirements #255, and #239 (formerly 3.3.1.3). Related to
         #241 (System Useful).
         Rachel Smith: Formerly 3.1.3.6 (System Desirable).

    3.1.1.21   The database has a field(s) for rights and copyright information (#81,
        revised).
         The Pachyderm database must have a field or fields to allow entry of rights and copyright
         information for identification purposes (where did it come from and who created the
         record), and for declaring the rights (who is allowed to use it under what circumstances).
         Entry or application of this information, however, will not be enforced. This means that
         users are not forced to supply this information, and the Pachyderm system does not
         prevent authors from using assets in a manner outside of the uses allowed.
         Rationale:
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Holly Witchey
         System Components: Authoring Tool, Assets (Database), Other
         Stakeholders
                  Global Concern: Global Concern (all stakeholders)
         Official Priority: essential
         Desired Priority: wishlist
         Comments


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                       16
Section 3.1.1: System Essential Requirements
         Metadata Team: This is based on requirements #203 (formerly 3.3.1.1), #81, and #67
         (formerly 3.9.3.6).
         Rachel Smith: Formerly 3.6.1.3 (System Wishlist).




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                 17
Section 3.1.1: System Essential Requirements
3.1 Essential Requirements (continued)

3.1.2 User Interface & Usability Requirements
    3.1.2.1 User Friendly Interface Design (#113)
         Features should be obvious and accessible on the web pages via clear icons. Options,
         such as printing, should be simple and easy to adopt.
         Rationale: Adopt “Instructional Design” theory to web (user interface) development.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Wendy Shapiro
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Pedagogy Experts (templates), User Interface Designers, Metadata
                  Experts, Programmers
                  End Users: Viewers (Museum), Other End Users, Viewers (Education)
         Official Priority: essential
         Desired Priority: useful

    3.1.2.2 KISS (#276)
         Keep the interface simple. not all users will have propellers on their heads...
         Rationale: ease of use
         Notes:
         Volatility: stable
         Clarity: clear (Can't do much about the propellers, I guess)
         Recorded by: D'Arcy Norman
         System Components: Authoring Tool, Assets (Database), Templates, Other
         Stakeholders
                  Developers: User Interface Designers, Pedagogy Experts (templates),
                  Programmers
                  End Users: Authors (Education), Authors (Museum), Production Staff
         Official Priority: essential
         Desired Priority: useful

    3.1.2.3 Accessibility for Pachyderm authoring interface (#234, revised)
         Persons with disabilities must be able to use the Pachyderm authoring environment,
         according to ADA/Section 508 accessibility codes.
         Rationale: Universities and gov't institutions may be required to comply with accessibility
         codes.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Tim Svenonius
         System Components: Authoring Tool
         Stakeholders
                  Developers: Pedagogy Experts (templates), Programmers, User Interface
                  Designers, Metadata Experts
                  End Users: Project Managers, Authors (Museum), Authors (Education),
                  Production Staff
         Official Priority: essential
         Desired Priority: essential




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                     18
Section 3.1.2: UI & Usability Essential Requirements
         Comments
         Unknown: Much easier in the html authoring side to do this, than perhaps making the
         presentation side (flash) completely accessible.
         Rachel Smith: Formerly 3.2.1.5. Replaces #138 (formerly 3.2.1.3).

    3.1.2.4 Accessibility for Pachyderm presentations (#226, revised)
         Accessibility for Pachy presentations must be implemented in the Flash shells. Newer
         versions of Flash (MX & later) support ADA/Section 508 accessibility compliance. E.g.,
         need to have text field associated with images, graphics and other non-textual elements
         that contain a visual description of that element; the user should be able to adjust the text
         size on the screen when viewing the learning object or select text reader version; etc.
         Rationale: Certain institutions (federal & state funded) are required to make all their
         public websites accessible.
         Notes:
         Volatility: stable
         Clarity:
         Recorded by: Tim Svenonius
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Pedagogy Experts (templates), User Interface Designers, Metadata
                  Experts, Programmers
                  End Users: Viewers (Education), Viewers (Museum), Production Staff, Project
                  Managers
         Official Priority: essential
         Desired Priority: essential
         Duplicates: Accessibility and ADA compliance (#138), ADA Compliance - User (#142),
         Accessibility for Pachyderm presentations (#226)
         Comments
         Unknown: The combination of Flash, dynamically driven content and accessibility seems
         to be suspect.
         Michelle LaMar: Using new Flash may be a problem; changing templates may be hard.
         Rachel Smith: Formerly 3.2.1.6. Replaces #142 (formerly 3.2.1.4) and #266 (formerly
         3.2.1.7). All were UI Essential.

    3.1.2.5 Easily begin a new project (#34, revised)
         It should be easy for an author to begin a new project (one-click if possible).
         Rationale: This will make the system easier for authors to use.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Rachel Smith
         System Components: Authoring Tool
         Stakeholders
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: essential
         Desired Priority: essential

    3.1.2.6 Entering assets must be an easy process (#140, revised)
         Users want to be able to easily enter assets, making it usable by a novice, but still retain
         the ability to enter many fields.
         Rationale: If it's not easy to enter assets the people will revolt.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Michelle LaMar

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                       19
Section 3.1.2: UI & Usability Essential Requirements
         System Components: Assets (Database)
         Stakeholders
                  Developers: User Interface Designers
                  End Users: Maintenance Staff, Authors (Education), Project Managers, Authors
                  (Museum), Production Staff
         Official Priority: essential
         Desired Priority: useful
         Comments
         Team Leaders: Mike is looking into plug-in tools (4/29/04).

    3.1.2.7 Metadata can be manually created and/or edited by means of a metadata input
        screen/method (#36, revised)
         A user who uploads a new asset should be prompted to fill out metadata related to that
         asset when it is uploaded.
         Rationale: This will help to keep track of and classify assets in the database.
         Notes:
         Volatility: stable
         Clarity: needs refinement (by System, UI, and Metadata Teams)
         Recorded by: Rachel Smith
         System Components: Authoring Tool, Assets (Database)
         Stakeholders
                  Developers: Metadata Experts, User Interface Designers, Programmers
                  End Users: Authors (Education), Production Staff, Authors (Museum)
         Official Priority: essential
         Desired Priority: essential
         Comments
         Metadata Team: Includes requirements #146 (formerly 3.1.1.9), #36 (formerly 3.2.1.10),
         and #277 (formerly 4.1.47).

    3.1.2.8 Asset availability (#190)
         Ability to determine at point of authoring whether the asset actually exists or is just a
         pointer
         Rationale: Awkward to wait until publish stage to find out this information
         Notes:
         Volatility: stable
         Clarity: refine
         Recorded by: Michelle LaMar
         System Components: Authoring Tool
         Stakeholders
                   End Users: Authors (Education), Production Staff, Authors (Museum),
                   Maintenance Staff
         Official Priority: essential
         Desired Priority: useful

    3.1.2.9 Dummy or placeholder media instead of empty space (#301, revised)
         Authors will see some media every place it would appropriately be used in a module; they
         can, at their leisure, replace it with other media.
         Rationale: Placeholder media gives the author a more complete picture of the visual look
         and feel than empty space.
         Notes:
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: Claire Stewart
         System Components: Authoring Tool, Templates
         Stakeholders

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                        20
Section 3.1.2: UI & Usability Essential Requirements
                  Developers: User Interface Designers, Programmers
                  End Users: Authors (Education), Production Staff, Authors (Museum)
         Official Priority: essential
         Desired Priority: desirable
         Comments
         Rachel Smith: Formerly 3.2.3.2 (UI Desirable), replaces #187 (formerly 3.2.1.15, UI
         Essential).

    3.1.2.10      Pachyderm 2.0 logo placement (#308)
         At appropriate points, the authoring tool(s) should display the logo or other "branding"
         that identify them as Pachyderm 2.0.
         Rationale: To ensure the product has a clear identity
         Notes: This does conflict with branding content with the authoring institution's logo/look --
         this is about the authoring interface and perhaps any opening "splash" screens if they are
         part of the final product.
         Volatility: stable
         Clarity: clear
         Recorded by: Larry Johnson
         System Components: Templates
         Stakeholders
                  End Users: Authors (Education), Production Staff, Authors (Museum)
         Official Priority: essential
         Desired Priority: essential

    3.1.2.11      Interchangeable Branding (#185a, new)
         The skin for a presentation, which designates the look-and-feel, (perhaps contained
         within a single file) can be swapped in easily. The skin file describes all of the elements in
         the outside border, including
              • border color
              • inclusion or exclusion of the upper left navigation cube
              • program title graphic
              • credit boxes
              • organization logo
              • color of the back arrow
              • color of help text
         Rationale: Many institutions want to customize presentations to reflect corporate identity
         or their own stylistic choices.
         Recorded by: Usbaility & Interface Group
         System Components: Authoring Tool, Templates, Other
         Stakeholders
                  Developers: User Interface Designers, Pedagogy Experts (templates),
                  Programmers
                  End Users: Production Staff, Viewers (Museum), Authors (Education), Viewers
                  (Education), Authors (Museum)
         Official Priority: essential
         Desired Priority: desirable
         Comments
         Rachel Smith: Formerly part of 3.9.2.1 (UI Unprioritized, #185).

    3.1.2.12      Authoring tool usable by non-technical people (#148)
         The tool should be in a known paradigm, such as Web form entry
         Rationale: Broad user base
         Notes:
         Volatility: stable


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                        21
Section 3.1.2: UI & Usability Essential Requirements
         Clarity: clear
         Recorded by: Michelle LaMar
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: User Interface Designers, Pedagogy Experts (templates),
                  Programmers
                  End Users: Authors (Education), Authors (Museum), Production Staff
         Official Priority: essential
         Desired Priority: essential
         Comments
         Tom Hapgood: I think the ideal is to have them author within the look of the chosen
         screen design ("wysiwyg"). Still using web forms of course, unless we want to go to a
         Flash authoring which could enable more drag/drop options (I think)
         UI Group, Spring Meeting: We know there are other requirements for a wysiwyg
         interface. We think that would be "desirable."
         Rachel Smith: Formerly 4.1.17 (Process).

    3.1.2.13      Non-programmers love Pachyderm authoring!! (#162)
         People who can only type, point and click are able to create new Pachyderm units.
         Rationale: This is the underlying rationale of the program.
         Notes: This capacity assumes that the authoring environment is set up and has some
         degree of technical support, ways to get data assets into the database, etc. etc.
         Volatility: stable
         Clarity: clear
         Recorded by: John Weber
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Programmers, Pedagogy Experts (templates), User Interface
                  Designers
                  End Users: Authors (Education), Production Staff, Authors (Museum), Project
                  Managers
         Official Priority: essential
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 4.1.18 (Process).

    3.1.2.14      View a list of projects (#197)
         Authors must be able to see a list of their projects in the system and their status
         (complete, in-process, etc.).
         Rationale: To allow authors to find projects.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Jared Bendis and Claire Stewart
         System Components: Authoring Tool
         Stakeholders
                   Developers: User Interface Designers, Programmers
                   End Users: Authors (Education), Project Managers, Maintenance Staff, Authors
                   (Museum), Production Staff
         Official Priority: essential
         Desired Priority: essential
         Comments
         Unknown: This seems like the highest-level authoring screen after logging-in. The author
         will likely be authoring multiple presentations and need to choose one of them as a first
         step.


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                    22
Section 3.1.2: UI & Usability Essential Requirements
         Usability Group, Spring Meeting: In-process might need to be further elaborated, e.g.,
         “awaiting assets…”
         Rachel Smith: Formerly 4.1.27 (Process).

    3.1.2.15      Full Size Template Examples (#202)
         When building screens in the authoring tool, give the author easy access to a completed
         example of the screen type they are working on (e.g. variety of media screen). The
         example should be large enough to read and make meaning of the screen's elements.
         Rationale: The completed example provides the author with a reference that will help her
         figure how she might fill in the different elements of the screen.
         Notes: A small version of this exists in pachyderm 1.0, but it is not large enough to make
         meaning of the screen elements. If the authoring interface goes to an "edit in place"
         paradigm for the authoring interface (as has been discussed), this kind of completed
         reference screen might still be useful.
         Volatility: stable
         Clarity: clear
         Recorded by: Lou Zweier
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Pedagogy Experts (templates), User Interface Designers
                  End Users: Authors (Education), Authors (Museum), Production Staff
         Official Priority: essential
         Desired Priority: useful
         Comments
         Unknown: This would be greatly enhanced through a wysiwyg editing environment.
         Rachel Smith: Formerly 4.1.29 (Process).

    3.1.2.16      Assigning Metadata to Pachyderm Assets (#270)
         Require authors to add metadata to pachyderm assets when they are input into the asset
         database. A minimum of information should be required from the author (Name, job title,
         institution, contact info (email), asset title, asset owner, others???). Some of this
         information can come from the user's pachyderm profile (see other requirement).
         Rationale: Requiring the addition of this information will prevent unattributed media from
         being published in presentations. Supports responsible used of copyrighted material.
         Provides important information for asset management and discovery.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Lou Zweier
         System Components: Authoring Tool, Templates
         Stakeholders
                   Developers: User Interface Designers, Programmers, Metadata Experts
                   End Users: Maintenance Staff, Authors (Education), Viewers (Museum), Project
                   Managers, Viewers (Education), Authors (Museum), Production Staff
         Official Priority: essential
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 4.1.44 (Process).

    3.1.2.17      Pachyderm 2.0 logo placement (#308)
         At appropriate points, the authoring tool(s) should display the logo or other "branding"
         that identify them as Pachyderm 2.0.
         Rationale: To ensure the product has a clear identity
         Notes: This does conflict with branding content with the authoring institution's logo/look --
         this is about the authoring interface and perhaps any opening "splash" screens if they are

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                       23
Section 3.1.2: UI & Usability Essential Requirements
         part of the final product.
         Volatility: stable
         Clarity: clear
         Recorded by: Larry Johnson
         System Components: Templates
         Stakeholders
                  End Users: Authors (Education), Production Staff, Authors (Museum)
         Official Priority: essential
         Desired Priority: essential

    3.1.2.18      Branding Pachyderm: To Be or Not To Be (#74)
         This issue springs from my reading of scenario 72, wherein Sharon searches the
         Pachyblog and Pachyderm users page after she finds a Pachyderm module on the Lord
         of the Rings. Although we want Pachyderm to become a household word for developing
         modules, do we really anticipate a day when every module we do will be identified in
         some way as a pachyderm production? With a little elephant icon somewhere?
         Rationale:
         Notes: This is just to open discussion on this issue.
         Volatility: unspecific
         Clarity:
         Recorded by: Holly Witchey
         System Components: Other
         Stakeholders
                  Global Concern: Global Concern (all stakeholders)
         Official Priority: unspecific
         Desired Priority: unspecific
         Comments
         Rachel Smith: Formerly 3.7.1 (Issues).




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                               24
Section 3.1.2: UI & Usability Essential Requirements
3.1 Essential Requirements (continued)

3.1.3 Metadata Requirements
    3.1.3.1 Learning Object creation (#248)
         ability to produce reusable, interoperable, standards-based “learning objects”
         Rationale: We Promised. And playing well with others is a Good Thing...
         Notes:
         Volatility: stable
         Clarity: refine (definition of "interoperable" and what standards we are talking about
         would help)
         Recorded by: D'Arcy Norman
         System Components: Authoring Tool, Assets (Database), Templates
         Stakeholders
                   Developers: Metadata Experts
                   End Users: Authors (Education), Production Staff, Authors (Museum),
                   Maintenance Staff
         Official Priority: essential
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 3.1.1.21 (System Essential).

    3.1.3.2 The Pachyderm system will use Dublin Core as the standard metadata format
        for all assets in the system (#152, revised)
         The role of the descriptive metadata is to describe the original object.
         Rationale: To ensure consistent tracking and discovery of assets in the pachyderm
         database.
         Notes: The Dublin Core fields are: Title, Creator, Subject, Description, Publisher,
         Contributor, Date, Type, Format, Identifier, Source, Language, Relation, Coverage, and
         Rights (see http://dublincore.org/documents/dces/).
         Two additional sets of metadata will also be supported: system metadata (to be defined
         by programmers as they build the system) and technical metadata (the metadata team
         will define by 5/5/04, see requirement #314).
         Volatility: stable
         Clarity: clear
         Recorded by: Lou Zweier, Mike Mattson, Tim Svenonius
         System Components: Authoring Tool
         Stakeholders
                   Developers: Metadata Experts, User Interface Designers, Programmers
                   End Users: Authors (Education), Production Staff, Authors (Museum)
         Official Priority: essential
         Desired Priority: essential
         Comments
         Metadata Team: This includes #152 and also #205 (formerly 3.3.2.1, Metadata Useful).

    3.1.3.3 The system must support different levels of description (new).
         The system must support different levels of description, including describing the learning
         object as a whole, and describing the individual media objects. Dublin Core can be the
         metadata standard for both. Completed Pachyderm documents should contain, at
         minimum, a descriptive Dublin Core record that describes the completed learning object.
         If possible, each completed Pachyderm document should also contain descriptive
         records for every media asset within the learning object.
         Volatility: stable
         Clarity: needs refinement


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                     25
Section 3.1.3: Metadata Essential Requirements
         Recorded by: Metadata Team, Spring Meeting 2004
         System Components: Assets (Database)
         Official Priority: essential

    3.1.3.4 Pachyderm productions are searchable and standards compliant (#182)
         (no description)
         Rationale: We promised this feature in the About the Project document, and it is also
         highly desirable in order to guarantee wide user adoption.
         Notes: We need to define the "key" standards of search, archiving, etc.
         Volatility: unspecific
         Clarity: clear
         Recorded by: John Weber
         System Components: Assets (Database)
         Stakeholders
                  Developers: Metadata Experts
                  End Users: Project Managers, Maintenance Staff, System Administrators,
                  Production Staff
         Official Priority: essential
         Desired Priority: essential
         Comments
         Joshua Archer: The essential component is in regards to the general presentation. It is
         desirable to have access to the individual content component metadata as well.
         Team Leaders: Michelle, Claire, Tim & Mike will discuss (4/29/04).
         Rachel Smith: Formerly 3.9.3.1 (Metadata Unprioritized).

    3.1.3.5 Standardize technical metadata (and related issues) (#314, revised).
         Standardize technical metadata and allow the user to provide it AND/OR the system to
         apply this information by auto-detecing it as media are uploaded [WE NEED ANOTHER
         WEEK TO DEFINE THE TECHNICAL METADATA FIELDS THAT WILL BE
         SUPPORTED]

         The role of the technical metadata is to describe the digital surrogate. A starting point for
         the list of technical metadata is: Address/location (URL and/or file name), Owner, Content
         Type (mime type), Size (file size in bytes), Creation date, Creator, Modification date,
         Modifier.

         [Kathleen's system] automatically generates: file size, file width, file height, bits per pixel,
         file name, file creator, file type, volume name, volume created, file created, file modified,
         record created, record modified, pixels per inch.

         Additional needed: duration (for sound and video), OTHER???
         Rationale:
         Notes: This will save the authors time (no need to manually enter tedious information!)
         and also be useful for statistical and management purposes.
         Volatility: medium-term change likely
         Clarity: needs refinement
         Recorded by: Joshua Archer
         System Components: Authoring Tool, Assets (Database)
         Stakeholders
                  Developers: Metadata Experts, Programmers
                  End Users: Authors (Education), Production Staff, Maintenance Staff, System
                  Administrators, Authors (Museum)
         Official Priority: essential
         Desired Priority: useful
         Comments


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                           26
Section 3.1.3: Metadata Essential Requirements
         Metadata Team: This is based on requirements #314, #205 (formerly 3.3.2.1), and #65
         (formerly 3.1.2.9).
         Rachel Smith: Formerly 3.9.3.4 (Metadata Unprioritzed).




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                  27
Section 3.1.3: Metadata Essential Requirements
3.1 Essential Requirements (continued)

3.1.4 Template Requirements
    3.1.4.1 template design: timeline scroll (#296)
         open timeline screen in middle of timeline not at end so both arrows function
         Rationale: users who try to scroll left at start think screen doesn't work.
         Notes:
         Volatility: stable
         Clarity: refine (Or, might just mean that on load, the timeline doesn't have a left arrow
         until a scroll begins (tom))
         Recorded by: deborah howes
         System Components: Templates
         Stakeholders
                  Developers: Programmers
                  End Users: Viewers (Museum), Viewers (Education)
         Official Priority: essential
         Desired Priority: desirable
         Comments
         Template team: the functionality of the timeline needs to be clear.

    3.1.4.2 Design of templates (#297)
         Pachyderm templates need to continue to be elegant in their simplicity and function.
         Rationale: Authoring with templates is easy, understanding the function of template is
         clear.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Wendy Shapiro
         System Components: Templates
         Stakeholders
                  Global Concern: Global Concern (all stakeholders)
         Official Priority: essential
         Desired Priority: essential

    3.1.4.3 template design: comparison headings (#306)
         make three different headings for each of the comparison texts: e.g. body, pollock and
         body, hesse and body.
         Rationale: viewers were confused by changing text
         Notes:
         Volatility: stable
         Clarity: refine
         Recorded by: deborah howes
         System Components: Templates
         Stakeholders
         Developers: User Interface Designers, Pedagogy Experts (templates)
         End Users: Viewers (Museum), Authors (Education), Viewers (Education), Authors
         (Museum)
         Official Priority: essential
         Desired Priority: wishlist
         Comments
         Template Team: The specific text associated with the specific object needs to be
         identified as such. It would be good for authors to be able to put titles above all text
         blocks identifying them.


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                        28
Section 3.1.4: Template Essential Requirements
    3.1.4.4 Variety of Media Template: change caption under VOM main image thumbnail
        (#310)
         When user triggers a video from one of the thumbnails on the right side of the Variety of
         Media screen, it opens in the Main Image area on the left. The caption for the original
         main image, however, remains in place--giving an erroneous title for the video. The
         suggestion is to update the caption to reflect the new media file that has moved there.
         Rationale: So people will have the correct title for the video!
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Leonard Steinbach
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Education), Viewers (Museum)
         Official Priority: essential
         Desired Priority: essential
         Comments
         Template Team: This is a simple bug fix. Do it!

    3.1.4.5 Asset comparison module (#244)
         Allow authors to build modules that let users compare any asset with any other asset.
         Rationale: Comparison module independent of timeline.
         Notes:
         Volatility: stable
         Clarity: refine
         Recorded by: Jared Bendis and Claire Stewart
         System Components: Templates
         Stakeholders
                  Developers: User Interface Designers, Programmers
                  End Users: Authors (Education), Production Staff, Authors (Museum)
         Official Priority: essential
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 3.4.2.1 (Template Useful); re-prioritized.
         Tim: Comparison needs to become its own template, independent of Timeline template.
         Clicking on the images in the comparison may link to other screens, zooms, etc. Relates
         to #48 (formerly 3.9.4.3).

    3.1.4.6 template design: formal analysis screen (#280)
         make template accommodate up to 10 hot spots as default with possibility to add more
         (instead of current potential 6).
         Rationale: with larger screen size, we could accommodate more details.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Deborah Howes
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Museum), Authors (Education), Viewers (Education),
                  Authors (Museum)
         Official Priority: essential
         Desired Priority: desirable
         Comments


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                        29
Section 3.1.4: Template Essential Requirements
         Rachel Smith: Formerly 3.4.2.3 (Template Useful); re-prioritized.
         Template Team: This is essential for interdisciplinary subjects and archeological; all parts
         identification in science, and more…

    3.1.4.7 template design: slider gallery larger image (#289)
         want to have larger images (in addition to allowing the images to be enlarged)
         Rationale: images are too small and space can accommodate it.
         Notes:
         Volatility: medium-term change likely
         Clarity: refine (Depends on template sizes/resolution)
         Recorded by: deborah howes
         System Components: Templates
         Stakeholders
                  Developers: User Interface Designers
                  End Users: Production Staff, Viewers (Education), Viewers (Museum)
         Official Priority: essential
         Desired Priority: desirable
         Comments
         Rachel Smith: Formerly 3.4.2.5 (Template Useful); re-prioritized.
         Template Team: It is essential that we be able to make images bigger; how this is
         implemented is a global issue.

    3.1.4.8 template design: onion skin redesign (#293)
         rethink relationship of elements. Currently it hides too much material and very hard to
         write for. arrows not good icon. too many split-level directions.
         Rationale: the page is too confusing. idea is good but information is not well-presented.
         Notes:
         Volatility: stable
         Clarity: clear (How, remains to be seen, but the idea is clear, that the onion skin needs a
         bit of a redesign)
         Recorded by: deborah howes
         System Components: Templates
         Stakeholders
                   Developers: User Interface Designers
                   End Users: Authors (Education), Viewers (Museum), Authors (Museum), Viewers
                   (Education)
         Official Priority: essential
         Desired Priority: useful
         Comments
         Rachel Smith: Formerly 3.4.2.6 (Template Useful); re-prioritized.
         Template Team: We strongly urge redoing this screen!!! Although it works in its current
         iteration, it doesn't work well from the user's point of view or the author's.

    3.1.4.9 template design: timeline dates (#299)
         make dates clickable for additional content or make the appearance of dates optional.
         Rationale: dates do not have large function right now in the timeline.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: deborah howes
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Museum), Authors (Education), Viewers (Education),
                  Authors (Museum)

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                      30
Section 3.1.4: Template Essential Requirements
         Official Priority: essential
         Desired Priority: desirable
         Comments
         Rachel Smith: Formerly 3.4.2.7 (Template Useful); re-prioritized.
         Deb Howes: It is essential if we continue to call this a timeline!

    3.1.4.10      template design: text (#128)
         size of text--particularly the text used in content and instruction areas, not necessarily
         headings-- needs to be larger (or scalable) for all templates.
         Rationale: users had trouble reading print
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Deborah Howes
         System Components: Templates
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Education), Other End Users, Viewers (Museum)
         Official Priority: essential
         Desired Priority: essential
         Comments
         Michelle LaMar: Text size changes may be hard wihtout changing the templates. See
         issue of template edits.
         Rachel Smith: Formerly 3.2.1.17 (UI & Usability, Essential).

    3.1.4.11      template design: placement of user help hints (#153, revised)
         Users needed more obvious help to use the templates
         Rationale: Directions for using the templates (usually in the bright orange border at the
         bottom) was not in obvious place, and animated arrows were not as helpful as they could
         be
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Deborah Howes
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Education), Viewers (Museum)
         Official Priority: desirable
         Desired Priority: useful
         Comments
         Rachel Smith: Formerly 3.2.1.17 (UI & Usability, Essential).

    3.1.4.12      Slider template: provide titles for text stops (#181)
         Add title to each text stop on the slider,
         Rationale: Users don't always notice that the text is changing on the right as the imager
         changes on the left.
         Notes: It might be useful for the title to be in another color.
         Volatility: stable
         Clarity: clear
         Recorded by: Peter Samis
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Pedagogy Experts (templates), User Interface Designers,
                  Programmers

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                         31
Section 3.1.4: Template Essential Requirements
                  End Users: Viewers (Education), Authors (Education), Viewers (Museum),
                  Authors (Museum)
         Official Priority: essential
         Desired Priority: useful
         Comments
         Rachel Smith: Formerly 3.2.1.22 (UI & Usability, Essential).

    3.1.4.13      artist in context: navigation clean-up (#223)
         revisit relationship between previewing/choosing from left nav list and selection of images
         on phone dial.
         Rationale: This relationship inspired some confusion in visitor testing.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Deborah Howes
         System Components: Templates
         Stakeholders
                   Developers: Programmers, User Interface Designers
                   End Users: Viewers (Education), Viewers (Museum)
         Official Priority: essential
         Desired Priority: essential
         Duplicates: artist in context: hot spot behavior in phone dial (#225)
         Comments
         Rachel Smith: Formerly 3.2.1.23 (UI & Usability, Essential).

    3.1.4.14      artist in context: hot spot behavior in phone dial (#225)
         revisit consistency of mouse over and selection to give predictable results in phone dial.
         Rationale: source of confusion in visitors
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Deborah Howes
         System Components: Templates
         Stakeholders
                  Developers: User Interface Designers
                  End Users: Viewers (Museum), Viewers (Education)
         Official Priority: essential
         Desired Priority: useful
         Comments
         Rachel Smith: Formerly 3.2.1.24 (UI & Usability, Essential).

    3.1.4.15      artwork screen design: central image link (#232)
         make central image link more obvious
         Rationale: users did not always understand that central image was a potential link and
         therefore missed essential info.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Deborah Howes
         System Components: Templates
         Stakeholders
                  Developers: User Interface Designers
                  End Users: Viewers (Museum), Viewers (Education)
         Official Priority: essential
         Desired Priority: desirable

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                         32
Section 3.1.4: Template Essential Requirements
         Comments
         Rachel Smith: Formerly 3.2.1.25 (UI & Usability, Essential).

    3.1.4.16      template design: zoom screen (#237)
         tools to manipulate zoom need to be more obvious visually and conceptually.
         Rationale: users did not see zoom tool and did not easily understand how to use it
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Deborah Howes
         System Components: Templates
         Stakeholders
                  Developers: User Interface Designers
                  End Users: Viewers (Museum), Viewers (Education)
         Official Priority: essential
         Desired Priority: desirable
         Comments
         Rachel Smith: Formerly 3.2.1.26 (UI & Usability, Essential).

    3.1.4.17      Zoom template: reorganize lower banner (#263)
         Reorganize lower banner to accommodate object ID and caption without interfering with
         zoom and audio slides.
         Rationale: Currently, captions easily interfere with left end of zoom slider if they contain
         too many characters. Some users have found lower banner functionality confusing.
         Check the zoom audio hot spots, too.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Peter Samis
         System Components: Templates
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Education), Viewers (Museum)
         Official Priority: essential
         Desired Priority: useful
         Comments
         Rachel Smith: Formerly 3.2.1.27 (UI & Usability, Essential).

    3.1.4.18      template design: navigation (#176)
         consistent placement of back button and other nav elements on all templates.
         Rationale: users were confused by changing location of nav.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Deborah Howes
         System Components: Templates
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Education), Viewers (Museum)
         Official Priority: essential
         Desired Priority: desirable
         Comments
         Rachel Smith: Formerly 4.1.21 (Process).

    3.1.4.19      Comparison Time Line Orientation (#178)

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                           33
Section 3.1.4: Template Essential Requirements
         Open the time line such that its initial orientation is in the middle of the time span....so
         that users can go forward or back; it currently starts at the beginning of the time line, so
         that although there is an arrow pointing left (toward an earlier period) it does function in
         that direction
         Rationale: The appearance of a function button (left arrow) that does not function is
         misleading and frustrating to the user...starting in the middle provides some orientation to
         the period covered..
         Notes:
         Volatility: unspecific
         Clarity: refine
         Recorded by: Leonard Steinbach
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Pedagogy Experts (templates), User Interface Designers,
                  Programmers
                  End Users: Viewers (Education), Authors (Education), Viewers (Museum),
                  Authors (Museum)
         Official Priority: unspecific
         Desired Priority: desirable
         Comments
         Jared Bendis: Timeline starting position need to be a parameter.
         Rachel Smith: Formerly 4.1.22 (Process).

    3.1.4.20      template design: text color (#179)
         use colored text consistently to indicate link.
         Rationale: now red text is sometimes a link sometimes not. this confused users.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Deborah Howes
         System Components: Templates
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Education), Viewers (Museum)
         Official Priority: essential
         Desired Priority: desirable
         Comments
         Rachel Smith: Formerly 4.1.23 (Process).

    3.1.4.21      template design: breadcrumbs (#193)
         enable users to know what screens they have already seen and which are yet to be
         discovered
         Rationale: users, especially those who are used to web navigation, were confused about
         where to go next and were looking for help from the interface to tell them.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Deborah Howes
         System Components: Templates
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Education), Viewers (Museum)
         Official Priority: essential
         Desired Priority: desirable
         Duplicates: site architecture: index (#307)


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                      34
Section 3.1.4: Template Essential Requirements
         Comments
         Rachel Smith: Formerly 4.1.26 (Process).

    3.1.4.22      template design: media element symbols and associated text (#249)
         make media element symbols consistent. For example, always use speaker for audio and
         camera for video. also accompanying text should be more descriptive.
         Rationale: users were surprised that media elements were indicated differently from
         template to template. they could not anticipate the nature form the content by only looking
         at the name of the speaker. they needed more info and also wanted to know how long
         the audio/video would take to play (they wanted a status bar).
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Deborah Howes
         System Components: Authoring Tool
         Stakeholders
                  Developers: User Interface Designers
                  End Users: Viewers (Museum), Viewers (Education)
         Official Priority: essential
         Desired Priority: desirable
         Comments
         Rachel Smith: Formerly 4.1.38 (Process).

    3.1.4.23      Dual function Timeline: access Exploration screens AND compare objects
        (#48)
         Users may use the Timeline in 2 different modes: 1. as a way into the rich content of the
         exploration screens (Variety of Media, Slider, etc.) 2. for comparisons between objects
         (as in Pachy 1.0)
         Rationale: Timeline becomes a universal interface: to documents, ephemera, and
         interpretive material about the pictures on it, and to relations between the different
         objects or phenomena it depicts.
         Notes: Could be achieved with a toggle, or dual mode approach? Give users a choice of
         which mode they want to turn on. In one case, they click on an object and it takes you to
         the "Artwork screen (surrounded by questions & topics); in the other case, you click on it
         and other related objects gather round for drag-and-drop comparisons.
         Volatility: unspecific
         Clarity: refine
         Recorded by: Peter Samis
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: User Interface Designers, Pedagogy Experts (templates),
                  Programmers
                  End Users: Project Managers, Viewers (Museum), Authors (Education), Viewers
                  (Education), Authors (Museum)
         Official Priority: essential
         Desired Priority: desirable
         Comments
         Template Team: If the timeline becomes a major way to display content objects, we need
         a way to go directly to additional deep content about those objects.
         Rachel Smith: Formerly 3.9.4.3 (Template Unprioritized).

    3.1.4.24      Enable replacement of transitional sound effects by new ones (#159)
         Users can replace transition and screen sound effects package with a different set.
         Rationale: Just as we change the skins in different presentations, giving them different
         visual brands, users may want to replace the acoustical "look-and-feel" as well.

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                       35
Section 3.1.4: Template Essential Requirements
         Notes: Probably best reserved for the Project Manager level.
         Volatility: unspecific
         Clarity: refine
         Recorded by: Peter Samis
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: User Interface Designers, Programmers
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: essential
         Desired Priority: desirable
         Comments
         Template Team: institutions need to be able to turn sounds off and on and also to
         customize them.
         Rachel Smith: Formerly 3.9.4.6 (Template Unprioritized).

    3.1.4.25      template design: consistent use of symbols (#165)
         develop menu of symbols that are associated consistently with specific actions across
         templates
         Rationale: P1.0 uses the triangle symbol in a variety of ways, but viewers are confused
         that they don't produce same content
         Notes: maybe using a (c) symbol for the ID/technical label next to the image.
         Volatility: unspecific
         Clarity: clear
         Recorded by: Deborah Howes
         System Components: Templates
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Museum), Viewers (Education)
         Official Priority: essential
         Desired Priority: unspecific
         Duplicates: Art label icon (#163)
         Comments
         Rachel Smith: Formerly 3.9.4.7 (Template Unprioritized).

    3.1.4.26      Multi-layer image zoom (#191)
         Zoom in on images while navigating through multiple layers.
         Rationale:
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Jared Bendis and Claire Stewart
         System Components: Templates
         Stakeholders
                  Developers: Programmers, Pedagogy Experts (templates), User Interface
                  Designers
                  End Users: Authors (Education), Production Staff, Authors (Museum), Project
                  Managers
         Official Priority: essential
         Desired Priority: useful
         Duplicates: template design: zoom screen (#237)
         Comments
         Template Team: This feature would allow multilayered zoom images. It is likely to be an
         essential feature in some disciplines and not essential in others.
         Rachel Smith: Formerly 4.1.25 (Process).



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                      36
Section 3.1.4: Template Essential Requirements
3.1 Essential Requirements (continued)

3.1.5 Help & Documentation Requirements
    3.1.5.1 Context-sensitive technical help (#137, revised)
         Pachyderm must have a help system with these distinct components: 1) a system for
         authors that is available online (but not necessarily built into the authoring environment);
         2) a help system for end users (probably needs to be built into the system); 3) a FAQ
         document, which can be part of each help system. The help systems need to be
         updateable.
         Rationale:
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Claire Stewart and Jared Bendis
         System Components: Authoring Tool
         Stakeholders
                  Developers: Programmers, Metadata Experts, User Interface Designers
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: essential
         Desired Priority: essential
         Comments
         Template Team: This requirement synthesizes #137 (formerly 3.2.2.8), #35 (formerly
         3.2.2.9), and #75 (formerly 3.2.2.10)
         Rachel Smith: Formerly 3.2.2.8 (UI Useful).

    3.1.5.2 Credits for the Pachyderm Project team and SFMOMA (#309)
         We'll need to think through wording to recognize the contribution of the IP behind Pachy
         2.o from SFMOMA, as well as an authoring credit for the project team.
         Rationale: Giving credit where due seems right....
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Larry Johnson
         System Components: Other
         Stakeholders
                  Developers: Pedagogy Experts (templates), User Interface Designers,
                  Programmers, Metadata Experts
         Official Priority: essential
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 3.5.1.1 (Other Requirements).




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                       37
Section 3.1.5: Help & Documentation Essential Requirements
3.2 Useful Requirements

3.2.1 System, Database & Security Requirements
    3.2.1.1 Automated account creation (#33)
         The process of creating an account should be able to be automated (for instance, filling
         out a form online and receiving email confirmation) rather than requiring human
         oversight. Oversight should still be possible if desired.
         Rationale: This will lower the overhead for system maintenance and enable new users to
         get started more quickly.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Rachel Smith
         System Components: Authoring Tool
         Stakeholders
                  Developers: Programmers
                  End Users: Authors (Education), Production Staff, Maintenance Staff, Authors
                  (Museum)
         Official Priority: useful
         Desired Priority: useful
         Comments
         Rachel Smith: Formerly 3.1.1.3.

    3.2.1.2 Authors have profiles, and information in the profiles can be used to assist in
        populating metadata fields, such as the system metadata that indicates who
        created the record (#151, revised).
         Authors have profiles with key demographic information (subject interest, name, address,
         email address, stored preferences)
         Rationale: Speeds authoring.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Claire Stewart and Jared Bendis
         System Components: Authoring Tool, Assets (Database)
         Stakeholders
                  Developers: User Interface Designers, Programmers
                  End Users: Maintenance Staff, Authors (Education), Production Staff, System
                  Administrators, Authors (Museum)
         Official Priority: useful
         Desired Priority: desirable
         Duplicates: User Profile to assist with Metadata entry (#141)
         Comments
         Unknown: For system group: profile should allow for some subject preferences/interest.
         VCard might be a good starting point.
         Metadata Team: Includes requirements #141 (formerly 3.1.2.1), #151, and #155 (formerly
         3.9.3.7).

    3.2.1.3 Save items to a personal workspace while authoring (#47)
         Pachyderm authors may mark items that they are considering using in a presentation and
         save them to a personal workspace so when they come back they can pick up where
         they left off.



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                  38
Section 3.2.1: System Useful Requirements
         Rationale: Creates a "study carrel"-like workspace where users can isolate the media
         they need for a project, then return and author it in stages or as time permits.
         Notes: They don't necessarily need to copy the media itself to their workspace--pointers
         to the media might suffice. That said, if people then want to work offline, they may need
         to exercise a "make self-contained" option, and zip and carry the selected media with
         them.
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: Peter Samis
         System Components: Authoring Tool
         Stakeholders
                  Developers: User Interface Designers, Programmers
                  End Users: Authors (Education), Project Managers, Authors (Museum),
                  Production Staff
         Official Priority: useful
         Desired Priority: useful

    3.2.1.4 Publish to various screen resolutions/sizes (#52, revised)
         Make the publishing architecture able to publish templates of different sizes & scaling
         capabilities.
         Rationale: With LCDs now operating at a default of 1280 x 1024, Pachy 1.0
         presentations are getting smaller & smaller! Conversely, authors might want to deliver
         content to smaller, PDA-sized screens. Both of these trends indicate a potential need for
         multiple template sizes, perhaps redesigned according to the needs of their respective
         target platforms.
         Notes:
         Volatility: stable
         Clarity: refine (Need a list of screen sizes to support)
         Recorded by: Peter Samis
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: User Interface Designers, Programmers
                  End Users: Viewers (Education), Authors (Education), Project Managers,
                  Viewers (Museum), Authors (Museum)
         Official Priority: useful
         Desired Priority: desirable
         Duplicates: Publish to various screen resolutions/sizes (#51)
         Comments
         Rachel Smith: Related to #143 (Templates Useful).

    3.2.1.5 Kiosk/Live Web Editions (#73)
         Ability for author to indicate whether an edition of a pachyderm module is intended for
         internal use (kiosk edition with ancillary web links stripped) or live internet version.
         Rationale: For most museums, and some universities, there are dead terminals and live
         terminals (so the Director never runs across anyone looking at porn in the Armor Court).
         This facility just makes for cleaner systems on dead terminals.
         Notes:
         Volatility: stable
         Clarity: refine (Other versions: CD-R, archive?)
         Recorded by: Holly Witchey
         System Components: Authoring Tool, Assets (Database)
         Stakeholders
                   End Users: Viewers (Education), Other End Users, Viewers (Museum)
         Official Priority: useful
         Desired Priority: useful


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                    39
Section 3.2.1: System Useful Requirements
         Duplicates: Delivery in multi-modes (#235)

    3.2.1.6 Better asset search (#184)
         One should be able to search for assets without knowing exact spelling; general search
         function
         Rationale: Ease of use
         Notes:
         Volatility: medium-term change likely
         Clarity: refine (A listing of exactly what parameters are searchable for an asset is
         needed.)
         Recorded by: Michelle LaMar
         System Components: Authoring Tool
         Stakeholders
         Official Priority: useful
         Desired Priority: desirable

    3.2.1.7 Batch-upload raw assets (#236, revised)
         Authors should be able to add multiple media assets at once. Pachyderm authors must
         be able to easily add pieces of media (audio, video, pictures, other graphics, etc) from
         their local storage (hard disk, cd-rom, USB drive, or other portable storage media, etc.) to
         their Pachyderm presentation. Ideally, this would be a single step process of uploading
         and using the media, as opposed to a multi-step process of loading the media into the
         Pachyderm authoring system and then using the media in a specific presentation.
         Rationale: This will save time.If authors are not able to easily use media from their own
         personal collections in Pachyderm presentations, this will likely be a barrier to authors
         choosing to use this tool.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Jared Bendis and Claire Stewart
         System Components: Assets (Database)
         Stakeholders
                  Developers: Programmers
                  End Users: Authors (Education), Production Staff, System Administrators,
                  Authors (Museum)
         Official Priority: useful
         Desired Priority: essential
         Duplicates: Allow authors to easily add media to asset database (#93), Batch-upload
         metadata (#241)
         Comments
         Rachel Smith: Includes portions of #93 (formerly 3.1.2.10).

    3.2.1.8 Metadata can be batch-imported (1 or more at a time) as a structured XML
        record upload (#241, revised).
         Authors can upload multiple metadata records at once. Metadata should be easy to add
         and/or upload along with raw assets. The Metadata team will provide mappings for the
         top 3-5 metadata formats to the Dublin Core that will be the native Pachyderm format.
         This import may select only a subset of the original XML. We suggest that the mapping
         be accomplished my means of XSLT, because then users who use other standards can
         write their own transformations.
         Rationale: Speeds population of the database, increases reusability of content.
         Notes: Will this support one file with many records, or many records each as an
         individual file.
         Volatility: stable
         Clarity: clear

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                      40
Section 3.2.1: System Useful Requirements
         Recorded by: Jared Bendis and Claire Stewart
         System Components: Assets (Database)
         Stakeholders
                  Developers: Metadata Experts, Programmers
                  End Users: System Administrators, Authors (Education), Production Staff,
                  Authors (Museum)
         Official Priority: useful
         Desired Priority: essential
         Duplicates: Allow authors to easily add media to asset database (#93), Batch-upload
         assets (#236)
         Comments
         Michelle LaMar: Related to #236 and #255.
         Metadata Team: Based on requirements #241, #255 (formerly 3.1.3.6), and #239
         (formerly 3.3.1.3).

    3.2.1.9 Auto-generation of required image sizes and metadata from master files (#103)
         Author does not need to batch process images to fit all required sizes for the templates
         before authoring. As long as a single file of adequate resolution is supplied, Pachyderm
         will automatically derive all subsidiary sizes and enter the metadata into the authoring
         database.
         Rationale: Faculty and curators may or may not have access to Photoshop, and certainly
         aren't thinking in terms of making multiple derivative images. They just want to point and
         publish.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Peter Samis
         System Components: Assets (Database)
         Stakeholders
                  Developers: Metadata Experts, Programmers
                  End Users: Authors (Education), Project Managers, Authors (Museum),
                  Production Staff
         Official Priority: useful
         Desired Priority: useful

    3.2.1.10      Support for Math Symbols (#318)
         Pachyderm should include support for displaying and entering mathematical formulae
         and special symbols.
         Rationale: Math faculty have specifically requested this.
         Notes: There are some outside apps which allow math folks to capture an image of an
         equation, which maybe could be imported as an asset (gif, jpg, etc)... but this is kind of
         clumsy.
         Volatility: medium-term change likely
         Clarity: refine (How should this be done? Linking to a math editor? Including one?)
         Recorded by: Rachel Smith
         System Components: Authoring Tool
         Stakeholders
                  End Users: Authors (Education), Viewers (Education)
         Official Priority: useful
         Desired Priority: useful

    3.2.1.11      Build in upgrade path (#63)
         Leave an upgrade path so that we can federate Pachyderm with external databases like
         the NSDL libraries, and efforts like AMICO and MOAC.



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                         41
Section 3.2.1: System Useful Requirements
         Rationale: We're already writing grant proposals for it :-) Seriously, this will make
         Pachyderm easier to use for authors who have access to those databases.
         Notes:
         Volatility: short-term change likely
         Clarity: unclear (I don't know what you mean by an "upgrade path")
         Recorded by: Rachel Smith
         System Components: Other
         Stakeholders
                  Developers: Programmers, Metadata Experts
         Official Priority: useful
         Desired Priority: essential

    3.2.1.12      Printing Options & Script Programming (#115, revised)
         Provides 5 printing options – 1. All (hidden/visible) content with screen layout 2. All
         content without screen layout 3. Only visible content without screen layout 4. Only visible
         content with screen layout 5. Text-only output.
         Rationale: Additional scripts included in the package that (1) brings pop-up windows w/
         the options (2)recognizes user’s printing command
         Notes:
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: Wendy Shapiro
         System Components: Authoring Tool
         Stakeholders
                  Developers: User Interface Designers
                  End Users: Viewers (Museum), Viewers (Education)
         Official Priority: useful
         Desired Priority: useful
         Duplicates: must enable printing (#126)
         Comments
         Michelle LaMar: We need to consider if all the printing options are needed or even
         desired. In particular, printing non-visible content within the screen layout may not be
         possible.

    3.2.1.13      Links to outside content or functions (#220)
         Allow a pachyderm author to put a link on the screen that goes to a web-based resource
         outside of the pachyderm presentation. The link can appear as hot text or as a clickable
         image. This function should be available from any Pachyderm screen type.
         Rationale: This will facilitate access to functions that are currently outside the scope of
         Pachyderm, e.g. assessments, other learning objects, annotation tools or discussion
         tools, etc.
         Notes: This functionality exists already on the Variety of Media screen and Slider Gallery.
         Volatility: stable
         Clarity: refine (Where would the content of the link load? New browser window?)
         Recorded by: Lou Zweier
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: User Interface Designers, Pedagogy Experts (templates),
                  Programmers
                  End Users: Viewers (Museum), Authors (Education), Viewers (Education),
                  Authors (Museum), Production Staff
         Official Priority: useful
         Desired Priority: useful

    3.2.1.14      Preview Page/Module Appearing in Separate Window (#284)


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                      42
Section 3.2.1: System Useful Requirements
         Author would like to be able to see the result of their work prior to a full publishing of a
         pachyderm module in order to effect changes.
         Rationale: Saves time, energy, and allows for more direct expression of author's
         creativity by giving them immediate access to how their module will look.
         Notes: This may well be moot if the authoring system is designed to mimic the look of
         templates.
         Volatility: stable
         Clarity: refine (Is this a preview of a single screen (currently available) or the whole
         presentation?)
         Recorded by: Holly Witchey
         System Components: Authoring Tool
         Stakeholders
                  Developers: Programmers
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: useful
         Desired Priority: desirable
         Comments
         Unknown: This will/would be much easier with the wysiwyg authoring environment. If the
         authoring happens within the actual presentation look, then the author always has an
         actual visual context to the entry.

    3.2.1.15      Publication should be managed by Pachyderm (#281)
         There are currently some tweaks that a user must do post-pachyderm-production in order
         to complete a module. It would be great if P2 would just package up the whole shebang,
         and stick it on the hard drive somewhere, all shiny and ready to go. All of the
         modifications should happen within the authoring environment – no modifications made
         post-publish and no changes in server configuration.
         Rationale: ease of use. quality control.
         Notes:
         Volatility: stable
         Clarity: refine (Need detail of tweaks currently required.)
         Recorded by: D'Arcy Norman
         System Components: Authoring Tool
         Stakeholders
                  End Users: Authors (Education), Production Staff, Authors (Museum)
         Official Priority: useful
         Desired Priority: useful

    3.2.1.16      Page index for entire presentation (#285)
         A Pachyderm 2.0 Presentation should have an automatically generated index of all
         screens. A "table of contents" would be great, so users could hit a "Table of Contents"
         button and be taken to a central menu where they could navigate to any part of the
         presentation.
         Rationale: easier navigation of content is a Good Thing.
         Notes:
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: D'Arcy Norman
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Pedagogy Experts (templates), User Interface Designers,
                  Programmers
                  End Users: Viewers (Museum), Viewers (Education)
         Official Priority: useful
         Desired Priority: desirable


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                       43
Section 3.2.1: System Useful Requirements
         Duplicates: Index of Screens (#238), site architecture: index (#307)
         Comments
         Rachel Smith: Formerly 3.1.3.26 (System Desirable).

    3.2.1.17      Load screens created by other Pachyderm users (#189)
         Authors who have worked independently on projects in Pachyderm should be able to use
         each other's authored material.
         Rationale: Facilitates distributed work.
         Notes:
         Volatility: short-term change likely
         Clarity: clear
         Recorded by: Jared Bendis and Claire Stewart
         System Components: Authoring Tool
         Stakeholders
                  Developers: User Interface Designers, Programmers
                  End Users: Authors (Education), Project Managers, Maintenance Staff, Authors
                  (Museum), Production Staff
         Official Priority: useful
         Desired Priority: desirable
         Comments
         Rachel Smith: Formerly 3.5.2.19 (Out of Scope).




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                               44
Section 3.2.1: System Useful Requirements
3.2 Useful Requirements (continued)

3.2.2 User Interface & Usability Requirements
    3.2.2.1 Art label icon (#163)
         Change the triangle to a symbol which signifies basic object identifier information e.g.
         copyright symbol
         Rationale: The pervasive use of a triangle to represent different types of information is
         not as informative queue as it should be
         Notes:
         Volatility: stable
         Clarity: refine
         Recorded by: Leonard Steinbach
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Education), Viewers (Museum)
         Official Priority: useful
         Desired Priority: useful
         Comments
         Rachel Smith: Formerly 3.2.1.21 (UI Essential).

    3.2.2.2 Authoring Within Screen Design (#127)
         During the authoring process, the author should be able to start by choosing a screen
         design (skin?) and then actually author the screen within the look and feel.
         Rationale: Will greatly facilitate authoring by giving an actual visual context to the
         authoring, and will allow author to have constant preview of the screen being authored.
         Notes:
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: Tom Hapgood
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Pedagogy Experts (templates), User Interface Designers,
                  Programmers
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: useful
         Desired Priority: essential

    3.2.2.3 Functionality of preview screen - links (#168)
         Preview screen should be fully functional - links should be active wherever possible, such
         as enlargement, zoom, et al.
         Rationale: See screens in context. Preview functionality as well as look.
         Notes:
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: Michelle LaMar
         System Components: Authoring Tool
         Stakeholders
                  Developers: User Interface Designers
                  End Users: Authors (Education), Production Staff, Authors (Museum)
         Official Priority: useful
         Desired Priority: desirable
         Duplicates: Preview feature (#154)


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                        45
Section 3.2.2: UI & Usability Useful Requirements
    3.2.2.4 Print out screen flow during authoring and final product (#167)
         User should be able to print learning object project at any point in the authoring process.
         Rationale: Printout servers as an interim storyboard; for discussion, to hand into
         instructor for comments/edits. Visual trail.
         Notes:
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: Ted/Wendy
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: useful
         Desired Priority: essential

    3.2.2.5 Annotate an image with media (#188)
         Author will be able to identify hotspots on an image and attach various types of
         annotations: text, audio, other images, hypertext or email links, etc.
         Rationale:
         Notes:
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: Jared Bendis and Claire Stewart
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: User Interface Designers, Programmers
                  End Users: System Administrators, Authors (Education), Production Staff,
                  Authors (Museum)
         Official Priority: useful
         Desired Priority: useful
         Comments
         Wendy Shapiro: Could be a new template.

    3.2.2.6 Menu lists should not be infinitely long (#275)
         The authoring tool has some pages that list stuff. These lists can get really really long.
         This is Bad. It would be cool if lists on menu screens were a little smarter - pagination,
         filtering, and whatnot.
         Rationale: make it easier to find my stuff
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: D'Arcy Norman
         System Components: Authoring Tool
         Stakeholders
                   Developers: User Interface Designers
                   End Users: Authors (Education), Production Staff, Authors (Museum)
         Official Priority: useful
         Desired Priority: useful

    3.2.2.7 Organize Assets Based on Various Criteria (#77)
         Give author the ability to organize and reorganize media assets based on various criteria
         (by date, by size, by subject or artist alphabetically).
         Rationale:
         Notes:


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                         46
Section 3.2.2: UI & Usability Useful Requirements
         Volatility: stable
         Clarity: clear
         Recorded by: Holly Witchey
         System Components: Authoring Tool, Assets (Database)
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: useful
         Desired Priority: essential

    3.2.2.8 Meaningful media asset help (#164)
         The system must tell the author what media parameters are.
         Rationale: Will avoid problems with media (files much too big or in wrong format, etc)
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Claire Stewart and Jared Bendis
         System Components: Authoring Tool, Assets (Database), Templates
         Stakeholders
                  Developers: User Interface Designers, Metadata Experts, Programmers
                  End Users: Authors (Education), Project Managers, Maintenance Staff, Authors
                  (Museum), Production Staff
         Official Priority: useful
         Desired Priority: useful

    3.2.2.9 Graphical menus with brief content summaries (#42)
         High level overview of content below. Click or mouse over icons for short summaries of
         content they lead to.
         Rationale: So people don't have to follow extended navigational pathways to find out
         where the content they seek resides. Table of Contents function.
         Notes: cf. the rollovers in the phone dial in current version of Pachyderm that reveal
         artwork title or topic heading. Pachy 1.0 also has a 1-2 paragraph summary lower left of
         the unifying theme for everything on that "phone dial," and a 1-2 sentence summary
         within the dial itself.
         Volatility: stable
         Clarity: refine
         Recorded by: Peter Samis
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Education), Viewers (Museum)
         Official Priority: useful
         Desired Priority: useful

    3.2.2.10      Stronger High-light for Clickable Objects (#253)
         Provide a strong (more noticeable) high-light for clickable graphics on pachyderm
         screens. Currently, a thin orange border indicates an object highlight.
         Rationale: In user tests, the current highlight was often missed by users.
         Notes:
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: Lou Zweier
         System Components: Templates
         Stakeholders



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                       47
Section 3.2.2: UI & Usability Useful Requirements
                  Developers: Pedagogy Experts (templates), User Interface Designers
                  End Users: Viewers (Education), Viewers (Museum)
         Official Priority: useful
         Desired Priority: useful
         Comments
         Unknown: This will have to be looked at graphically and see how much we can expand
         the highlight language without going overboard.

    3.2.2.11      Expand size of slider activation points (#304)
         To activate new images using the slider you currently have to roll over the circles which
         each cover a very small "active" screen area. This active area should be expanded a little
         bit wider than the circle itself, and higher to encompass the text.
         Rationale: This would make it substantially easier and faster to navigate... especially for
         persons who find targeting the bull's eye more daunting.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Leonard Steinbach
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Education), Viewers (Museum)
         Official Priority: useful
         Desired Priority: desirable

    3.2.2.12      provide choice of object ID or caption for each media file (#250, revised)
         Give the author the choice over whether to display the asset metadata with an object. i.e.,
         to use authority-controlled metadata for museum label text or scientific taxonomies
         (Display or Not), or simple captions customizable by screen Ephemera (Display or Not),
         etc.
         Rationale: Object metadata, while important, may not be necessary to include on every
         screen. The object metadata may interfere with the ability to display other information
         needed for the screen.
         Notes: At present, all artworks are accompanied by an object ID, which is wedded to
         them in an .swf file. This functionality is important for any image associated with an
         authority file, e.g., species names in botany or zoology as well as artworks.
         Volatility: medium-term change likely
         Clarity: refine (not sure if they would get either an ID or a caption -- why not both?)
         Recorded by: Peter Samis
         System Components: Authoring Tool, Assets (Database), Templates
         Stakeholders
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: useful
         Desired Priority: useful
         Comments
         Rachel Smith: Formerly 4.1.39 (Process).

    3.2.2.13      Pachyderm Authoring Should Be Fun (#252)
         The overall pachyderm authoring experience should be pleasant.
         Rationale: Otherwise people won't use it.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Jared Bendis and Claire Stewart



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                     48
Section 3.2.2: UI & Usability Useful Requirements
         System Components: Authoring Tool, Assets (Database), Templates
         Stakeholders
                  Global Concern: Global Concern (all stakeholders)
         Official Priority: useful
         Desired Priority: essential
         Comments
         Unknown: Why else are we all involved in this project?
         Rachel Smith: Formerly 4.1.40 (Process).

    3.2.2.14      ability to group screens by project (#273, revised)
         In the authoring tool, it would be cool if we could sort screens by project project (in
         addition to currently available sorts, such as by screen type, by title, and by date last
         modified), rather than the never-ending-list-of-screens that is there now.
         Rationale: better for workflow. easer to find my stuff.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: D'Arcy Norman
         System Components: Authoring Tool, Assets (Database), Templates, Other
         Stakeholders
                  Developers: Metadata Experts, Programmers
                  End Users: Authors (Education), Production Staff, Authors (Museum)
         Official Priority: useful
         Desired Priority: useful
         Comments
         Usability Group, Spring Meeting: Do we need to create a new entity called “project” that
         exists within an author’s directory?
         Rachel Smith: Formerly 4.1.46 (Process).

    3.2.2.15      Flash Components (#208)
         The new version of Flash MX 2004 allows for a component based structure of functions.
         This would allow for new templates to be easily created from the component library in
         flash. This would facilitate the designer /programmer to combine functions from different
         templates. For example the zoom function could be incorporated with any template
         directly and would not require a linking of multiple templates. This allows the designer to
         think in terms of tasks rather than templates.
         Rationale: This would be the first step toward template generation.
         Notes: Assumes a rebuild rather than a refactor of existing code
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: Mike Mattson
         System Components: Templates
         Stakeholders
                   Developers: Pedagogy Experts (templates), User Interface Designers,
                   Programmers
         Official Priority: useful
         Desired Priority: useful




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                        49
Section 3.2.2: UI & Usability Useful Requirements
3.2 Useful Requirements (continued)

3.2.3 Metadata Requirements
    3.2.3.1 Object Label text (#192)
         Images in Pachy presentations each contain a core group of data fields automatically. A
         sub-group always appears, and additional fields appear when the user chooses to
         expand the label. The selection of data fields should be customizable for an institution or
         for a given presentation. The style of the data should also be customizable, including text
         size and color, and which fields appear in the short version of the Object Label vs. the
         expanded version.
         Rationale: The core data fields will vary from one institution to the next. e.g., for
         museums, "creator" is often the first piece of data on the label; for sciences, the common
         name then the Latin, etc.
         Notes:
         Volatility: unspecific
         Clarity: clear
         Recorded by: Tim Svenonius
         System Components: Assets (Database)
         Stakeholders
                  Developers: Pedagogy Experts (templates), User Interface Designers, Metadata
                  Experts, Programmers
                  End Users: Viewers (Education), Viewers (Museum), Authors (Education),
                  Authors (Museum)
         Official Priority: useful
         Desired Priority: desirable
         Comments
         Rachel Smith: Formerly 3.9.3.3 (Metadata Unprioritized).

    3.2.3.2 Allow all fields to repeat as many times as the metadata creator chooses new).
         Volatility: stable
         Clarity: clear
         Recorded by: Metadata Team, Spring Meeting 2004
         System Components: Assets (Database)
         Official Priority: useful
         Comments
         Metadata Team: This is a new requirement based on requirements #241 (formerly
         3.1.2.12), #256 (formerly 3.1.3.6), #239 (formerly 3.3.1.3), and #240 (formerly 3.6.3.1).

    3.2.3.3 Allow fields to have as many user-defined qualifiers as the metadata creator
        chooses (new).
         These could be attached to the data before it is imported, or they could be
         created/assigned/applied in manual data entry. Qualifiers are ignored in search and
         browse, are only used to provide information to the author.

         Example 1: DC.Title.Main <dc.title type="main"> and DC.Title.Alternate
         <dc.title type="alternate"> are the same to the system in terms of building a
         search index, but they help to give the author more precise information about the record
         as she views it.

         Example 2: DC.Subject.AAT and DC.Subject.LCSH
         <dc.subject type="aat">Men</dc.subject><dc.subject
         type="aat">Horses</dc.subject><dc.subject type="aat">Great



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                        50
Section 3.2.3: Metadata Useful Requirements
         Plains</dc.subject><dc.subject type="lcsh">Arapaho
         Indians.</dc.subject>
         For search and browse purposes, this record has 4 subjects: Men, Horses, Great Plains,
         and Arapaho Indians. It may help the author, however, when displaying the record, to
         show the qualifiers so that they know which subject headings are from the Art and
         Architecture Thesaurus (AAT) and which are Library of Congress Subject Headings
         (LCSH)

         Volatility: stable
         Clarity: clear
         Recorded by: Metadata Team, Spring Meeting 2004
         System Components: Assets (Database)
         Official Priority: useful

    3.2.3.4 Descriptions of remote objects in asset database (#66, revised)
         The asset database must contain descriptions of objects that reside in external
         repositories and are linked to, rather than phyically located within the system.
         Parameters for this might be: things that are accessible via http:// or rtsp:// request.
         Rationale: Saves the time of the user. Makes re-typing author, title, subject, etc.
         unnecessary.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Claire Stewart
         System Components: Assets (Database)
         Stakeholders
                  End Users: Authors (Education), Other End Users, Authors (Museum)
         Official Priority: useful
         Desired Priority: desirable
         Comments
         Rachel Smith: Formerly 3.9.3.5 (Metadata Unprioritized).




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                       51
Section 3.2.3: Metadata Useful Requirements
3.2 Useful Requirements (continued)

3.2.4 Template Requirements
    3.2.4.1 template design: slider gallery stops (#288)
         accommodate up to 10 stops on the slider bar without requiring users to scroll to see
         more stops on the line. also allowing for more space for longer/more words associated
         with each stop.
         Rationale: larger screen size could accommodate this
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: deborah howes
         System Components: Templates
         Stakeholders
                  Developers: User Interface Designers, Programmers
                  End Users: Production Staff, Viewers (Museum), Viewers (Education)
         Official Priority: useful
         Desired Priority: desirable
         Comments
         Template Team: If the visibility of the scroll function were more evident, this would help
         with the current implementation of 6 stops.

    3.2.4.2 template design: screen size (#143, revised)
         Each template must specify its size and scaling parameters. Authors must have a way to
         specify this.
         Rationale: will be presented on a variety of monitors. current version displays small on
         large monitors
         Notes:
         Volatility: stable
         Clarity: refine
         Recorded by: Deborah Howes
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Pedagogy Experts (templates), User Interface Designers,
                  Programmers
                  End Users: Viewers (Museum), Viewers (Education)
         Official Priority: useful
         Desired Priority: useful
         Comments
         Rachel Smith: Related to #52, System Useful. Formerly 3.2.1.18 (UI Essential).

    3.2.4.3 template design: make contextual sound optional (#149)
         Make transitional sound effects optional
         Rationale: While many people love the sound effects that accompany them through the
         screens and transitions, others find them irritating. They should have the option to turn
         them off.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Peter Samis
         System Components: Authoring Tool, Templates
         Stakeholders



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                         52
Section 3.2.4: Template Useful Requirements
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Education), Viewers (Museum)
         Official Priority: useful
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 3.2.2.14 (UI Useful).

    3.2.4.4 template design: image enlargement (#161)
         enable all images (or as many as possible) to be clickable and lead to a subsequent
         screen displaying much larger image, either a zoom or a fixed size. Could also link to
         related media (audio, video, etc..)
         Rationale: users really wanted to see images larger and explore them in depth.
         Notes:
         Volatility: stable
         Clarity: refine
         Recorded by: Deborah Howes
         System Components: Authoring Tool, Templates
         Stakeholders
                   Developers: Programmers, User Interface Designers
                   End Users: Viewers (Education), Viewers (Museum)
         Official Priority: useful
         Desired Priority: desirable
         Comments
         Jared Bendis: Perhaps not ALL.
         Template Team: It is useful to have a capacity to make images bigger in their fixed
         positions. Whether this is achieved via zoom screens attached to all images, or by flat
         pages with maximum size images can be determined at a later date based on issues of
         technical difficulty, loading times for web programs, etc.
         Template Team: We would like to see the images possible to be made larger, for all
         sizes; if the image size of the base template is larger than 800 x 600, they need to be
         bigger within that frame; if we go to a 1054 x 768 window, they would automatically need
         to be bigger.

         We would also like to see it possible to enlarge any image by clicking and going to a
         larger image or a zoom screen.
         Rachel Smith: Formerly 3.2.2.15 (UI Useful). Includes #204 (formerly 4.1.30) and #157
         (formerly 3.9.4.5).

    3.2.4.5 artist in context screen: easy redesign (#210)
         ability to change order, size number, placement of hotspots.
         Rationale: phone dial shape was not always most useful design depending on number of
         hotspots and look and feel of presentation, or character of images/thumbnails.
         Notes: key to projects success for speedy adoption. we could also supply 6 or so ready
         to go design variations with different number of hot spot locations--e.g. 5, 10, 50, 100...
         Volatility: stable
         Clarity: clear
         Recorded by: Deborah Howes
         System Components: Authoring Tool, Templates
         Stakeholders
                   Developers: Programmers, User Interface Designers
                   End Users: Viewers (Museum), Authors (Education), Viewers (Education),
                   Authors (Museum)
         Official Priority: useful
         Desired Priority: useful
         Comments


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                     53
Section 3.2.4: Template Useful Requirements
         Rachel Smith: Formerly 3.2.2.18 (UI Useful).

    3.2.4.6 Page Numbers (#229)
         Provide a page number, or other simple and unique way of identifying each screen in a
         pachyderm presentation.
         Rationale: Provide an easy way for users and authors to refer to screens in a
         presentation.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Lou Zweier
         System Components: Templates
         Stakeholders
                  Developers: User Interface Designers, Metadata Experts, Pedagogy Experts
                  (templates)
                  End Users: Authors (Education), Production Staff, Viewers (Education), Viewers
                  (Museum), Authors (Museum), Project Managers
         Official Priority: useful
         Desired Priority: useful
         Comments
         Rachel Smith: Formerly 3.2.2.19 (UI Useful).

    3.2.4.7 template design: comparison screen (#305)
         put in some more directions/icons about content. viewers needed help to understand why
         text was there, and how to change text.
         Rationale: user confusion
         Notes:
         Volatility: stable
         Clarity: refine
         Recorded by: deborah howes
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: User Interface Designers
                  End Users: Authors (Education), Viewers (Museum), Authors (Museum), Viewers
                  (Education)
         Official Priority: useful
         Desired Priority: desirable
         Comments
         Rachel Smith: Formerly 3.2.2.23 (UI Useful).

    3.2.4.8 Book Viewer template: add sound capability to these zooms (#257)
         Allow sound files to be played in book viewer zoom mode
         Rationale: Sometimes the documents in this template will have appropriate audio
         components or counterparts: e.g., showing sheet music and playing sound recording of
         same.
         Notes: This wasn't originally spec'd in v. 1, but we have often regretted that! This is not a
         design challenge: if we just use the zoom screen as it currently works, we're there.
         Volatility: unspecific
         Clarity:
         Recorded by: Peter Samis
         System Components: Authoring Tool, Assets (Database), Templates
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Museum), Authors (Education), Viewers (Education),
                  Authors (Museum)

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                       54
Section 3.2.4: Template Useful Requirements
         Official Priority: unspecific
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 3.5.2.27 (Out of Scope).

    3.2.4.9 Template: Comparison Screen with dual zoom feature (#62)
         This split screen template compares two images side by side, allows viewer to zoom in
         on either, and to go through a still or animated picture sequence on either side.
         Rationale: Visual comparison is a fundamental pedagogical strategy in art history,
         medicine, and many other fields. In Pachy 1.0, we regret only having this screen
         available to us through the Timeline; we often want its functionality as an exploration
         screen in the Artists in Context section as well.
         Notes: Comparisons of two images on equal footing are essential. The abilities to 1.
         zoom and 2. refresh the images (1 or both) in sequence are desirable.
         Volatility: unspecific
         Clarity: clear
         Recorded by: Peter Samis
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Programmers, Pedagogy Experts (templates), User Interface
                  Designers
                  End Users: Viewers (Education), Authors (Education), Viewers (Museum),
                  Authors (Museum)
         Official Priority: unspecific
         Desired Priority: essential
         Comments
         Template Team: This is a very very very useful option; the images need to be bigger, but
         whether this is achieved by going to two zoomable screen or to a full-size images can be
         determined at a later date based on degree of difficulty.
         Rachel Smith: Formerly 3.9.4.4 (Template Unprioritzed). Similar to #161.

    3.2.4.10      collaboration web template: media element (#259)
         selected thumbnails should immediately launch associated media files and not require a
         second click under the center image
         Rationale: users thought that it was too time consuming to make double selection for
         each thumbnail.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Deborah Howes
         System Components: Other
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Education), Viewers (Museum)
         Official Priority: useful
         Desired Priority: desirable
         Comments
         Rachel Smith: Formerly 4.1.41 (Process).




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                   55
Section 3.2.4: Template Useful Requirements
3.2 Useful Requirements (continued)

3.2.5 Help & Documentation Requirements
    3.2.5.1 Document Copyright Policy (#76, revised)
         Clearly state the copyright policy for presentations created with Pachyderm.
         Rationale: If we are providing a tool through which copyright laws can be circumvented
         or ignored, don't we at least on paper somewhere need to (or have the moral obligation
         to) state copyright restrictions--surely Microsoft must do this somewhere in all their
         documentation.
         Notes: Is somebody working on this basic documentation document already? Do we
         need to think about it yet?
         Volatility: unspecific
         Clarity:
         Recorded by: Holly Witchey
         System Components: Authoring Tool, Other
         Stakeholders
                  Global Concern: Global Concern (all stakeholders)
         Official Priority: unspecific
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 3.7.2 (Issue).

    3.2.5.2 Training Modules w/ meaningful Learning Objectives (#105)
         Training modules should be designed based on audience’s needs and learning
         behaviors.
         Rationale: Dummy demos could help trainees to visualize the final products. If the
         features are being presented in a meaningful way to the users, they might change the
         impression of the system.
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Wendy Shapiro
         System Components: Other
         Stakeholders
                  Developers: Pedagogy Experts (templates)
                  End Users: Authors (Education), Authors (Museum), Maintenance Staff
         Official Priority: useful
         Desired Priority: useful
         Comments
         Rachel Smith: Formerly 4.1.8 (Process).

    3.2.5.3 Training materials available online (#134)
         Authors can access a variety of training materials in a variety of media (video is
         specifically mentioned here) on demand; can accessed from anywhere and easily move
         around between training modules.
         Rationale: Authors have to learn how to author, by themselves, without depending on
         direct interaction or physical proximity to support staff.
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Claire Stewart and Jared Bendis
         System Components: Other
         Stakeholders


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                     56
Section 3.2.5: Help & Documentation Useful Requirements
                  Developers: User Interface Designers, Pedagogy Experts (templates),
                  Programmers
                  End Users: Authors (Education), Authors (Museum), Production Staff
         Official Priority: useful
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 4.1.15 (Process).

    3.2.5.4 Context-sensitive pedagogical help (#139)
         Users have access to help that explains what kind of learning certain templates best
         support; a variety of pedagogical advice (what types of media, etc.)
         Rationale: Naive authors might not be aware of what templates best do.
         Notes:
         Volatility: unspecific
         Clarity: clear
         Recorded by: Claire Stewart and Jared Bendis
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Metadata Experts, Pedagogy Experts (templates), User Interface
                  Designers, Programmers
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: useful
         Desired Priority: useful
         Comments
         Rachel Smith: Formerly 4.1.16 (Process).




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                   57
Section 3.2.5: Help & Documentation Useful Requirements
3.3 Desirable Requirements

3.3.1 System, Database & Security Requirements
    3.3.1.1 Full media preview while authoring (#46, revised)
         Authors can access and view media files and metadata without leaving the Pachyderm
         asset list to assure best choice of media for their presentation.
         Rationale: Facilitates the selection of the right media asset (or LO) at the time of
         authoring.
         Notes:
         Volatility: medium-term change likely
         Clarity: refine (When can they preview it? Only during authoring? Can they look at it
         outside of Pachyderm?)
         Recorded by: Peter Samis
         System Components: Authoring Tool
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: desirable
         Desired Priority: desirable
         Comments
         Usability Group, Spring Meeting: This single requirement synthesizes former
         requirements 3.1.3.2 (#46), 3.1.3.7 (#135), and 3.2.2.3 (#98)

    3.3.1.2 Upload audio, video and other assets to Pachyderm database (#41, revised)
         An author should be able to upload audio, video, and other media files from their local
         hard drives into the asset database for use in authoring presentations. These files will
         also have to be pre-processed and transcoded into files supported natively by Flash and
         Quicktime. It is very important to have documentation that will outline the process and
         recommend utilities to accomplish these tasks.
         Rationale:
         Notes:
         Volatility: stable
         Clarity: refine (What specific formats will be allowed?)
         Recorded by: Michelle LaMar
         System Components: Authoring Tool, Assets (Database)
         Stakeholders
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: desirable
         Desired Priority: desirable
         Comments
         Metadata Team: This requirement includes #41 and #31 (formerly 3.4.1.1).

    3.3.1.3 Ability to upload media (#144)
         Authors must be able to add new media assets (and metadata) while authoring.
         Rationale: Authors must be able to add own content.
         Notes:
         Volatility: short-term change likely
         Clarity: refine (What does "while" mean? With another window? Automated entry of
         assets?)
         Recorded by: Claire Stewart and Jared Bendis
         System Components: Authoring Tool, Assets (Database)
         Stakeholders



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                    58
Section 3.3.1: System Desirable Requirements
                  Developers: User Interface Designers, Metadata Experts, Programmers
                  End Users: Authors (Education), Project Managers, Maintenance Staff, System
                  Administrators, Authors (Museum), Production Staff
         Official Priority: desirable
         Desired Priority: essential
         Comments
         Mike Mattson: May need to look at third party tools such as ALOHA/Reload metadata
         editors.

    3.3.1.4 Allow import of assets from external sources (#173)
         Allow users to directly import assets and metadata from any standards based database
         or file (standard to be defined) into the Pachyderm asset database. This import includes
         the assets (or a pointer to the asset location), and associated metadata.
         Rationale: Allow authors to easily find and incorporate resources from large collections
         which they have access to that are outside the Pachyderm asset database.
         Notes: This function is supported in Pachyderm 1.0 with Filemaker Pro only. This
         requirement generalizes this functionality to any database or file which conforms to the
         standard we define for this function. Automatic import of resources directly from other
         repositories like such as Amico, ArtStor, etc. is considered out of scope for version 2.0
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: Lou Zweier, Mike Mattson, Tim Svenonius
         System Components: Authoring Tool, Assets (Database)
         Stakeholders
                   Developers: User Interface Designers, Programmers, Metadata Experts
                   End Users: System Administrators, Authors (Education), Project Managers,
                   Authors (Museum), Production Staff
         Official Priority: desirable
         Desired Priority: essential
         Comment
         Michelle LaMar: This may need to be split into two requirements at some point.

    3.3.1.5 Metadata is editable (#160)
         Authors should be able to edit metadata for assets used in a project.
         Rationale: Authors must be able to make changes to descriptive information at any time.
         Notes: Are these edits global to the Pachyderm database or local to the project?
         Volatility: medium-term change likely
         Clarity: refine (Does any author get to edit any metadata? Do we need to track
         changes?)
         Recorded by: Claire Stewart and Jared Bendis
         System Components: Authoring Tool, Assets (Database)
         Stakeholders
                  Developers: Metadata Experts, User Interface Designers, Programmers
                  End Users: Authors (Education), Production Staff, Authors (Museum)
         Official Priority: desirable
         Desired Priority: unspecific

    3.3.1.6 Support for 3D and simulations (#49, revised)
         Any 3D files will need to be pre-processed into a file format that is supported natively by
         Flash or Quicktime.
         Rationale: Useful for simulations, animations. LOs will be produced in these formats: we
         want to be able to accommodate and showcase them.
         Notes:
         Volatility: stable
         Clarity: clear

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                        59
Section 3.3.1: System Desirable Requirements
         Recorded by: Peter Samis
         System Components: Authoring Tool, Assets (Database), Templates
         Stakeholders
                  Developers: Programmers, Metadata Experts
                  End Users: Viewers (Museum), Authors (Education), Authors (Museum), Viewers
                  (Education)
         Official Priority: desirable
         Desired Priority: essential
         Duplicates: 3-d (#247)
         Comments
         Metadata Team: This includes requirements #49 and #247 (formerly 3.1.3.10).

    3.3.1.7 Capability to limit asset search by media type (#64)
         When searching or browsing for existing assets to integrate in a Pachyderm object, it
         should be possible to limit by media type (images only, audio only, etc.)
         Rationale: Users will be able to narrow their search for reusable assets; particularly
         useful if the repository of assets is of any significant size.
         Notes:
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: Claire Stewart
         System Components: Authoring Tool, Assets (Database)
         Stakeholders
                   Developers: Programmers
                   End Users: Authors (Education), Production Staff, System Administrators,
                   Authors (Museum)
         Official Priority: desirable
         Desired Priority: useful
         Comments
         Joshua Archer: The metadata requirement is that there be a type field, captured in a later
         requirement.

    3.3.1.8 Sharing of Pachyderm assets (#265)
         When importing an asset into pachyderm, the author should be given an option (e.g. a
         checkbox) to share the use of that item with other pachyderm authors. This should
         include a confirmation that they have the right to grant use by other authors.
         Rationale: Support building a large collection of copyright cleared materials for use by
         pachyderm authors.
         Notes: Allowing more than one level of sharing (everyone, groups, institution, etc) is
         desirable, but may be out of scope for version 2.0
         Volatility: medium-term change likely
         Clarity: refine (Are we talking just about other authors that are using the same database
         (authoring server) or authors using other instances?)
         Recorded by: Lou Zweier, Mike Mattson, Tim Svenonius
         System Components: Authoring Tool, Assets (Database), Other
         Stakeholders
                  Developers: Programmers, Metadata Experts, Pedagogy Experts (templates),
                  User Interface Designers
                  End Users: Authors (Education), Production Staff, Authors (Museum), Project
                  Managers
         Official Priority: desirable
         Desired Priority: useful
         Comments
         Michelle LaMar: There is an implication here that the current version (1.0) partitions



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                    60
Section 3.3.1: System Desirable Requirements
         author work space and does not allow sharing of assets. That is not true, currently
         assets, screens and presentations are open to all authors.

    3.3.1.9 Templates Specify Asset Size (#199, revised)
         Templates should specify sizing parameters for assets they can contain.
         Rationale: Produce highest quality possible for end user.
         Notes:
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: Ted/Wendy
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Programmers
                  End Users: Authors (Education), Viewers (Museum), Authors (Museum), Viewers
                  (Education)
         Official Priority: desirable
         Desired Priority: desirable

    3.3.1.10      Pachyderm emails permanent URLs (#221)
         When authors publish modules, they receive an email from the Pachyderm system
         containing the permanent URL.
         Rationale: Efficient level of automated communication.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Jared Bendis and Claire Stewart
         System Components: Authoring Tool
         Stakeholders
                  Developers: Programmers
                  End Users: Authors (Education), Authors (Museum), System Administrators
         Official Priority: desirable
         Desired Priority: desirable

    3.3.1.11   Support for bit-map graphical interfaces with hot spots interface leading to
        exploration screens (#50)
         Ability to link exploration screens to hot spots on a map (or other image).
         Rationale: Right now exploration screens are linked only from Artwork (question)
         screens and Context (Table of Contents phone dial) screens. Authors may also want to
         access these deep content screens from hot spots in an information-rich image, such as
         a museum map (or a historical map, or a molecular diagram, for that matter).
         Notes: Two precedents: 1.SFMOMA's KVEC feature (www.sfmoma.org/education/kvec)
         2. The current Formal Analysis template, which has this focused bitmap hot spot
         functionality, but only leads to a paragraph about each topic, not a whole screen.
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: Peter Samis
         System Components: Authoring Tool, Templates
         Stakeholders
                   Developers: Pedagogy Experts (templates), User Interface Designers,
                   Programmers
                   End Users: Viewers (Education), Authors (Education), Viewers (Museum),
                   Authors (Museum)
         Official Priority: desirable
         Desired Priority: useful
         Comments

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                  61
Section 3.3.1: System Desirable Requirements
         Tim: Formal analysis template can become a main interface once its flexibility is
         improved. We need the option to link hotspots to audio commentary and other screens in
         addition to details/texts. Relates to #188 (formerly 3.2.2.6).

    3.3.1.12      Text searching (#59)
         ability to bring up a screen based on a term used in the body text
         Rationale: Useful for students, visitors, researchers, and search engines.
         Notes:
         Volatility: medium-term change likely
         Clarity: refine (Where would the search box be placed? How to scan Flash text? Need
         separate database for searches?)
         Recorded by: Peter Samis
         System Components: Templates
         Stakeholders
                   Developers: Programmers, Metadata Experts
                   End Users: Viewers (Education), Viewers (Museum)
         Official Priority: desirable
         Desired Priority: useful

    3.3.1.13      Linking to Pachyderm Screens (#243)
         Allow a web browser to link directly to any individual pachyderm screen.
         Rationale: Allow users to link directly to a specific portion of a pachyderm presentation.
         Makes Pachyderm presentations more flexible by allowing screens to be accessed
         individually. Allows users to bookmark specific screens that interest them.
         Notes: Some authors may not like this, so it might be desirable to include the ability to
         disallow this on a presentation by presentation basis.
         Volatility: stable
         Clarity: clear
         Recorded by: Lou Zweier
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Pedagogy Experts (templates), User Interface Designers,
                  Programmers
                  End Users: Viewers (Education), Authors (Education), Viewers (Museum),
                  Authors (Museum)
         Official Priority: desirable
         Desired Priority: useful

    3.3.1.14      individual & Group comments/Annotations (#283, revised)
         Authoring system should allow peer reviews of projects in process.
         Rationale: This feature will have immediate practical need for user-testing and
         debugging, but longer term, it's a way for users to provide feedback to content authors on
         design and teaching/learning value.
         Notes: Essential for alpha/beta- testing; maybe highly desirable for end product of Pachy
         2.0 release. Applies to both the end product and authoring environment (for testing only).
         Volatility: medium-term change likely
         Clarity: refine
         Recorded by: Ted Kahn
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: User Interface Designers, Pedagogy Experts (templates),
                  Programmers
                  End Users: Viewers (Museum), Authors (Education), Viewers (Education), Other
                  End Users, Authors (Museum), Project Managers



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                         62
Section 3.3.1: System Desirable Requirements
         Official Priority: desirable
         Desired Priority: essential
         Duplicates: Support for personalized accounts to view selected content & personal
         annotations (#94), Annotations in Pachyderm Continued... (#196)
         Comments
         Rachel Smith: Formerly 3.2.2.24 (System Useful).

    3.3.1.15      Sharing of Pachyderm Assets (#267, revised)
         Allow authors to share assets (assets, screens, presentations) they have authored with
         other pachyderm authors.
         Rationale: Promote sharing of content and re-use of quality materials.
         Notes: Allowing more than one level of sharing (everyone, groups, institution, etc) is
         desirable, but may be out of scope for version 2.0
         Volatility: medium-term change likely
         Clarity: refine
         Recorded by: Lou Zweier, Mike Mattson, Tim Svenonius
         System Components: Authoring Tool, Assets (Database), Templates
         Stakeholders
                  Developers: Programmers, Pedagogy Experts (templates), User Interface
                  Designers
                  End Users: Authors (Education), Production Staff, Authors (Museum), Project
                  Managers
         Official Priority: desirable
         Desired Priority: useful
         Comments
         Rachel Smith: Formerly 3.5.2.33 (Out of Scope).
         Josh Archer: There are some user group issues with this.

    3.3.1.16      Mechanism for Archiving Pachyderm Publications/Editions (#72)
         Ability for an author to archive editions of a pachyderm publication (particularly those that
         are going to have a long life-span and multiple editions).
         Rationale: We are creating a new kind of publication and need to be thinking about it as
         a publication metaphor--we don't want to get five years down the road and have lost all
         the information about the first and second generation publications of pachyderm
         presentations. Plus, since many of end-users will be students and teachers (who cannot
         always be counted upon to revisit the source material listed in their syllabi) we want them
         to at least be able to know that what they are searching for did exist at one time and--may
         be retrievable.
         Notes: I think this is an important requirement that has lots of implications for how the
         author might work. I haven't had a chance to play with the interface so I'm not sure if what
         I'm describing exists of not. When a module is created the author should be able to
         provide a short text description of what's contained in the module (which might also have
         accessibility uses). When an edition is "retired" the edition itself could be stored
         elsewhere, while the short text description could exist as a searchable index for past
         publications/editions.
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: Holly Witchey
         System Components: Authoring Tool, Assets (Database)
         Stakeholders
                   Global Concern: Global Concern (all stakeholders)
         Official Priority: desirable
         Desired Priority: wishlist
         Comments
         Rachel Smith: Formerly 3.6.1.2 (System Wishlist).


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                       63
Section 3.3.1: System Desirable Requirements
    3.3.1.17   Allow advanced users to create new/custom Pachyderm Templates (#95,
        revised)
         Allow advanced authors or technical support personnel who have the appropriate Flash
         skills to create new templates for Pachyderm without modifying the authoring code or
         environment.
         Rationale: This would provide greater visual variety among presentations produced with
         Pachyderm. It would also allow institutions, departments, or individuals to create branding
         that is consistent with their organizations "look".
         Notes: A similar requirement was proposed (#96, now omitted) which would allow
         advanced users to edit the interaction design of existing templates.
         Volatility: medium-term change likely
         Clarity: refine (This is a major feature and needs to be outlined in detail.)
         Recorded by: Lou Zweier
         System Components: Authoring Tool, Templates, Other
         Stakeholders
                   Developers: User Interface Designers, Programmers
                   End Users: Viewers (Education), Other End Users, Authors (Education),
                   Production Staff, Viewers (Museum), Authors (Museum)
         Official Priority: desirable
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 3.6.1.7 (System Wishlist).

    3.3.1.18      Authors can authorize others to edit their projects (#201)
         Authors can share or otherwise authorize other system users to edit their
         modules/projects.
         Rationale: Increases re-usability of content, facilitates distributed authoring
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Jared Bendis and Claire Stewart
         System Components: Authoring Tool
         Stakeholders
                  Developers: User Interface Designers, Programmers
                  End Users: Authors (Education), Project Managers, Maintenance Staff, Authors
                  (Museum), Production Staff
         Official Priority: desirable
         Desired Priority: desirable
         Comments
         Rachel Smith: Formerly 3.6.1.20 (System Wishlist).

    3.3.1.19      Permit addition of custom templates (#216)
         The architecture of Pachyderm must support custom templates. The authoring interface
         must be template-independent, and must be easily adapted to support custom templates
         as added. The templates must conform to certain specifications in order to function within
         Pachyderm.
         Rationale: Authors from various disciplines want to use the existing authoring
         environment, but wish to create new templates based on their field or pedagogy, or may
         wish to make variations on existing templates.
         Notes:
         Volatility: stable
         Clarity: refine (Need more clarity on how templates get added to the system, what the
         constraints are if any.)

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                     64
Section 3.3.1: System Desirable Requirements
         Recorded by: Tim Svenonius
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Pedagogy Experts (templates), Programmers, User Interface
                  Designers
                  End Users: Project Managers, Authors (Museum), Authors (Education),
                  Production Staff, Viewers (Education), Maintenance Staff, Viewers (Museum),
                  System Administrators
         Official Priority: desirable
         Desired Priority: essential
         Comments
         Rachel Smith: Related to #95. Formerly 3.6.1.23 (System Wishlist).




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                   65
Section 3.3.1: System Desirable Requirements
3.3 Desirable Requirements (continued)

3.3.2 User Interface & Usability Requirements
    3.3.2.1 Spell checker (#70)
         An optional spell checker can flag problems with media object records or with the text
         entered elsewhere.
         Rationale: May catch problems that will negatively impact user's ability to find objects to
         use in Pachyderm projects.
         Notes: Would this have to be disabled for some users? (students, for example?)
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: Claire Stewart
         System Components: Authoring Tool
         Stakeholders
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: desirable
         Desired Priority: desirable

    3.3.2.2 Interchangeable Branding/Style extends into the content area (#185b, new)
         Ability to change the color, font, and shape of navigational elements within the templates
         to match/complement those in the border. In effect, supplying a different style sheet for
         the same template.
         Rationale: Many institutions want to customize presentations to reflect corporate identity
         or their own stylistic choices. This requirement extends the modifications made in the
         border/nav bar to produce a consistent look and feel throughout the screen.
         Recorded by: Usbaility & Interface Group
         System Components: Authoring Tool, Templates, Other
         Stakeholders
                   Developers: User Interface Designers, Pedagogy Experts (templates),
                   Programmers
                   End Users: Production Staff, Viewers (Museum), Authors (Education), Viewers
                   (Education), Authors (Museum)
         Official Priority: desirable
         Desired Priority: desirable
         Comments
         Rachel Smith: Formerly part of 3.9.2.1 (#185)

    3.3.2.3 Copyright (#114)
         Includes the copyright info/policy and the content source (attribution) in the printout/web
         page.
         Rationale:
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Wendy Shapiro
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Metadata Experts, Programmers
                  End Users: Maintenance Staff, Viewers (Museum), Authors (Education),
                  Production Staff, Viewers (Education), Other End Users, Authors (Museum)
         Official Priority: desirable
         Desired Priority: essential
         Comments


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                          66
Section 3.3.2: UI & Usability Desirable Requirements
         UI & Usability Team: contingent on printing.
         Rachel Smith: Formerly 3.2.1.20 (UI Essential).

    3.3.2.4 Support for multi-lingual interface and products (#315)
         Perhaps beginning with French (for Canada) but expandable to any language, the
         authoring tool should be designed to be flexible in both its display language for the
         authoring tool and the resultant Flash presentation.
         Rationale: Globalization is the goal; immediate funding opportunities factor heavily as
         well.
         Notes: Menu choice will determine phrases in authoring tool; presentation display
         phrases; templates; keyboard/character set; language of metadata, etc. Input mechanism
         required for above tables.
         Volatility: stable
         Clarity: refine (Full list of modules affected would be nice.)
         Recorded by: Mark
         System Components: Authoring Tool, Templates
         Stakeholders
                  Global Concern: Global Concern (all stakeholders)
         Official Priority: desirable
         Desired Priority: essential
         Comments
         Mark: Early decision here is needed as it will affect all aspects of programming and
         design.
         Team Leaders: Don't preclude the possibility of adding this later.
         Rachel Smith: Formerly 3.2.1.29 (UI Essential).

    3.3.2.5 User specifies metadata display option as part of his/her preferences (new)
        This can be done at the profile level, the project level, or the screen level.
        Rationale:
        Volatility:
        Clarity:
        Recorded by: UI & Usability Team
        System Components: Authoring Tool
        Stakeholders
                 End Users: Authors (Education), Authors (Museum)
        Official Priority: desirable
        Desired Priority: useful
        Comments
        Rachel Smith: Formerly part of 4.1.39 (#250). Written at Spring Meeting.

    3.3.2.6 Control of Sound Volume Level (#278)
         User or instructor (in class) should be able to adjust the audio level.
         Rationale: Hearing levels and ambient environment are going to vary across classroom,
         museum, home and library environments, so users need to be able to raise or lower
         sound level--in general and at any particular point in a module.
         Notes:
         Volatility: short-term change likely
         Clarity: refine (Might be obvious, but couldn't they just adjust the system volume? With
         remote, etc.)
         Recorded by: Ted Kahn and Wendy Shapiro
         System Components: Templates, Other
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Education), Viewers (Museum)



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                   67
Section 3.3.2: UI & Usability Desirable Requirements
         Official Priority: desirable
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 4.1.48 (Process).




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004   68
Section 3.3.2: UI & Usability Desirable Requirements
3.3 Desirable Requirements (continued)

3.3.3 Metadata Requirements
    3.3.3.1 Allow authors importing metadata to write new transformations (XSLT) to map
        their data formats to the Pachyderm Dublin Core elements (new).
         Volatility: stable
         Clarity: clear
         Recorded by: Metadata Team, Spring Meeting 2004
         System Components: Assets (Database)
         Official Priority: desirable
         Comments
         Metadata Team: This is a new requirement based on #241 (formerly 3.1.2.12), #255
         (formerly 3.1.3.6), and #239 (formerly 3.3.1.3).

    3.3.3.2 Records from the Pachyderm database can be exported in either a delimited
        format or an XML format or, ideally, both/either. (new).
         Volatility: stable
         Clarity: clear
         Recorded by: Metadata Team, Spring Meeting 2004
         System Components: Assets (Database)
         Official Priority: desirable

    3.3.3.3 System metadata is used to track the life cycle of the metadata record itself
        (new).
         Among the allowed system metadata should be system-generated record ID,
         comments/notes, record creator, last-modified date. Anything else that will never be
         visible to other authors and end-users (people who use the completed learning object)
         should be contained within the system metadata.
         Volatility: stable
         Clarity: clear
         Recorded by: Metadata Team, Spring Meeting 2004
         System Components: Assets (Database)
         Official Priority: desirable
         Comments: (new requirement based on #314 (formerly 3.9.3.4) and #151 (formerly
         3.9.3.7).




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                    69
Section 3.3.3: Metadata Desirable Requirements
3.3 Desirable Requirements (continued)

3.3.4 Template Requirements
    3.3.4.1 Organize Comparison Timeline by concept (rather than by date) (#40)
         The circular bubbles have to be able to arrange themselves across the screen, and then
         around a central concept, without chronology as the Timeline's sole organizing principle.
         Rationale: Authors will want to compare things that are not chronologically determined,
         e.g., in this case "performance assessment" and "reading disabilities."
         Notes:
         Volatility: medium-term change likely
         Clarity: refine (This is really about separating the timeline and the comparison
         functionalities.)
         Recorded by: Peter Samis
         System Components: Authoring Tool, Templates
         Stakeholders
                   Developers: Pedagogy Experts (templates), Programmers
                   End Users: Viewers (Education), Authors (Education), Viewers (Museum),
                   Authors (Museum), Project Managers
         Official Priority: desirable
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 3.1.3.18 (System Desirable).

    3.3.4.2 Automatic Slide Show (#274)
         This is a feature that lets the instructor (or user) run through an existing set of slides on
         self-run/automatic timing, similar to a timed slide projector or the same feature in
         PowerPoint.
         Rationale: identified by students from Rachel's user study in watching/using 'Voices and
         Images of CA Art' in an SJSU class.
         Notes:
         Volatility: short-term change likely
         Clarity: clear (Hmmm... maybe s/he should just link out to a ppt presentation?)
         Recorded by: Ted Kahn and Wendy Shapiro
         System Components: Templates, Other
         Stakeholders
                  End Users: Viewers (Education), Viewers (Museum)
         Official Priority: desirable
         Desired Priority: useful
         Comments
         Rachel Smith: Formerly 3.5.2.34 (Out of Scope).




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                        70
Section 3.3.4: Template Desirable Requirements
3.3 Desirable Requirements (continued)

3.3.5 Help & Documentation Requirements
    3.3.5.1 Authors have access to sample database (#170)
         Existing media assets are available to authors for training purposes.
         Rationale: Authors becoming familiar with the system can tinker.
         Notes:
         Volatility: stable
         Clarity: refine (Assets pre-populated in install script? Assets from own institution?)
         Recorded by: Claire Stewart and Jared Bendis
         System Components: Assets (Database)
         Stakeholders
                  Developers: Metadata Experts, User Interface Designers, Programmers
                  End Users: Authors (Education), Production Staff, Authors (Museum)
         Official Priority: useful
         Desired Priority: desirable
         Comments
         Rachel Smith: Formerly 4.1.19 (Process).

    3.3.5.2 Authoring documentation (#206)
         Easily available tutorial (in Pachyderm?) and documentation for authors
         Rationale: \"He had forty-two boxes, all carefully packed with his name stencilled on
         each. But since he omitted to mention the fact they were all left behind on the beach.\" -
         Lewis Carroll, \"The Hunting of the Snark\"
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Mark Burstein
         System Components: Other
         Stakeholders
                  End Users: Authors (Education), Production Staff, Authors (Museum),
                  Maintenance Staff
         Official Priority: desirable
         Desired Priority: desirable
         Comments
         Rachel Smith: Formerly 4.1.31 (Process).

    3.3.5.3 Media Library (#219)
         Provide media library of background sounds and images.
         Rationale: Not all authors will have these assets available.
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Ted/Wendy
         System Components: Other
         Stakeholders
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: desirable
         Desired Priority: useful
         Comments
         Rachel Smith: Formerly 4.1.32 (Process).

    3.3.5.4 On-line site for Design styles and layouts (#224)


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                         71
Section 3.3.5: Help & Documentation Desirable Requirements
         Provide on-line site for design styles and layouts both positive and negative. Perhaps
         have a rating system.
         Rationale: Variety - place to share user feedback.
         Notes:
         Volatility: short-term change likely
         Clarity: clear
         Recorded by: Ted/Wendy
         System Components: Other
         Stakeholders
                  Developers: Programmers
                  End Users: Authors (Education), Viewers (Museum), Authors (Museum), Viewers
                  (Education)
         Official Priority: desirable
         Desired Priority: useful
         Comments
         Rachel Smith: Formerly 4.1.33 (Process).

    3.3.5.5 On-line learning community (#231)
         On-line learning community to share successes and ways to use a completed Pachyderm
         object.
         Rationale: A way to share and build a knowledge network.
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Ted/Wendy
         System Components: Other
         Stakeholders
                  End Users: Authors (Education), Viewers (Education), Authors (Museum),
                  Viewers (Museum)
         Official Priority: desirable
         Desired Priority: useful
         Comments
         Rachel Smith: Formerly 4.1.34 (Process).

    3.3.5.6 Examples of student work (#233)
         Samples of student's Pachyderm projects; eportfolio, research project, etc.
         Rationale: Serve as guidance for students
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Ted/Wendy
         System Components: Other
         Stakeholders
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: desirable
         Desired Priority: useful
         Comments
         Rachel Smith: Formerly 4.1.35 (Process).




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                72
Section 3.3.5: Help & Documentation Desirable Requirements
4. Gap Requirements (Placeholder)




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004   73
Section 4: Gap Requirements
5. Wishlist Requirements
5.1 System, Database & Security Wishlist
    5.1.1     Searching by keyword or theme (#60)
         Search utility that allows quick perusal of key ideas and themes treated in each
         Pachyderm presentation, with URL links to the appropriate screens, and the ability to
         save the searches and progress through the relevant URLs.
         Rationale: Multimedia presentations can be overwhelming, if all you're looking for is a
         particular theme or fact and you don't know where to look. The tendency is to give up.
         This gives a vital glimpse at what's under the hood, and directs users to the screens most
         germane to their research task.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Peter Samis
         System Components: Templates
         Stakeholders
                  Developers: Metadata Experts, Programmers, User Interface Designers
                  End Users: Authors (Education), Viewers (Education), Viewers (Museum),
                  Authors (Museum)
         Official Priority: wishlist
         Desired Priority: essential
         Duplicates: Text searching (#59)
         Comments
         Rachel Smith: Formerly 3.1.2.6 (System Useful).

    5.1.2     Archive Search System (#110)
         Allow users to save results of asset search in user account.
         Rationale:
         Notes:
         Volatility: medium-term change likely
         Clarity: unclear (By "Archive" do you mean the asset database, or something exterior? )
         Recorded by: Wendy Shapiro
         System Components: Authoring Tool, Assets (Database)
         Stakeholders
                  End Users: Viewers (Education), Viewers (Museum)
         Official Priority: wishlist
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 3.1.2.7 (System Useful).

    5.1.3     Create a shared workspace within the authoring environment (#100)
         Teacher can assemble a set of media assets and reserve them in a digital workspace for
         students to author into their own Pachy-based assignments
         Rationale:
         Notes: Workspace should be password-protected, assuring the assets are only used by
         the intended audience (IP protection).
         Volatility: short-term change likely
         Clarity: refine
         Recorded by: Peter Samis
         System Components: Authoring Tool, Assets (Database)
         Stakeholders



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                    74
Section 5.1: System Wishlist
                  Developers: User Interface Designers, Pedagogy Experts (templates),
                  Programmers
                  End Users: Authors (Education), Authors (Museum), Production Staff
         Official Priority: wishlist
         Desired Priority: wishlist
         Comments
         Jared Bendis: This appears to be about building sub-databases and giving access to
         various users. It appears outside the scope of this project.
         Rachel Smith: Formerly 3.5.2.12 (Out of Scope).

    5.1.4     Multiple delivery formats (#200)
         While the current version of Pachyderm 1.0 is delivered in Flash we should be able to
         publish in multiple formats such as xhtml and CSS.
         Rationale: Flexibility
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Mike Mattson
         System Components: Templates, Other
         Stakeholders
                  End Users: Viewers (Education), Viewers (Museum)
         Official Priority: wishlist
         Desired Priority: useful
         Comments
         Group decision: Wishlist this. Formerly 3.5.2.20 (Out of Scope).

    5.1.5 Archiving and finding assets across instances of Pachyderm installed on
        separate servers (#303, revised)
         Assets should be easily archived and found.
         Rationale: Ease of authoring; with ease of finding assets there will be greater interest in
         using the tool.
         Notes: Revised and reprioritized at Spring Meeting.
         Volatility: unspecific
         Clarity:
         Recorded by: Wendy Shapiro
         System Components: Assets (Database)
         Stakeholders
                  Developers: Metadata Experts
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: wishlist
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 3.5.2.36 (Out of Scope).

    5.1.6     Eliminating duplicate media objects (#69)
         As media objects are added, they are de-duplicated, so that the same scan of Van
         Gogh's Sunflowers (for example) doesn't appear twice
         Rationale: Saves space, eliminates user confusion
         Notes: Image pattern matching? or just comparing file names?
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: Claire Stewart
         System Components: Assets (Database)
         Stakeholders



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                      75
Section 5.1: System Wishlist
                  Developers: Programmers
                  End Users: Authors (Education), Production Staff, Authors (Museum)
         Official Priority: wishlist
         Desired Priority: wishlist

    5.1.7     Annotation windows (#86)
         Viewers of Pachyderm presentations may call up one or more annotation windows to
         comment on a given screen's content. The contents of these annotation windows can be
         exported to a word processor for formatting.
         Rationale: Supports students' critical review and analysis of the content of any
         presentation screen, and creation of a personal cognitive pathway through the
         presentation. Once exported to a word processing program, the evidence of the
         intellectual content gleaned by students is clear.
         Notes: Is this feature internal to Pachyderm, or might it be accommodated by combining
         Pachyderm with blog software? Scenario also stipulates that annotations should support
         collaboration between 2 or more students.
         Volatility: medium-term change likely
         Clarity: refine
         Recorded by: Peter Samis
         System Components: Assets (Database), Templates, Other
         Stakeholders
                  Developers: Pedagogy Experts (templates), User Interface Designers,
                  Programmers
                  End Users: Viewers (Museum), Viewers (Education)
         Official Priority: wishlist
         Desired Priority: useful
         Duplicates: Annotation windows (#92), Annotation Function (#125)
         Comments
         Josh Archer: At some point this should be combined with #125. There are access and
         export issues to consider.

    5.1.8     Drag and drop authoring of templates (#99)
         User selects media files from the Pachy database and drags them onto a template to
         author a screen.
         Rationale: If computers are so smart, let them insert the metadata and path names. Just
         ask the authors to choose an appropriate template, then preview and select the media
         files and tell Pachyderm where to place them!
         Notes: This would knock the socks off PowerPoint (yet again?)!
         Volatility: stable
         Clarity: clear
         Recorded by: Peter Samis
         System Components: Authoring Tool, Assets (Database), Templates
         Stakeholders
                  Developers: Programmers, Metadata Experts, User Interface Designers
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: wishlist
         Desired Priority: desirable

    5.1.9     Authoring wizard (#101)
         "A wizard for new users that leads them through creating an interaction (templates)."
         Rationale: Hey, we need all the help we can get!
         Notes:
         Volatility: short-term change likely
         Clarity: unclear (Current system is, in principle, a "wizard." What does this mean?)
         Recorded by: Peter Samis

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                    76
Section 5.1: System Wishlist
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: wishlist
         Desired Priority: useful

    5.1.10 Interaction Design Template Authoring Tool (#123)
         Provide a tool within pachyderm, or as a separate tool, that facilitates the creation or
         modification of the interaction design templates by non-technical users.
         Rationale: Allow customizability of Pachyderm by a wider audience (non-technical
         users).
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Lou Zweier
         System Components: Authoring Tool
         Stakeholders
                  Developers: User Interface Designers, Pedagogy Experts (templates),
                  Programmers
                  End Users: Authors (Education), Authors (Museum), Production Staff
         Official Priority: wishlist
         Desired Priority: wishlist
         Comments
         Template Team: We think that some of the function of this will be achieved by decoupling
         the existing template hierarchy.

    5.1.11 Annotation Function (#125)
         Allow users to annotate pachyderm presentations. This annotation function could be at
         the presentation, screen, guiding question, or media element level. Annotations could be
         private (viewable only by the user who input them), or public (viewable by all).
         Rationale: Allow a dialog among users about the questions/topics covered by the
         pachyderm presentation. Allow a user to keep notes on their thoughts and insights
         developed while using the presentation, presumably to use them in a paper or other
         critical work. Another purpose could be to provide feedback to the author on their
         creation.
         Notes:
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: Lou Zweier
         System Components: Authoring Tool, Templates
         Stakeholders
                   Developers: Pedagogy Experts (templates), User Interface Designers,
                   Programmers
                   End Users: Viewers (Education), Authors (Education), Viewers (Museum),
                   Authors (Museum)
         Official Priority: wishlist
         Desired Priority: unspecific
         Duplicates: Annotation windows (#86), Annotation windows (#92), Support for
         personalized accounts to view selected content & personal annotations (#94)
         Comments
         Josh Archer: Combine with #86 at some point.

    5.1.12 Skin Switcheroo After Completion of Authoring (#129)



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                   77
Section 5.1: System Wishlist
         After an author completes the authoring of an exhibit/lecture in a certain skin or screen
         design, s/he can switch to a different skin, assuming all template elements are identical.
         Rationale: Perhaps a faculty member would like to keep their presentation of the
         material "fresh" across semesters by changing the "look and feel." Plus, faculty will use
         one presentation (lecture) many times, replacing images and text often, and will see a
         need to re-colorize or use a different text treatment as a presentation evolves.
         Notes: Will number of template elements need to be identical? Problems are unused
         elements versus utilized elements on a template and where and how blank spaces are
         displayed or collapse, etc. For instance, if "Skin One" calls for a large main image at
         upper left and the author does not utilize that space [but the template is still visually
         appealing or acceptable], what happens if s/he switches to "Skin Two" and the lack of
         using a main image lessens its effectiveness or even "breaks" the design in some way?
         Volatility: stable
         Clarity: clear
         Recorded by: Tom Hapgood
         System Components: Authoring Tool, Templates
         Stakeholders
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: wishlist
         Desired Priority: desirable

    5.1.13 Pachyderm is modular (#136)
         Pachyderm units or productions can be linked to other, existing units after they are built
         without complete new authoring needed, easily creating a composite anthology.
         Rationale: I'm not sure we really need this, but the "About the Project" doc seems to
         imply this feature and it would be useful.
         Notes: Other interpretations of "modular" are possible.
         Volatility: medium-term change likely
         Clarity: refine (What types of units are we referring to? )
         Recorded by: John Weber
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Pedagogy Experts (templates)
                  End Users: Viewers (Museum), Authors (Education), Viewers (Education),
                  Authors (Museum), Project Managers
         Official Priority: wishlist
         Desired Priority: desirable

    5.1.14 Pachy-Module Created From Assets Stored in Folder Rather Than Database
        (#145)
         Pachyderm version that accommodates the author who doesn't have access to or doesn't
         want to use a database but for ease of use wants to create a pachy-module with assets
         stored in a folder.
         Rationale: Whether this is a real or perceived situation (plopping assets in folders rather
         than databases) this requirement illustrates the author's need not to be bothered by the
         mechanical details involved in creating a pachyderm module.
         Notes: The general issue here is how user friendly can we make Pachyderm. Ultimately
         is it desirable that the author doesn't have to know where and how the assets live, they
         just need to know how to put them in a folder and then pachyderm does all the work.
         Volatility: short-term change likely
         Clarity: unclear (Not sure if this requirement is that Pachyderm can work without a
         database (very unlikely) or that the user need not know about the database (desirable))
         Recorded by: Holly Witchey
         System Components: Authoring Tool, Assets (Database)
         Stakeholders


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                         78
Section 5.1: System Wishlist
                  Developers: Programmers, Metadata Experts, User Interface Designers
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: wishlist
         Desired Priority: desirable
         Comments
         Michelle LaMar: The priority of this requirement may change after it is clarified.

    5.1.15 Detection of appropriate media (#166)
         Pachyderm will detect and alert the author about media prepared incorrectly, such as:
         wrong resolution, file format, audio level, etc.
         Rationale:
         Notes: May be problematic
         Volatility: medium-term change likely
         Clarity: refine (What exact conditions constitute incorrect media?)
         Recorded by: Claire Stewart and Jared Bendis
         System Components: Authoring Tool, Assets (Database)
         Stakeholders
                  Developers: User Interface Designers, Metadata Experts, Programmers
                  End Users: Maintenance Staff, Authors (Education), Production Staff, Authors
                  (Museum)
         Official Priority: wishlist
         Desired Priority: wishlist

    5.1.16 Users are grouped (#209)
         Users are broken into groups that have associated rights, permissions and
         characteristics.
         Rationale: Users (authors) may want granular access to content (modules and assets).
         Notes: Can users be in more than one group at once?
         Volatility: stable
         Clarity: refine (Not sure if we are talking about admin users vs. authors, or differentiating
         authors. I've assumed the latter.)
         Recorded by: Jared Bendis and Claire Stewart
         System Components: Authoring Tool, Other
         Stakeholders
                  Developers: User Interface Designers, Programmers
                  End Users: Maintenance Staff, Authors (Education), Production Staff, System
                  Administrators, Authors (Museum)
         Official Priority: wishlist
         Desired Priority: useful

    5.1.17 Finished modules are hosted on the Pachyderm server (#212)
         When authors publish their modules, they are served from the Pachyderm server.
         Rationale: Eliminates the need to establish a separate hosting solution.
         Notes:
         Volatility: medium-term change likely
         Clarity: refine
         Recorded by: Jared Bendis and Claire Stewart
         System Components: Assets (Database)
         Stakeholders
                  Developers: Programmers
                  End Users: Maintenance Staff, Authors (Education), Project Managers, System
                  Administrators, Authors (Museum), Production Staff
         Official Priority: wishlist
         Desired Priority: desirable



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                       79
Section 5.1: System Wishlist
    5.1.18 Annotating assets in a module (#37, revised)
         Authors should be able to add annotations to assets.
         Rationale: Another way to include information about assets.
         Notes: Suggestions from the scenario: annotate a certain part of an asset by setting a
         link point; add a web link to an asset; add media to an asset. Include a comment link in
         the annotation that generates a web email to the author.
         Volatility: unspecific
         Clarity: refine
         Recorded by: Rachel Smith
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Programmers, Metadata Experts
                  End Users: Viewers (Education), Viewers (Museum), Authors (Education),
                  Authors (Museum)
         Official Priority: wishlist
         Desired Priority: desirable
         Comments
         Rachel Smith: Formerly 3.9.4.1 (Templates Unprioritized).




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                       80
Section 5.1: System Wishlist
5. Wishlist Requirements (continued)

5.2 User Interface & Usability Wishlist
    5.2.1     Drag and Drop Organization from an Outline Field (#287)
         Ability of the author to reorganize material based on outline page view simply by dragging
         and dropping a page from one place to another.
         Rationale: Something a tech-savvy user has come to expect from other web design tools
         so they might reasonably expect to do it in pachyderm.
         Notes:
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: Holly Witchey
         System Components: Authoring Tool
         Stakeholders
                  Developers: Programmers, User Interface Designers
         Official Priority: wishlist
         Desired Priority: wishlist
         Comments
         Rachel Smith: Formerly 3.6.1.26 (System Wishlist).

    5.2.2     Look-and-feel Authoring Tool (#122)
         Provide a tool within pachyderm, or as a separate tool, that facilitates the creation or
         modification of look-and-feel templates by non-technical users. The Look and Feel are
         made up of the color scheme, graphic elements, and layout of the screen.
         Rationale: This would allow customizability of the look-and-feel of pachyderm authored
         presentations by a wider audience (non-technical users).
         Notes:
         Volatility: short-term change likely
         Clarity: clear
         Recorded by: Lou Zweier
         System Components: Authoring Tool
         Stakeholders
                  Developers: User Interface Designers, Pedagogy Experts (templates),
                  Programmers
                  End Users: Production Staff, Authors (Education), Authors (Museum)
         Official Priority: wishlist
         Desired Priority: wishlist




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                       81
Section 5.2: UI & Usability Wishlist
5. Wishlist Requirements (continued)

5.3 Metadata Wishlist

None.




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004   82
Section 5.3: Metadata Wishlist
5. Wishlist Requirements (continued)

5.4 Template Wishlist
    5.4.1     Redesign of Pachy 1.0 screen templates for PDA format (#61)
         Screen types such as Context, Artwork, Video Focus, Formal Analysis & Book Viewer will
         need to be adapted to deliver just-in-time rich media experiences via the smaller content
         vehicle of the wi-fi PDA.
         Rationale: It is clear that PDAs represent an important option in the museum education
         toolbox moving forward. They are equally prevalent on college campuses. Adapting
         Pachy templates to PDA size will be a strong selling point, empowering us to deliver just-
         in-time content when it is most needed--and meeting the market trend just when a PDA
         content solution is most needed!
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Peter Samis
         System Components: Templates
         Stakeholders
                  Developers: Pedagogy Experts (templates), User Interface Designers,
                  Programmers
                  End Users: Viewers (Education), Authors (Education), Viewers (Museum),
                  Authors (Museum)
         Official Priority: wishlist
         Desired Priority: desirable
         Comments
         Group decision: Wishlist this. Formerly 3.5.2.6 (Out of Scope).

    5.4.2     Pachyderm Templates Sized/Simplified for PDA Display (#230)
         Creation of a set of templates structured to meet the requirements of display on pda.
         Rationale: PDAs becoming more and more ubiquitous there will come a time when
         authors will want to design pachy-modules for display on pdas.
         Notes: This is an easy requirement to pull out but not an easy requirement to describe--
         presumably all templates will have to be skinned down for display. What kind of display
         will be standard size. Need to create a new set of sizes for images for display on
         pda...and on and on. This is basically the creation of a mini-pachyderm system.
         Volatility: short-term change likely
         Clarity: clear
         Recorded by: Holly Witchey
         System Components: Templates
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Museum), Authors (Education), Viewers (Education),
                  Authors (Museum)
         Official Priority: wishlist
         Desired Priority: wishlist
         Comments
         Unknown: They just need to make PDAs bigger...
         Group decision: Wishlist this. Formerly 3.5.2.23 (Out of Scope).




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                    83
Section 5.4: Template Wishlist
5. Wishlist Requirements (continued)

5.5 Help & Documentation Wishlist
    5.5.1     Real-time technical support via chat (#292)
         The Pachyderm system will include real-time technical support via chat for authors who
         need assistance.
         Rationale: Users should be able to get help immediately, and should not have to rely on
         an in-person visit, or phone help, to get it.
         Notes:
         Volatility: short-term change likely
         Clarity: clear
         Recorded by: Claire Stewart
         System Components: Authoring Tool, Assets (Database), Templates, Other
         Stakeholders
                  Developers: Programmers
                  End Users: Authors (Education), System Administrators, Authors (Museum),
                  Maintenance Staff
         Official Priority: wishlist
         Desired Priority: wishlist
         Comments
         Rachel Smith: Formerly 3.6.1.27 (System Wishlist).

    5.5.2     Intelligent advisor tracks the author's progress (#298)
         The Pachyderm context-sensitive help system pushes help and support information to
         authors rather than waiting for them to go looking for help.
         Rationale: Users may be more inclined to use help if it is clearly relevant to what they
         are doing at that exact moment.
         Notes:
         Volatility: short-term change likely
         Clarity: clear
         Recorded by: Claire Stewart
         System Components: Authoring Tool
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: wishlist
         Desired Priority: wishlist
         Comments
         Michelle LaMar: I think this is a bad idea. The MS paper-clip annoys most people I've
         talked to, and MS spent a lot of time and effort on that feature.
         Rachel Smith: Formerly 3.6.1.28 (System Wishlist).

    5.5.3     Testing & feedback module (#87)
         Support for password-protected tests/quizzes in Pachyderm presentations. Allows
         authoring quizzes in diverse question/answer formats. Access to further subject matter
         content is contingent on passing of quizzes. Allows student feedback about the quiz.
         Automatically tallies test results and sends to both students and professor. [In fact, all of
         these are separate requirements for the testing module.]
         Rationale: Assures that student has mastered preliminary content required for
         understanding more advanced lessons. Serves as built-in review and internalization of
         content, and as diagnostic/grading tool for professor. Also serves as feedback tool from
         student to professor.
         Notes: Could these results be achieved by linking Pachyderm to a Web CT/Blackboard


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                            84
Section 5.5: Help & Documentation Wishlist
         or Breeze-like engine that has these quiz, feedback, and administrative functions already
         built in? The applications would have to talk to each other/trigger events, so that access
         to further Pachy content could be made contingent on passing the test. Or perhaps
         Pachy would function within the Web CT environment, and Web CT would dole out the
         new Pachy modules as each new test was passed. That seems more likely.
         Volatility: short-term change likely
         Clarity:
         Recorded by: Peter Samis
         System Components: Other
         Stakeholders
                   Developers: User Interface Designers, Programmers, Pedagogy Experts
                   (templates)
                   End Users: Authors (Education), Viewers (Education)
         Official Priority: wishlist
         Desired Priority: useful
         Comments
         Rachel Smith: Formerly 3.6.5.2 (Unclassified Wishlist).

    5.5.4     Staff Training Development/ Learning Modules (#107)
         A set of compressive training modules is required for users to learn about the system.
         Rationale: Each training module should focus on different goal and objectives
         (needs/tasks/issues). The training methods should be designed for different type of
         audiences.
         Notes: Based on the audience’s learning behavior, training should focus on the benefits
         of adopting Pachyderm. --> Link to their daily research/teaching events.
         Volatility: medium-term change likely
         Clarity:
         Recorded by: Wendy Shapiro
         System Components: Authoring Tool, Assets (Database), Templates
         Stakeholders
                  Developers: Pedagogy Experts (templates)
         Official Priority: wishlist
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 3.6.5.3 (Unclassified Wishlist).




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                    85
Section 5.5: Help & Documentation Wishlist
6. Process Requirements
Process requirements are generally descriptions of end-user activities which were captured
during the requirements-gathering process. They are beyond our ability to implement and are
included here for reference purposes.

    6.1 Bug tracking system (#183)
         During development and beyond, an efficient and easy-to-use system for reporting and
         tracking bugs
         Rationale: Sanity. QA.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: Michelle LaMar
         System Components: Other
         Stakeholders
                  Developers: User Interface Designers, Programmers
                  End Users: Production Staff, System Administrators, Maintenance Staff
         Official Priority: essential
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 3.1.1.24 (System Essential).

    6.2 Hosted modules can be access-restricted (#217)
         When modules are published and hosted on the Pachyderm server, user-level access
         restrictions can be applied.
         Rationale: Some modules may be appropriate for only some users.
         Notes:
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: Jared Bendis and Claire Stewart
         System Components: Other
         Stakeholders
                   Developers: Programmers
                   End Users: Viewers (Education), System Administrators, Authors (Education),
                   Project Managers, Viewers (Museum), Authors (Museum), Production Staff
         Official Priority: wishlist
         Desired Priority: wishlist
         Comments
         Rachel Smith: Formerly 3.6.1.24 (System Wishlist).

    6.3 Collaborative teamwork (#108)
         1. Photo Studios – Produce images 2. Media Department – Video clips 3. Info Producer –
         Content editing/translation 4. Web Group – Web Interface 5. Pachyderm Expert – Project
         Coordination
         Rationale: A comprehensive training can help team members to define the project scope
         and identify his/her role in the production team. Allow Deadline (Time schedule) for each
         tasks are needed to avoid the delays. learning curve period.
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Wendy Shapiro
         System Components: Other
         Stakeholders



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                    86
Section 6: Process Requirements
         Official Priority: unspecific
         Desired Priority: essential

    6.4 Hard Drive (#116)
         An additional hard drive is needed to store the existing assets.
         Rationale:
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Wendy Shapiro
         System Components: Other
         Stakeholders
                  Developers: Metadata Experts, Programmers
                  End Users: Authors (Education), Production Staff, Maintenance Staff, System
                  Administrators, Authors (Museum)
         Official Priority: unspecific
         Desired Priority: essential

    6.5 Size of the Digital Assets Database Server (#118)
         - How much the database should be “enough” in this case? Should start with a smaller
         size server first then expend? Or should they start with a bigger one to prepare for the
         future? - How many assets are existed and how many more assets will be produced
         (within what time frame)? - How much budget does the department has for this project? -
         How many professors will be using this system? Is this system is required to be used for
         all social science professors?
         Rationale:
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Wendy Shapiro
         System Components: Other
         Stakeholders
                  Developers: Programmers, Pedagogy Experts (templates), User Interface
                  Designers, Metadata Experts
                  End Users: Maintenance Staff, Authors (Education), System Administrators,
                  Production Staff, Authors (Museum), Project Managers
         Official Priority: unspecific
         Desired Priority: essential

    6.6 Assistants (#119)
         Need students to catalogue and input the existing digital assets into the Pachyderm
         database.
         Rationale:
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Wendy Shapiro
         System Components: Other
         Stakeholders
                  End Users: Authors (Education), Production Staff, Authors (Museum),
                  Maintenance Staff
         Official Priority: unspecific
         Desired Priority: essential

    6.7 Pachyderm is "updateable" (#133)

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                   87
Section 6: Process Requirements
         There is a periodic review and updating of aspects of Pachyderm that are tied to
         programs such as Flash or any other evolving environmental components and conditions.
         Whether this happens via an open source model or a top-down teamwork approach
         overseen by the Pachyderm team and NMC can be discussed.
         Rationale: We need to keep it alive as standards and the interactive environment evolve
         technologically.
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: John Weber
         System Components: Other
         Stakeholders
                  Global Concern: Global Concern (all stakeholders)
         Official Priority: unspecific
         Desired Priority: essential
         Comments
         Group decision: Process requirement.

    6.8 consistent naming of media files (#268)
         either call everything *media* or use *video* to describe audio files that are accompanied
         by moving images as well as true video files.
         Rationale: sometimes audio files are accompanied by moving images which the viewer
         interprets as a video, but the label says audio.
         Notes:
         Volatility: stable
         Clarity:
         Recorded by: Deborah Howes
         System Components: Templates, Other
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Museum), Authors (Education), Viewers (Education),
                  Authors (Museum)
         Official Priority: essential
         Desired Priority: unspecific
         Comments
         Michelle LaMar: This requirement is referring to problems that users had in dealing with
         audio and video clips within a finished Pachyderm module.
         Group decision: Process requirement.




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                    88
Section 6: Process Requirements
7. Out of Scope Requirements
Out of scope requirements are considered to be beyond the scope of the Pachyderm project.
These were captured during the requirements-gathering process and are recorded here for
reference.

    7.1 Forms-based input for student responses (#44)
         Ability to answer questions pegged to content and post observations and/or conclusions
         in a structured way. Can be shared with other team member/collaborators and/or
         instructors. They can annotate and/or reply in turn.
         Rationale: Encompasses not just the passive inquiry/research phase of learning, but the
         active processing and application phase: communicating one's thoughts & conclusions
         for purposes of collaboration and teacher feedback.
         Notes: Makes Pachyderm a 2-way communication tool, not just a way to publish
         presentations of rich content. Might this also be done by pairing Pachyderm with a blog or
         Wiki?
         Volatility: short-term change likely
         Clarity: refine
         Recorded by: Peter Samis
         System Components: Authoring Tool, Templates
         Stakeholders
                   Developers: Programmers, Pedagogy Experts (templates), User Interface
                   Designers
                   End Users: Authors (Education), Viewers (Education)
         Official Priority: wishlist
         Desired Priority: unspecific

    7.2 Allow users to input audio annotations (#45)
         Taking "Forms-based input for student responses" one step further, this requirement
         anticipates a system that would allow students to make audio annotations pegged to
         content published in Pachyderm presentations. It presumes a Pachyderm
         communications center with at least 2-way (and perhaps many to many) audio
         functionality.
         Rationale: For collaborative teams, or student-teacher interaction, models delivery of
         oral reports about content in the Pachyderm presentation.
         Notes: Once again, could this be achieved by linking Pachyderm presentations with
         already existing conferencing software (e.g., Breeze or icohere?). Presumes the ability to
         tag annotations to specific points in the Pachy presentation.
         Volatility: short-term change likely
         Clarity: clear
         Recorded by: Peter Samis
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Programmers, Pedagogy Experts (templates), User Interface
                  Designers
                  End Users: Viewers (Museum), Authors (Education), Viewers (Education)
         Official Priority: wishlist
         Desired Priority: wishlist
         Duplicates: Allow users to input audio annotations (#53), Creating an Audio Annotation:
         When I'm Calling Yooo--oo--ooo-oo (#261)

    7.3 Virtual Gallery (#57)
         Simulation of a "virtual visit" to museum galleries as interface to deeper content
         Rationale: Many museums see (and visitors) see the spatial metaphor of their own
         galleries as the best interface for probing the meanings associated with each work. This


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                       89
Section 7: Out of Scope Requirements
         would give them that option.
         Notes: I think we would do well to work with Jordan Klineman and the folks who are
         developing Virtual Galleries to ensure compatibility with Pachy 2.0
         Volatility: unspecific
         Clarity: refine
         Recorded by: Peter Samis
         System Components: Templates
         Stakeholders
                  Developers: User Interface Designers, Metadata Experts, Programmers
                  End Users: Viewers (Education), Viewers (Museum), Authors (Education),
                  Project Managers, Authors (Museum)
         Official Priority: unspecific
         Desired Priority: wishlist

    7.4 Arrange Objects in Your Own Gallery (#58)
         Ability for users to manipulate and arrange objects/artworks in a "virtual gallery" and save
         or post the products for future reference/others to see.
         Rationale: Perhaps more powerful than a virtual gallery walk-through, the invitation to
         actually make choices about which objects go where, and to articulate the relationships
         thereby created, is a user-centered, engaging learning strategy.
         Notes: Once again, I would recommend partnering with Jordan Klineman and his Virtual
         Gallerie team. (SFMOMA has done more rudimentary versions of this feature: our Art as
         Experiment, Art as Experience Gallery Experience feature and Make Your Own Gallery in
         the exhibition Points of Departure. Jordan is doing it better!
         Volatility: unspecific
         Clarity: refine
         Recorded by: Peter Samis
         System Components: Templates
         Stakeholders
                   Developers: Metadata Experts, Pedagogy Experts (templates), Programmers,
                   User Interface Designers
                   End Users: Viewers (Education), Viewers (Museum), Project Managers
         Official Priority: unspecific
         Desired Priority: wishlist
         Duplicates: Virtual Gallery (#57)

    7.5 Ability for remote users to add and/or modify content (#79)
         Multiple users in multiple locations to add text content and upload assets to a frequently
         changing system.
         Rationale: Rationale according to Scenario 66 is user who wants to use Pachyderm to
         create an organic web site (family-tree type) where visitors in multiple locations can add
         content to a site.
         Notes: This is a nice concept but would seem to be beyond the scope of our project--
         probably want to keep a reign on making this product try and do and be everything. I'm
         willing to bet there is already an off-the-shelf product that "Tony" could use instead of
         trying to have Pachyderm fill this need. Peter's note: Pachyderm 1.0 does already work
         like this in a limited way. Anybody with access privileges can add to or modify texts, and
         even change media out, over the Web. I'm not sure it supports uploading assets from
         multiple locations, though. This also raises the issue of security: once one person has
         authored a presentation, can others tamper with it? Question of password-protected
         access at the directory or presentation level.
         Volatility: stable
         Clarity: refine
         Recorded by: Holly Witchey



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                         90
Section 7: Out of Scope Requirements
         System Components: Authoring Tool, Assets (Database), Other
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Museum), Authors (Education), Viewers (Education),
                  Authors (Museum)
         Official Priority: essential
         Desired Priority: wishlist
         Comments
         Group decision: Out of Scope.

    7.6 Documentation for edits to shared modules (#80)
         Ability for authors sharing modules to quickly see and track how modules have been
         changed--primarily with regard to content.
         Rationale:
         Notes: The scenario posed a module that was going to be shared by two colleagues.
         Don't know whether a notes field exists as a place to comment on recent changes.
         Volatility: short-term change likely
         Clarity: refine
         Recorded by: Holly Witchey
         System Components: Authoring Tool
         Stakeholders
                   Developers: Programmers, User Interface Designers
                   End Users: Authors (Education), Authors (Museum)
         Official Priority: wishlist
         Desired Priority: wishlist

    7.7 The Opera Continues: Pachyderm as a Tool for Harassment in the Workplace (#83)
         A mechanism to insure that Pachyderm is used only for good, and never for evil.
         Rationale: Clearly Sharon T. needs to seek help from professionals and Forest, a classic
         enabler needs to extricate himself from the situation and settle down with his life-partner
         Pat on a farm in New Zealand. ( Forest raised his 11 younger brothers and sisters on his
         own after his parents were lost in a freak Antarctic disaster involving thousands of
         penguins and a barrel of fresh fish.) But will he......?
         Notes: Somebody else write the next chapter---what will Forest do? I'm thinking maybe
         SuperSamis arrives with his trusty aquatic sidekick Pachy-Perch and saves the day by
         imprisoning both in the Mrs. Paul's Frozen Fish Factory until they chill out. ****Sorry
         Rachel, I just needed a break from real requirements for a moment and was carried away
         by the scenario.
         Volatility: unspecific
         Clarity:
         Recorded by: Holly Witchey
         System Components: Other
         Stakeholders
                  End Users: Authors (Museum)
         Official Priority: unspecific
         Desired Priority: wishlist

    7.8 Pachy presentations triggered by transmission of data from PDA (#91)
         Content is automatically organized according to reference codes visitor has transmitted
         from a PDA, and then presented to visitor on a touchscreen computer display.
         Rationale: While we take great pains to organize information into canonical, meaningful
         relationships, the fact of the matter is that museums are free-choice learning
         environments, and each visitor's itinerary creates a personalized thread of understanding.
         By using a handheld device to record objects of interest, visitors can customize their
         educational experience to the content that is most relevant to them.

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                     91
Section 7: Out of Scope Requirements
         Notes: Note: This is a duplication of requirement #90. (A craven attempt to stuff the ballot
         box for "Requirements Guru" status, or a glitch in the data entry process? ;-)
         Volatility: unspecific
         Clarity:
         Recorded by: Peter Samis
         System Components: Templates
         Stakeholders
                  Developers: Programmers, Metadata Experts
                  End Users: Viewers (Museum)
         Official Priority: unspecific
         Desired Priority: desirable
         Comments
         Group decision: Out of Scope.

    7.9 Assessment Template (#124)
         Provide a Pachyderm template that allows authors to include an assessment of what the
         user has learned. Examples of an assessment could be a quiz with multiple choice, short
         answer, matching, or true/false questions.
         Rationale: Authors would like to get some measure of the effectiveness of the materials
         they create. Also, the assessment could serve as a way to provide feedback to the user
         on what they are learning (a self assessment).
         Notes: This function should be built to relevant standards (e.g. IMS QTI) so that it can
         report its results to LMS's or other systems that manage assessment data.
         Volatility: unspecific
         Clarity: clear
         Recorded by: Lou Zweier
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Pedagogy Experts (templates), User Interface Designers,
                  Programmers
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: unspecific
         Desired Priority: wishlist
         Comments
         Group decision: Out of Scope.

    7.10          Item Finder Wizard (#156)
         For each media type, the item finder wizard should immediately accesses that designated
         media asset repository in the database.
         Rationale: Eliminate extra step in existing process. Simplify.
         Notes:
         Volatility: short-term change likely
         Clarity: unclear (I'm not sure what this means)
         Recorded by: Ted/Wendy
         System Components: Assets (Database)
         Stakeholders
                  Developers: Pedagogy Experts (templates), User Interface Designers
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: wishlist
         Desired Priority: essential
         Comments
         Group decision: Out of Scope

    7.11          Dumbo-Modules: Creating A Custom Pachyderm Tour On the Fly (#171)



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                      92
Section 7: Out of Scope Requirements
         Primarily for a museum--if you've got your database of works and you've got a set of
         clean templates. Create a mechanism to allow the average visitor to create simply
         Pachyderm modules that reinforce what they liked on their visit.
         Rationale: The uses of this would be multiple--teachers could craft pre-tour visits,
         families could create one-of-a-kind experiences that have a life after the actual visit.
         Notes: The complex issue here is how does the visitor search the database for the
         images they want in a useful fashion--maybe the hand-held device isn't required at all--
         just a lovely visual mechanism for searching the collection.
         Volatility: unspecific
         Clarity:
         Recorded by: Holly Witchey
         System Components: Other
         Stakeholders
                  Developers: Programmers
                  End Users: Viewers (Museum), Viewers (Education)
         Official Priority: unspecific
         Desired Priority: desirable
         Comments
         Out of scope.

    7.12          Multiple-choice question assessments (#175)
         Authors can build assessments into Pachyderm learning objects.
         Rationale: May want to use learning objects for evaluation/testing/assessment.
         Notes:
         Volatility: unspecific
         Clarity: clear
         Recorded by: Claire Stewart and Jared Bendis
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: User Interface Designers, Pedagogy Experts (templates),
                  Programmers
                  End Users: Viewers (Museum), Authors (Education), Viewers (Education),
                  Authors (Museum), Project Managers
         Official Priority: unspecific
         Desired Priority: wishlist
         Duplicates: Assessment Template (#124), Pachyderm Incorporates Assessment
         Modules (#186)
         Comments
         Group decision: Out of Scope.

    7.13          Pachyderm Incorporates Assessment Modules (#186)
         Pachyderm modules for use in educational settings need to be able to accommodate
         different types of assessment modules.
         Rationale: In order to make the pachyderm tool valuable for educators as both an
         informative and instructional tool.
         Notes: Question is does they pachyderm authoring tool itself need to be able to allow
         and author to create assessment modules or just to link to other sites/tools with which
         assessment programs can be created.
         Volatility: unspecific
         Clarity: clear
         Recorded by: Holly Witchey
         System Components: Authoring Tool, Templates, Other
         Stakeholders




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                       93
Section 7: Out of Scope Requirements
                  Developers: Programmers
                  End Users: Authors (Education), Viewers (Museum), Authors (Museum), Viewers
                  (Education)
         Official Priority: unspecific
         Desired Priority: useful
         Duplicates: Testing & feedback module (#89), Assessment Template (#124)
         Comments
         Group decision: Out of Scope.

    7.14          IMS Learning Design (#218)
         Use IMS Learning Design as the structure to describe the pedagogical process and intent
         of the instructional task. Pachyderm has been described as a collection of pedagogical
         templates. IMS Learning Design is based on the Educational Modeling Language which
         provides a language that is easily understandable by humans and also machine readable
         as structured metadata that is expressed in an IMS content package. This provides a
         level of abstraction that creates activity structures that can be stored as objects and later
         modified and reused.
         Rationale: LD provides a standardized way to describe the teaching and learning
         process.
         Notes: http://www.imsglobal.org/learningdesign/index.cfm
         Volatility: unspecific
         Clarity:
         Recorded by: Mike Mattson
         System Components: Authoring Tool, Assets (Database), Templates
         Stakeholders
                  Developers: Pedagogy Experts (templates), Metadata Experts, Programmers
                  End Users: Authors (Education), Authors (Museum)
         Official Priority: unspecific
         Desired Priority: essential
         Comments
         Group decision: Out of Scope.

    7.15          Pachyderm must interoperate (#222)
         Must be interoperable with the range of current and emerging collections of digital
         materials found in libraries and museums across North America.
         Rationale: We thought this sounded good on the grant.
         Notes:
         Volatility: stable
         Clarity:
         Recorded by: Michelle LaMar, et al.
         System Components: Authoring Tool, Assets (Database)
         Stakeholders
                  Developers: Programmers, Metadata Experts
                  End Users: Maintenance Staff, System Administrators, Authors (Education),
                  Project Managers, Authors (Museum), Production Staff
         Official Priority: unspecific
         Desired Priority: wishlist
         Comments
         Group decision: Out of Scope.

    7.16          Template building tool (#246)
         Tool to aid in creation of new templates by non-programmers
         Rationale: To allow normal people to create new templates.
         Notes: this is hard
         Volatility: stable

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                       94
Section 7: Out of Scope Requirements
         Clarity: clear
         Recorded by: Michelle LaMar, et al.
         System Components: Authoring Tool, Templates
         Stakeholders
                  End Users: Authors (Education), Project Managers, Authors (Museum),
                  Production Staff
         Official Priority: wishlist
         Desired Priority: wishlist
         Duplicates: Interaction Design Template Authoring Tool (#123)
         Comments
         Group decision: Out of Scope.

    7.17       build entry wizard/guidelines to help select templates based on bandwidth
        (#256)
         authors should know which templates/media files are possible to use with low bandwidth
         connections.
         Rationale: help authors think about delivery of content
         Notes:
         Volatility: stable
         Clarity: refine
         Recorded by: Deborah Howes
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Museum), Authors (Education), Viewers (Education),
                  Authors (Museum)
         Official Priority: useful
         Desired Priority: wishlist
         Comments
         Group decision: Out of Scope.

    7.18          Blog features (#258)
         The Pachyderm system should support common blogging features such as comments.
         Rationale: Makes a connection between Pachyderm and another, heavily-used,
         technology.
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Claire Stewart
         System Components: Other
         Stakeholders
                  Developers: User Interface Designers, Programmers
                  End Users: System Administrators, Authors (Education), Production Staff,
                  Authors (Museum)
         Official Priority: unspecific
         Desired Priority: wishlist
         Comments
         Group decision: Out of Scope.

    7.19          User comments (#260)
         Allow the users to be able to add text comments about the presentation or the individual
         assets in context. These would be similar to the RSS trackback feature so that users can
         comment in context about the individual asset. Group discussions would be a great
         addition.



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                   95
Section 7: Out of Scope Requirements
         Rationale: Engage the users and encourage commentary by individuals or groups.
         Notes:
         Volatility: short-term change likely
         Clarity: clear
         Recorded by: Mike Mattson
         System Components: Other
         Stakeholders
                  Developers: User Interface Designers, Metadata Experts, Pedagogy Experts
                  (templates), Programmers
                  End Users: Authors (Education), Viewers (Education), Viewers (Museum),
                  Authors (Museum), Project Managers
         Official Priority: desirable
         Desired Priority: desirable
         Comments
         Group decision: Out of Scope.

    7.20          Data analysis or statistical tools (#262)
         Pachyderm should support some kind of data set retention and manipulation.
         Rationale: Some authors may want to perform mathematical manipulations of content.
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Claire Stewart
         System Components: Assets (Database), Templates, Other
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Authors (Education), System Administrators, Authors (Museum)
         Official Priority: unspecific
         Desired Priority: wishlist

    7.21          Video Display and Control (#279)
         Exert author control of the appearance/size of video objects
         Rationale: Improved bandwidth and compression allows for larger screen displays for
         video at acceptable quality; small window could deprive learner of useful detail; this is
         also significantly important if projected before a group.
         Notes: To the extent this control is governed by Flash restrictions, we should understand
         where this capability is heading.
         Volatility: unspecific
         Clarity:
         Recorded by: Leonard Steinbach
         System Components: Assets (Database), Templates
         Stakeholders
                  Developers: User Interface Designers, Pedagogy Experts (templates),
                  Programmers
                  End Users: Viewers (Museum), Authors (Education), Viewers (Education),
                  Authors (Museum), Production Staff
         Official Priority: unspecific
         Desired Priority: useful
         Comments
         Group decision: Out of Scope.

    7.22          Quiz (#228)
         Investigate the use of the IMS QTI specification for creating quiz and tests. If a flash
         component library is used it would be relatively easy to attach simple true/false, multiple
         choice and drag and drop exercises.

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                          96
Section 7: Out of Scope Requirements
         Rationale: Important for k-12 and university adoption.
         Notes: http://www.imsglobal.org/question/index.cfm
         Volatility: medium-term change likely
         Clarity: refine (We need more information on how the quiz would work and what would
         happen with the results.)
         Recorded by: Mike Mattson
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Metadata Experts, Pedagogy Experts (templates), Programmers
                  End Users: Authors (Education), Viewers (Education), System Administrators,
                  Authors (Museum)
         Official Priority: wishlist
         Desired Priority: useful
         Comments
         Group decision: Out of Scope. Formerly 3.6.1.25 (System Wishlist).

    7.23          Pachy Wizard Template (#78)
         Identification of key types of presentations and a wizard template system to walk author
         through creation of same.
         Rationale: Several of the scenarios indicate that this tool might be handed off willy-nilly
         (who is he anyway?) to unprepared authors. This might also serve as a training module
         for the system.
         Notes:
         Volatility: short-term change likely
         Clarity: refine
         Recorded by: Holly Witchey
         System Components: Authoring Tool, Templates, Other
         Stakeholders
                  Developers: Programmers, Metadata Experts, Pedagogy Experts (templates),
                  User Interface Designers
                  End Users: Authors (Education), Production Staff, Authors (Museum), Project
                  Managers
         Official Priority: desirable
         Desired Priority: useful
         Comments
         Group decision: Out of Scope.
         Rachel Smith: Formerly 4.1.3 (Process).

    7.24          Ability for Multiple Users to Communicate During Online Experience (#84)
         Some way for end-users, all of whom have to view a module, to view it remotely from one
         another and still communicate with one another.
         Rationale: 21rst Century Learners are used to being able to text message one another
         anytime, anyplace. Anyway to give that to them here.
         Notes: Peter's note: Enabling Pachyderm to interact with a blog would seem to be an
         answer here.
         Volatility: unspecific
         Clarity:
         Recorded by: Holly Witchey
         System Components: Other
         Stakeholders
                  Developers: Programmers, User Interface Designers
                  End Users: Viewers (Education), Other End Users, Viewers (Museum)
         Official Priority: unspecific
         Desired Priority: wishlist



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                          97
Section 7: Out of Scope Requirements
         Comments
         Rachel Smith: Formerly 4.1.4 (Process).

    7.25          Testing & feedback module (#89)
         Support for password-protected tests/quizzes in Pachyderm presentations. Allows
         authoring quizzes in diverse question/answer formats. Access to further subject matter
         content is contingent on passing of quizzes. Allows student feedback about the quiz.
         Automatically tallies test results and sends to both students and professor. [In fact, these
         are all separate requirements for the testing module.]
         Rationale: Assures that student has mastered preliminary content required for
         understanding more advanced lessons. Serves as built-in review and internalization of
         content, and as diagnostic/grading tool for professor. Also serves as feedback tool from
         student to professor.
         Notes: Could these results be achieved by linking Pachyderm to a Web CT/Blackboard
         or Breeze-like engine that has these quiz, feedback, and administrative functions already
         built in? The applications would have to talk to each other/trigger events, so that access
         to further Pachy content could be made contingent on passing the test. Or perhaps
         Pachy would function within the Web CT environment, and Web CT would dole out the
         new Pachy modules as each new test was passed. That seems more likely.
         Volatility: unspecific
         Clarity:
         Recorded by: Peter Samis
         System Components: Other
         Stakeholders
                   Developers: Programmers, Pedagogy Experts (templates), User Interface
                   Designers
                   End Users: Authors (Education), Viewers (Education)
         Official Priority: unspecific
         Desired Priority: useful
         Comments
         Group decision: Out of Scope. Formerly 4.1.5 (Process).

    7.26          Training pairs Old Hats to Newbies as mentors (#102)
         Seasoned faculty who are familiar with the authoring process show the uninitiated ones
         how to do it, and ways to think about making their course content interactive
         Rationale: No one understands a professor's hesitation to author--or instructional goals--
         as well as a colleague. Newbie (scratching head): "If s/he can do it, I can do it."
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Peter Samis
         System Components: Authoring Tool, Other
         Stakeholders
                  End Users: Authors (Education), Production Staff, Authors (Museum)
         Official Priority: unspecific
         Desired Priority: desirable
         Comments
         Group decision: Out of Scope. Formerly 4.1.6 (Process).

    7.27          Grouping Trainees (#104)
         It is helpful to categorize trainees and design specific training courses for different
         learners.
         Rationale:
         Notes:
         Volatility: unspecific

Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                      98
Section 7: Out of Scope Requirements
         Clarity:
         Recorded by: Wendy Shapiro
         System Components: Other
         Stakeholders
                  Developers: Pedagogy Experts (templates)
                  End Users: Authors (Education), Maintenance Staff, Authors (Museum),
                  Production Staff
         Official Priority: unspecific
         Desired Priority: useful
         Comments
         Group decision: Out of Scope. Formerly 4.1.7 (Process).

    7.28          Standard Presentation Tool/System (#106)
         Allow trainers to deliver same presentation/training in different sites without any
         technology transfer or additional equipment.
         Rationale: Training standards & materials need to be identified.
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Wendy Shapiro
         System Components: Other
         Stakeholders
                  Developers: Pedagogy Experts (templates)
         Official Priority: unspecific
         Desired Priority: essential
         Comments
         Group decision: Out of Scope. Formerly 4.1.9 (Process).




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                  99
Section 7: Out of Scope Requirements
8. Assumptions
These assumptions were captured during the requirements-gathering process and are noted here
for reference.

    8.1 Define target audience (#290)
         The target audiences for the Pachyderm tool are: 1. Educators wanting a presentation
         tool 2. Museum educators 3. Museum visitors 4. Students/life long learners using a pre-
         created Pachyderm object 5. Students/life long learner using Pachyderm as an authoring
         tool
         Rationale: In creating a high quality Pachyderm tool it is important to define the target
         audience.
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Wendy Shapiro
         System Components: Other
         Stakeholders
                  Global Concern: Global Concern (all stakeholders)
         Official Priority: unspecific
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 4.1.49 (Process).

    8.2 Create Pachyderm Objects (#291)
         Develop a range of high-quality immersive discovery-based learning experiences after
         Pachyderm tool is created.
         Rationale: We need examples to demonstrate and share.
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Wendy Shapiro
         System Components: Other
         Stakeholders
                  End Users: Authors (Education), Viewers (Education), Authors (Museum),
                  Viewers (Museum)
         Official Priority: unspecific
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 4.1.50 (Process).

    8.3 Educator's Tool (#295)
         Pachyderm is a software tool that allows and encourages educators to produce multi-
         media teaching materials quickly, with minimal training, supporting a broad range of
         teaching philosophies, learning styles, educational objectives and presentation styles.
         Rationale: With this tool, educators who are not technology experts will feel comfortable,
         effective and efficient expressing themselves through multimedia, and find that the
         lessons they develop hold great long term value for themselves and their students.
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Wendy Shapiro
         System Components: Other
         Stakeholders
                  Global Concern: Global Concern (all stakeholders)


Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                   100
Section 8: Assumptions
         Official Priority: unspecific
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 4.1.51 (Process).

    8.4 MAKE NEW CONTENT! (#242)
         Central to the project is the development of several major new visitor and learning
         experiences by the museum and university partners using the new environment.
         Rationale: These will constitute a comprehensive test of the software and prove its worth
         as an authoring environment — as well as provide exemplars for how it might be used.
         Notes: we promised.
         Volatility: unspecific
         Clarity:
         Recorded by: D'Arcy Norman
         System Components: Other
         Stakeholders
                  Developers: Pedagogy Experts (templates)
                  End Users: Production Staff
         Official Priority: unspecific
         Desired Priority: essential
         Comments
         Rachel Smith: Formerly 4.1.36 (Process).

    8.5 Unlimited range of topics for content (#198)
         Need to be able to use Pachyderm to create presentations on any topic, including
         science, health, etc... To provide a nonlinear alternative to PowerPoint presentations.
         Rationale: Availability of content to non-art-museum users.
         Notes:
         Volatility: stable
         Clarity: clear
         Recorded by: D'Arcy Norman
         System Components: Authoring Tool, Templates
         Stakeholders
                  Developers: Pedagogy Experts (templates)
                  End Users: Authors (Education), Authors (Museum), Production Staff
         Official Priority: essential
         Desired Priority: useful
         Comments
         Rachel Smith: Formerly 4.1.28 (Process).

    8.6 Voices and Images Presentation (#213)
         Voices and Images is comparable to Pachyderm - results are valid for Pachyderm
         project.
         Rationale:
         Notes: This means that data collected by observing people using Voices & Images is
         assumed to be relevant for Pachyderm.
         Volatility: unspecific
         Clarity:
         Recorded by: Ted/Wendy
         System Components: Other
         Stakeholders
         Global Concern: Global Concern (all stakeholders)
         Official Priority: unspecific
         Desired Priority: unspecific



Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                      101
Section 8: Assumptions
9. Issues
These issues were captured during the requirements-gathering process and are noted here for
reference. We may wish to discuss these issues further.

    9.1 How Do We Want Them to Find Us? (#85)
         Scenario 53 describes people seeking for specific content and ultimately finding a
         pachyderm module with that content, after a long involved search. How do we want
         people to find our information?
         Rationale: In the Universe of Pachy-land will authors be encouraged to list their products
         so people who know about Pachyderm can find subject modules? This seems
         reasonable. I think we do not want to confuse our enthusiasm for this project, with the
         content that ultimately results. Remember, Pachyderm once free can be used to build
         sites on everything from Global Warming to the Support of the KuKluxKlan. Beautiful
         useful templates about Renoir can just as easily be used to display pornography.
         Notes:
         Volatility: unspecific
         Clarity:
         Recorded by: Holly Witchey
         System Components: Other
         Stakeholders
                  Global Concern: Global Concern (all stakeholders)
         Official Priority: unspecific
         Desired Priority: wishlist
         Comments
         Joshua Archer: Perhaps we need to leverage our links with Merlot. Do we need to
         change publishing so that a rider file comes along with the .swf file, for indexing on
         search engines?

    9.2 MORE TEMPLATES! (#194)
         More Flash templates developed that are less specific to MSOMA and museums. ( The
         ability of users to create their own templates somehow? )
         Rationale: Flexibility in authoring, and in contexts of use.
         Notes:
         Volatility: medium-term change likely
         Clarity: clear
         Recorded by: D'Arcy Norman
         System Components: Authoring Tool, Templates
         Stakeholders
                   Developers: Pedagogy Experts (templates)
                   End Users: Authors (Education), Authors (Museum), Production Staff
         Official Priority: useful
         Desired Priority: useful
         Comments
         Unknown: This seems like a discussion to be had about templates AND screen designs,
         more likely about screen designs ?
         Rachel Smith: Formerly 3.2.2.16 (UI Useful). May be related to Template Authoring
         requirements (#246, #256, #78).




Pachyderm 2.0 Requirements Document (version 1.5) | 5/19/2004                                   102
Section 9: Issues

								
To top