1 / 22

Information Architecture in the real world

Information Architecture in the real world. Paul Arellanes parellan@us.ibm.com ptaarellanes@yahoo.com. What you have covered so far…. Rich internet applications Database driven websites Content management systems XML and semantic web IA considerations for videos

nerice
Download Presentation

Information Architecture in the real world

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Information Architecture in the real world Paul Arellanes parellan@us.ibm.com ptaarellanes@yahoo.com

  2. What you have covered so far… • Rich internet applications • Database driven websites • Content management systems • XML and semantic web • IA considerations for videos • Information visualization • Architecture and designing for accessibility • Social bookmarking • API (and IA) • Mashup

  3. Paul Arellanes (parellan@us.ibm.com)IBM Power Systems Hardware and SoftwareInformation Architect and Strategist 1999 - 2006 2004 - 2006 2004 - 2010 2006 - 2010 1999 1999 - 2002 2002 - 2004 Lead Writer – AIX Installation information AIX Security information Developer in AIX Installation team Information Architect IBM Power Systems hardware and software products BS Computer Science & BS Math New Mexico State University, Las Cruces, NM • Technical Mentor • IBM Technical Customer Advocate • IBM Patent review board joined Information Development team to create the Task Analysis methodology Joined IBM Taught classes to IBM Service and Support personnel; IBM Business Partners

  4. Role of the IA • During Fall Plan, review Line Items and ensure ID estimates are valid. If no ID estimates are identified, then work with Line Item owner to ensure whether ID work is needed. • Review additional Line Items that come in after Fall Plan and ensure ID estimates are valid. If no ID estimates are identified, then work with Line Item owner to ensure whether ID work is needed. • Review PCRs, RFS's, PMRs, critsit/high-severity defects that cause a change in plan to the information strategy for a project. • Determine the information strategy for a project's product documentation needs (i.e. infocenter content, Helps, hardcopy, eLearning, release notes, distributed media content, ESP content, OEM content, embedded content, support center content, etc) • Provide input and status to ID project manager on overall schedule, risks, and dependencies. • Work with Lead Writer (or writers) to understand what the information design is for a given project. • Provide input to ID Translation Planner on translation schedule, risks, and dependencies. • Work with UCD/UX focal points assigned to project. Update the project information design based on UCD/UX activities. • Read initial development design docs. Create initial skeleton IA information design. Post to Wiki. • Review initial skeleton IA information design with development architects, development leads, etc. Work through questions and comments on the development design docs and the initial ID design. • Review updated IA information design with development architects, development leads, etc. Work through questions and comments on the development design docs and the initial ID design. • Work with Lead Writer to determine how to efficiently work on the IA information design. • Update IA information design with comments / questions from developers, service, RAS, test, ESP, UCD/UX, and other project stakeholders. • Work with writer(s) assigned to project. Update initial design with comments / questions from writers. • Work with writers on content navigation, content organization, task-based writing, titles, preparing content for content builds. • Attend regular development status meetings (usually weekly). Update information design as appropriate per development plan changes. • Work with Build and Tools Architect (BTA) to determine how new projects are set up for source control, content builds, content delivery, content publishing, and content updates. Work with BTA to determine if currently existing projects are impacted by changes based on new projects. • Help identify gaps/deficiencies in writing process. Help identify gaps/deficiencies in content building, delivery, publishing processes. Provide input as requirements to build and tools team.

  5. What else do I do? • User interface design • Graphic design • Software development • Usability engineering • Content management • Knowledge management • Translation planning • Accessibility planning

  6. My toolbox • DITA-XML • XHTML, PDF, TROFF, XML, RDF • CSS • Flash, • Visio, OmniGraffle, Wiki, PowerPoint • javascript, Perl, PHP, MySQL, shell script • Grep, awk, sed, regular expressions • Eclipse Help System • Drupal, iPhone, iPad • …

  7. Additional skills • Linking strategy • File naming conventions • Titles / short descriptions • Structuring, organizing, and labeling, managing, finding

  8. Developing a Task Flow • Define users • Define competition • Define Usability Focus Areas • Define Customer Task Focus Area – in / out scope • Create Task Flow Diagram • Create General Scenarios • Create Specific Scenarios from General Scenarios • Conduct / create content inventory • Store project designs

  9. 1.Define users • User group 1 – Real Customers • Global - all markets • Current and prospective customers • Medium and large customers – MLx • Small Medium Business (SMB) – later in year • User group 2 – User roles • HW and SW installers (IBM and Customers) • System administrators, network administrators • IT planners and IT management • Service and support staff • Users change as the end to end task flow proceeds

  10. 2.Define Competition • Outside competition • Based on the Marketing Plan • Refer to marketing section in business plan • Inside competition • Prior deliverables: (ie. Previous IBM server product targeting the same market) • Collect comparison data against previous IBM server product

  11. 3.Define Usability Focus Areas • Gather Requirements • Evaluate competition • Not part of plan scope, except as noted on previous chart • Evaluate design (iterative) • Test implementation for usability • Conduct Survey (post GA) • Marketing does this – Customer Sat for usability • 90 day call back input • Service and support feedback

  12. 4a.Define Customer Task Focus Areas - In scope for project • Plan for purchase • Order • Plan for arrival of order • Receive, setup • Configure, configure virtualization options • Install OS • Set up for service • Install fixes • Manage system(s)

  13. 4b.Define Customer Task Focus Areas -Out of scope for this project • Managing the environment, hardware and software • VSM, IBM Systems console, … • Maintaining hardware and software over time • Upgrading

  14. 5. Create Task Flow Diagram

  15. 6. Create Scenarios Assumptions: This version assumes a System Plan to deploy

  16. 7a. IBM Server Deployment Scenario Task 2: Unpack ship group and locate setup instructions Task 4: Complete server setup Task 3: Initial server setup Task 1: Receive Shipment • Configure and attach console (HMC) • Connect cables and external I/O devices • Attach power cables and connect to power • Start the system • Locate rails / related hw, and cable management arm • Move rail install materials (including doc if printed) to install location • Determine rack install location • Install rails and cable management arm • Locate system box unpack instructions • Unpack and remove system from packaging • Transfer system to install location • Position server in rack • Locate packing list from outside of ship box • Receive shipment into inventory using MTMS (per company processes) • Coordinate ship box with related order components (if necessary) • Transfer ship box to holding area for installer • Verify number of ship boxes for order completeness • Identify ship box to be installed via MTMS • Open ship group box • Locate install documentation • Print from HW IC / DVD • View HW IC / DVD (local) • View HW IC / DVD (remote) • Locate kitting report and perform inventory Red text signifies areas where content is missing.

  17. Receiver HMC Kitting Report Printed Install doc Legal / Lic docs Printed Install doc Install roadmap Install roadmap Unpack Instructions Packing List Internet Power HW IC Installer Task 1: Receive Shipment Locate packing list, receive into inventory, coordinate with related order components and move to staging area. Task 2: Unpack ship group and locate setup instructions Verify ship group completeness and identify system to be installed by MTMS. Open ship group box, locate install doc, kitting report and perform inventory. Task 3: Initial server setup Move rails, CMA, and doc to install location and install. Return to staging area and follow unpack instructions to remove the system from packaging. Install system into rack. Task 4: Complete setup Connect and configure HMC. Attach cables and external I/O devices. Attach power cables and connect to power. Start system. 7b. IBM Server Deployment Scenario Rails CMA Rails Task 5: Partition and Operating system installation System Cables and I/O Devices Rails CMA Install Location Staging Area

  18. 8. Conduct / create content inventory

  19. 9. Store project designs in team Wiki

  20. Where is information headed? Books vs web sites vs ??? (Information Architecture for the World Wide Web, 3rd Edition)

  21. References

  22. Paul Arellanes • ptaarellanes@yahoo.com • http://www.facebook.com/arellanes • http://twitter.com/paulthomas_tx • http://www.linkedin.com/in/paularellanes

More Related