Transcript
Page 1: Communicating Drupal: Documentation and Discovery

Communicating Drupal: Documentation and Discovery

Jeff Traynor

7/15/14

Prepared For: DrupalCamp LA 2014

Solutions Architect

Page 2: Communicating Drupal: Documentation and Discovery

Achieve’s Footprint

What would you say you do here?

Page 3: Communicating Drupal: Documentation and Discovery

Architecture

In De Architectura, Marcus Vitruvius Pollio describes three

fundamental principles which great architecture should accomplish:

• Firmatis: It should stand up robustly and remain in good condition

— it should be durable.

• Utilitas: It should be useful and function well for the people using it

— it should be functional.

• Venustatis: It should delight people and raise their spirits — it should be beautiful.

Page 4: Communicating Drupal: Documentation and Discovery

Achieve at a GlanceLongevity

Page 5: Communicating Drupal: Documentation and Discovery

Scale

Page 6: Communicating Drupal: Documentation and Discovery

Physics

Page 7: Communicating Drupal: Documentation and Discovery

Environment

Page 8: Communicating Drupal: Documentation and Discovery

Cost of Construction

Page 9: Communicating Drupal: Documentation and Discovery

Documentation Matters

Documentation is a source of clarity • “If you can’t explain it to a six year old, you don’t understand it

yourself” – Albert Einstein

Documentation is a mechanism for accountability • Managing budgets, scope, an expectations• Advocating for project stakeholders

Documentation is a site of collaboration • Documenting process and collaborative creation• Recording the decision making process

!

Page 10: Communicating Drupal: Documentation and Discovery

Feasibility Study

Page 11: Communicating Drupal: Documentation and Discovery

Business Requirements

Why?

Page 12: Communicating Drupal: Documentation and Discovery

Business Requirements

Customer ProfileStrategic Initiative Problem Analysis

Goals & Objectives Target Audience

Stakeholders Project Team

Timeline & Milestones

Page 13: Communicating Drupal: Documentation and Discovery

Business Requirements

Who?

Page 14: Communicating Drupal: Documentation and Discovery

User Personas

Page 15: Communicating Drupal: Documentation and Discovery

Schematic Design

Page 16: Communicating Drupal: Documentation and Discovery

Information Architecture

Where?

Page 17: Communicating Drupal: Documentation and Discovery

Information Architecture

!Documents Produced:

• Sitemap Diagrams• User Flow Diagrams• Systems Integration Diagrams

Page 18: Communicating Drupal: Documentation and Discovery

Design Development

Page 19: Communicating Drupal: Documentation and Discovery

Prototyping

What?

Page 20: Communicating Drupal: Documentation and Discovery

Prototyping

Page 21: Communicating Drupal: Documentation and Discovery

Construction Documents

Page 22: Communicating Drupal: Documentation and Discovery

Functional Requirements

How?

Page 23: Communicating Drupal: Documentation and Discovery

Functional Requirements

Page 24: Communicating Drupal: Documentation and Discovery

Functional Requirements

Features Content Types

Taxonomies Views

Modules Workflows

Integrations

Page 25: Communicating Drupal: Documentation and Discovery

Functional Requirements

Proprietary Specifications vs

Performance Specifications

Page 26: Communicating Drupal: Documentation and Discovery

Contract Administration

Page 27: Communicating Drupal: Documentation and Discovery

Architecture & Planning

!Documents Produced:

• Epics & User Stories• DevOps Plan• Development Plan• Sprint Plan and Milestones

Page 28: Communicating Drupal: Documentation and Discovery

Thank You

it’s not magic, it’s excellence.

Jeff Traynor Solutions Architect

[email protected] @jtray


Top Related