Corrupt SharePoint Database Recovery Software is the “need of the hour” as SharePoint Recovery is required by many organizations.Therefore SharePoint Disaster Recovery is required by many clients as corruption is inevitable and users can only protec (more)
Corrupt SharePoint Database Recovery Software is the “need of the hour” as SharePoint Recovery is required by many organizations.Therefore SharePoint Disaster Recovery is required by many clients as corruption is inevitable and users can only protected it through SharePoint recovery tool:http://www.sharepointrecoverytool.com/ (less)
Corrupt SharePoint Database Recovery Software is the “need of the hour” as SharePoint Recovery is required by many organizations.Therefore SharePoint Disaster Recovery is required by many clients as corruption is inevitable and users can only protec (more)
Corrupt SharePoint Database Recovery Software is the “need of the hour” as SharePoint Recovery is required by many organizations.Therefore SharePoint Disaster Recovery is required by many clients as corruption is inevitable and users can only protected it through SharePoint recovery tool:http://www.sharepointrecoverytool.com/ (less)
From:
easter11jonas
Views: 68
Comments: 0
Take a look on the Slide Show file to see How to Recover Corrupt SharePoint Database by using SysTools SharePoint Recovery Tool. Follow the link: http://www.nsftopst.com/sharepoint-document-recovery.html
Slide 1: Speaker : Kalpesh Parmar (Vic) Technical Evangelist Infragistics
Slide 2: he te r? at Ar Fo Wh re He We
ck He
UX = UI ??? Just another buzzword...
Why should I care? What can it do for me?
What is It?
UX?
How do I make software for people?
Q uo Vadis ?
Slide 3: What We’ll Cover
What is User Experience?
It’s Everywhere You Want to Be What Makes Good UX? Competencies
Why User Experience? Incorporating UX into Development Some UX Pointers for .NET
Slide 4: User Experience is Everything
That’s Preposterous! What about
Database? OOD? The –ilities? Security/Privacy? Batch Processes? ??
UX is the Overall Experience
Slide 5: Reliabilit
y
ty bili ala
Ma in
Secu rity
tai na
bil ity
ity abil t dap A
Sc
Performa nce
Extensibi
lity
g na Ma
il ab e
ity
Respo nsiven
ess
User Experience is Everything
Eff
St y ilit ab
Priva c
y
Brandin g
nc icie y
ility eusab R
ilit vailab A y
en Resili
ce
Robustness
Agility
Slide 6: What Makes Good UX?
User Experience Honeycomb
Courtesy of Peter Morville
Slide 7: Guiding Principles
Design from the Outside In
Don’t Think About What You/the App Need; Think About What
the User Knows and What the User Needs Don’t Assume: Preempt Questions/Avoid Confusion by Guiding Users Make Software Smarter, More Context Aware Consistency. Consistency. Consistency.
Slide 8: UX Competencies
Information Architect (findable, usable)
Chiefly concerned with organization of information, focusing on
navigation, search, page layout, & app structure.
Interaction Designer (usable, desirable)
Focuses on granular interactions, usually at the view level but
also higher level such as how navigation works and transitions between focus/tasks.
Usability Engineer/Tester (usable, accessible)
Focuses on ensuring (testing) ease of use and user performance—
users can achieve what they need with minimal effort and maximum efficiency.
Slide 9: UX Competencies-cont
HCI, CHI (usable, accessible)
Human-computer or computer-human interaction specialists are typically more research-oriented and experimental than usability engineers but share similar goals of making computers more usable and intuitive to users. Focuses on look and feel to establish good will and perception, enhances positive associations between app and user, helps communicate information effectively, creates consistent and distinguishing visual design, and establishes credibility by providing a finished, polished look. Chief Experience Officer on projects. Must ensure solutions provide the desired business value, which means overall UX.
Visual Designer (desirable, credible)
Software Architect (useful, valuable, *)
Slide 11: Valuable Experience Diagram
Slide 12: Why Should I Care?
“I only build internal
apps. Users don’t have to like them.” “I’m too busy; it’s hard enough just getting the functional requirements done.” “I have to learn LINQ, SharePoint, Silverlight, Entity Framework, etc. I already have enough to know.”
Slide 13: Find What You Want Know Where You Are
Slide 14: Communicating Visually
Slide 15: Establishing Trust
Slide 16: The Reality
Humans Can Separate Feelings from Thinking And Act Only on Thinking Humans are Thinky-Feely Creatures – Our Thoughts and Feelings Influence Each Other and Our Actions (Productivity)
Slide 17: How Much Should I Invest in UX?
company portal users opt-in online tools (google, yahoo) ecommerce software (amazon, expedia) shrink-wrap consumer software (quicken, ms money) enterprise class accounting (sap, oracle) Internal use reduce costs crm applications commercial sale generates revenue (salesforce.com, siebel)
user adoption
compelled use call center software company time tracking
purpose
Slide 18: Doing UX
User-Centered Design (UCD) UX-Friendly Methodology Personas Usability Testing Patterns Refactoring
Slide 19: Choosing a UX-Friendly Process
Agile
(Domain-Driven Design Object Thinking Test-Driven Development Behavior Driven Development )
Slide 20: UX Design Process
Slide 21: Personas
Meet Bob, Ivan, and Alice
“Hi Bob, Ivan, and Alice!”
Slide 22: Usability Testing
Imagination only goes so far… Tunnel Vision/Thinking Lightweight – “How to Test with Folks You Have Lying
Around”
Usability by Inspection
Heavyweight – Full Usability Testing
Usability Professional Usability Testing Labs (One-Way Mirrors) Field Research – Observing Users Eye Tracking, and More
Slide 23: UX Patterns
Building on Patterns Idea of
Alexander et al Building Things That Live or are Livable Not Algorithms; Not Code; Not Components Discovered—NOT Invented Describe (Good) Open-ended Solutions to Problems Encountered in Specific Contexts Seed the Language UX Pattern Catalogues: infragistics.com/ux
Slide 24: Parts of a Pattern
Slide 25: Refactoring
Continuous Improvement Continuous Feedback Baby Steps
Slide 26: Keep the Focus on User’s Experience
Slide 27: Building Great UX with .NET
What does .NET give you?
A Great Development Platform and Runtime(s) Visual Studio ASP.NET AJAX WPF Expression Suite Silverlight
What does .NET NOT give you?
UX-Friendly Methodology UX Expertise Human-Centered Thinking
Slide 28: Visual Studio
Rapid Dev Tooling Integrated Unit Testing Class DSL Integrated Guidance Integration with Expression Future DSLs (DSL Tools)? “D” Language
Slide 29: ASP.NET AJAX
Minimize/Eliminate Context
Switching
Death to full page refreshes!
Enhance Perceived Performance
Modularize page and reduce server load. Reduce rendering time by only updating relevant areas.
UX Enhancements
Animations Autocomplete / Suggestions Modal Popups / Dialogs Drag-n-Drop Areas More…
http://www.openlaszlo.org
Slide 30: Expression Blend & WPF
Designer-Developer Workflow
Better Separation of UI and Code Share Same Project Files
Simple, Designable Animations Declarative Bindings & Triggers Embedded 3D, Video, Audio, &
Other UI Goodies “Lookless” Controls
Slide 31: Silverlight
Cross-Platform WPF –
Bring Goodness of WPF to Web Enable Richer UI Paradigms for Web Applications AJAX on (cheap) Steroids
“Cheap” means lower TCO More Reliable Framework & Behavior Built-in Multimedia Support Multiple Language Support Dynamic Language Support
Slide 32: What .NET Does NOT Provide
UX-Friendly Methodology UX Expertise & Design Human-Centered Thinking
Slide 33: Great tools help, but ultimately, you have to learn how to use them to build great experiences.
Slide 34: at Wh
he t we
ck he ov c r? e
UX = UI Just another buzzword...
Why should I care? What can it do for me?
id d
What is It?
UX?
How do I make software for people?
Quo Vadis ?
Slide 35: Resources
http://www.designinginterfaces.com http://www.welie.com http://developer.yahoo.com/ypatterns http://ui-patterns.com http://www.lukew.com/ff http://www.boxesandarrows.com http://www.uxmatters.com http://www.uxmag.com
Slide 36: Don’t Forget!
All the tooling in the world will only go so far. You need to change your approach to
developing software:
“Design from the outside in!”
Contact Details Kalpesh Parmar (Vic) Vic@Infragistics.com