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
