Microsoft Visio 2007 Training Session
-
Upload
orbit-one-we-create-coherence -
Category
Technology
-
view
8.059 -
download
3
description
Transcript of Microsoft Visio 2007 Training Session
www.orbitone.com
Raas van Gaverestraat 83B-9000 GENT, BELGIUM E-mail [email protected] Website www.orbitone.com
Tel. +32 9 330 15 00VAT BE 456.457.353Bank 442-7059001-50 (KBC)
Viktor Bardadym8 January, 2010
Microsoft Visio 2007 training
Why Visio? A diagram says more than 1000 words
The proof is as follows: Let ACB be a right-angled triangle with right angle CAB. On each of the sides BC, AB, and CA, squares are drawn, CBDE,
BAGF, and ACIH, in that order. From A, draw a line parallel to BD and CE. It will perpendicularly
intersect BC and DE at K and L, respectively. Join CF and AD, to form the triangles BCF and BDA. Angles CAB and BAG are both right angles; therefore C, A, and G
are collinear. Similarly for B, A, and H. Angles CBD and FBA are both right angles; therefore angle ABD equals
angle FBC, since both are the sum of a right angle and angle ABC. Since AB and BD are equal to FB and BC, respectively, triangle ABD
must be congruent to triangle FBC. Since A is collinear with K and L, rectangle BDLK must be twice in area
to triangle ABD. Since C is collinear with A and G, square BAGF must be twice in area to
triangle FBC. Therefore rectangle BDLK must have the same area as square BAGF =
AB2. Similarly, it can be shown that rectangle CKLE must have the same
area as square ACIH = AC2. Adding these two results, AB2 + AC2 = BD × BK + KL × KC Since BD = KL, BD* BK + KL × KC = BD(BK + KC) = BD × BC Therefore AB2 + AC2 = BC2, since CBDE is a square.
8 January, 2010Microsoft Visio workshop
Pythagorean Theorem
c2 = a2 + b2
Why Visio? A diagram says more than 1000 words
See!
8 January, 2010Microsoft Visio workshop
Pythagorean Theorem
c2 = a2 + b2
Attention!
Chessboard paradox
8 x 8 = 64 13 x 5 = 65
8 January, 2010Microsoft Visio workshop
8 January, 2010Microsoft Visio workshop
Before you open Visio
Define who is the target audience for your diagram. developers, project manager, the customer, outsiders, …
Always try to make diagrams that as many people as possible understand!
Start with a sketch on whiteboard (or paper)Is quick and easy, and allows you to wipe parts, change, brainstorm.
Make a picture of the whiteboard (use your mobile phone).
8 January, 2010Microsoft Visio workshop
Getting started
Demo & exercise filesC:\temp\visio\
8 January, 2010Microsoft Visio workshop
Visio glossary
Stencil
Tool selecto
r
Task pane
Shape master
ShapeConnector
Foreground page tab
Background page tab
Theme
Visio – general approach
Microsoft Visio workshop8 January, 2010
Drag & dropChoose right toolUse central places
Choose right tool
Shape handles
Toolbar
Right click on right place
8 January, 2010Microsoft Visio workshop
Choose right tool
Arrows – move objectsFine tune position:
•shift + arrows
Exercise 1Make connectors straight
Shortcut keysMultiple selection:
•shift + click•ctrl + click
Select all: •ctrl + a
8 January, 2010Microsoft Visio workshop
Use central places
Microsoft Visio workshop8 January, 2010
Document propertiesPage propertiesBackgroundsThemes
8 January, 2010Microsoft Visio workshop
Document Properties
How to open
What to enter
Where is used
Document title
Project or client
8 January, 2010Microsoft Visio workshop
Page Properties
Rename page
Where is used
Page setup
Open page setup
Use BOTH when resize or
rotate
Microsoft Visio workshop
Activity Diagramflowchart
SitemapService ArchitectureData ModelOther
(not regularly used at O1)UML diagramsGantt chartPERT networkorganisational chart (organigram),office layout,driving directions,...
Types of charts
8 January, 2010
Microsoft Visio workshop
AuthorProject Manager or developer
AudienceDevelopersTestersSometimes client/stakeholder
GoalExplain the logical flow
HowVisio template
Activity Diagram
8 January, 2010
Microsoft Visio workshop
Activity Diagram
8 January, 2010
Microsoft Visio workshop
Exercise 2: make a chart of loop
Calculate n! = 1 2 … (∙ ∙ ∙ n-1) ∙ n
8 January, 2010
Microsoft Visio workshop
Activity Diagram
For any logical sequence of some complexityShould exist BEFORE implementation starts
Keep it simpleGive brief information about what happens “connect to web service”, “write to database”, “validate user input”, …
Don’t talk about classes, method names, Nhibernate, … Be specific
No: “user gives input” > “data is saved”Yes: “user enters his personal information” > “data is saved to database”
8 January, 2010
http://en.wikipedia.org/wiki/Flowcharthttp://en.wikipedia.org/wiki/Activity_diagram
Microsoft Visio workshop8 January, 2010
Author: Project Manager
Audience: Webmasters, clients
Goal: Structure of website
How: Visio template
Sitemap
Microsoft Visio workshop
Sitemap
Representation of site structureDescribe SharePoint sites, page, navigation shortcuts
8 January, 2010
Microsoft Visio workshop8 January, 2010
Author: Project Manager or developer
Audience: System Engineer
Goal: Give an overview of the technical components of a system
How: Visio template
Service Architecture Diagram
Microsoft Visio workshop
Service Architecture Diagram
8 January, 2010
Microsoft Visio workshop
Service Architecture Diagram
Diagram with:Physical locations and servers ServicesComponentsBoundariesCommunication between the components
Where should I install what?How do the services interact?What protocols (TCP ports) are used? (firewall)
8 January, 2010
Microsoft Visio workshop
AuthorBusiness Architect or Project Manager
AudienceClient/stakeholderSometimes developer
GoalSimple representation of data and relationships
HowVisio template
Data Model
8 January, 2010
Microsoft Visio workshop
Data Model (simplified)
8 January, 2010
Microsoft Visio workshop
Data Model (class diagram)
8 January, 2010
Microsoft Visio workshop
Other - organsational chart
8 January, 2010
Microsoft Visio workshop
Watch red flagsClient’s logo
Keep background clean & safe
Stay connectedNo “orphan” connectors
StructureNo “Spaghetti chart”
Do’s and Dont’s
8 January, 2010
8 January, 2010Microsoft Visio workshop
Client’s logo
8 January, 2010Microsoft Visio workshop
Keep background pages clean & safe
Demo 3: overlapping chartsDon’t remove or change background headers
8 January, 2010Microsoft Visio workshop
Stay connected!
No “orphan connections”
Demo 4: link it!
8 January, 2010Microsoft Visio workshop
Basta, no more pasta!
Exercise 5: make the flowchart plain
Microsoft Visio workshop33
General guidelines
Include documentation in ALL time estimates/proposalsShow completed documentation to the customer!
Do not start development of any complex logic without an activity diagram
Use it as communication between all parties!Do not deploy on production servers without documentation
Test your documentation when deploying on staging!Do not “finish” a project without proper documentation
Write the docs during the work, not after!Store on SharePoint Intranet
8 January, 2010
Microsoft Visio workshop
Q & A’s
8 January, 2010