In
attendance: Andrew Geraghty,
Denis Roi, Ian Skerret, Susan Iwai, Mike Milinkovich
Absent: Bjorn Freeman-Benson
Phoenix Project
Status
Call
- Requirements Gathering (Use Case
Analysis / Functional Requirements
Survey)
<--! moving forward use cases will be considered a collection
of scenarios related to a particular goal or function. The use case survey will
be a list of 'functional requirements' to help us drive out 'non-functional
requirements and the scenarios therein.
Use cases are to to identify,
clarify, and organize system requirements (In this case the web site and
administration interface). The use case is made up of a set of possible
sequences of interactions between the web site, administrators and
users The use case should contain all system activities that have
significance to the administrators and/or users. A use case can be thought of as
a collection of possible scenarios related to a particular goal
or function.
A use case (or set of use
cases) has these characteristics:
- Organizes 'functional' requirements
- Models the goals of
system/actor (user) interactions
- Records paths (called
scenarios) from trigger events to goals
- Describes one main flow
of events (also called a basic course of action), and possibly other ones,
called exceptional flows of events (also called alternate courses of action)
- Is multi-level, so that
one use case can use the functionality of another one.
Some new functional requirements tabled to be added to use
case survey include:
- a content ranking system (similar
to that found on EPIC, used for rating plug-ins, article, books, projects,
etc...)
- user profiling in order to filter information
- multimedia content (i.e. interactive tutorials and tours)
--!>
- Card Sorting/ Conceptual Information Architecture first
level
<!-- the card sorting exercise is progressing
well although in this meeting consensus was that there need to be some
changes to the draft of our conceptual IA:
1. "GETTING STARTED", although an important grouping is not a
top level navigation item that should be made available throughout
the entire site. It will should appear in certain sections of the site
and its content will change to suit appropriate context and appropriate
audience.
2. The four top level zones moving forward will be drafted to
show: 1. "PROJECTS" 2. "MEMBERSHIP" 3. "COMMUNITY" and 4.
"DOWNLOADS"
*MEMBERSHIP This grouping will focus
on the value added to the Eclipse community by members as well as emphasise the
benefits of membership. It is also important to keep in mind that this section
should allow for members to maintain their own brand around their
offerings.
*DOWNLOADS -
will be redrafted to reflect groupings that organise them by project and
topic
3. Andrew will re-draft the conceptual IA and distribute it
on the phoenix-dev mailing list. Revisions will be made based on that feedback.
--!>
<!-- a wire-frame was distributed for discussion purposes
intended to illustrate how requirements could be organised based in
the context of a specific web page. The wire-frame is meant to be an example of
another tool for requirements gathering moving forward and does not
necessarily reflect a actual web page at this time<<
<!-- the site vocabulary is evolving through iterations of the
IA, use case analysis and so on. As navigation vocabulary becomes more refined
it will be communicated through the phoenix-mailing list
--!>
Other
Items
<!-- Andrew & Bjorn have been asked to draft a governance
proposal designed to enable projects to best manage their web presence with
the least amount of interference from the foundation; keeping the needs of the
entire community in mind --!>
Canary
Home Page - moving
forward
<!-- there will a a link posted to the quick fix home page
proposal for community feedback. This home page mock-up will be maintained
alongside Eclipse.org home page for one week at which time the phoenix team
will cease to update the page due to limited resources at this time.
--!>