You are currently browsing the daily archive for October 31, 2006.
Most people love Apple’s products like Mac, iPod, Naro. And recently the 37 signals is so popular, too. This brings me a high interesting for the topic: Usability vs. User Experience.
My experience is when the project is just from scratch then the Usability takes first. Once stackholders see it and play it, so they add their opinion to the project. After that we move to User Experience.
But when I look at Apple’s iPod successful story, I find they design the everything from hardware that has the circle button, screen and storage HD to software that has iTune, protected copy right, download payment.
I asked myself how do we know the really User Experience, then base on that to design our Usability? I thought we have to learn, absort and consume the idea from media, social trend and your special talent.
User experience From Wikipedia
Usability From Wikipedia
Usability vs. User Experience
Usability 101: Introduction to Usability
The Elements of User Experience
The user experience for Mac OS X applications
User Experience Design
37 signals: Getting Real
The most obvious and simple way to improve a Website’s performance is by scaling up hardware. But scaling the hardware does not work in all cases and is definitely not the most cost-effective approach. Other solutions can improve performance, without extra costs for the hardware. This blog is to show you how-to and what tips a developer needs to care. If you decide to try this article’s recommendations, keep in mind this article provides suggestions only. Performance tuning is as much an art as it is a science.
- Set a goal: Before you begin tuning your J2EE application’s performance, set a goal. Often this goal addresses the maximum concurrent users the application will support for a given limit on response times. But the goal can also focus on other variables—for example, the response times should not increase more than 10 percent during the peak hour of user load.
- Identify problem areas: It is important to identify the bottlenecks when you start making changes to improve performance. A little investigation into problems might reveal the specific component that causes poor performance. For example, if the CPU usage on an application server is high, you will want to focus on tuning the application server first.
- Follow a methodical and focused path: Once the goal is set, try to make changes that are expected to have the biggest impact on performance. Your time is better spent tuning a method that takes 10 seconds but gets called 100 times than tuning a method that takes one minute but gets called only once. In an ideal world, you test one change at a time before using it in a production environment. You make one change and stress-test it. If the change results in positive impact, only then will you make it permanent.
- Stress tool: Mercury Interactive’s LoadRunner, JMeter.
- Performance monitor: To monitor your CPU, RAM, Hard driver, Networking.
- Web application server tuning: Apache server , Tomcat web server or JBoss server tuning .
- Database tuning: Microsoft SQL server, Oracel server tuing.
- Application tuning: This is the most developers work on. I will explain the details later.
- Java code optimization: Java Virtual Machine Profiler Interface (JVMPI), JProbe.
- SQL query optimization: tool like SQL Profiler.
- Performance improvement on threads.
- Performance improvement on memory leak.
- Performance improvement on writing best java code.
- Performance imporvement on data tier (JDBC) connection.
- Performance improvement on application architecture.
Book: Apress-Pro Java EE 5 Performance Management and Optimization.
How to extract maximum performance from your J2EE Web applications
Improving J2EE application performance
Load and Performance Test Tools