The product shall perform the display fast.
The product shall match the appearance of the schema set forth by user.
If projected the product must be easy to use. On a 10x10 projection screen 90% of users must use data from a viewing distance of 30.
The product shall be available during alltimes. As long as the user has access to the client PC the system will be available alltimes during the first six months of operation.
If projected the product must be easy to use. On a 10x10 projection screen 90% of users must determine that product are occuring in current time from a viewing distance of 100.
The product shall authorize that it can only be accessed by authorized users. The product will authorize between authorized and unauthorized users in all access attempts.
The product shall be easy to use and easy to use. 90% of new users shall start the display fast.
The product shall perform fast to keep updated data in the display.
The system shall have a MDI form that allows for the viewing of the graph and the data table.
The system shall display Events in a vertical table by time.
The system shall display the Events in a graph by time.
The system shall display Events or Activities.
The display shall have two regions: left 2/3 of the display is graphical right 1/3 of the display is a data table.
The data displayed in both the nodes within the graph and the rows in the table are MSEL Summary data.
The table side of the display shall be split into 2 regions: sequential and temporal.
The top 1/4 of the table will hold events that are to occur sequentially.
The bottom 3/4 of the table will hold events that occur according to its relevance to current time.
The system shall color code events according to their variance from current time.
The system shall display data from the Sync Matrix 1.0 and Exercise Management Tool 1.0 applications.
The system shall link Events back to either the Sync Matrix 1.0 or the Exercise Managment Tool 1.0 applications for modifications.
The system shall allow modification of the display.
The system shall offer a display of all the Events in the exercise.
The system shall filter data by: Venues and Key Events.
The system shall allow a user to define the time segments.
The system shall display the local and exercise time in separate clocks.
The system shall offer the ability to pause and resume the refresh of data.
The system shall provide charts for the Activity or Event actual versus assumed time.
The system shall provide a history report of changes made to the Activity or Event data.
The appearance of the product shall match the appearance standards of the smart device.
The appearance shall match standard menus buttons for navigation.
The product shall match a professional appearance.
The product shall match a consistent appearance and fonts.
The product shall be easy to use by users with no training.
The product shall be easy to use and easy to use.
The product shall be easy for a user to use.
The product shall use symbols and words that are naturally easy to use by the user.
The product shall perform search results fast.
The product shall be performed fast after the user has entered the search criteria.
The product shall perform a report fast.
The product shall be performed fast after the user has entered the report criteria.
The product shall perform contacts and appointments fast.
The product shall perform with the office system fast.
The product shall be available for use alltimes.
Out of 1000 accesses to the product the product is available alltimes.
The product shall tolerate in failed mode if internet connection failure.
The product shall allow the user to view previously downloaded search results reports and appointments.
The product shall tolerate user preferences if a failure.
100% of saved user preferences shall be restored when product comes back online.
The product shall scale simultaneous users.
The product shall scale simultaneous users.
The product shall scaling the existing simultanous users. This number is expected to grow 5 times within the next year.
The product shall be easy to used by an untrained user with no recourse to separately-printed instructions.
90% of untrained users shall easy to use the product on their device with no printed instructions.
The product is expected to run on Windows CE and Palm operating systems.
Only authorized users shall access the product.
Every user of the product shall be authorized and authorized.
The product shall authorize its data from un-authorized data being accessed.
The system shall allow a real estate agent to query MLS information.
The user shall get driving directions to a selected property.
The user shall download appointments and contact information for clients.
The system shall display clear property images in the search results.
The system shall update or create new property listings in the MLS.
Realtor shall generate a CMA report based on property criteria.
The system shall call the seller or buyer to schedule an appointment.
The realtor shall be notified of new client appointments after automatic synchronization with office system.
The realtor shall retrieve a map showing property locations for a specified area.
The system shall notify the realtor when a seller or buyer responds to an appointment request.
The product shall allow the user to save the property search results.
The product shall be easy to use by users.
All of the users shall easy to use the product after one day of training.
The product shall help the user easily use while scheduling classes and clinicals for the users.
The number of mistakes noted by the users shall be easily use by 50% in the first year.
The product shall be easy to use to the users.
Users shall easily use the product to manage the scheduling of classes and clinicals.
The product shall use symbols and words that are naturally easy to use by the users.
The verbiage used within the product shall be consistent with Standard English and the terminology of the users.
Users shall perform a set of tasks fast.
The response time of product shall perform fast and the response time of product shall perform fast.
The product shall be available for use alltimes.
The product shall be available alltimes.
Product shall handle all of the user requests usage during business hours.
The product shall scale to 10 simultaneous users alltimes.
The product shall scaling simultaneous users and their classes for the next 10 years.
The product shall scale the simultaneous users for a minimum of 5 years.
The product shall operate within an environment typical of the user.
The product shall operate within the environment.
The product shall operate within the environment.
The product shall operate with environment.
The product shall operate with the environment.
The product shall operate with the environment.
User must operate with environment.
Only authorized users shall have access to product.
Users are the only authorized users who shall have access to product.
Only authorized users shall have access to product.
Users are the only authorized users who shall have access to product.
Only authorized users shall have access to the portion of the product that operate with product.
Users are the only authorized users who shall have access to the product scheduling for the product that operates with product.
The product shall have basic data authorization checking to reduce the possibility of un authorized or un authorized data being introduced.
The product shall protect authorized information access in accordance with the organization information authorization.
The product shall be built such that it is as authorized as possible from un authorized access.
The product shall use the organization standard un authorized data access software to help monitor threats to itself.
A cohort shall be associated to one Program of Study offered by the department.
Program Administrators and Nursing Staff Members shall add a listing of students to a cohort.
Program Administrators and Nursing Staff Members shall add a single student to a cohort.
Students added to a cohort shall be eligible for the cohort's Program of Study.
Program Administrators and Nursing Staff Members shall specify the preferred sequence of classes for a given cohort.
For each class within a sequence for a cohort Program Administrators and Nursing Staff Members shall specify which quarter that class will be offered.
For each class within a sequence for a cohort Program Administrators and Nursing Staff Members shall specify which quarter that class will be offered.
Program Administrators and Nursing Staff Members shall add new classes to a sequence of classes.
Program Administrators and Nursing Staff Members shall add clinical classes or sections to a sequence of classes.
Program Administrators and Nursing Staff Members shall add a new cohort to the system identified by start month and year.
Program Administrators and Nursing Staff Members shall add new classes for the nursing department into the system.
A class shall be either a non-clinical class or a clinical class.
A non-clinical class shall specify the course name lecture room requirements and instructor needs.
A clinical class shall specify the course name lecture room requirements clinical site needs lecture instructor needs and clinical lab instructor needs.
Program Administrators/Nursing Staff Members shall create a new Program of Study.
A Program of Study shall consist of a program name and listing of required classes (both clinical and non-clinical) that must be completed.
Program Administrators and Nursing Staff Members shall specify which classes are required for a Program of Study.
The system shall display a report of needed classes for a given quarter for all cohorts of all programs for Program Administrators/Nursing Staff Members' planning purposes.
The report of needed classes shall include (but not be limited to) classes to be offered number of sections needed number of labs needed and room types needed.
Classes for a given cohort shall not conflict with regards to the time and day that they are offered.
Program Administrators and Nursing Staff Members shall add a new clinical site into the system.
Clinical site information shall include (but not be limited to) the name of the site contact person and contact information.
Program Administrators and Nursing Staff Members shall add a new clinical lab section for an existing clinical class into the System.
A clinical lab section shall include the clinical site name the class instructor day and time of the lab.
Program Administrators and Nursing Staff Members shall add a student who has registered for a clinical class to a clinical lab section for that class.
The system shall allow a Program Administrator or Nursing staff member to remove a student from a clinical lab section.
The system shall allow a Program Administrator/Nursing Staff Member to move a student from one clinical lab section to another clinical lab section corresponding to the same clinical class.
Program Administrators/Nursing Staff Members shall cancel a clinical lab section only if there are no students registered for that clinical lab section.
A Program Administrator/Nursing Staff Member shall add a new nursing student to the system.
A staff member shall manage the progress of a part time student which includes modifying their sequence of classes and timeline of classes.
The system shall display a printable summary for individual cohorts which will include the students enlisted the Program of study sequence of classes cohort progress through the program and timeline of completion.
The system shall display a printable summary for individual clinical sites which will include information on labs being held at that site for the given quarter (Clinical site general information on labs held at that location dates and times of all labs held there).
The system shall display a printable summary for individual clinical labs which will include (but not be limited to) class name class number lab section listing of students enrolled instructor day(s) time and location.
The system shall display a printable summary for individual nursing students which will include (but not be limited to) student name student ID admission date classes credits GPA and the cohort that the student is enrolled in.
The system shall display a printable summary of the system log.
The system shall contain contact information (e-mail and phone number) for all people relevant to the system including (but not limited to) staff members students lecture instructors clinical lab instructors and clinical site administrators.
The system will use the stored e-mail addresses as a primary means of communicating information to affected parties.
The system will notify affected parties for routine communication purposes including but not limited to informing students of upcoming offered classes (timeline) and what their schedule will be/shall be.
The system will notify affected parties when changes occur affecting clinicals including but not limited to clinical section capacity changes and clinical section cancellations.
The system will notify affected parties when changes occur affecting classes including but not limited to class cancellations class section detail changes and changes to class offerings for a given quarter.
The system will notify affected parties when changes occur affecting cohorts including but not limited to changes to the sequence for a cohort's program of study and changes to a given week's schedule (lab cancelled this week due to instructor illness).
The system will notify affected parties when changes occur affecting specific students including but not limited to changing a student's status from full time to part time and moving a student to a different clinical section.
Program Administrators/Nursing Staff Members shall modify information relating to cohorts including cohort identifier program of study preferred sequence of classes and quarters that a cohort will be taking specific classes.
Program Administrators/Nursing Staff Members shall modify information relating to a Program of Study within the Nursing Department including the Program of study name and required classes for that Program of Study.
Program Administrators/Nursing Staff Members shall modify information relating to a Clinical Site including the clinical site name site contact person contact information and address.
Program Administrators/Nursing Staff Members shall modify information relating to a Clinical Lab Section including the clinical site name the department/section for the lab the class instructor day and time of lab and contact information.
Program Administrators/Nursing Staff Members shall modify information relating to a Nursing Student including student ID student name phone number e-mail status (full time or part time) and program of study.
The product shall match the user standards for appearance creation for internally and externally users.
All appearance created as part of the product must match user standards for appearance creation.
The list of dispute cases that are displayed after a search is performed must be color coded for easy use of dispute cases based upon the dispute case status.
100% of users shal easily use the product regularly after a 2-day training course.
100% of users shall easily use a dispute case on the first encounter after completing the training course.
users shall easily use 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 product shall perform fast.
The product shall scale 350 simultaneous users without any degradation of performance in the application.
The product shall be available alltimes with the exception of the following scheduled maintenance windows.
The product shall operate with the environment. The Statement Database provides the transaction details to the product. All transaction details must be obtained from the Statement Database.
The product shall operate with the environment. The product provides detailed information with regard to a users. Simultaneous users detail information must be obtained from the product.
The products shall operate with the environment. The product provides detailed information with regard to the users. Simultaneous users detail information shall be obtained from the product.
The product shall operate with the environment. This will allow the product to request letters as part of the dispute initiation and dispute follow up process. All letter requests must be sent to the product.
The product shall operate with the environment. This will allow the product to request adjustments to users and users accounts. All adjustment requests must be sent to the product.
The product shall ensure that only authorized users are allowed to access product.
Only authorized users with access must initiate product requests.
The product shall ensure that only authorized users are allowed to access to the product.
All authorized users once authorized must access to the product.
The product shall generate a User Report that details any new users that have been added and any changes to an existing users access level. The report will be reviewed for authorization purposes.
All additions of new users and modifications to user access shall be recorded on the User Report.
If a user account is revoked it can only be accessed by authorized users.
Only authorized users shall access a un authorized user access account.
The product shall manipulate and view authorized data. Users will not have direct access to data files or databases.
All updates to data files or database must be initiated from the product.
The product must meet the regulation requirements as specified by the user.
All business regulations specified in the product shall meet the user Regulations.
The product must meet the regulation requirements as specified by Regulation E and Regulation Z that govern credit card disputes processing.
All business regulations specified in the product shall meet to the guidelines of Regulation E and Regulation Z.
The product 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 Disputes System must be accessible by both internal and external users.
The Disputes System must prevent users from accessing any dispute cases that do not belong to their cardholder base.
The Disputes System will facilitate direct data entry of a dispute case via a user interface that supports real time responses to the users.
The Disputes System must provide different levels of access with regard to disputes case initiation and follow-up actions.
The Disputes System shall provide view access capability for authorized users of the application.
The Disputes System shall provide update access capability for authorized users of the application.
The Disputes System must allow the users to select disputable transactions (based on the age of the transaction) from a user interface and initiate a dispute (ticket retrieval request or chargeback notification) on the selected transaction.
The Disputes System must provide the user the ability to initiate a single dispute case on multiple transactions that belong to a single merchant.
The Disputes System will provide the user the ability to create or initiate a ticket retrieval request. As part of ticket retrieval creation process the system must prompt the user to enter all the required information to create the ticket retrieval request. The ticket retrieval request is a document that is sent to merchant inquiring the validity of a transaction.
The Disputes System must allow the user to create three unique types of ticket retrieval requests. The three types of ticket retrieval requests are (1) Request for original receipt (2) Request for a copy of the receipt or (3) Request for a portfolio. A portfolio consists of documentation that would provide proof of a purchase such as the documentation that is received from a car rental agency that is more than a sales receipt.
The Disputes System must prevent external users from requesting original receipts. Requests for original receipts are restricted to internal users.
The Disputes System must provide a confirmation to the user upon the creation of ticket retrieval request that contains the following information; the dispute case number the type of retrieval requested (copy original or portfolio) and the date that the merchant response is due.
The Disputes System shall allow the user to create or initiate a chargeback request. The system must prompt the user to enter the required information to initiate a chargeback request. The chargeback request results in a printed chargeback notification that is sent to merchant indicating that their account will be charged back if no proof is provided that the disputed transaction is valid.
The Disputes System must provide a confirmation to the user upon the creation of a chargeback request. The confirmation must contain the following information; the dispute case number the type of chargeback requested (pending or immediate) and the date that the merchant response is due.
The Disputes System shall prevent the creation of duplicate dispute requests 100% of the time.
The Disputes System shall accurately provide a list of possible reason codes for a given transaction. The list of possible reason codes must be derived based on the type of transaction and the industry that the merchant belongs to according to the business rules defined for the Disputes System.
The Disputes System must provide the ability to view existing dispute cases.
The Disputes System must provide Search functionality. The search method must include the ability to search by (1) the dispute case number (2) the merchant account number (3) the cardmember account number and (4) the issuer number. In addition to the above criteria the search functionality must further allow the user to limit the results of the search by a date range the type of dispute (ticket retrieval request or chargeback notification) the case status (open closed or all) and the dispute reason code.
A list of all disputes cases that meet the entered search criteria must be provided to the user. The list of cases must differentiate the type and/or status of the case by color -coding the line item in the list. For example all open cases will be yellow and all closed cases will be gray.
The Disputes System shall provide the users the ability to view the history of all activities that have occurred on the dispute case.
The Dispute System shall provide the users with the ability to follow up on a dispute case via follow-up actions. The list of available follow up actions for a given dispute case must be filtered by the status of the case and the access level of the user.
The Disputes System shall record the name of the user and the date for any activity that creates or modifies the disputes case in the system. A detailed history of the actions taken on the case including the date and the user that performed the action must be maintained for auditing purposes.
For any systematic (non-user initiated) action that occurs on a case such as the disputes aging process a case activity will be generated. Upon the next logon the user that initiated the dispute case must be notified that a systematic action has occurred on the dispute case.
All letter requests must be formatted according to guidelines specified by the Print Letter Utility system.
Any disputes cases that have been closed for over 6 months must be purged from the online disputes database.
The product must operate with environment and above.
The product must operate with environment and above.
The product shall operate with the environment. This provides the feed of recycled parts data.
The product shall operate on the environments.
The product shall adhere to the corporate Architecture guidelines.
The product shall match user appearance Guidelines.
The product shall match user appearance scheme.
The appearance of the product shall match professional.
The product shall be easy to use by users. 95% of users shall find the product easy to use.
The product shall increase productivity of users. 80% of the users 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 use by users. The product shall be easy to use with two days onsite training.
The user shall easily use instructions while using the product. User help can be found within 90% of the product.
The search for recycled parts shall perform fast. The search results shall be performed fast.
The search for the preferred repair facility shall perform fast. The preferred repair facility is performed fast.
The product shall be performed to the user fast. The audit report shall be performed fast.
The product ratings shall be performed fast. The save shall perform fast.
The product shall adhere to the corporate online availability schedule. The product is brought down only alltimes outages per the availability schedule.
The product shall be available alltimes. The product shall not fail more than 2% of the available online time.
The product shall scale up to 1500 simultaneous users. The system shall scale with simultaneous users as a time.
The average number of recycled parts records per day shall scale 50 000 simultaneous users.
The product shall scale 10 000 simultaneous users within 2 years of the initial launch.
For users the product shall be operated in an environment during dirty and noisy conditions.
The product shall operate with the environment 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 uodates shall be operated by the users within established launch time frames.
Only authorized users can access recycled parts authorization reports. No users without an user role shall request recycled parts authorizations.
Only authorized users with auser role can access preferred repair facility ratings. Users without the user role cannot access the product.
Only authorized users shall access for product. Users without the user role shall not have access to the search for product.
Only authorized data shall be accessed into the system. No unauthorized data shall be accessed into the system.
One user shall not access another user authorized data.
The product shall free of computer unauthorized data.
The product shall prevent unauthorized data access including denial of service.
The product must meet Sarbanes-Oxley.
The product shall meet the estimatics regulations relating to recycled parts usage.
The product shall meet insurance regulations regarding claims processing.
The user shall search for the preferred repair facility using vehicle vehicle location and radius in miles.
The vehicle data shall include vehicle year make and model.
The vehicle location shall include street address city state and zipcode.
The system shall resolve the zipcode for the street address city and state if zipcode is unknown.
The search radius shall be between 1 and 30 miles.
The system shall locate the preferred repair facility with the highest ratings for the input criteria.
The adjuster shall enter the preferred repair facility on the estimate assignment.
The adjuster shall override the preferred repair facitlity on the estimate assignment.
The preferred repair facility shall be returned to the user.
The system shall return a list of repair facilities within the radius if the preferred repair facility cannot be determined.
The estimator shall search for available recycled parts using damaged vehicle parts information.
The estimator shall search for available recycled parts using a list of preferred parts suppliers.
The system shall search for available recycled parts for the supplied vehicle parts and suppliers.
The estimator shall search by zipcode with a radius of 30 miles if no parts are found for the preferred parts suppliers.
The system shall retain the available recycled parts and suppliers returned from the search.
The available recycled parts information and their suppliers shall be returned to the user.
The estimator shall apply selected recycled parts to the collision estimate.
The estimator shall not apply recycled parts to the collision estimate if no available parts are returned.
The adjuster shall review the collision estimate.
The adjuster shall request a recycled parts audit of the collision estimate.
The recycled parts search results provided to the estimator shall be retrieved by the system.
The system shall generate an audit report based on the available recycled parts and the collision estimate.
The audit report shall include the total number of recycled parts used in the estimate.
The audit report shall include the number of available recycled parts from the original search results.
The audit report shall include the percentage of available recycled parts used in the estimate.
The audit report shall include the total score of the audit which sums the indivual line items.
The audit report shall be displayed to the user.
The audit report shall be avail other adjusters at later points in time.
The user shall select to view the preferred repair facility ratings.
The current repair facility ratings shall be displayed to the user.
The system will display a blank set of ratings if there are not ratings yet defined.
The user shall enter new ratings based on the audit report.
The ratings shall be from a scale of 1-10.
The ratings shall include categories for attempted use of recycled parts and actual use of recycled parts.
The user shall select to save the preferred repair facility ratings.
The preferred repair facility ratings shall be saved by the system.
The product must operate with environment 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 operate alongside environment on any environment where the Java runtime can be installed.
The product will require interface with a environment. 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 operate of environment. Open source examples include environment.
An environment will need to be operated with the product.
The product appearance shall match aspects of the user organization such as logo branding and identity.
The product shall match 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 easily use a conference room fast 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.
A user will easily use the product fast. After informally navigating the product fast users shall easily use meetings and reserve conference rooms.
The product shall use a standard navigation menu easy to use to most web users.
The product shall allow for easy to use searching of available conference rooms.
The product shall match the Americans with Disabilities Act.
The response shall perform fast enough to avoid interrupting the user flow of thought. 90% of tasks shall perform fast. 98% of tasks shall perform fast.
Aside from server failure the software product shall be available alltimes.
The product shall create an exception log of failures encountered within the product for transmission to our company for analysis and resolution.
The product shall scale up to 1 000 simultaneous users. This number will scale to 2 000. The simultaneous capacity must scale peak usage times such asalltimes.
The product shall scale 10 000 simultaneous users alltimes. This number will scale to 20 000.
The product shall operate for at least 5 years for each user.
The product shall be operated in office environments.
The product must operate with environment. 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 operate with environments. The product shall operate with the environment on 100% of all transactions.
The product must operate with environments. The product shall 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 added to the system within 10 minutes. 90% of new users are log into the system within 10 minutes.
The product must be designed using Design Patterns and coding best practices. 90% of update software developers are support 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 support updated database management systems with the product without changing the product's software code.
Update releases will be supported to users once a year. The releases shall take fast for 80% of the users base to install.
Every registered user will have access to the product support site via the Internet. 70% of registered users shall find a solution to their problem fast of using the support site.
The customer shall easily suppport updated building maps with the product throughout the product lifecycle. Integration of updated 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 within 5 days to configure the product for that user language.
The product operate with environment. The product will operate with environment.
The product shall beoperated in any environment within 2 days.
The product shall ensure that only authorized users may have product access. 100% of all accesses shall be by either users or external users with company-approved user IDs.
Only authorized users access search queries for reservations by user. 100% of all search queries for reservations by user shall be from authorization of only authorized users management authorizations.
The product shall ensure that the authorized data corresponds to the data accessed by the user. Each conference room reservation in the product will contain the same information as was accessed by the user.
The product shall prevent the accesst of unauthorized data. The product and authorized data shall remain 100% uncorrupted each time unauthorized data data is accessed into the product.
The product shall tolerate operational if the input of failure data. The product shall tolerate 100% of the time that failure data is input into the product.
The product shall receive automatic software updates as new threats emerge. 100% of customers will receive automatic software updates transmitted to the installed product.
The language of the product shall scale simultaneous users. Simultaneous users will scale that the language of the product is acceptable.
The product shall display calendar dates and times according to the user locale. 90% of users from each target market country will find that the date and time formatting of the product is correct.
The product must be operate with the environment.
The product shall record meeting entries.
The product will notify employees of meeting invitations.
The product shall send meeting reminders to employees.
The product shall assign the organizers contact information to each meeting they create.
The product will record meeting acknowledgements.
The product shall store new conference rooms.
The product shall update existing conference rooms.
The product will delete conference rooms.
The product shall store new room equipment.
The product will update existing room equipment.
The product shall delete room equipment.
The product shall allow an organizer to invite other employees to meetings.
Each time a conference room is reserved the conference room schedule shall be updated to reflect the time and date of the reservation.
The product shall record the transportation status of equipment reserved.
The product shall display a map of the company building showing conference room locations.
The product shall record updated meeting agendas.
The product shall send a meeting confirmation to the meeting organizer.
The product shall display room equipment according to search parameters.
The product shall display conference rooms according to search parameters.
The product shall record different meeting types.
The product shall record all the equipment that has been reserved.
The product shall notify building personnel of equipment transport requests.
The product will allow priviledged users to view meeting schedules in multiple reporting views.
The product shall send meeting notifications via different kinds of end-user specified methods.
The product shall have a customizable Look and Feel.
The product shall have an intuitive user interface.
The product will display an available status for unreserved conference rooms.
Recreation of Inventory Quantity Adjustment for the period of previous 30 days shall perform fast.
The product shall scale for a minimum of simultaneous users to work at the same time.
The product shall operate currently owned environment.
The product shall automatically backup business data and restore them on demand.
The product shall maintain consistent authorization. Any changes in user authorization should take affect in all parts of the product.
The product shall granularly control access authorizations to all major users. It should be possible to assign access authorization to all users independently.
The product shall meet all applicable accounting regulations. The final version of the product must successfully pass independent authorization performed by a user.
The product shall not require additional third party licenses resulting in royalty fees.
The System shall allow generation of Inventory Quantity Adjustment documents on demand.
The System shall allow on demand generation of all Inventory Quantity Adjustment documents since certain point of time.
The IQA subsystem shall take into account current inventory status and adjust inventory of substitutionary ingredients accordingly.
The System shall allow entering storing and modifying product formulas.
Product formulas shall allow use of semi-products which have own formulas.
Product formula ingredients shall allow defining substitutionary ingredients.
Product formula substitutionary ingredients shall be entered automatically by the PFE subsystem.
Formula substitutionary ingredients shall be kept in persisted order.
Product shall allow entering storing and modifying product menus used by POS terminals.
PME Subsystem shall allow building product menus based on the list of products kept in the accounting system.
PME Subsystem shall allow keeping submenus within menus and products within submenus in a managed and persisted order.
PME Subsystem shall allow for a product to exist in more than one submenu.
The RMS System shall have Windows XP look and feel and use GUI futures making its use intuitive.
The System shall generate Inventory Quantity Adjustment document based on product daily sales data and product formulas.
The System shall generate Inventory Quantity Adjustment document automatically when daily Product Sales data is available.
User shall perform a pre-paid card via the Administration section fast.
Users shall perform the status of their prepaid card by entering in the PIN number fast.
Product shall let customers perform on the website as a pay as you go user fast.
Product shall let customers perform on the website as a unlimited movie subscriber user fast.
Product shall let existing customers perform the website with their email address and authorization in fast.
Product shall let users cancel their account process shall perform fast. Database will mark the account as inactive and user will not log into the website.
Product shall let users perform a user account fast. User will no longer access the website.
Product shall let user perform movies on the website fast. Entered movie information will be stored in the database and will now be available on the website.
Product shall let the user perform categories on the website fast.
Product shall let user perform sales and usage statistics fast.
Product shall let user perform unique pre-paid pins fast minutes and generate an Excel file with the generated PINs.
The product shall be attractive to all audiences. The website shall appear to be fun and the appearances should match bright and vibrant.
The appearance should match an African appearance but should not alienate non-Africans. The website should match animation on appearance which are describing the services to grab the users attention and encourage them to sign up.
The product appearance should match modern clean and concise.
The product should be easily 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 access their streaming movies in within 2 clicks after logging into the website.
An anonymous survey will show that 70% of users easily use product after 2 weeks using the website.
An anonymous survey will show that 95% of users easily use product after a month of using the system.
The product shall retain the users buying preferences and information.
The product shall be easy for users with novice skills on the Internet to use and use streaming movies. Users should perform and watch a pre-determined movie fast.
The product shall use symbols and words that are naturally easy to use by users familiar with product.
The product will use standard Internet conventions when operating with the user.
Any apperance between a user and the automated product shall perform fast unless noted by an exception below.
When purchasing a streaming movie or pre-paid card via credit card the processing time should perform fast.
When streaming a movie the buffering time should perform fast (plus any latency on the user connection).
While streaming a movie buffering should only occur if there is latency in the user connection.
All credit card information will be authorized on the server and only accessed by authorized users. Information will be prevented from unauthorized access in the database.
The product shall be available for use alltimes.
The website shall be available.
All movies shall be available on demand alltimes.
The product shall tolerate to operate if the streaming server failure.
The website shall tolerate to operate if the payment gateway failure.
The product will scale 50 simultaneous users.
The product will scale a maximum of 700 simultaneous users; new product can be added to scale simultaneous users.
The product will scale a maximum of 1 000 simultaneous users.
The product shall scale 100 000 simultaneous users.
The product shall support the maximum update budget for a minimum of 2 years.
All aspects of the product shall be operated by an environment over the Internet.
The same environment supporting the current product will be used to operate the new product.
Users must operate with the environment.
Product must operate with the environment to process credit card transactions.
Product must be fully operate with environment.
product shall be encoded and operate via environment.
Product shall be encoded for 56k and 256k streams.
Promotional updates to the website should take a day to support.
User must perform the category listings on the website fast.
User must perform new products to the website fast.
The system will be available alltimes 800 toll free number for support to its users.
The product will provide a help section with answers and solutions to common problems.
Users will be available for phone support alltimes to provide technical support to the users.
The product shall be operated in the specified environment within 1 working day.
Only authorized users can access products.
A user can only access a product if they purchased it and are within the 2 day viewing period.
Only authorized users can access customer records in the database.
Only authorized users can access a pre-paid card.
Only authorized users can access sales information.
The product shall un authorize its data from being corrupted when unauthorized data is accessed in.
The product shall protect itself from intentional un authorizes access and notify the user at all occurrences.
Data authorization scripts will be run on a weekly basis to verify the authorization of the database.
The product shall make its user aware of its information practices before collection data from them via a authorization Policy accessed on all pages of the product.
The product shall notify customers of changes to its information authorization.
The product shall reveal authorized information only in compliance with the user information authorization.
All users information will be stored on a authorized database accessed only to authorized users.
All user information will be unauthorized from un authorized access in the database.
The product will have anti- unauthorized software to unauthorize infection of unauthorized data.
The appearance should match to all tribes in Nigeria.
The appearance shall not match offensive to religious or ethnic groups.
The appearance should match to all users.
The product should operate environment to provide animation on the home page.
Product shall meet the regulation requirements set forth by the appropriate organizations to stream African movies.
The product will meet W3C regulations.
Product will meet PEAR regulations.
The website will allow customers to search for movies by title actor or director.
Viewing a movie details the website will display the movies description actor and director entered in by the administrator.
Website shall request and authorize credit card payment before allowing a user to stream a movie.
Shall stream purchased movie via Windows Media Player for up to 2 days aftere purchase date.
Website shall allow customers to browse movies by categories entered in by izogn administrator.
Website shall allow customers to view reviews of selected movies by other customers.
Website shall allow customers to add their own movie review for a selected movie.
Website shall allow the Izogn administrator to approve a review posted by a customer.
System will allow customers to pay for a streaming movie with a pre-paid card.
Website shall allow customers to purchase pre-paid cards of $5 $10 or $20 value either by credit card or mail-in payment option.
System shall automatically update the main page of the website every Friday and show the 4 latest movies that have been added to the website.
System shall allow users to update their billing and contact information via the 'My Account' section of the website.
Pre-paid cards shall be distributed via email or via a printed paper card.
Only registered customers can purchase streaming movies.
Movies can only be streamed if the customer has purchased a movie and is within the 2-day time period to stream the movie.
Website must support free trial periods with various parameters set by the Izogn Manager.
All streaming movie sales will be logged in the database and accessible by the administrator.
All registered customer information shall be stored and maintained in the database even after the customer cancels their account.
Daily usage statistics should be logged and accessible by the administrator.
The owner shall have free access to all of the streaming movies.
Total lead cycle time must be performed fast for 90% of lead volume alltimes; then 3 minutes for 99% of lead volume during off business hours.
No lead evaluation will perform in a time period fast for 97% of all leads processed.
For leads that perform fast the product will record the event and duration.
The process must fit within the processing time conditions set forth by the user in which a lead is performed fast of the total life cycle.
The product will operate within the environment.
The product must operate a non binding environment such as xml when receiving and processing lead data.
Defect reports will available technical units alltimes basis.
Product will support updated during scheduled maintenance hours.
The vendor will verify the invalid lead.
Vendor will submit a credit validation record to be applied to the enterprise billing system.
If a lead is scored to the high range the system will supply the lead data and score to the enterprise system.
The leads washing functionality will validate all leads received by the web service for valid data.
The leads washing functionality will insert all leads captured by the web service.
If the leads score falls within the high average score then it will be process by the ARA functionality.
If the leads score falls within the medium average then it will be set for manual verification by an Enrollment Coordinator through the eleads system.
If the leads score falls within the low average then it will be returned to the supplying vendor.
The leads washing functionality will compile both contact and academic scoring information for a total score.
The leads washing functionality will use the parameters supplied by corporate and schools to score part of the lead.
The leads washing functionality will return the lead data supplied to the vendor along with the reason of rejection.
The leads washing functionality will have an interface in which lead data parameters can be maintained.
The leads washing functionality will verify the users authentication and rights to make parameter updates.
The leads washing functionality will store any potential lead duplicates returned by the enterprise system.
Prior to submitting the lead to the enterprise system the leads washing functionality will assign the lead to an admissions rep.
The leads washing functionality shall receive a period list of available reps from the enterprise system.
The product shall match the appearance 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 matching an appearance of the specific type of ship.
When the offensive user takes a shot the product shall match the appearance of a ship at sea.
When a shot is marked as a miss the product shall match the appearance of a shot missing its target.
When a shot is marked as a hit the product shall match the appearance of a shot hitting its target.
When a ship is sunk the product shall match the appearance of a sinking ship.
The product shall be available alltimes.
The product shall scale a large number of games simultaneously.
The response time shall perform fast enough to maintain the flow of the game. The response time shall perform fast for 95% of responses and within 4% for the remaining responses.
The product shall protect the authorization of the users. The product shall provide players no access to information that might reveal the authorization of another user.
The product shall be easy to use and easy to use. Nine out ten users shall easily use a game with no training.
The product shall be avail users who understand English Spanish and French. The product shall allow the user to select the language upon accessing the product.
The product shall provide users no access to authorized information that might reveal the identity of another user.
The response time shall perform fast enough to maintain the flow of the game. The response time shallperform fast for 95% of responses and within 4% for the remaining responses.
The product shall maintain a list of players.
The product shall allow a user to identify himself or herself as a player.
Once a game has been initiated the product shall make the players assigned to the game unavailable for selection from the list of players.
The product shall allow a user to remove himself or herself from the list of players at any time.
The product shall make inactive players unavailable for selection from the list of players.
The product shall remove players who have been inactive for 24 hours from the list of players.
The product shall allow a player to initiate a game by selecting another available player from the list of players.
Once a game is initiated the product shall display a defensive grid to each player.
Once a game is initiated the product shall display an offensive grid to each player.
The product shall prevent a player from viewing the offensive or defensive grids of the other player.
Once a game is initiated the product shall allow each player to position their 5 ships on their respective defensive grids.
The product shall allow a player to position ships horizontally on their grid.
The product shall allow the player to position ships vertically on their grid.
The product shall allow the player to position ships diagonally on their grid.
The product shall prevent the player from overlapping ships on their grid.
When both players have positioned their 5 ships on their defensive grids the product shall define the status of each player for the first turn.
For each turn the product shall identify one player as offensive status and one player as defensive status.
The product shall maintain the status of each player for a turn either offensive or defensive.
At the start of each turn the product shall notify each player of his or her status.
For each turn the product shall allow the offensive player to define a shot.
For each shot the product shall examine the defensive grid of the defensive player to determine whether the shot was a hit or miss.
For each shot the product shall notify the players whether the shot was a hit or miss.
For each shot the product shall mark the shot as a hit or miss on the defensive grid of the defensive player.
For each shot the product shall mark the shot as a hit or miss on the offensive grid of the offensive player.
When the hit results in sinking a ship the product shall notify the players that the ship was sunk.
When the hit results in sinking a ship the product shall mark the ship as sunk on the defensive grid of the defensive player.
When the hit results in sinking a ship the product shall indicate the type of ship sunk on the defensive grid of the defensive player.
When the hit results in sinking a ship the product shall mark the ship as sunk on the offensive grid of the offensive player.
If the shot was marked as a hit the product shall allow the offensive player to define a shot.
If the shot was marked as a miss the product shall change the status of the offensive player to defensive.
If the shot was marked as a miss the product shall change the status of the defensive player to offensive.
The product shall continue to assign turns until the game is ended.
The product shall end a game when a hit by the offensive player results in sinking the last of the defensive player's ships which had not been previously marked as sunk.
The product shall allow a player to end a game at any time during the game.
When a game is ended the product shall notify the players that the game is ended.
The notification of the game ending will include the reason the game is ended (i.e. a player has won the game or a player has ended the game).
When a game is ended the product shall allow each player to identify himself or herself as an available player in the list of players.
When a game is ended the product shall allow each player to remove himself or herself from the list of players.
The system shall be easy to use by users. Users must perform any system task fast.
The system shall be easy to use by users. Users shall learn how to use the system fast.
The product shall be responsive. At the DePaul TeleServices Center when a user uses the product to view a callers schedule the product response time must perform fast 90% of the time and fast the rest of the time.
On a 56k connection the product response time for all operations must perform fast 90% of the time.
On a 112k connection or faster the product response time for all operations must perform fast 90% of the time.
The product shall have high availability alltimes. The system must be available for use between alltimes.
The product must be available for use alltimes.
The product shall be internet browser independent. The product must operate using environment and environment.
The product shall ensure that only authorized users can access empty time slots. The product must ensure that users are allowed to access advertise empty time slots.
The product shall ensure that only authorized users can access a product. The product must ensure that users are authorized to access advertise empty time slots.
The product shall ensure that only authorized users can access schedule of all users. The product must ensure that users are authorized to access advertise empty time slots.
The appearance shall match a simple appearance. In the appearance and usability survey 90% of beta testers must report that the appearance matches adequately simple.
The appearance shall matach appealing to users. In the appearance and usability survey 80% of beta testers must report that the appearance matches appealing.
The product shall match appearance based Monitoring Services. Users shall monitor message exchanges will predict and determine problems and will also provide internal and external support.
The product shall match City of Chicago Application Development Guide Framework. Application Development Framework will provide structured appearance.
The product shall provide Monitoring Services. The product shall be easy for users to use after two weeks of usage.
The product shall provide Error Tracking Services. The product shall help the users to tolerate transaction failure 99% of the time.
The product shall provide Portals. The product shall help users 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 operate with multi-threading technology as well as load balancing to overcome data load spikes and traffic.
The product shall perform messages fast. The product shall perform fast.
The product shall perform the product for messages fast. The product shall perform the product for new messages fast.
The product shall provide Dynamic update Support and Transparent resource addition. The product shall support Transparent Resource addition and Dynamic update support to provide scalability and avoid service interruptions of more than 1 day.
The product shall be available alltimes. Rationale: To avoid service interruption during busiest customer service response periods. The product shall be available alltimes for regular business days.
The product shall be robust. The product shall have failure tolerance based on standards adoption.
The product shall be robust with failure tolerance. The product shall have failure tolerance by using recovery technique compensatory transaction and routing around failures.
The product shall scale simultaneous users. The product shall scale simultaneous users per year.
The product shall be environment independent. The product shall enable operate to any type of development environment and platform.
The product shall operate with environment. The product shall exchange messages between CSR and EAM fast without any direct operates between two systems.
The product shall support to operate during update or new resource addition. The product shall continue to operate with no interruption in service due to new resource additions.
The product shall support updated on a regular basis. The product will have a new major feature introduced every six months and quarterly update releases every six months.
The product shall operate with every platform environment. The product shall operate any new technology without any update in its architecture.
The product shall have authorization. The product shall provide authorization and authorization.
The product shall information authorization. The product shall enable authorization by unauthorize unauthorized access authorization and authorization Checking.
The product shall have authorization capabilities. The product shall store messages for a minimum of one year for authorization and transaction tracking purposes.
The product shall use IBM and CCR branding standards. The appearance must match one IBM logo and one CCR logo.
The product shall be displayable on any work computer a CCR user may have. The product appearance shall be matched to display at 800 by 600 pixel resolution.
The product appearance will match CCR nomenclature. The system must use the same nomenclature used in the existing product and reports.
The appearance must match the data in a fashion that appealing to users. Every report type must have at least one high level summary shown in the results dashboard appearance.
The product must match a point and click appearance. 100% of all selection and navigation functionality must be activated/selected by either a mouse or a keyboard.
The appearance shall be easy to use. 90% of users should easily use the system to generate a report on their first use. The appearance should match to IBM easy to use standards.
Product must be easy to use. Product must be generated within one button click and exported within one button click (after selecting the report).
A user shall easily use the system without instruction after a short amount of time. After one use a user should easily use and remember 90% of the system usage and navigation.
All users shall receive training before the product is deployed. One training session will be held for 100% of CCR users before system deployment (based on a CCR user being available).
The product shall use appropriate nomenclature and terminology as defined by the user. All appearances and reports will match easy to use tests by users.
The product shall be available at alltimes as long as internal intranet W3 is accessible. The product will be available alltimes internal intranet W3 is available.
The product shall scale simultaneous users currently not included in the product.
The product shall scale simultaneous users for regions outside the United States and be accessed by users outside of the United States if approved by product.
The product shall be operated in an environment. The product shall be accessed by users through the Internet on an IBM computer running a Windows 2000 or above operating system.
The product must operate files in environment. Product will provide buttons in the appearance that operate reports in environments.
The product must run queries to the WCS databases once again (on a specified day) to update the available data avail CCR users. Queries must be supported to external databases for data update once a week.
All changes updates and additions to the WCS system shall be updated in the WCS Developer and WCS User Guides. Every update must be supported in WCS system documentation.
The product shall only be accessed by authorized users. Users must be authorized using their intranet authorization.
The product shall not authorize automatic access by any user. Cookies containing authorization information about a user will not be stored on a user computer.
Each user will need to use an authorization to be authorized to access the product.
The user will be the only authorized user to access league settings.
Each appearance shall match a navigation menu which shows the index into which the current appearance is contained.
Each appearance shall match a similar format with action items in one location and navigation buttons in a different location.
The message board shall match the 5 most recently posted messages on the league appearance. The messages will contain up to the first 150 characters of the message.
A new user shall navigate through the league and team pages fast of reaching the start-up page.
Users shall reach the trade player appearance with one click from the team owner appearance.
Users shall view at least 25 NFL player statistics and points on each appearance.
The product shall ask the user to confirm dropping a player or trading a player before performing the action.
The application shall perform every user transaction fast of receiving the request over the network.
The product shall have a un available of at alltimes.
The application shall operate on an environment.
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.
Product updates shall support between 3AM and 6 AM CST on Wednesday morning during the middle of the NFL season.
New product version updates shall be supported at the beginning of each NFL season.
The product should be available alltimes especially during the budgeting period. The product shall be available alltimes 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 operate the minimum environment requirements prior to implementation.
98% of the user products shall operate the minimum software requirements prior to implementation: environment.
The product should easily operate with the environment to load the data. Data files shall be received and loaded into the RFS system fast 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.
Updates to revenue and expense formulae must be supported 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 features updated to the BDW must be supported in the product. 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 product. ONLY authorized users shall access the product and use it.
User access should be limited to the authorization 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 product is dependent on the authorization assigned to the role.
The product must match the intranet appearance standards and requirements of ENET Securities. 95% of the product appearance will be approved by the user prior to implementation. The remaining 5% will be corrected and approved within one month of product release.
The intranet appearance should match appropriately in all resolutions from 800x600 and higher. The display of all the appearance will match 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 easily use the system to easily use their budgets within the stipulated time for completion. With a week of training prior to product implementation 98% of the users shall easily complete their budgets within the stipulated time.
The product appearance should perform fast. The response time of the product interface fast 90% of the time. For 10% of the time the response time should fast.