The system shall refresh the display every 60 seconds.
The application shall match the color of the schema set forth by Department of Homeland Security.
If projected the data must be readable. On a 10x10 projection screen 90% of viewers must be able to read Event / Activity data from a viewing distance of 30.
The product shall be available during normal business hours. As long as the user has access to the client PC the system will be available 99% of the time during the first six months of operation.
If projected the data must be understandable. On a 10x10 projection screen 90% of viewers must be able to determine that Events or Activities are occuring in current time from a viewing distance of 100.
The product shall ensure that it can only be accessed by authorized users. The product will be able to distinguish between authorized and unauthorized users in all access attempts.
The product shall be intuitive and self-explanatory. 90% of new users shall be able to start the display of Events or Activities within 90 minutes of using the product.
The product shall respond fast to keep up-to-date data in the display.
The look and feel of the system shall conform to the user interface standards of the smart device.
The user interface shall have standard menus buttons for navigation.
The system shall have a professional appearance.
The product shall have a consistent color scheme and fonts.
The system shall be used by realtors with no training.
The system shall be intuitive and self explanatory.
The product shall be easy for a realtor to learn.
The product shall use symbols and words that are naturally understandable by the realtor community.
The product shall produce search results in an acceptable time.
The search results shall be returned no later 30 seconds after the user has entered the search criteria.
The product shall generate a CMA report in an acceptable time.
The CMA report shall be returned no later 60 seconds after the user has entered the CMA report criteria.
The product shall synchronize contacts and appointments in an acceptable time.
The product shall synchronize with the office system every hour.
The product shall be available for use 24 hours per day 365 days per year.
Out of 1000 accesses to the system the system is available 999 times.
The product shall operate in offline mode whenever internet connection is unavailable.
The product shall allow the user to view previously downloaded search results CMA reports and appointments.
The product shall retain user preferences in the event of a failure.
100% of saved user preferences shall be restored when system comes back online.
The product shall be able to support multiple remote users.
The product shall be able support 1000 simultaneous users.
The product shall be capable of handling the existing 1000 users. This number is expected to grow 5 times within the next year.
The product shall be installed by an untrained realtor without recourse to separately-printed instructions.
90% of untrained realtors shall be able to install the product on their device without printed instructions.
The product is expected to run on Windows CE and Palm operating systems.
Only registered realtors shall be able to access the system.
Every user of the system shall be authenticated and authorized.
The product shall prevent its data from incorrect data being introduced.
The system shall be easy to use by the Program Administrators/Nursing Staff Members.
All of the users shall be able to use the system after one day of training.
The system shall help the user avoid making mistakes while scheduling classes and clinicals for the nursing students.
The number of mistakes noted by the students shall be decreased by 50% in the first year.
The system shall be intuitive to the Program Administrators/Nursing Staff Members.
2 out of 3 Program Administrators/Nursing Staff Members shall successfully be able to use the system to manage the scheduling of classes and clinicals.
The system shall use symbols and words that are naturally understandable by the user community.
The verbiage used within the system shall be consistent with Standard English and the terminology of the national Nursing Community.
Staff members shall be able to complete a set of tasks in a timely manner.
The response time of general student management tasks shall take no longer than 5 seconds and the response time of schedule generation shall take no longer than 30 seconds.
The system shall be available for use between the hours of 8am and 6pm.
The system shall achieve 95% up time.
system shall be able to handle all of the user requests/usage during business hours.
The system shall cater to 10 simultaneous users from 9am to 5pm.
The system shall be capable of processing 100% of nursing students and their classes for the next 10 years.
The system shall be expected to manage the nursing program curriculum and class/clinical scheduling for a minimum of 5 years.
The system shall able to operate within a business office environment typical of the Nursing Department at DePaul University.
The system shall be used within the specifications defined by the computers used by the Program Administrators/Nursing Staff Members.
The system shall operate within the Windows XP Professional operating system.
The system shall interface with CampusConnect's central server.
The system shall interface with the faculty central server.
The system shall interface with the student master server.
We must be able to interface with any HTML browser.
Only authorized users shall have access to clinical site information.
Program Administrators/Nursing Staff Members are the only people who shall have access to clinical site details.
Only authorized users shall have access to students' personal information.
Dr Susan Poslusny and Dr Julie Donalek are the only people who shall have access to students' personal information.
Only authorized users shall have access to the portion of the system that interfaces with CampusConnect.
Fit Criterion: Dr Susan Poslusny and Karen Sysol are the only people who shall have access to the final class section scheduling for the system that interfaces with CampusConnect.
The system shall have basic data integrity checking to reduce the possibility of incorrect or invalid data being introduced.
The system shall protect private information in accordance with the organization's information policy.
The system shall be built such that it is as secure as possible from malicious interference.
The system shall use the organization's standard virus protection software to help monitor threats to itself.
The Disputes application shall comply with the corporate standards for user interface creation for internally and externally used applications.
All screens created as part of the Disputes application must comply with corporate standards for interface creation.
The list of dispute cases that are displayed after a search is performed must be color coded for easy identification of dispute cases based upon the dispute case status.
100% of the cardmember and merchant services representatives shall use the Disputes application regularly after a 2-day training course.
100% of cardmember services representatives shall be able to successfully create a dispute case on the first encounter after completing the training course.
100% of merchant services representatives shall be able to successfully perform a follow up action on a dispute case on the first encounter after completing the training course.
The maximum wait time for a user navigating from one screen to another within the Disputes application shall be no more than 5 seconds.
The Disputes application shall support 350 concurrent users without any degradation of performance in the application.
The Disputes application shall be available 24x7x365 with the exception of the following scheduled maintenance windows. Monday - Saturday 3:00am to 4:00am EST Sunday 1:00amd to 5:00am EST.
The Disputes application shall interface with the Statement Database. The Statement Database provides the transaction details to the Disputes System. All transaction details must be obtained from the Statement Database.
The Disputes application shall interface with the Cardmember Information Database. The Cardmember Information Database provides detailed information with regard to a cardmember. All cardmember detail information must be obtained from the Cardmember Information Database.
The Disputes applications shall interface with the Merchant Information Database. The Merchant Information Database provides detailed information with regard to the merchant. All merchant detail information shall be obtained from the Merchant Information Database.
The Disputes application shall interface with the Letters application. This will allow the Disputes application to request letters as part of the dispute initiation and dispute follow up process. All letter requests must be sent to the Print Letter Utility application.
The Disputes application shall interface with the Cardmember Posting and Billing System. This will allow the Disputes application to request adjustments to cardmember and merchant's accounts. All adjustment requests must be sent to the Cardmember Posting and Billing System.
The Disputes application shall ensure that only users with the appropriate access level are allowed to initiate dispute requests.
Only users with Update access must be able to initiate dispute requests.
The Disputes application shall ensure that only authorized users are allowed to logon to the application.
All authorized users once authenticated must be able to logon to the Disputes System.
The Disputes System shall generate a User Report that details any new users that have been added and any changes to an existing user's access level. The report will be reviewed for auditing purposes.
All additions of new users and modifications to user's access shall be recorded on the User Report.
If a user account is revoked it can only be re-instantiated by the System Administrator.
Only the System Administrator shall be able to reset a revoked user logon account.
The Disputes application shall manipulate and view business data. Users will not have direct access to data files or databases.
All updates to data files or database must be initiated from the Disputes System.
The Disputes application must conform to the legal requirements as specified by the Merchant Operating Regulations.
All business rules specified in the Disputes System shall be in compliance with the Merchant Operating Regulations.
The Disputes application must conform to the legal requirements as specified by Regulation E and Regulation Z that govern credit card disputes processing.
All business rules specified in the Disputes System shall be in compliance to the guidelines of Regulation E and Regulation Z.
The Disputes application must maintain a detailed history of every action that a user takes on a dispute case. This ensures a complete audit trail if questions arise later on with regard to a particular dispute case.
All actions that modify an existing dispute case must be recorded in the case history.
The product must support Internet Explorer 5.5 and above.
The product must support Mozilla Firefox 1.0 and above.
The product shall interface with the Choice Parts System. This provides the feed of recycled parts data.
The product shall run on the existing hardware for all environments.
The product shall adhere to the corporate Architecture guidelines.
The product shall comply with corporate User Interface Guidelines.
The product shall comply with corporate color scheme.
The appearance of the product shall appear professional.
The product shall be easy to use by Adjusters and Collision Estimators. 95% of Adjusters and Collision Estimators shall find the product easy to use.
The product shall increase productivity of Collision Estimators. 80% of the Collision Estimators shall agree their productivity has increase within 1 month of using the product.
Users shall feel satisfied using the product. 85% of all users will be satisfied with the product.
The product shall be easy to learn by Adjusters and Collision Estimators. The product shall be learned with two days onsite training.
The user shall easily locate instructions while using the product. User help can be found within 90% of the system.
The search for recycled parts shall take no longer than 15 seconds. The search results shall be returned in under 15 seconds.
The search for the preferred repair facility shall take no longer than 8 seconds. The preferred repair facility is returned within 8 seconds.
The recycled parts audit report shall be returned to the user within 10 seconds. The audit report shall be returned within 10 seconds.
The preferred repair facility ratings shall be saved within 5 seconds. The save shall occur within 5 seconds.
The product shall adhere to the corporate online availability schedule. The application is brought down only within 98% of the scheduled outages per the availability schedule.
The product shall achieve a 98% uptime. The product shall not fail more than 2% of the available online time.
The product shall be able to handle up to 1500 simultaneous users. The system shall perform with 1500 users as a time.
The average number of recycled parts records per day shall be 50 000.
The product shall be able to handle 10 000 concurrent users within 2 years of the initial launch.
For estimators the product shall be able to be operated in a repair facility during dirty and noisy conditions.
The product shall interface with the ChoiceParts system once per day at approximately 1:00 AM.
The maintenance of the product will fall within the established corporate maintenance windows.
The product shall be supported using the corporate support center.
Product installations and upgrades shall be handled by the middleware technology team within established launch time frames.
Only adjusters can request recycled parts audit reports. No users without an adjuster role shall request recycled parts audits.
Only adjusters with a supervisor role can update preferred repair facility ratings. Users without the supervisor role cannot access the repair facility ratings.
Only collision estimators shall search for recycled parts. Users without the collision estimator role shall not have access to the search for recycled parts.
Only valid data shall be entered into the system. No invalid data shall be entered into the system.
One insurance company shall not be able to view another insurance companys claim data.
The product shall free of computer viruses.
The system shall prevent malicious attacks including denial of service.
The product must comply with Sarbanes-Oxley.
The product shall comply with the estimatics laws relating to recycled parts usage.
The product shall comply with insurance regulations regarding claims processing.
The product must work with most database management systems (DBMS) on the market whether the DBMS is colocated with the product on the same machine or is located on a different machine on the computer network.
The product will function alongside server software on any operating system where the Java runtime can be installed.
The product will require collaboration with a database management system (DBMS). The DBMS may be located on the same machine as the product or on a separate machine residing on the same computer network.
The product must make use of web/application server technology. Open source examples include Apache web server Tomcat and the JBoss application server.
A database management system such as Oracle DB2 MySql or HSQL will need to be integrated with the product.
The product's Look and Feel shall be able to incorporate aspects of the customer's organization such as logo branding and identity.
The product shall have a conservative and professional appearance.
The product shall make the users want to use it. 80% of the users surveyed report they are regularly using the product after the first 2 weeks post-launch.
The product shall be easy to use. 90% of users will be able to successfully reserve a conference room within 5 minutes of product use.
The product shall give users feedback when necessary. 80% of the users surveyed report that the product accurately confirms their actions.
The product shall allow the user to select a chosen language from one of the target market countries.
The product shall allow for customization of start page and views preferences.
An employee will be able to successfully use the product within a few minutes. After informally navigating the product for less than 15 minutes users shall be able to successfully setup meetings and reserve conference rooms.
The product shall use a standard navigation menu familiar to most web users.
The product shall allow for intuitive searching of available conference rooms.
The product shall conform to the Americans with Disabilities Act.
The response shall be fast enough to avoid interrupting the user's flow of thought. 90% of tasks shall complete within 5 seconds. 98% of tasks shall complete within 8 seconds.
Aside from server failure the software product shall achieve 99.99% up time.
The product shall create an exception log of problems encountered within the product for transmission to our company for analysis and resolution.
The product shall be capable of handling up to 1 000 concurrent requests. This number will increase to 2 000 by Release 2. The concurrency capacity must be able to handle peak scheduling times such as early morning and late afternoon hours.
The product shall be able to process 10 000 transactions per hour within two years of its launch. This number will increase to 20 000 by Release 2.
The product shall be expected to operate for at least 5 years for each customer installation.
The product shall be used in office environments.
The product must be able to interface with any HTML browser. The product shall transmit data between the user and the product without problems. The product shall display HTML properly in 80% of all HTML browsers tested (minimum is to test 8 browsers).
The product must be able to interface with various database management systems. The product shall communicate successfully with the database management system on 100% of all transactions.
The product must be able to interface with various email servers. The product shall be able to send email.
The product shall be available for distribution via the Internet as a binary or ZIP file.
The product shall be available for distribution as a packaged CD.
The product will be available for licensing as a one-server two-five servers or five-or-more servers license.
A new user must be able to be added to the system within 10 minutes. 90% of new users are able to log into the system within 10 minutes.
The product must be designed using Design Patterns and coding best practices. 90% of maintenance software developers are able to integrate new functionality into the product with 2 working days.
The product must be highly configurable for use with various database management systems for the end users. 80% of end users are able to integrate new database management systems with the product without changing the product's software code.
Maintenance releases will be offered to customers once a year. The releases shall take no longer than 5 minutes for 80% of the customer base to install.
Every registered user will have access to the product's support site via the Internet. 70% of registered users shall find a solution to their problem within 5 minutes of using the support site.
The customer shall be able to easily integrate new building maps with the product throughout the product's lifecycle. Integration of new maps with the product shall be possible with little to no support from product support staff.
The product shall be translated into foreign languages other than the target market countries' languages in future releases. For each emerging target market it shall take no more than 5 days to configure the product for that market's language.
The product is expected to integrate with multiple database management systems. The product will operate with Oracle SQL Server DB2 MySQL HSQL and MS Access.
The product shall be able to be installed in any operating environment within 2 days.
The product shall ensure that only company employees or external users with company-approved user IDs may have product access. 100% of all logons shall be by either company employees or external users with company-approved user IDs.
Only managers are able to perform search queries for reservations by user. 100% of all search queries for reservations by user shall be from logons of only management logons.
The product shall ensure that the database's data corresponds to the data entered by the user. Each conference room reservation in the system will contain the same information as was entered by the user.
The product shall prevent the input of malicious data. The product and/or adjacent hardware/software systems' data shall remain 100% uncorrupted each time malicious data is input into the product.
The product and/or dependent databases/filesystems shall remain operational as a result of the input of malicious data. The product and/or dependent databases/filesystems shall not crash 100% of the time that malicious data is input into the product.
The product shall have the ability to receive automatic software updates as new threats emerge. 100% of customers will be able to receive automatic software updates transmitted to the installed product.
The language of the product shall accommodate all of the target market countries. 90% of survey respondents from each target market country will find that the language of the product is acceptable.
The product shall be able to display calendar dates and times according to the user's locale. 90% of survey respondents from each target market country will find that the date and time formatting of the product is correct.
The product must be developed with the J2SE/J2EE programming language libraries.
Recreation of Inventory Quantity Adjustment for the period of previous 30 days shall take no more than 30min.
The System shall allow for a minimum of 6 users to work at the same time.
The System shall utilize currently owned computer equipment.
The System shall be able to automatically backup business data and restore them on demand.
The System shall maintain consistent security. Any changes in user passwords and/or permissions should take affect in all parts of the System.
The System shall granularly control access rights to all major subsystems. It should be possible to assign access rights to all subsystems independently.
The System shall meet all applicable accounting standards. The final version of the System must successfully pass independent audit performed by a certified auditor.
The System shall not require additional third party licenses resulting in royalty fees.
Administrator shall be able to activate a pre-paid card via the Administration section in under 5 seconds.
Customer shall be able to check the status of their prepaid card by entering in the PIN number in under 5 seconds.
System shall let customers register on the website as a pay as you go user in under 5 minutes.
System shall let customers register on the website as a unlimited movie subscriber user in under 10 minutes.
System shall let existing customers log into the website with their email address and password in under 5 seconds.
System shall let customers cancel their account process shall take no longer than 2 minutes. Database will mark the account as inactive and user will not be able to log into the website.
System shall let administrator de-activate a customer account in under 1 minute. Customer will no longer be able to access the website.
System shall let administrator add/remove movies on the website in under 5 minutes. Entered movie information will be stored in the database and will now be available on the website.
System shall let the administrator add/remove categories on the website in under 5 minutes.
System shall let Izogn Manager access sales and usage statistics in under 2 minutes.
System shall let administrators generate unique pre-paid pins in under 2 minutes and generate an Excel file with the generated PINs.
The website shall be attractive to all audiences. The website shall appear to be fun and the colors should be bright and vibrant.
The website should have an African feel but should not alienate non-Africans. The website should use animation on pages which are describing the services to grab the users attention and encourage them to sign up.
The website design should be modern clean and concise.
The product should be able to be used by 90% of novice users on the Internet.
Users should only have to navigate through a maximum of 4 pages to create an account with the website.
Users should be able to access their streaming movies in under 2 clicks after logging into the website.
An anonymous survey will show that 70% of customers are comfortable purchasing streaming movies after 2 weeks using the website.
An anonymous survey will show that 95% of customers are comfortable using and purchasing pre-paid cards after a month of using the system.
The product shall retain the customer's buying preferences and information.
The product shall be easy for customers with novice skills on the Internet to purchase and watch streaming movies. Customers should be able to purchase and watch a pre-determined movie in under 3 minutes.
The product shall use symbols and words that are naturally understandable by users familiar with websites.
The website will use standard Internet conventions when interacting with the user.
Any interface between a user and the automated system shall have a maximum response time of 5 seconds unless noted by an exception below.
When purchasing a streaming movie or pre-paid card via credit card the processing time should have a maximum response time of 15 seconds.
When streaming a movie the buffering time should take no longer than 10 seconds (plus any latency on the user's connection).
While streaming a movie buffering should only occur if there is latency in the user's connection.
All credit card information will be secured on the server and only accessible by authorized Izogn administrators. Information will be encrypted in the database.
The website shall be available for use 24 hours per day 365 days per year.
The website shall achieve 99.5% up time.
All movies shall be streamed on demand at any time of the day.
The website shall continue to operate if the streaming server goes down.
The website shall continue to operate if the payment gateway goes down.
The streaming server will support 50 simultaneous streaming connections.
"The streaming server will support a maximum of 700 movies; new servers can be added to support more movies."
The server will support a maximum of 1 000 simultaneous users.
The website shall be capable of supporting 100 000 customers.
The product shall be expected to operate within the maximum maintenance budget for a minimum of 2 years.
All aspects of the website shall be accessed by a web browser over the Internet.
The same hardware supporting the current website will be used to support the new system.
We must be able to interface with the following browsers: IE 5.X 6.0 Netscape 6.x 7.x 8.x and Firefox 1.0.
Website must interface with the CyberSource API to process credit card transactions.
Website must be fully operational with MSN TV2.
Movies shall be encoded and streamed via Windows Media Player 9.0.
Movies shall be encoded for 56k and 256k streams.
Promotional updates to the website should take a day to update.
Izogn Administrator must be able to update the category listings on the website within 2 minutes.
Izogn Administrator must be able to add new products to the website within 2 minutes.
The system will provide a 24 hour 800 toll free number for support to its customers.
The website will provide a help section with answers and solutions to common problems.
Velkat staff will be available for phone support between 7am-7pm M-F to provide technical support to the Izogn administrators.
The product shall be able to be installed in the specified environment within 1 working day.
Only registered customers can purchase streaming movies.
A customer can only stream a movie if they purchased it and are within the 2 day viewing period.
Only authorized personnel can access customer records in the database.
Only administrators can activate a pre-paid card.
Only authorized personnel can access sales information.
The website shall prevent its data from being corrupted when incorrect data is entered in.
The website shall protect itself from intentional abuse and notify the administrator at all occurrences.
Data integrity scripts will be run on a weekly basis to verify the integrity of the database.
The website shall make its user aware of its information practices before collection data from them via a Privacy Policy accessible on all pages of the website.
The system shall notify customers of changes to its information policy.
The system shall reveal private information only in compliance with the organization's information policy.
All customer information will be stored on a secure database accessible only to authorized personnel.
All credit card information will be encrypted in the database.
The streaming server will have anti-virus software to prevent infection of malicious viruses.
The website should cater to all tribes in Nigeria.
The website shall not be offensive to religious or ethnic groups.
The website should appeal to all Africans not only Nigerians.
The website should use Flash to provide animation on the home page.
IzognMovies shall meet the licensing requirements set forth by the appropriate organizations in order to stream African movies.
The website will comply with W3C standards.
The PHP code will comply with PEAR standards.
Total lead cycle time must be completed in 5 minutes for 90% of lead volume between the business hours of 8AM CST to 8PM CST; then 3 minutes for 99% of lead volume during off business hours.
No lead evaluation will complete in a time period longer than 25 seconds for 97% of all leads processed.
For leads that process longer than 25 seconds the system will record the event and duration.
The process must fit within the processing time conditions set forth by the Auto Rep Assignment process in which a lead is assigned within 3 minutes of the total life cycle.
The lead washing process will operate within the established physical web service structure.
The washing process must use a non binding neutral data format such as xml when receiving and processing lead data.
Defect reports will be available to technical units on a 24x7 basis.
Washing parameters will be updated during scheduled maintenance hours.
The product shall simulate the look of ships at sea.
The product shall display the grids within a circle as a view from a periscope.
The product shall display each type of ship in a grid using an image of the specific type of ship.
When the offensive player takes a shot the product shall simulate the sound of a ship at sea.
When a shot is marked as a miss the product shall simulate the sound of a shot missing its target.
When a shot is marked as a hit the product shall simulate the sound of a shot hitting its target.
When a ship is sunk the product shall simulate the sound of a sinking ship.
The product shall be available 24 hours per day seven days per week.
The product shall able to handle a large number of games simultaneously.
The response time shall be fast enough to maintain the flow of the game. The response time shall be no more than 2 seconds for 95% of responses and no more than 4% for the remaining responses.
The product shall protect the identity of the players. The product shall provide players no access to information that might reveal the identity of another player.
The product shall be intuitive and self-explanatory. Nine out ten users shall be able to successfully complete a game with no training.
The product shall be available to players who understand English Spanish and French. The product shall allow the user to select the language upon accessing the product.
The product shall provide players no access to information that might reveal the identity of another player.
The response time shall be fast enough to maintain the flow of the game. The response time shall be no more than 2 seconds for 95% of responses and no more than 4% for the remaining responses.
The system shall be easy to use by callers and supervisors. Callers and supervisors must be able to accomplish any system task within 2 minutes.
The system shall be easy to learn by callers and supervisors. Callers and supervisors shall learn how to use the system within 10 minutes.
The system shall be responsive. At the DePaul TeleServices Center when a supervisor uses the system to view a callers schedule the system response time must be no more than 2 seconds 90% of the time and no more than 5 seconds the rest of the time.
On a 56k connection the system response time for all operations must be no more than 6 seconds 90% of the time.
On a 112k connection or faster the system response time for all operations must be no more than 3 seconds 90% of the time.
The system shall have high availability every day of the year. The system must be available for use between 12:00AM and 6:00PM all days of the year.
The system must be available for use between 7:00AM and 11:59PM all days of the year.
The product shall be internet browser independent. The product must run using Internet Explorer and Netscape Navigator.
The product shall ensure that only supervisors can advertise empty time slots. The product must ensure that supervisors are allowed to access advertise empty time slots.
The product shall ensure that only supervisors can enter a caller's schedule. The product must ensure that supervisors are allowed to access advertise empty time slots.
The product shall ensure that only supervisors can view schedule of all callers. The product must ensure that supervisors are allowed to access advertise empty time slots.
The interface shall have a simple look. In the interface and usability survey 90% of beta testers must report that the interface is adequately simple.
The interface shall be appealing to callers and supervisors. In the interface and usability survey 80% of beta testers must report that the interface is appealing.
The product shall provide GUI based Monitoring Services. System Administrators shall monitor message exchanges will predict and determine problems and will also provide internal and external support.
The product shall comply with City of Chicago Application Development Guide Framework. Application Development Framework will provide structured Graphical User Interface.
The product shall provide Monitoring Services. The product shall be easy for System Administrators and DBAs to use after two weeks of usage.
The product shall provide Error Tracking Services. The product shall help the System Administrators and DBAs to resolve transaction errors 99% of the time.
The product shall provide Portals. The product shall help System Administrators to analyze the transactions with ad-hoc reporting and KPIs (Key Performance Indicators).
The product shall provide Asynchronous Messaging. The product shall provide asynchronous messaging to enable parallel processing and reduce the overhead in communications.
The product shall provide Multi-threading and Load Balancing. The product shall provide multi-threading technology as well as load balancing to overcome data load spikes and traffic.
The product shall process messages within 2 seconds. The product shall have a maximum message processing time of 2 seconds.
The product shall poll the system for messages every second. The product shall poll the system for new messages at a maximum of every 1 second.
The product shall provide Dynamic Change Support and Transparent resource addition. The product shall support Transparent Resource addition and Dynamic Change support to provide scalability and avoid service interruptions of more than 1 day.
The product shall be available 99% of the time. Rationale: To avoid service interruption during busiest customer service response periods. The product shall be available 99.99% of the time for regular business days.
The product shall be robust. The product shall have fault avoidance based on standards adoption.
The product shall be robust with fault tolerance. The product shall have fault tolerance by using recovery technique compensatory transaction and routing around failures.
The product shall be able to process all transactions. The product shall process minimum of 1 million transactions per year.
The product shall be platform independent. The product shall enable access to any type of development environment and platform.
The product shall interface CSR and Datastream. The product shall exchange messages between CSR and EAM on a real time basis without any direct interfaces between two systems.
The product shall continue to operate during upgrade change or new resource addition. The product shall be able to continue to operate with no interruption in service due to new resource additions.
The product shall be updated on a regular basis. The product will have a new major feature introduced every six months and quarterly maintenance releases every six months.
The product shall operate with every platform. The product shall accommodate any new technology without any change in its architecture.
The product shall have security. The product shall provide authentication and authorization.
The product shall information Security. The product shall enable privacy by encryption WS-Security and Integrity Checking.
The product shall have audit capabilities. The product shall store messages for a minimum of one year for audit and transaction tracking purposes.
The system shall use IBM and CCR branding standards. The interface must have one IBM logo and one CCR logo.
The system shall be displayable on any work computer a CCR user may have. The system interface shall be formatted to display at 800 by 600 pixel resolution.
The system interface will use CCR nomenclature. The system must use the same nomenclature used in the existing WCS system and reports.
The interface must summarize the data in a fashion that's appealing to CCR management. Every report type must have at least one high level summary shown in the results dashboard/interface.
The system must use a point and click interface. 100% of all selection and navigation functionality must be able to be activated/selected by either a mouse or a keyboard.
The interface shall be easy to use. 90% of users should be able to successfully use the system to generate a report on their first use. The interface should adhere to IBM usability standards.
Reports must be easy to generate. Reports must be generated within one button click and exported within one button click (after selecting the report).
A user shall be able to use the system without instruction after a short amount of time. After one use a user should understand and remember 90% of the system usage and navigation.
All CCR users shall receive training before the WCS system is deployed. One training session will be held for 100% of CCR users before system deployment (based on a CCR user being available).
The WCS system shall use appropriate nomenclature and terminology as defined by the Corporate Community Grants organization. All interfaces and reports will undergo usability tests by CCR users.
The WCS system shall be available at all times as long as IBM's internal intranet W3 is accessible. The WCS system will be available 95% of the time IBM's internal intranet W3 is available.
The WCS system shall have the ability to connect other designated WCS databases currently not included in the system.
The WCS system shall have the ability to include data for regions outside the United States and be accessed by users outside of the United States if approved by CCR management.
The WCS system shall be run in a Windows environment. The WCS shall be accessed by users through the Internet on an IBM computer running a Windows 2000 or above operating system.
The Brio portion of the WCS system must be able to export files in spreadsheet form (Microsoft Excel and Lotus 1-2-3 formats). Brio will provide buttons in the user interface that produce/export reports in .xls or .123 file formats.
The WCS system must run queries to the WCS databases once again (on a specified day) to update the available data available to CCR users. Queries must be made to external databases for data refresh once a week.
All changes updates and additions to the WCS system shall be updated in the WCS Developer and WCS User Guides. Every change must be reflected in WCS system documentation.
The system shall only be accessed by authorized Corporate Community Grants (CCR) employees. Users must be authenticated using their IBM intranet user name and password.
The WCS system shall not allow automatic logins by any user. Cookies containing WCS login information about a user will not be stored on a user's computer.
Each team owner will need to use a username and password in order to be authenticated to reach the team owner's page.
The Commissioner will be the only authorized user per league to adjust league settings.
Each page shall contain a navigation menu which shows the index into which the current page is contained.
Each page shall contain a similar format with action items in one location and navigation buttons in a different location.
The message board shall contain the 5 most recently posted messages on the league page. The messages will contain up to the first 150 characters of the message.
A new user shall be able to navigate through the league and team pages within 30 seconds of reaching the start-up page.
Users shall be able to reach the add drop and trade player pages with one click from the team owner's page.
Users shall be able to view at least 25 NFL player statistics and points on each page.
The application shall ask the user to confirm dropping a player or trading a player before performing the action.
The application shall be able to complete every user transaction within one fourth of a second of receiving the request over the network.
The application shall have a downtime of at most 10 minutes per year.
The application shall run on a web application server.
A primary database will be used to store cached data for active users.
A secondary database will be used to store historical statistics and data.
Application updates shall occur between 3AM and 6 AM CST on Wednesday morning during the middle of the NFL season.
New System version releases shall be released at the beginning of each NFL season.
The RFS system should be available 24/7 especially during the budgeting period. The RFS system shall be available 90% of the time all year and 98% during the budgeting period. 2% of the time the system will become available within 1 hour of the time that the situation is reported.
98% of the user workstations shall meet the minimum hardware requirements prior to implementation. Minimum Hard Disk Space: 400MB.
98% of the user workstations shall meet the minimum software requirements prior to implementation: Microsoft Internet Explorer 5.0. Microsoft .NET Framework 1.1. Microsoft Internet Explorer Web Controls.
The RFS system should be able to easily interface with the BDW environment in order to load the data. 7 data files shall be received from the BDW and loaded into the RFS system within 3 hours one day prior to the start of budgeting process every year. The data will be as of October month-end. Test files (7) shall be loaded up to 5 times throughout the year from the BDW.
Changes to revenue and expense formulae must be applied to the RFS system every year prior to the budgeting process start. Revenue and expense formulae will be updated within one week of their receipt after which 2 weeks will be allotted to testing of the budget calculations to be conducted jointly by the project development team and PCG Finance.
New branches/complexes/districts/regions and revenue/expense accounts added to the BDW must be reflected in the RFS system. 100% of the entities (mentioned above) available as of October month-end will be loaded into the RFS system prior to the budget start process.
Only authorized user shall access the RFS system. ONLY users that exist in the UAS system with the RFS system assigned to their role(s) shall access the RFS system and use it.
User access should be limited to the permissions granted to their role(s) Each level in the PCG hierarchy will be assigned a role and users will be assigned to these roles. Access to functionality within RFS system is dependent on the privileges/permission assigned to the role.
The product must comply with the intranet page standards and requirements of ENET Securities. 95% of the product look & feel will be approved by the Architecture group prior to implementation. The remaining 5% will be corrected and approved within one month of product release.
The intranet pages should display appropriately in all resolutions from 800x600 and higher. The display of all the pages will be correct in 95% of the resolutions prior to implementation. The remaining 5% will be corrected within a week of notification of the incorrect display.
The users should be able to easily use the system to successfully complete their budgets within the stipulated time for completion. With a week of training prior to product implementation 98% of the users shall complete their budgets within the stipulated time.
The product interface should be fast. The response time of the product interface should not exceed 2 seconds 90% of the time. For 10% of the time the response time should not be more than 10 seconds. Not be more than 10 seconds.