03-18-2019, 09:08 PM
(03-18-2019, 08:57 PM)trainspotter139 Wrote:(03-18-2019, 07:10 PM)ijmorlan Wrote: Well said. Based on the sample account statement posted to an earlier posting in this thread, I am not impressed. In addition to the issues mentioned by people, it appears that many transactions (as understood by anybody using the system) are listed twice in the transaction listing.
One of the challenges that often arises in computer systems is displaying information in a meaningful way. Just because a direct dump of the database contents is not meaningful to users does not mean they are wrong. In this case the transaction listing gets a big fail from me.
And that is my (partial) professional opinion.
With more information and time, I could give a more complete opinion which would include suggested fixes and perhaps hints as to how the poor interface came about. But there is no new information other than “the transaction listing was faked” which could reverse my judgement that the interface is bad. I don’t have to know why it is that way or what challenges may exist to know it’s bad.
And by the way, the Region, and every organization of any significant size, should have its own programming staff. Not for absolutely everything, obviously, but to create small and medium scale systems that connect together everything else and cover gaps in other systems. Every organization is an IT organization now. Suggesting that they shouldn’t have programmers is like, and really almost the same thing as, suggesting that they shouldn’t have managers but instead contract out all management activity. In short, utterly insane.
the system often processes multiple actions on the card during a card tap. I personally think they should do a summary of those actions with an expander to see more details like the individual actions that occurred at that specific timestamp.
The fact that multiple entries are made in a database is irrelevant to a user. From their perspective only one thing happened, they paid to get on the bus.
The back end implementation should not drive the front end. The user needs should drive the front end experience.
Too their credit however, GRT knows about the issue, and this is at least not final: