Re: [IxDA Discuss] Shift from Legacy system to web UI interface application
Hi Trip, Thanks a lot for your inputs and I cudn't agree more on what you have mentioned. Its really important to conduct a contextual study to understand the users and their environment. Plus understand the strategy or business logic behind the change from legacy to web. With respect to this application, currently the development team has created the following. The application is a data entry form, where the first page is a table list with data rows. When users need to view/edit one or multiple rows, they can select the rows and click view/edit. This will open up the view/edit form for the first selected row and once finished the user clicks next it will got to the next page and so on. Thanks again, Rony On Sat, 1 Mar 2008 20:47:00, Trip O'Dell [EMAIL PROTECTED] wrote: Hi Rony - Hi, Can anyone guide me in understanding, what are the key factors to be considered while redesigning a legacy (green screen) application to a web UI interface application?. That's an intriguing question, but I'm not sure its the right one. What does the application currently do? What's the advantage in moving it to the web? How could the new application grow to be more valuable to the customer than the old (as opposed to just a replacement for existing technology). If the customer has held on to the system this long, they're either really cheap, or the existing system is a critical part of their business. This means the existing users can already tell you their main likes and dislikes about the system. If you start with the existing users, what they like and dislike about existing workflows specifically and their job more generally you'll have a pretty good idea of where to start with porting the functionality over to the new system. As for the technology, I'm not sure what the requirements are, but there are a lot of emerging solutions that allow the flexibility of a desktop app with the convenience of a web App. (Check out Adobe Flex/AIR or Google Gears) You may want to consider something like this over a straight up web app (which only work when connected to the web/network). The advantage of this sort of approach is that it would allow you to adapt the application to different types of devices and form factors depending on the user task - consoles, hand held, lap top, sensor system. Also, these applications can work in a sometimes connected environment, storing data locally and then posting to the server when its available - a good solution for a warehouse or something where wireless can be problematic. Just a thought. Especialy with reagards to task flows, forms and the toggle between keyboard and mouse. Sorry if this topic as already been discussed, maybe someone can provide me the thread. Thanks a ton! Rony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=26622 Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Shift from Legacy system to web UI interface application
data entry speed is one of the prime advantages of green screen apps. web apps don't really excel at this due to their emphasis on mouse-based input. i'd focus on building in lots of key-based redundancy for common tasks such as tabbing between fields, etc. also, web forms can reduce many green screen menus, which can speed certain tasks and eliminate others. another challenge you'll have is the fact that green screen apps are 'single-tasking' - they assume control over the entire environment whereas web apps run insider a browser with limited control over state on an OS that can have multiple windows open. you'll have devise some interesting ways of keeping the user's focus on the task while still allowing them to maintain efficiency. On Thu, Feb 28, 2008 at 6:01 AM, Rony Philip [EMAIL PROTECTED] wrote: Hi, Can anyone guide me in understanding, what are the key factors to be considered while redesigning a legacy (green screen) application to a web UI interface application?. Especialy with reagards to task flows, forms and the toggle between keyboard and mouse. Sorry if this topic as already been discussed, maybe someone can provide me the thread. Thanks a ton! Rony Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help -- -- www.flyingyogi.com -- Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Shift from Legacy system to web UI interface application
Hello Rony, Legacy applications may not be the most aesthetic, but they are often quite efficient and when moving from legacy to GUI or WUI (Web user interface), keeping the efficiency can be quite a challenge. If you are looking at applications like order-entry or financial apps where people are working with forms and data all day, then you might consider minizing keyboard-mouse transitions (those are slow), examine workflow and optimal layout of required and optional fields. For the highest frequency operations, it might be useful to gather some baseline data for comparison. Youl could also use the GOMS Keystroke-level modeling to compare different designs for your Web interface. The GOMS KLM is quite powerful for doing relative comparisons and examining expert usage. I went through this in the early 1990s when legacy moved to Windows and for those will admit it, the first Windows versions of legacy app were often worse than the legacy app even if they looked more usable. Here is a note that I wrote in respone to a question like yours in the STC Usability SIG newsletter in 1998. By Chauncey Wilson, edited by Robi Gunn Reprinted from Usability Interface, Vol 4, No. 4, April 1998 http://www.stcsig.org/usability/newsletter/9804-character2gui.html Chauncey On Thu, Feb 28, 2008 at 6:01 AM, Rony Philip [EMAIL PROTECTED] wrote: Hi, Can anyone guide me in understanding, what are the key factors to be considered while redesigning a legacy (green screen) application to a web UI interface application?. Especialy with reagards to task flows, forms and the toggle between keyboard and mouse. Sorry if this topic as already been discussed, maybe someone can provide me the thread. Thanks a ton! Rony Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
