Client Meeting: 10.24

Participants

For Blink:

Kelly Franznick

Karen Clark

For Lost Heroes:

Randy Keller

Alex Mikitik

Grethe Tilly

 

 

  1. Communication
    1. Client Communication
      1. Email - Primary form of communication. Client response is/will be prompt. Also a venue for small file exchange.
      2. Telephone - Limited, best not to abuse.
      3. Meetings - Sparse. Client is generally busy so meetings should be kept at a minimum. Should explore possibility of regular meeting times.
      4. Website - Though briefly discussed at the meeting, I feel that this is a good time to discuss the projects website. It should serve as forum for both parties to review all project related material. (Read notes later on)
    2. Team Communication
      1. Email - Primary communication between team & Grethe. Also a good form of quick mass communication between all team members.
      2. Telephone - Immediate communication for those located in Olympia.
      3. Meetings - Regular (read: weekly) meeting times are a must. They will occur primarily between those team members located in Olympia. Further meeting schedules must be worked out though. At minimum, meetings will occur once a week.
      4. Website - See notes below
  2. Client Needs
    1. Basic Needs
      1. Mapping Editor - Client must be able to create a tree structured, icon & text based navigational map for a given project and/or platform.
        1. Tree Structured - Basically, a hierarchy that is navigable by both the Mapping Editor and a text-based tree.
        2. Icons & Text - Destination, objects, relationships, will all be represented by icons and labeled with text. A standard set of icons is to be included with the option of adding more as needed.
      2. Wireframe Editor - The second major function of the software. The Wireframe Editor is used to create actual mockups (a.k.a. wireframes) for the destinations defined in the Mapping Editor.
        1. Master Templates - Client should be able to create a layout (or partial layout) that extends to every page defined in the Mapping Editor. This includes functionality (see below).
        2. Drawing Tools - As this is a graphical layout, the client will need to a set of tools to allow the creation of any content needed. Examples include boxes, scrollbars, select boxes, etc. Elements should be functional if designated so.
        3. Functionality - Any elements which are not strictly design oriented should contain functionality. This includes buttons clicking, navigation working, pull down boxes selectable, etc. The limit of an element’s functionality is very basic (so no database calls or imbedded applets).
        4. Integration - Each wireframe must correspond with a destination defined in the Mapping Editor. Wireframe destinations should be accessible through both of the design views (Mapper and Wireframer) and the more general text view.
      3. Print Capabilities - Each of the two main editing views of the software must be able to print exactly what is displayed on screen.
      4. Save Capability - The software must be able to save a file so that it may be worked on later. For compatibility reasons, the save file should be platform independent.
      5. Expandable (Scalable) - Client must be able to add components to applicable portions of the software. These additions should be either program specific or project specific.
    2. Advanced Needs
      1. Code Generation - (Wireframer) Have the software able to output web pages based on the wireframe models.
      2. Navigator Window - (Mapper)Have a Photoshop-like navigation window to quickly move about a site map.
      3. PDF Output Format - Have the software able to export its maps/wireframes in PDF format.
      4. Auto-Map Feature - Have the software able to import an existing website and map it automatically.
      5. Isometric Mapping - Have the software create a 3-D map with a printable, isometric view of the site map.
  3. Project Website
    1. Site Goals
      1. Provide information about the team
        1. Names
        2. Contact info
        3. Job roles
        4. Weekly schedules
        5. Alter ego
      2. Provide information about the project
        1. Project mission
        2. Client needs
        3. Meetings
        4. Design documents
        5. Glossary
    2. Team Information
      1. Names - The superhero’s name and powers
      2. Contact info - The best Bat-Signal to use
      3. Job roles - How this hero contributes to the team
      4. Weekly schedules - The mammoth tasks the hero is performing that week
      5. Alter ego - The hero’s secret identity (but don’t tell)
    3. Project Information
      1. Project mission - A set of goals the team will strive to achieve. These are also guidelines the team will follow in the course of completing their mission.
      2. Client Needs - So that everyone may be informed and on the same page, the client’s needs will be solidly defined early on and rigidly followed (hopefully avoiding creep).
      3. Meetings - Client and team meeting schedules. Also the rough minutes/decisions of each meeting.
      4. Design documents - All the material generated from project’s design and analysis phase. Perhaps in PDF format?
      5. Glossary - When we say Bat-Signal, we mean email. Our internal terminology.
    4. Future Plans
      1. Streamline Site Production - Hopefully by using some nifty technologies, we can make maintaining the site easier.
      2. Site Home - Need to migrate the site to a stable webspace that maybe supports said nifty technologies.