Conversations with Architects about Drupal Research, Documentation, - - PowerPoint PPT Presentation

▶
conversations with architects about drupal
SMART_READER_LITE
LIVE PREVIEW

Conversations with Architects about Drupal Research, Documentation, - - PowerPoint PPT Presentation

Sep 10, 2022 568 likes •1.13k views

Conversations with Architects about Drupal Research, Documentation, and Process Je ff Traynor, Solutions Architect Friday, January 31, 14 Friday, January 31, 14 Good Architecture Conversations with Architects about Drupal Friday, January 31,

slide-1
SLIDE 1

Conversations with Architects about Drupal

Research, Documentation, and Process Jeff Traynor, Solutions Architect

Friday, January 31, 14

slide-2
SLIDE 2

Friday, January 31, 14

slide-3
SLIDE 3

Good Architecture

Conversations with Architects about Drupal

Friday, January 31, 14

slide-4
SLIDE 4

Good Architecture

Conversations with Architects about Drupal

In his book De Architectura, Marcus Vitruvius Pollio describes three fundamental principles of what great architecture should accomplish:

Friday, January 31, 14

slide-5
SLIDE 5

Good Architecture

Conversations with Architects about Drupal

In his book De Architectura, Marcus Vitruvius Pollio describes three fundamental principles of what great architecture should accomplish:

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

— it should be durable.

Friday, January 31, 14

slide-6
SLIDE 6

Good Architecture

Conversations with Architects about Drupal

In his book De Architectura, Marcus Vitruvius Pollio describes three fundamental principles of what 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.

Friday, January 31, 14

slide-7
SLIDE 7

Good Architecture

Conversations with Architects about Drupal

In his book De Architectura, Marcus Vitruvius Pollio describes three fundamental principles of what 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.

Friday, January 31, 14

slide-8
SLIDE 8

History

Conversations with Architects about Drupal

Architecture Web Development

Friday, January 31, 14

slide-9
SLIDE 9

History

Conversations with Architects about Drupal

  • The Craftsman

Architecture Web Development

Friday, January 31, 14

slide-10
SLIDE 10

History

Conversations with Architects about Drupal

  • The Craftsman
  • The Master Builder

Architecture Web Development

Friday, January 31, 14

slide-11
SLIDE 11

History

Conversations with Architects about Drupal

  • The Craftsman
  • The Master Builder
  • The Architect

Architecture Web Development

Friday, January 31, 14

slide-12
SLIDE 12

History

Conversations with Architects about Drupal

  • The Craftsman
  • The Master Builder
  • The Architect

Why? Architecture Web Development

Friday, January 31, 14

slide-13
SLIDE 13

History

Conversations with Architects about Drupal

  • The Craftsman
  • The Master Builder
  • The Architect

Why?

  • Technology

Architecture Web Development

Friday, January 31, 14

slide-14
SLIDE 14

History

Conversations with Architects about Drupal

  • The Craftsman
  • The Master Builder
  • The Architect

Why?

  • Technology
  • Standardization

Architecture Web Development

Friday, January 31, 14

slide-15
SLIDE 15

History

Conversations with Architects about Drupal

  • The Craftsman
  • The Master Builder
  • The Architect

Why?

  • Technology
  • Standardization
  • Specialization

Architecture Web Development

Friday, January 31, 14

slide-16
SLIDE 16

History

Conversations with Architects about Drupal

  • The Craftsman
  • The Master Builder
  • The Architect

Why?

  • Technology
  • Standardization
  • Specialization

Architecture Web Development

Friday, January 31, 14

slide-17
SLIDE 17

History

Conversations with Architects about Drupal

  • The Craftsman
  • The Master Builder
  • The Architect

Why?

  • Technology
  • Standardization
  • Specialization
  • The Developer

Architecture Web Development

Friday, January 31, 14

slide-18
SLIDE 18

History

Conversations with Architects about Drupal

  • The Craftsman
  • The Master Builder
  • The Architect

Why?

  • Technology
  • Standardization
  • Specialization
  • The Developer
  • The Webmaster

Architecture Web Development

Friday, January 31, 14

slide-19
SLIDE 19

History

Conversations with Architects about Drupal

  • The Craftsman
  • The Master Builder
  • The Architect

Why?

  • Technology
  • Standardization
  • Specialization
  • The Developer
  • The Webmaster
  • The Site Builder

Architecture Web Development

Friday, January 31, 14

slide-20
SLIDE 20

History

Conversations with Architects about Drupal

  • The Craftsman
  • The Master Builder
  • The Architect

Why?

  • Technology
  • Standardization
  • Specialization
  • The Developer
  • The Webmaster
  • The Site Builder

Why? Architecture Web Development

Friday, January 31, 14

slide-21
SLIDE 21

History

Conversations with Architects about Drupal

  • The Craftsman
  • The Master Builder
  • The Architect

Why?

  • Technology
  • Standardization
  • Specialization
  • The Developer
  • The Webmaster
  • The Site Builder

Why?

  • Technology

Architecture Web Development

Friday, January 31, 14

slide-22
SLIDE 22

History

Conversations with Architects about Drupal

  • The Craftsman
  • The Master Builder
  • The Architect

