Your SlideShare is downloading. ×
Software Visualization - Lessons from the Motion Picture Industry.
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Software Visualization - Lessons from the Motion Picture Industry.

2,502
views

Published on

The practice of storyboarding was developed out of the need to provide more information to the film’s director, cast and crew to better understand the narrative and how to better communicate the …

The practice of storyboarding was developed out of the need to provide more information to the film’s director, cast and crew to better understand the narrative and how to better communicate the message and details for creation of the movie.


As storyboards supplemented the information in a movie script, other visual artifacts such as Universal Modeling Language (UML) diagrams, Swimlane diagrams and more were implemented in the software definition process.
Most of these, however, were targeted towards the technical audience such as the architects and developers.

Published in: Technology, Education

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,502
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
34
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Storyboarding – Then & Now
    Robert Grashuis, Chief Visualization Officer
  • 2. “68% of projects fail, run late, or are OVER budget.”- The Standish Group, 2009 Chaos Summary Report
    “70% of REWORK is attributed to correcting requirements errors.” - Meta Group
    “30% of project costs are REWORK .”- Forrester Research
  • 3.
  • 4. Storyboarding
    Storyboarding is an integral part of the software definition process today.
    The value storyboarding provides is to supplement the requirements with additional information for a better understanding of the requirements and their context within the system as a whole.
    The origins of storyboarding is rooted in the motion picture industry.
  • 5. Storyboarding
    The traditional process of storyboarding was developed at the Walt Disney studios in the 1930’s. Storyboards were used for animated cartoon movies, such as “The Three Little Pigs”.
    Throughout the 1930‘s the usage of storyboards grew dramatically. By 1940 storyboards were ubiquitous in all movie studios and thus became an integral part of the process of making movies.
  • 6. Storyboarding
    The practice of storyboarding was developed out of the need to provide more information to the film’s director, cast and crew to better understand the narrative and how to better communicate the message and details for creation of the movie.
  • 7. Storyboarding
    In the traditional Software Development Life Cycle (SDLC), the equivalent to the movie script is the Vision document.
    While the Vision document contains the project purpose and its goals, it is still a text-only description that can be ambiguous and subject to misinterpretation by the stakeholders.
  • 8. Storyboarding
    For the the movie production process, storyboards filled informational gaps in the script by introducing details about the camera position, lighting, scenery/set environments and also action or movement on screen.
  • 9. Storyboarding
    As storyboards supplemented the information in a movie script, other visual artifacts such as Universal Modeling Language (UML) diagrams, Swimlane diagrams and more were implemented in the software definition process.
    Most of these, however, were targeted towards the technical audience such as the architects and developers.
  • 10. Storyboarding
    While UML diagrams and other visual representations were helping the technical audience in software definition, there was still a need to more effectively communicate with business stakeholders.
    The advent of the Use Case was and still is a very popular means of conveying how the user and system interacts with each other through primary and alternate flows.
  • 11. Storyboarding
    In addition, some software development teams recognized the need for a detailed rendering of the user interface elements.
    For this, the screen wireframe and design composition were introduced.
    The wireframe articulated the hierarchy of information on a screen and highlighted the navigation and other features.
    This was a significant step forward for software definition.
  • 12. Storyboarding
    As the process of movie making matured, the techniques and technologies to support the process improved as well.
    Storyboards made the transition from static renderings to simple animations. Typically, photographs, sketches and even clay models were animated.
    These motion-based storyboards were called Storyboard Animatics.
  • 13. Storyboarding
    Storyboard Animatics offered an even richer level of detail that included timing, direction of motion and other kinematic behaviors.
  • 14. Storyboarding
    In contrast, the software definition process utilized code-based prototyping to validate a software feature or functionality.
    The draw-back to prototypes was that they were costly to produce and often only represented a small fragment of the system.
    In the end, most prototypes were throw-away and did little to help articulate the “big picture” for stakeholders.
  • 15. The Paradox
    While the software definition process and its artifacts multiplied over the years with different methods such as Waterfall, Rational Unified Process, Agile and more – the surprising fact was that projects were failing at a higher rate than ever before.
  • 16. Increased Complexity and Costs
    The reason for this was that software applications were also increasing in both size and complexity.
    While “traditional” processes and artifacts were helping, there still was a significant need to communicate more effectively and efficiently than ever before to ensure project success.
  • 17. Consumer Demand
    The motion picture industry was experiencing the same dilemma.
    Audiences were more savvy and demanding more from entertainment. With the bar raised, filmmakers also needed to improve their process and tools to more effectively create their art.
  • 18. Storyboarding to Previsualization
    With the advent of increased computing power at lower costs, the process of storyboarding made another leap forward.
    Storyboard animatics made the transition from simple animated photos to computer generated imagery.
    This next advance was labeled Previsualization.
  • 19. Previsualization
    For the first time, Previsualization allowed the Director, cast and crew to envision every shot, sequence and f/x in their movie prior to engaging in actual production.
    This allowed the filmmaker the ultimate in planning and analysis to ensure that every aspect of the movie was correct before engaging in costly production.
  • 20. Previsualization – The Movie
  • 21. Visualization for Software Definition
    Today, the ability to previs a software application has become a reality as well.
    Using scenarios as the initial “sketches” of a storyboard, visualization tools allow software definition teams to model entire applications before writing a single line of code.
  • 22. Visualization for Software Definition
    Similar to the AutoCAD/CAM technologies that revolutionized the automotive, aeronautical and construction industries, software visualization tools allow the creation of a simulated application to help stakeholders better understand the look & feel, behaviors and all other aspects of the application before it is built.
  • 23. Visualization – People & Process
    As visualization has “closed the communications gap” for filmmakers, it is providing the same benefits to software application development.
    With these new capabilities, both the people and process involved in application visualization are evolving as well.
    As the first requirements agency, OneSpring is a pioneer in visualization for software definition.
  • 24. The Traditional Approach
    Most methods for software definition provide the critical details needed to truly understand the application too late in the lifecycle.
  • 25. The Traditional Approach
    Requirements 101
    The old way:
  • 26. The Traditional Approach
    Requirements 101
    The old way:
  • 27. The Traditional Approach
    Requirements 101
    The old way:
  • 28. The Traditional Approach
    Requirements 101
    The old way:
  • 29. The Traditional Approach
    Requirements 101
    The old way:
  • 30. The Stream Process™ occurs at the beginning of the lifecycle and provides stakeholders the ability to experience and validate their requirements from the start.
    OneSpring
    The New Approach
  • 31. The Modern Approach
    An improved approach:
  • 32. The Modern Approach
    An improved approach:
  • 33. The Modern Approach
    An improved approach:
  • 34. The Modern Approach
    An improved approach:
  • 35. The Modern Approach
    An improved approach:
  • 36. The Modern Approach
    An improved approach:
  • 37. The Modern Approach
    An improved approach:
  • 38. The Modern Approach
    An improved approach:
  • 39. The Modern Approach
    An improved approach:
  • 40. The Stream Process™ is a framework for how to better innovate and collaborate using visualization.
    The New Approach
  • 41. Accelerating the time to understanding provides a far greater return on investment
    OneSpring
    100%
    50%
    Traditional
    0%
    The Benefit
  • 42. Thank you!
    For more information on how previsualization can help you make the most of your software projects, visit www.onespring.net, email clarity@onespring.net or call us toll-free, 1-888-472-1840.