backgroud:
1. The FBN travel agents use a legacy system written in Cobol that accesses an IMS database through 3270 screens.
2. FBN uses TransMaster to process the credit cards for flight purchases. FBN communicates with TransMaster via a secured socket across a dedicated line.
3. FBN also has a frequent flyer mileage system that tracks mileage earned and used. when customers decide to book awards travel the agent must place the customer on hold and go to a shared computer to retrieve the customers mileage account status.
non-functional requirements:
1. FBN does not wish to re-write frequent flyer mileage system at this time, but would like to have the content available to the customer using the web and the travel agent using an application.
2. FBN would like to make the user interface more appealing for their travel agents by replacing the 3270 terminal with one that can support a graphical user interface.
3. FBN currently books 20,000 airfares per day and they are expecting that to increase 10 fold within the first month of going national.
4. we are projecting to have 20 Travel Agents and 200 web users concurrently using the system initially. These numbers are expected to increase monthly over the next couple of months to reach what we feel will be our maximum of 20 Travel Agents and 600 web users.
5. need to ensure that the Travel Agents have the fastest system possible in order to meet the customer expectations, therefore we have a hard requirement that response time never exceed 5 seconds. We have assumed that most web users will still be using 28.8 modems, so response time cannot exceed 10 seconds more than 20% of the time.
functional requirements:
related information:
1. simple pricing scheme consists of one price for first class and one price for coach.
2. the flat price is per destination, but it does not matter when you purchase the ticket.
1. The FBN travel agents use a legacy system written in Cobol that accesses an IMS database through 3270 screens.
2. FBN uses TransMaster to process the credit cards for flight purchases. FBN communicates with TransMaster via a secured socket across a dedicated line.
3. FBN also has a frequent flyer mileage system that tracks mileage earned and used. when customers decide to book awards travel the agent must place the customer on hold and go to a shared computer to retrieve the customers mileage account status.
non-functional requirements:
1. FBN does not wish to re-write frequent flyer mileage system at this time, but would like to have the content available to the customer using the web and the travel agent using an application.
2. FBN would like to make the user interface more appealing for their travel agents by replacing the 3270 terminal with one that can support a graphical user interface.
3. FBN currently books 20,000 airfares per day and they are expecting that to increase 10 fold within the first month of going national.
4. we are projecting to have 20 Travel Agents and 200 web users concurrently using the system initially. These numbers are expected to increase monthly over the next couple of months to reach what we feel will be our maximum of 20 Travel Agents and 600 web users.
5. need to ensure that the Travel Agents have the fastest system possible in order to meet the customer expectations, therefore we have a hard requirement that response time never exceed 5 seconds. We have assumed that most web users will still be using 28.8 modems, so response time cannot exceed 10 seconds more than 20% of the time.
functional requirements:
related information:
1. simple pricing scheme consists of one price for first class and one price for coach.
2. the flat price is per destination, but it does not matter when you purchase the ticket.
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
