US1YFARE
Veteran
- Mar 31, 2004
- 3,932
- 54
Oh lordy I just can't go on.
Oh yes you can, and please do...I'm getting tired of whining and still haven't gotten any cheese....
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Oh lordy I just can't go on.
I wouldn't take his not responding in a negative way tadjr. My suspicion is yours is but one of many. He's probably so sick of hearing about the website. He knows it's not going well and somewhere along lifes way those e-mails are getting forwarded to the IT folks to address on a case by case basis.
You hit the nail on the head....I also work in IT and do major system implementations. There is no way they could have tested this at all. It's not like the big things worked but little 'bugs' here and there occurred. There are/were big things that just plain bombed. Whomever was managing this project is responsible for what went into production (I would have lost my job if I had done this), but I do have to wonder what their marching orders were, such as get it out there no matter what the condition....who knows. But, this far into production, you would think that all development resources would have been deployed to ensure it was perfect long before now.This is ludicrous. I've been in the IT field for 15 years. I've done installations, upgrades, migrations to new platforms of all sorts of Database types, Operating Systems, application suites. Many of these involved moving legacy code or simply interfacing it to new technologies. I suspect at USAirways the latter is occuring - interfacing the CRS with a web front end. I know that's over simplifying it, but in a nutshell that's what it is.
In a typical Promote to Production(P2P) system environemnt, you have a development system that has some mock data and a lot of code changes going on. This is where the interfaces between the web engine and the CRS are built and beat to he11. Some of that code will make it to production, some won't. But before any of it goes to productive operation, it goes to a clean Q/A environemnt that is an exact replica of the live, productive environment, but without all the data (flights, customers, etc.). So, the replication is really the core code that makes it all work. Data is data, so that's not important in a QA enviornment as long as it's useful and representative of what real data would be.
The QA would have a lot of mock data that could be used to run many, many, many simulations and test scenarios. Finally when the Q/A testing is done, the final code changes are approved and sent to production. But if they fail in QA, they get checked and fixed in the development environment and tested again in QA. That circle continus until it's right.
To me, it sounds like they developed in one system and sent it straight to the productive environment. Or, worse yet, they built the productive environment, gave it a cursory test, and then put it out there. But then what to they use to make fixes and test them now???
Many of you here are IT savvy and probably understand this stuff, so if I offended anyone's intelligence forgive me. I'm just scratching my head (as are many of you) that this kind of stuff is going on after 1+ months since "go-live".
I wouldn't take his not responding in a negative way tadjr.
HAPPY BOOKINGS. B)
Unless MCO is down to 3 non-stops from PHL in November, which are sold out, the website is still screwed up.
Don't forget we are an LCC now...Low Class Carrier. The website to me just looks like the old AWA website. Remember what an international powerhouse they were.Oh yes you can, and please do...I'm getting tired of whining and still haven't gotten any cheese....