Why?

  • Technology
  • Standardization
  • Specialization
  • The Developer
  • The Webmaster
  • The Site Builder

Why?

  • Technology
  • Standardization

Architecture Web Development

Friday, January 31, 14

slide-23
SLIDE 23

History

Conversations with Architects about Drupal

  • The Craftsman
  • The Master Builder
  • The Architect

Why?

  • Technology
  • Standardization
  • Specialization
  • The Developer
  • The Webmaster
  • The Site Builder

Why?

  • Technology
  • Standardization
  • Specialization

Architecture Web Development

Friday, January 31, 14

slide-24
SLIDE 24

The (Obvious) Differences

Conversations with Architects about Drupal

Friday, January 31, 14

slide-25
SLIDE 25

Friday, January 31, 14

slide-26
SLIDE 26

Friday, January 31, 14

slide-27
SLIDE 27

Friday, January 31, 14

slide-28
SLIDE 28

Friday, January 31, 14

slide-29
SLIDE 29

Friday, January 31, 14

slide-30
SLIDE 30

The Role of Documentation

Conversations with Architects about Drupal

Friday, January 31, 14

slide-31
SLIDE 31

The Role of Documentation

Conversations with Architects about Drupal

Clarity

  • “If you can’t explain it to a six year old, you don’t understand it

yourself” – Albert Einstein

Friday, January 31, 14

slide-32
SLIDE 32

The Role of Documentation

Conversations with Architects about Drupal

Clarity

  • “If you can’t explain it to a six year old, you don’t understand it

yourself” – Albert Einstein Accountability

  • Budgets & Scope creep
  • “Being an Advocate for the Owner”

Friday, January 31, 14

slide-33
SLIDE 33

The Role of Documentation

Conversations with Architects about Drupal

Clarity

  • “If you can’t explain it to a six year old, you don’t understand it

yourself” – Albert Einstein Accountability

  • Budgets & Scope creep
  • “Being an Advocate for the Owner”

Collaboration

  • A shared understanding
  • A tool creative process

Friday, January 31, 14

slide-34
SLIDE 34

Feasibility Study

Conversations with Architects about Drupal

Friday, January 31, 14

slide-35
SLIDE 35

User Personas

Conversations with Architects about Drupal

Friday, January 31, 14

slide-36
SLIDE 36

Schematic Design

Conversations with Architects about Drupal

Friday, January 31, 14

slide-37
SLIDE 37

Information Architecture

Conversations with Architects about Drupal

Friday, January 31, 14

slide-38
SLIDE 38

Design Development

Conversations with Architects about Drupal

Friday, January 31, 14

slide-39
SLIDE 39

Wireframes

Conversations with Architects about Drupal

Friday, January 31, 14

slide-40
SLIDE 40

Construction Documents

Conversations with Architects about Drupal

Friday, January 31, 14

slide-41
SLIDE 41

Design Mockups

Conversations with Architects about Drupal

Friday, January 31, 14

slide-42
SLIDE 42

Contract Administration

Conversations with Architects about Drupal

  • Proprietary Specifications
  • Performance Specifications

Friday, January 31, 14

slide-43
SLIDE 43

Technical Design Document

Conversations with Architects about Drupal

Friday, January 31, 14

slide-44
SLIDE 44

A Process Oriented Approach

Conversations with Architects about Drupal

“Seek to understand a design problem before chasing after

  • ther solutions.”

Friday, January 31, 14

slide-45
SLIDE 45

A Process Oriented Approach

Conversations with Architects about Drupal

“Don’t force-fit solutions to old problems onto new problems.”

Friday, January 31, 14

slide-46
SLIDE 46

A Process Oriented Approach

Conversations with Architects about Drupal

“Remove yourself from prideful investment in your project.”

Friday, January 31, 14

slide-47
SLIDE 47

A Process Oriented Approach

Conversations with Architects about Drupal

“Be slow to fall in love with your ideas.”

Friday, January 31, 14

slide-48
SLIDE 48

A Process Oriented Approach

Conversations with Architects about Drupal

“Make design decisions conditionally, with the understanding that they might not work as you continue towards a solution.”

Friday, January 31, 14

slide-49
SLIDE 49

A Process Oriented Approach

Conversations with Architects about Drupal

“Know when to change and when to stick to previous decisions.”

Friday, January 31, 14

slide-50
SLIDE 50

A Process Oriented Approach

Conversations with Architects about Drupal

“Accept as normal the anxiety that comes from not knowing what to do.”

Friday, January 31, 14

slide-51
SLIDE 51

A Process Oriented Approach

Conversations with Architects about Drupal

“Always ask ‘What if...?’ regardless

  • f how satisfied you are with

your solution”

Friday, January 31, 14

slide-52
SLIDE 52

A Process Oriented Approach

Conversations with Architects about Drupal

“Properly gaining control of the design process feels like losing control of the design process.”

Friday, January 31, 14

slide-53
SLIDE 53

A Process Oriented Approach

Conversations with Architects about Drupal

“An improved design process is the most important thing you’ll take with you to your next project.”

Friday, January 31, 14

slide-54
SLIDE 54

Thank You

Please ¡get ¡in ¡touch ¡at: ¡

www.imagexmedia.com

Friday, January 31, 14