Flashy XM Specification

From Open Source Ecology
Jump to: navigation, search

Contents

Specification

Flashy XM is a platform designed to meet these specifications:

  • Provides world-wide GVCS 50 development perspective including on-the-ground implementation at FeF
  • Utilizes wiki technology as the backbone for 0-barrier access to editing
  • Allows for zero click-level access to all work product for ~100 development steps on any of the 50 GVCS tools and on other tools in development at FeF
    • Transparency on work product (~100 development steps) provides granularity in viewing work product - thereby facilitating review process
  • Allows Planning and Review
    • Planning Survey sent to each developer every month, logged in database in alternate Work Log window, broken down by person
    • Review Survey sent 30 days after Planning Survey, logged as Planning Survey
    • Default function of Control Panel is to visualize progress - by quantity of tasks completed in Panel
  • Shows ongoing progress
    • Gantt charts in Work Log window
    • Work Log for every task
    • Work Log breakdown by person
    • Burndown graph is created based on number of Control Panel steps completed
  • Shows log of completed tasks and links to work product
  • Has survey form for meetings for automatic logging of meeting minutes onto Wiki; external API embedded; possible use of EtherPad
  • CAD problem statement, GVCS 50, OSE Campus facility, and Flash Mobs (technique development) are prominent work areas of Flashy XM platform
  • Shows ongoing progress on project development via videos and vlogs
  • Intended to be transparent by showing a tutorial right on the platform
  • Facilitates Flash Mob development sessions
    • Shows a map + list of participants
    • Shows announcements of the next Flash Mob Session
    • Contains Flash Mob Recruiting Survey
  • Allows anyone in the world with an internet connection to view the work product of all OSE Projects worldwide
  • Provides a board for listing tasks and their state of completion
  • Open to participation on task logging and task assignment; one joins a team by fulfilling a task on the Task Board
  • Interface may be redesigned by non-computer programmers
    • Basic instructionals on wiki + Google Docs + embedding content
  • Shows Status Brief for each project, and shows status of 100+ development steps of open source product development for each project
  • Shows a Systems Diagram for entire project
  • Shows interface between systems
  • Shows burndown graph of development
  • Shows development team
  • Facilitates external review
  • Connects to file repository and versioning system
  • Facilitates development sprints
  • Platform may be applied to any part of development, from technology to infrastructure to organization etc.
  • Includes zero-attention span eye candy elements

Core Development Elements

The interface should focus on and facilitate:

  • Modular design
    • Contract-first design and manufacturing - Systems Engineering Breakdown Diagram and Interface Design
  • Design for manufacturing and re-manufacturing according to OSE Specifications of simplicity, stock part use, minimum machining + fabrication, low part count, low unique part count
  • Lifetime design
    • Design for disassembly
    • design for re-manufacturing
    • Stock replacement parts
  • Test-driven design
    • A test or model or simulation is created to determine functionality
    • Assessment of functionality should be easy
  • Flash Mob development facilitation
  • Flash Fab development facilitation
    • Contract-first design distributed to a number of fabricators

Zero Click Level Access

  • To facilitate 0 click level access to graphics product such as CAD files - previews must be generated automatically
    • Media Wiki extensions for jpg, Sketchup, Solidworks, AutoCAD, FreeCAD, QCad, etc.

Scalability and Replicability

  • Interface should be scalable to GVCS-scale projects (50 machines with ~100 tasks each) for about 5-10,000 entries at zero click level
  • Platform is scalable extensively and intensively to any number of development projects
  • Goal is to facilitate replication of GVCS-type enterprises to ~5000 local areas as a means to creating autonomous economic regions that engage in global trade for non-essential goods - according to Strategic Plan
  • As in Specification above - interface may be redesigned by non-computer programmers to allow adaptation
    • Modifications can be made non-programmers
    • Instructionals are provided about the interface

Distillation Basic Operational Points

The Flashy XM is in development. As we shake it down, we arrive at common practice shared by the group. The following is a list of that practice.

  1. Any task completed from Scrumy Task Board should be Work Logged.
  2. Logging a task done in the Work Log is intended in part for review. Without posting a link to a completed task, review is not possible, and a log entry as such has limited value. Please post links to all Work Log items.
  3. For Project Management, the Flashy XM Administrator feeds links into the Flashy XM Platform as steps are completed, pulling those links from Work Log
  4. Experienced: In Control Panel, link to a wiki page with embedded Google Doc and link to its edit. This allows Docs to show up automatically in wiki pages, visible to the whole world - to address the public invisibility of Google docs.
Personal tools
Namespaces

Variants
Actions
Navigation
Open Source Ecology
Toolbox
Topics