New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Abel Avram on Feb 12, 2009
In this article, Naysawn Naderi makes a summary of About Face 3, Alan Cooper’s book, noting some key takeaway points. The User Interface plays an important role in an application, be it a desktop one, a web application or a mobile one, and the guidelines contained by the article help creating better interfaces.
Read: What Would Alan Cooper Do?
The key points contained by Naysawn’s article are:
Design for Intermediates Users – Most products are developed for either beginners or advanced users, but they should target the intermediate ones since they represent 80% of the target users.
Use Tools that Help Beginners to Become Intermediates – The interface should provide different helps for beginners than intermediates.
Less is More – Provide as little graphical controls as possible.
Design for the Probable, Provide for the Possible – Make most probably tasks to be most accessible (1 click), but also have options for possible tasks.
Eliminate Errors or Confirmation Dialogs – Avoid error and confirmation dialogs as much as possible.
Agile Development: A Manager's Roadmap for Success
18 agile and lean practices for effective software development governance
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
I agree with you that most error dialogs only make sense only to a programmer.
A good minimalist approach will be to have confirmation dialogs only for "destructive" and irreversible user actions (ie: disk formatting, overwriting existing files, etc.) In all other case, a status bar is just fine to display success or error messages without distracting the user.
Etienne.
www.symbiosoft.net
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
1 comment
Watch Thread Reply