ࡱ> M sxbjbj== WW)sIlZZZZZZZ@@@ADAy C~G2H2H2H I&3M4gNNyPyPyPyPyPyPy$z |tyZO I IOOty?RZZ2H2Hy?R?R?ROZ2HZ2H0y?RONy?R?RYsZZu2HC P&F7@O^4uu\y0yNu7}OP7}u?RZZZZ [SUN DEVIL COMPUTER] <> Project: Yodeler Software Requirements Specification ( 2000 SUN DEVIL COMPUTER Revision History DateRevisionDescriptionAuthorcreatedate \@ "MM/dd/yy" \* Mergeformat 09/25/011.0Initial VersionSushant Bhatia09/26/011.01Additional ImprovementsSushant Bhatia Table of Contents  TOC \o "1-3" 1. Purpose  GOTOBUTTON _Toc425134229  PAGEREF _Toc425134229 2 1.1. Scope  GOTOBUTTON _Toc425134230  PAGEREF _Toc425134230 2 1.2. Definitions, Acronyms, Abbreviations  GOTOBUTTON _Toc425134231  PAGEREF _Toc425134231 2 1.2.1. Definitions  GOTOBUTTON _Toc425134232  PAGEREF _Toc425134232 2 1.2.2. Acronyms  GOTOBUTTON _Toc425134233  PAGEREF _Toc425134233 2 1.3. References  GOTOBUTTON _Toc425134234  PAGEREF _Toc425134234 2 1.4. Overview  GOTOBUTTON _Toc425134235  PAGEREF _Toc425134235 2 2. Overall Description  GOTOBUTTON _Toc425134236  PAGEREF _Toc425134236 2 2.1. Product Perspective  GOTOBUTTON _Toc425134237  PAGEREF _Toc425134237 2 2.2. Product Architecture  GOTOBUTTON _Toc425134238  PAGEREF _Toc425134238 2 2.3. Product Functionality/Features  GOTOBUTTON _Toc425134239  PAGEREF _Toc425134239 2 2.4. User Characteristics  GOTOBUTTON _Toc425134240  PAGEREF _Toc425134240 2 2.5. Constraints  GOTOBUTTON _Toc425134241  PAGEREF _Toc425134241 2 2.6. Assumptions and Dependencies  GOTOBUTTON _Toc425134242  PAGEREF _Toc425134242 2 3. Specific Requirements  GOTOBUTTON _Toc425134243  PAGEREF _Toc425134243 2 3.1. Functional Requirements  GOTOBUTTON _Toc425134244  PAGEREF _Toc425134244 2 3.2. External Interface Requirements  GOTOBUTTON _Toc425134245  PAGEREF _Toc425134245 2 3.3. Internal Interface Requirements  GOTOBUTTON _Toc425134246  PAGEREF _Toc425134246 2 3.4. Internal Data Requirements  GOTOBUTTON _Toc425134247  PAGEREF _Toc425134247 2 3.5. Design and Implementation Constraints  GOTOBUTTON _Toc425134248  PAGEREF _Toc425134248 2 3.6. Other Requirements  GOTOBUTTON _Toc425134249  PAGEREF _Toc425134249 2 4. Non-Functional Requirements  GOTOBUTTON _Toc425134250  PAGEREF _Toc425134250 2 4.1. Safety Requirements  GOTOBUTTON _Toc425134251  PAGEREF _Toc425134251 2 4.2. Security and Privacy Requirements  GOTOBUTTON _Toc425134252  PAGEREF _Toc425134252 2 4.3. Environmental Requirements  GOTOBUTTON _Toc425134253  PAGEREF _Toc425134253 2 4.4. Computer Resource Requirements  GOTOBUTTON _Toc425134254  PAGEREF _Toc425134254 2 4.4.1. Computer Hardware Requirements  GOTOBUTTON _Toc425134255  PAGEREF _Toc425134255 2 4.4.2. Computer Hardware Resource Utilization Requirements  GOTOBUTTON _Toc425134256  PAGEREF _Toc425134256 2 4.4.3. Computer Software Requirements  GOTOBUTTON _Toc425134257  PAGEREF _Toc425134257 2 4.4.4. Computer Communication Requirements  GOTOBUTTON _Toc425134258  PAGEREF _Toc425134258 2 4.5. Software Quality Factors  GOTOBUTTON _Toc425134259  PAGEREF _Toc425134259 2 4.6. Packaging Requirements  GOTOBUTTON _Toc425134260  PAGEREF _Toc425134260 2 4.7. Precedence and Criticality of Requirements  GOTOBUTTON _Toc425134261  PAGEREF _Toc425134261 2 5. Qualification Provisions  GOTOBUTTON _Toc425134262  PAGEREF _Toc425134262 2 6. Requirements Traceability  GOTOBUTTON _Toc425134263  PAGEREF _Toc425134263 2 6.1. Upward Traceability  GOTOBUTTON _Toc425134264  PAGEREF _Toc425134264 2 6.2. Downward Traceability  GOTOBUTTON _Toc425134265  PAGEREF _Toc425134265 2  Purpose This SRS document highlights the requirements and behavior of the system with respect to the Headquarters department. It will define the in requirements that headquarters and other departments shall adhere to. The intended targets for this document are the departments of our company and the customer. Scope The scope of this document is to cover the Headquarters specifications as well as those placed on other departments that interact with Headquarters. Definitions, Acronyms, Abbreviations The following is a list of commonly used definitions used throughout this document: Definitions Product the overall system deliverable Headquarters Module the headquarters subsection of the product Report document that is sent to a recipient detailing required information Production process the whole process of the company from the time a customer orders a product to the time it is delivered to him. Record any data or document that is relevant to the production process. Process Update an instantaneous update that is sent to HQ as soon as the instigator even is fired. Budget The monies given to a department to allow it to function. It will be set prior to the quarter in which it will take effect. All expenditure related to the department will be in the budget. Account Different from a budget. The departments that have an account will use that account for purchasing/ revenue tallies. Acronyms HQ Headquarters HR Human Resources PU Process Update DR Daily Report References Give a list of documents are referenced within the text of this document: Overview The Headquarters Module will describe the functions and system interfaces of the headquarters section of the product. The goal of the headquarters module is to control and support all departments and their processes. Headquarters will attain reports and updates to ascertain the progression of each department and then provide feedback to any departments on some process. Headquarters main goal is to allow for smooth performance of each department. Overall Description Product Perspective This product will allow users to view the production process from start to finish by the use of reports. Each department will send reports to HQ about its condition with respect to the production process. System Interfaces HQ to Sales Sales to HQ HQ to Warehouse Warehouse to HQ HQ to Manufacture Manufacture to HQ HQ to Purchasing Purchasing to HQ HQ to HR HR to HQ HQ Internals All Departments Warnings HQ Budget allocation Accounts Communications Interface TBD (10/100 Ethernet) Memory Constraints N/A Product Architecture Overview the products architecture, covering the essential components of the system. Product Functionality/Features HQ should be able to allocate and review budgets of each department. It should also be able to handle daily reports from all departments, process update reports which are instantaneous, bring the HQ users attention to warnings generated by departments, give commands to each department and become a central figure in the control of the production process. User Characteristics The users will be divided into two groups. One group will consist of all the department managers and the other group the general employees. Constraints Performance Constraints The HQ database must be able to be store and retrieve reports and other relevant information that is passed to it. It should keep a log of all events that are dependant upon, are requested from and sent to HQ. The average downtime per year should not exceed 30 hours. The upper bound on the user response time should not exceed 5 seconds for any activity that does not involve the database. The database management software chosen by the company will ascertain the database response time. Interface Constraints The HQ module shall use a database to store all information about the production process. The interface shall provide some form of authentication that will determine the user group accessing the system. Assumptions and Dependencies It is assumed that the operating system that will support this software shall be Windows 98 or higher. It is assumed that the software system will be web based and might rely on a browser for some functionality. It is assumed that every document/report shall have a date and time stamp included in it. It is assumed that any report sent by a department to another is almost is dependant upon the communication line chosen. It is assumed that only full orders are shipped to customers and to other departments. It is assumed that all updates given to other departments will reflect when the update should take effect. It is assumed that all orders sent to our suppliers are final and must not be changed. If any discrepancies arise then HQ will inform Purchasing with the help of warnings. Purchasing will then be held responsible to rectify all appropriate problems. It is assumed that open positions in a department are to be filled. When a person is hired it is immediate/next day. It is assumed that when a person is hired they are paid an industry standard. HR is responsible to determine what the industry pay rate is. It is assumed that Sales will inform Warehouse when a replacement computer is needed and whom to ship it to. Sales will also inform Warehouse about the sales, returns and replacements. It is assumed that no raw material will be sold. Raw materials are stocked in the Warehouse. Warehouse will send HQ an invoice received for raw material orders detailing each raw material, its quantity and the invoice number. This invoice number must be the same as the invoice number from the purchasing department. Manufacturing can keep some raw materials at their production site. If they cannot store then they can always return to Warehouse and if Warehouse if full we assume that the raw materials can be stored in another building like the sales building or the purchasing building. Shipping cost for Warehouse will come from its budget. Each department will keep track of its own expenditure from the budget. It is assumed that manufacturing will know how to assemble to product that they are to create. It is assumed that the database for this software system shall be MS Access. Specific Requirements Functional Requirements Compatibility and compliance The system shall be compliant with the OS and browser on which it will run. The system shall meet legal and administrative requirements with respect to national and international laws laid down by the government. It shall also meet the best procedures for record keeping. The system shall be accountable and reliable The system is used in the normal business environment and any document or record created by the system shall be regarded as official. The performance and reliability of the system hardware that support this product shall be regularly tested. The system shall include quality controls that allow for consistent and accurate records. The system shall log all creation and use of records. Records Capture, Maintenance and Usability The system shall allow only authorized personnel to create or capture records. The system shall maintain records that are protected from accidental and intentional damage or deletion. The system shall ensure that all data shall be accessible to the relevant users. The system shall store all similar records into a logically coherent filing system. The system will ensure that records are easily accessed and retrieved in a timely manner. External Interface Requirements Each requirement will be marked with a (PU) or (DR) field next to it. The (PU) field represents those reports that are instantaneous updates. They are sent as son as the instigator even is fired. The (DR) field represents those reports that summarize the departments work. They are generally sent to HQ at the end of each day. (DR) will be found in those sections that pertain to reports from a department to HQ. HQ to Sales New product line (PU) Description: HQ will instruct sales that a new product line is to be sold. HQ will provide the necessary information to sales that will help it sell the product. Parameters -Date to make product available -Product line number -Product name -Product price Delete/Discontinue product line (PU) Description: HQ will inform sales that a current product is to be discontinued from sale. Parameters -Product line number -Date to discontinue product Update product line (PU) Description: A current product can be updated with regards to its name and price. Parameters -Product line number -Changed name -Changed price -Date to make new changes effective/available Sales to HQ Process Update on a sale (PU) Description: For every sale made to a customer a report must be sent to HQ. Parameters Expected -Order ID -Customer ID -Delivery due date per product line -Sale price per product line -Quantity per product line -Total revenue for the order Process Update on a return (PU) Description: For every product returned a report must be sent to HQ. This must be done per product. Parameters Expected -Order ID -Customer ID -Product line number -Refund amount Summary Report (DR) Description: The summary report outlines the happenings of a department since the last summary report. Sales will send to HQ a report for every product line that is being sold, or has been sold. Parameters expected -Quantity sold per product line (i.e. new orders for that day) -Price of each product sold per product line -Price for the total product sale on that day per product line -Total revenue for that day -All products returned to sales per product line and their quantities -Total reimbursement for the returned products per product line Requests to Fire employee Description: A department can request approval from HQ to fire an employee. The only person able to make such a decision is the manager. The parameters expected from the department are listed below. Once this is approved, the department making the request is notified and then HQ will inform HR to fire the person. Parameters expected -Department name -Manager ID -Employee ID (employee to be fired) -Reason for termination HQ to Warehouse New product line (PU) Description: The company will instruct the warehouse to the creation of a new product line. Parameters -Product ID -Product Name -Highest stock quantity -Ideal stock quantity -Minimum stock quantity Update a product line (PU) Description: Update the product line that already exists Parameters -Product ID -Changed product name -Highest stock quantity -Ideal stock quantity -Minimum stock quantity -Date change will take effect New raw material line (PU) Description: A new raw material line has to be stocked in warehouse. Parameters -Raw material number -Raw material name -Highest stock quantity -Ideal stock quantity -Minimum stock quantity -Date change will take effect Update raw material line (PU) Description: Update the relevant information of a raw material line that already exists in the warehouse records. Parameters -Raw material number -Raw material name -Highest stock quantity -Ideal stock quantity -Minimum stock quantity -Date change will take effect Warehouse to HQ Finished product from manufacturing (PU) Description: For every received product from manufacturing, a report is expected at HQ. Parameters Expected -Product line number -Quantity -Current stock (comprised of the old quantity in stock plus the new product line quantity) Returned product (PU) Description: Foe every received from a customer (directly to warehouse), a report is expected at HQ. (Warehouse should then send sales the Customer ID, data of purchase and order ID so that sales may refund the customer.) Parameters Expected -Customer ID -Order ID -Product line number -Quantity -Current stock Raw Material arrival from supplier (PU) Description: For every received raw material order from the supplier, a report is expected at HQ Parameters Expected -Invoice number -Quantity per raw material type Shipment to customer (PU) Description: For every shipment to a customer a report is expected at HQ. Parameters expected -Customer ID -Tracking number -Date originally intended to ship (date promised to customer) -Actual shipping date Raw material sent to manufacturing (PU) Description: For raw material sent to manufacturing, a report is expected at HQ. Parameters expected -Raw material number -Quantity Request to Manufacturing for product (PU) Description: For all orders to manufacturing, a report is expected at HQ. Parameters expected -Product line number -Quantity -Date expected Summary Report (DR) Description: For every product line/ raw material that is being stocked in warehouse or has been stocked at some point in time, HQ needs the parameters listed below. Parameters -Quantity in stock at the beginning of the day -Quantity in stock at the end of the day -Number of each product line requested from manufacturing for that day (which would have actually been ordered at some earlier date) -Number of received products from manufacturing per product line for that day -Number of orders actually shipped to customer -Number of faulty product per product line -Number of products returned by the customer directly to warehouse per product line. -Capacity of the warehouse per product line (i.e. the number of each product line that we can store) -Amount of received raw materials per raw material type. Requests to Fire employee Description: A department can request approval from HQ to fire an employee. The only person able to make such a decision is the manager. The parameters expected from the department are listed below. Once this is approved, the department making the request is notified and then HQ will inform HR to fire the person. Parameters expected -Department name -Manager ID -Employee ID (employee to be fired) -Reason for termination HQ to Manufacturing New product line (PU) Description: Manufacturing is informed of a new product line that must be manufactured. Parameters -Product ID -Product Name -Highest quantity production per day -Ideal quantity production per day -Minimum quantity production per day -Raw material ID -Raw material name -Raw material quantity to use in manufacturing Update product line (PU) Description: Update the relevant information of a product line Parameters -Product ID -Product name -Highest quantity production per day -Ideal quantity production per day -Minimum quantity production per day -Raw material ID -Raw material name -Raw material quantity to use in manufacturing -Date update should take effect Stop production of a product line (PU) Description: Stop production of a product line based on the date or count. (The date to stop production or the count of the number of produced products to stop on. Manufacturing keeps a record of the number of each product line that they produce.) Parameters -Product ID -Date/ Count to stop production on. Manufacturing to HQ Order to purchasing about raw materials (PU) Description: For an order to purchasing regarding the raw materials and quantities required, HQ should receive a report. Parameters expected -Raw material ID -Raw material quantity -Date expected Raw materials received from warehouse (PU) Description: For raw material received from warehouse, a report is expected at HQ. Parameters expected -Raw material ID -Raw material quantity Orders for products from Warehouse (PU) Description: For each order from warehouse that arrives at manufacturing, a report is expected at HQ. Parameters expected -Product line number -Quantity to manufacture Summary Report (DR) Description: For every product line HQ needs a daily report on the parameters listed below. Parameters expected -Number products produced per product line -Number requested per product line from warehouse -Number sent to warehouse per product line -Number produced but not forwarded to warehouse per product line -Raw material count for each raw material type at the beginning of the day -Raw material count for each raw material type at the end of the day -Number of raw material types used in production delimited by the raw material type -Requested orders to warehouse delimiting the raw material type and the quantity -Number of raw material type received from warehouse delimited by the raw material type -Predicted product line production for the next MONTH/QUARTER/YEAR Requests to Fire employee Description: A department can request approval from HQ to fire an employee. The only person able to make such a decision is the manager. The parameters expected from the department are listed below. Once this is approved, the department making the request is notified and then HQ will inform HR to fire the person. Parameters expected -Department name -Manager ID -Employee ID (employee to be fired) -Reason for termination HQ to Purchasing New raw material to order (PU) Description: The new raw material that purchasing should order. Parameters -Raw material ID -Raw material name -Maximum quota to order per month -Ideal quota to order per month -Minimum quota to order per month -Maximum price per unit to buy raw material -Date to make first shipment available at warehouse Update raw material order (PU) Description: Update the relevant information about the raw materials to order. Parameters -Raw material ID -Raw material name -Maximum quota to order per month -Ideal quota to order per month -Minimum quota to order per month -Maximum price per unit to buy raw material -Date changes will take effect on Stop purchase of raw material (PU) Description: Stop purchases of raw material. Parameters -Raw material ID -Date/ Count to stop purchasing on. (see manufacturing 3.2.5.3) Purchasing to HQ Order to supplier must result in a report to HQ (PU) Description: For each order made to the supplier the report to HQ should detail the parameters below. (Also consult purchasing account for any clarifications) Parameters expected -Raw material ID -Invoice number -Quantity per raw material -Total cost for order Summary Report (DR) Description: For every raw material order, HQ needs a report with the parameters below. Parameters expected -Amount ordered for that day per raw material type -Price per unit per raw material type -Amount expected today per raw material type Requests to Fire employee Description: A department can request approval from HQ to fire an employee. The only person able to make such a decision is the manager. The parameters expected from the department are listed below. Once this is approved, the department making the request is notified and then HQ will inform HR to fire the person. Parameters expected -Department name -Manager ID -Employee ID (employee to be fired) -Reason for termination HQ to HR Fire person (PU) Description: Fire a person from the company. We assume here that HR will then inform the employee by sending then a notification. We also assume that on average a two-week termination notice will be given. In HQ only the top level mangers can fire an employee in HQ. Parameters -Employee ID -Date to terminate on Layoff a certain number of employees from a department (PU) Description: Layoff a certain number of employees from a department. The choice of who to fire is left to HR. However, they are given productivity reports on the performance of all employees in each department. The persons with the lowest productivity will most likely be fired. Parameters -Department name Relocate a certain number of employees (PU) Description: Relocate employees from one department to where they are required. (HR is given the power to choose who will be relocated. They may use the employee documents that were recorded when the employee was hired.) Parameters -Department to get employees from -Department to move employees to Increase the number of employees in a department (PU) Description: Increase the number of employees of a department to a certain number. Parameters -Department name -Number of employees in that department after hiring Increase salary of a specified department (PU) Description: Increase the salary of a specified department based on performance. HR is given the power to evaluate performance and choose who will get a pay raise. Parameters -Department name HR to HQ Summary Report (DR) Description: HR needs to send HQ the following information. Parameters expected -New staff hired per department -Number of staff fired per department -Number of staff that quit per department -End of day total number of employees per department -Open positions per department Requests to Fire employee Description: A department can request approval from HQ to fire an employee. The only person able to make such a decision is the manager. The parameters expected from the department are listed below. Once this is approved, the department making the request is notified and then HR will fire the person. Parameters expected -Department name -Manager ID -Employee ID (employee to be fired) -Reason for termination All Department Warnings Send Warning Description: Warnings are messages sent by the user of the system to other departments that they interact with about some situation that could potentially cause problems. The warnings are a way for a department to bring the other departments attention to very important developments in the production process. Parameters Expected -Subject (Who the message is from and the department name) -Body (an explanation of the warning) HQ Budget Allocation HQ to All Departments (self included) Allocate Budget Description: HQ will assign to every department a budget prior to the quarter in which it will take effect. Parameters Dollar amount Quarter/Date on which it will take effect All Departments to HQ (increase budget request) Increase Budget Description: All departments are allowed to request a budget increase from HQ. Parameters expected Dollar amount to increase budget to Reason HQ Response to budget increase Approve Budget Description: HQ upon review will accept the new changes to the budget for the department requesting it. Parameters Dollar amount of new budget Reject Budget Description: HQ upon review will reject the budget from the department requesting a budget increase. Parameters Dollar amount of budget Reason for Rejection All Departments to HQ end of quarter report End of quarter budget report Description: At the end of each quarter, HQ expects a budget update that details the budget amount unspent by the department. Parameters expected Dollar amount of budget allocated Dollar amount of budget unspent HQ to all Departments Request report Description: HQ can request a budget report for a previously finished quarter. Once the report is received, the user will choose when to view it. Parameters Date /Quarter of report needed Account Sales Account Description: Sales account is a tally of the revenue generated for the company from sales to the customers. When sales department sends a sale report (PU) to HQ, HQ will increment the sale account to reflect the sale made. In the event of a product being returned, sales will inform HQ about it and if a replacement product is shipped, no changes have to be made. If a refund is requested then HQ will debit the amount from the sales account. Purchasing Account Description: The purchasing account is a cost price account setup for the purpose of tracking the cost of raw materials ordered. When purchasing purchases raw materials, the will inform HQ and HQ will increment the account to reflect the cost of raw materials so far. We assume that no raw materials have to be returned. HR Salaries Account Description: HR will inform HQ about the amount paid in salaries whenever they make a payment. HQ will add that amount to the salaries account to get the total salaries expenditure. HQ Internals Account Tallies Internal Interface Requirements 3.3.1 The interface shall be easy to use. It shall request users to log into the system for security. Internal Data Requirements 3.4.1 The internal data should be stored in the database. When quarter is completed all relevant information contained in the system will be backed up into the database. Non-Functional Requirements Safety Requirements Security and Privacy Requirements 4.2.1 The system shall provide security and privacy for managerial users as opposed to general employee users. Environmental Requirements Computer Resource Requirements Computer Hardware Requirements 4.2.1.1 Hardware shall consist of Pentium 3 or higher classed PCs Computer Hardware Resource Utilization Requirements Computer Software Requirements Computer Communication Requirements Software Quality Factors Packaging Requirements Precedence and Criticality of Requirements Qualification Provisions This section defines a set of qualification methods. For each requirement in Section 3, specify the methods to be used to ensure that the requirement has been met. A table may be used to present this information, or each requirement may be annotated with the method(s) to be used. Qualification methods may include: Demonstration, Test, Analysis, Inspection, Special. Requirements Traceability Upward Traceability Traceability from each requirement in this specification to the system or subsystem requirements it addresses. Downward Traceability Traceability from each system or subsystem requirement to the requirements contained in this specification Product Requirements Document ref ProjectName \* Mergeformat  Project: Yodeler  Page page i  PAGE i PAGE ii  PAGE iii Software Requirements Specification Software Requirement Specification Date savedate \* Mergeformat 9/26/2001 3:14 PMRev revnum \* Mergeformat 59Page page 1  *+.23_cdlmxy"#'(,-1267;<@AEFJKOPTUYZ^atⰥB*mHnHphujB*Uph >*B*ph5>*B*ph 5B*ph jB*ph56B*CJph B*ph j5B*mH phsH B*mH phsH @/012LM^_dmy%$If$$1$##P )wrxT`LLLLTLL%$1$If$$Ifl\!8  (04 laLFFFFL%$If$$Ifl\!8  (04 la%$1$IfN$$Ifl\!8  (04 la%$If !"#$NN$$Ifl\!8  (04 la%$If$%&'()*+,N$$Ifl\!8  (04 la%$If,-./01234TNNNNTNN%$If$$Ifl\!8  (04 la456789:;<NN$$Ifl\!8  (04 la%$If<=>?@ABCDN$$Ifl\!8  (04 la%$IfDEFGHIJKLNN$$Ifl\!8  (04 la%$IfLMNOPQRSTN$$Ifl\!8  (04 la%$IfTUVWXYZ[\TNNNNTNN%$If$$Ifl\!8  (04 la\]^_at oNLJHFF$$Ifl\!8  (04 la%$Iftu  67RSjkln     0 1 H I J L [ \ w x   1 2 3 5 P Q l m jUmHnHu mHnHu5;j5;UYo M 6 9 0 B PZoBR    4 5 6 8 J K f g ~    + , - / M N i j % & = > ? A b c ~  34KLMOopjUmHnHu mHnHu^!"=>UVWYz{   67RSjkln  %&=>?Amn56MNOQ   -.jUmHnHu mHnHu^Rf DJXdN.IJabce    ) "",,--l//O1P13332314V445555566779:;;;;<<}==t>>????>*CJ 5>*CJ\CJ *5\mH sH 5;j5;UjUmHnHu mHnHuO>G  3+;K]o)-p^p & F & F-.C 1 "";###0$$$p%%2&,''.(($*6+ & F & Fp^p & F6+m++,b,x,,,,--p..6/l///O000O1Q1q1333 & F ^& & F  & F  & F  & F3233334"414V444445X5c5x55555596M6W6d666 & F ^ & F  & F 6666a7u7777778889F9b999:>;R;c;o;;;;; & F  & F  & F ^;-<8<D<R<j<<<<<<==1=G=_=}=====>(>>>V>t>>? & F ^ & F ??$?7?O?e?}????-@A@V@`@@@AAAAAAB0BBBBB & F  & F ^ & F ?@@B0BBBCCkDD!E4E^HxH J!J4J5JKJKKL M?NRNSNNDOoOO&PPPSTUUUUUUW1WaXX YYSYXZkZ^[x[ ]!])]*];]u^^_`;aqabEbc cc"c6dPdeefffggghhhhhiiiiDjQjjk5\mH sH >*CJ 5>*CJ\5\\BB9CMCZCkCCCC8DLDaDkDDDDEE!E5EEEF>FFG@GkG^ & F  & F kGG%H^HxHIIII J!J5JKJJJJJJK5KFKYKKKKKKL & F  & F  & F ^L*LMLrLLLLL MNNN?NSNNN OO5ODOoOOOOO&PPP & F  & F  & F ^PPPP>QRQ}QQQRfRRRPSSSTAUUUfUrUUUUUUV & F ^` & F  & F ^V*V;VNVpVVVVW1WWWWWWWX?XaXXXXX YYSYYZ & F  & F ^ & F ZZ'ZBZXZlZZZ [1[^[x[\\\\ ]!]*];]G^R^_^u^^__ & F ^` & F  & F ^__```a;aqaaaabEbbbcc"c^crccccd6dPdee & F  & F  & F ^eeeeeffGg[gggggghuhhhhhhhHi\ii^ & F  & F  & F  & F ^`^iiiij(jDjRjjjjjk8kkkk l"l1llllllmn & F p^p & F  & F  & F ^kk8k l!l"l1llllmnnp'ppppppq#qqqrresmsssHwIwhwiw{w|wwwwwwwwwwwwwwwwwwwwwwwwwwwwxx x x&x'x8x9x:x>x?xVxWxYxZx[x`xaxfxgxhx mHnHu50JmHnHu0J j0JU jU>*CJ 5>*CJ\5\Snnp(pppppqqqIrJrKrgr{rr s'sFsessssp^p  & F0^`0^ & F  & F  & F st8tOtzttvv!v5vvv%w&w'w(w)w}w~wwwwwwwwww&`wwwwwwxxx x:x>x[x`xkxlxmxP$Ifhxixsx jUmxnxoxpxqxrxsxmkkiii$$Ifl\#04 lal6 0 0000*P/ =!"#$%80.00 &PP/ =!"#$%81 000 &PP/ =!"#$%8.00 &PP/ =!"#$%8+ 0&PP/ =!"#$%8+ 0&PP/ =!"#$%8+ 0&PP/ =!"#$%8+ 0&PP/ =!"#$%8' i0@0 Normal_HmH sH tH b@b Heading 12$$ & F<$d %d &d 'd @& 5CJ$KHD@D Heading 2$ & F<@&5CJD@D Heading 3$ & F<@&5CJ@@ Heading 4$ & F<@&5<< Heading 5 & F<@&5LL Heading 6 & F<@&6CJOJQJkHDD Heading 7 & F<@& OJQJkHHH Heading 8 & F<@&6OJQJkHL L Heading 9 & F<@&6CJOJQJkH<A@< Default Paragraph Font&)@& Page NumberF>@F Title$$$ a$5CJ$OJQJkH0!0 Paragraph4 @ ^@ 2O"2 Paragraph1 $Pa$,!2, Style2  p@ 0B0 Paragraph5 ^HORH Table of Contents$$ha$CJ$4@4 TOC 1xx ! 5;2@2 TOC 2 ! ^:2@2 TOC 3 ! ^60O!0 Paragraph2 ^0O!0 Paragraph3 p^p4@4 Header  !5CJ4 @4 Footer  !5CJ22 TOC 4 ! X^XCJ22 TOC 5 !  ^ CJ22 TOC 6 ! ^CJ22 TOC 7 ! ^CJ22 TOC 8! ! x^xCJ22 TOC 9" ! @^@CJFJ@2F Subtitle#$<1$a$6CJ$OJQJkH<OB< RevHistory$$$1$a$CJ$DORD Table Text %((1$_HmH sH tH <C@b< Body Text Indent &p^pMa b(Knrst 8 h    % R /012LM^_dmy !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_at oM690B P Z  o B Rf DJXdN>G  3+;K]o)-.C1;0 p!!2",##.$$$&6'm''(b(x(((())p**6+l+++O,,,O-Q-q-///2////0"010V000001X1c1x11111192M2W2d222222a3u3333334445F5b5556>7R7c7o77777-888D8R8j8888889919G9_9}99999:(:>:V:t::;;$;7;O;e;};;;;-<A<V<`<<<======>0>>>>>>9?M?Z?k????8@L@a@k@@@@AA!A5AAAB>BBC@CkCC%D^DxDEEEE F!F5FKFFFFFFG5GFGYGGGGGGH*HMHrHHHHH IJJJ?JSJJJ KK5KDKoKKKKK&LLLLLL>MRM}MMMNfNNNPOOOPAQUQfQrQQQQQQR*R;RNRpRRRRS1SSSSSSST?TaTTTTT UUSUUVV'VBVXVlVVV W1W^WxWXXXX Y!Y*Y;YGZRZ_ZuZZ[[[\\\];]q]]]]^E^^^__"_^_r____`6`P`aaaaaabbGc[ccccccdudddddddHe\eeeeef(fDfRfffffg8gggg h"h1hhhhhhijjl(lllllmmmInJnKngn{nn o'oFoeoooop8pOpzpprr!r5rrr%s&s's(s)ssssssssttt t:t>t[t`tktltmtntotpttt0000#0#0#0#0#0`$0$00%0%0%0%00%0%0%0%00%0%0%0%00%0%0%0%00%0%0%0%00%0%0%0%00%0%0%0%00%0%0%0%00%0%0%0%00%0%0%0%00%0%0%0%00%0%0%0%00%0%0%0%00%0%0%0%00%0%0%0%00%0%0%0%00%0%0%0%00%0%0%0%00%0%0%0%00@000000000000000000000000000000000000000@0 00 00D 00( 00X0X0X0X0X0X0X0X( 00000 00 00>`0> 0 0  0 0 0 0 0 0 0 0 0 0 0 0  0  0  0  0  00 000 0  0. 0  0 0  0 0   00 0 0 0 0   0 0 0 0 0 0 0 0 0 0  0  0  0  0  0@0 0 0b(b( 0x( 0(x( 0(x( 0x( 0)x( 0)x( 0)x( 0)x( 0x( &0l+x( 0l+x( 0l+x( 0l+x( 0l+x(0x( 0b(b(0Q-0Q- 0Q- 0/Q- 0/Q- 0/Q-0Q-0Q-0Q-0Q- 0/Q- 010Q- 010Q-0Q-0Q- 0/Q- 00Q- 00Q-0Q-0Q-0Q-0Q- 0Q- 01Q- 01Q- 01Q-0Q-0Q-0Q-0Q-0Q-0Q- 01Q- 02Q- 02Q-0Q-0Q-0Q-0Q- 01Q- 03Q- 03Q-0Q-0Q-0Q-0Q-0Q-0Q- 01Q- 05Q- 05Q-0Q-0Q-0Q-0Q- 0Q- 07Q- 07Q- 07Q-0Q-0Q-0Q-0Q-0Q- 07Q- 08Q- 08Q-0Q-0Q-0Q-0Q-0Q-0Q- 07Q- 0}9Q- 0}9Q-0Q-0Q-0Q-0Q-0Q-0Q- 07Q- 0t:Q- 0t:Q-0Q-0Q-0Q-0Q-0Q-0Q- 0Q- 0;Q- 0;Q- 0;Q-0Q-0Q-0Q- 0;Q- 0<Q- 0<Q-0Q-0Q-0Q-0Q-0Q- 0;Q- 0>Q- 0>Q-0Q-0Q- 0;Q- 0>Q- 0>Q-0Q-0Q-0Q-0Q- 0;Q- 0?Q- 0?Q-0Q-0Q- 0;Q- 0k@Q- 0k@Q-0Q-0Q-0Q- 0;Q- 0!AQ- 0!AQ-0Q-0Q-0Q-0Q-0Q-0Q-0Q-0Q-0Q- 0;Q- 0^DQ- 0^DQ-@0Q-@0Q-@0Q-0Q- 0Q- 0!FQ- 05FQ- 05FQ-0Q-0Q-0Q-0Q-0Q-0Q-0Q-0Q- 0!FQ- 0GQ- 0GQ-0Q-0Q-0Q-0Q-0Q-0Q-0Q-0Q-0Q- 0!FQ- 0HQ- 0HQ-0Q-0Q- 0Q- 0?JQ- 0SJQ- 0SJQ-0Q-0Q-0Q- 0?JQ- 0DKQ- 0DKQ-0Q-0Q- 0?JQ- 0KQ- 0KQ-0Q-0Q- 0?JQ- 0LQ- 0LQ-0Q-0Q-0Q-0Q-0Q-0Q-0Q-0Q-0Q-0Q- 0?JQ- 0OQ- 0OQ-@0Q-@0Q-@0Q-0Q-0Q- 0Q- 0QQ- 0QQ- 0QQ-0Q-0Q-0Q-0Q-0Q-0Q-0Q- 0QQ- 0SQ- 0SQ-0Q-0Q-0Q-0Q-0Q-0Q-0Q- 0QQ- 0aTQ- 0aTQ-0Q-0Q- 0Q- 0 UQ- 0UQ- 0UQ-0Q-0Q-0Q-0Q- 0 UQ- 0XVQ- 0XVQ-0Q-0Q-0Q- 0 UQ- 0^WQ- 0^WQ-@0Q-@0Q-@0Q-0Q- 0Q- 0!YQ- 0*YQ- 0*YQ-0Q-0Q- 0!YQ- 0uZQ- 0uZQ-0Q- 0!YQ- 0[Q- 0[Q-0Q-0Q- 0!YQ- 0;]Q- 0;]Q-0Q-0Q- 0!YQ- 0^Q- 0^Q-0Q- 0 Q- 0_Q- 0_Q- 0_Q-0Q-0Q-0Q-0Q-0Q- 0_Q- 06`Q- 06`Q-@0Q-@0Q-@0Q-0Q- 0 Q- 0aQ- 0bQ- 0bQ-0Q-0Q-0Q- 0 Q- 0cQ- 0cQ- 0cQ- 0cQ-0Q-0Q- 0cQ- 0cQ- 0dQ- 0dQ- 0dQ-0Q-0Q- 0cQ- 0eQ- 0eQ- 0eQ-0Q- 0eQ- 0DfQ- 0DfQ-0Q-0Q- 0cQ- 0fQ- 0gQ- 0gQ-0Q-0Q- 0cQ- 0 hQ- 0"hQ- 0"hQ-0Q-0Q- 0 Q- 0hQ- 0hQ- 0hQ- 0jQ- 0hQ- 0lQ- 0 Q- 0lQ-0Q- 0b(b(0l 0b(b(0m0b(`0In 0 0KnKn 0KnKn0{n 0KnKn 0KnKn( 0'o'o0Fo( 0'o'o( 0'o'o( 0'o'o 0KnKn 0KnKn 0KnKn 00zp`0zp 0 0rr0!r 0rr0[0[0[0[0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0@0 0UUffrrttHHHHHHHHHHHHHHHHHHHHHHHHHHHKt .?khxsx>MOPRZdh$,4<DLT\oR-6+36;?BkGLPVZ_einswmxsx?ABCDEFGHIJKLNQSTUVWXY[\]^_`abcefgirx@t  6Rjlm0HJK[w134Pl467Jf~+-.Mi % = ? @ b ~  3 K M N o ! = U W X z  6 R j l m % = ? @ m 5MOP  -Iacd   st 2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@2%@?R[acfmot{~-07=?K!!!!!8@0(  B S  ?& CompanyName ProjectName _Toc425134229 _Toc425134230 _Toc425134231 _Toc425134232 _Toc425134233 _Toc425134234 _Toc425134235 _Toc425134236 _Toc425134237 _Toc425134238 _Toc425134239 _Toc425134240 _Toc425134241 _Toc425134242 _Toc425134243 _Toc425134244 _Toc425134245 _Toc425134246 _Toc425134247 _Toc425134250 _Toc425134251 _Toc425134252 _Toc425134253 _Toc425134254 _Toc425134255 _Toc425134256 _Toc425134257 _Toc425134258 _Toc425134259 _Toc425134260 _Toc425134261 _Toc425134262 _Toc425134263 _Toc425134264 _Toc425134265 _Ref404131883DX> .b(x(Q-lmKngn{n o'oFoooop8pOpzpr!rrittt  !"#$%MIcF2B0w((p-mmfnznn&oEodooop7pNpypp r4rrnttt* r r(r4r5rArrrrr)sqtttC--77TTZ!Zqr)sqttt3333332MbB m )-.C((l++//10V00111117788;;??GGKDK Y!YGZRZ[[^_abccuddHe\eeeDfQfhhhijjlllllmmm o'o)s|sss t:t>t[tqtttnewuserFC:\Documents and Settings\cse46104\Desktop\Project\HEADQUARTER SRS.SRSnewuserFC:\Documents and Settings\cse46104\Desktop\Project\HEADQUARTER SRS.SRSnewuserFC:\Documents and Settings\cse46104\Desktop\Project\HEADQUARTER SRS.SRSnewuserFC:\Documents and Settings\cse46104\Desktop\Project\HEADQUARTER SRS.SRSnewuserFC:\Documents and Settings\cse46104\Desktop\Project\HEADQUARTER SRS.SRSnewuserkC:\Documents and Settings\cse46104\Application Data\Microsoft\Word\AutoRecovery save of HEADQUARTER SRS.asdnewuserkC:\Documents and Settings\cse46104\Application Data\Microsoft\Word\AutoRecovery save of HEADQUARTER SRS.asdnewuserkC:\Documents and Settings\cse46104\Application Data\Microsoft\Word\AutoRecovery save of HEADQUARTER SRS.asdnewuserkC:\Documents and Settings\cse46104\Application Data\Microsoft\Word\AutoRecovery save of HEADQUARTER SRS.asdnewuserkC:\Documents and Settings\cse46104\Application Data\Microsoft\Word\AutoRecovery save of HEADQUARTER SRS.asd  k%`ՒItʪO!R NX8-8ThHt,||N6']?D@0^`0.@0^`0..@p0^p`0...@@ 0^@ `0....@ 0^`0 .....@ 0^`0 ......@ 0^`0.......@ 0^`0........@ P0^P`0.........ss^s`5o(YY^Y`5o(.? ? ^? `5o(..%%^%`5o(...   ^ `5o( .... ^`5o( ..... ^`5o( ...... `^``5o(....... `^``5o(........`^``5o(p`p^p``5o(.@ `@ ^@ ``5o(..`^``5o(... `^``5o( .... `^``5o( ..... `^``5o( ...... P`P^P``5o(.......  ` ^ ``5o(........88^8`)^`.pp^p`.@ @ ^@ `.^`.^`.^`.^`.PP^P`.0^`05o(0^`05o(.p0p^p`05o(..@ 0@ ^@ `05o(... 0^`05o( .... HH^H`5o( ..... ^`5o( ...... P`P^P``5o(.......  ` ^ ``5o(........88^8`)^`.pp^p`.@ @ ^@ `.^`.^`.^`.^`.PP^P`.`^``o(p`p^p``o(.@ `@ ^@ ``o(..`^``o(... `^``o( .... `^``o( ..... `^``o( ...... P`P^P``o(.......  ` ^ ``o(........88^8`)^`.pp^p`.@ @ ^@ `.^`.^`.^`.^`.PP^P`.`^``o(p`p^p``o(.@ `@ ^@ ``o(..`^``o(... `^``o( .... `^``o( ..... `^``o( ...... P`P^P``o(.......  ` ^ ``o(........`^``o(p`p^p``o(.@ `@ ^@ ``o(..`^``o(... `^``o( .... `^``o( ..... `^``o( ...... P`P^P``o(.......  ` ^ ``o(........ k%8-8T]?O!Ht\2 It]2  NL]2 ||`70 70 U&        yn                ^_dmy !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_(s)ssst:t[tmtntttcanClose]2 @  t  st@UnknownGz Times New Roman5Symbol3& z Arial"AhYFYfJ'^0!20dtr 2Q#Software Requirements Specification1.0newusernewuserOh+'0 , H T ` lx$Software Requirements Specification1.0newuserewuewuNormalnewuser74uMicrosoft Word 9.0t@6)@@OF@ʤF^՜.+,08 px  Rational Software Corporationt0t $Software Requirements Specification Title  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijlmnopqrstuvwxyz{|}~Root Entry F1F1Tablek7}WordDocumentSummaryInformation(DocumentSummaryInformation8CompObjjObjectPool1F1F  FMicrosoft Word Document MSWordDocWord.Document.89q