NOTE: This template is shareware downloaded from www.processimpact.com.

All shareware payments are donated to the Norm Kerth Benefit Fund to help a consultant who is disabled with a brain injury. Please visit http://www.processimpact.com/norm_kerth.html to make a shareware payment ($10 suggested). Thank you!

Software Requirements Specification
For

<EMAAN ERP>
Version 1.0 approved

Prepared by <author>

<organization>

<date created>

eLearning versions of several popular Process Impact training seminars are available at www.processimpact.com/elearning.shtml, including “In Search of Excellent Requirements,” “Exploring User Requirements with Use Cases,” “Writing High-Quality Requirements,” “Software Inspections and Peer Reviews,” and “Project Management Best Practices”. Single-user and corporate-wide site licenses are both available.

Copyright © 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.

SoftwareRequirements Specification for <EMAAN ERP>

Page ii

Table of Contents
Table of Contents .......................................................................................................................... ii Revision History ............................................................................................................................ ii 1. Introduction ..............................................................................................................................1
1.1 1.2 1.3 1.4 1.5 2.1 2.2 2.3 2.4 2.5 2.6 2.7 Purpose............................................................................................................................................. 1 Document Conventions .................................................................................................................... 1 Intended Audience and Reading Suggestions .................................................................................. 2 Project Scope ................................................................................................................................... 2 References ........................................................................................................................................ 4 Product Perspective.......................................................................................................................... 4 Product Features .............................................................................................................................. 5 User Classes and Characteristics ..................................................................................................... 6 Operating Environment .................................................................................................................... 6 Design and Implementation Constraints .......................................................................................... 6 User Documentation ........................................................................................................................ 6 Assumptions and Dependencies ...................................................................................................... 7

2. Overall Description ..................................................................................................................4

3. System Features .......................................................................................................................7
3.1 System Feature 1 .............................................................................Error! Bookmark not defined. 3.2 System Feature 2 (and so on) ..........................................................Error! Bookmark not defined. 4.1 4.2 4.3 4.4 5.1 5.2 5.3 5.4

4. External Interface Requirements ...........................................................................................9
User Interfaces ............................................................................................................................... 19 Hardware Interfaces ....................................................................................................................... 19 Software Interfaces ........................................................................................................................ 19 Communications Interfaces ........................................................................................................... 20 Performance Requirements ............................................................................................................ 20 Safety Requirements ...................................................................................................................... 20 Security Requirements ................................................................................................................... 20 Software Quality Attributes ........................................................................................................... 20

5. Other Nonfunctional Requirements .....................................................................................20

6. Other Requirements .................................................................. Error! Bookmark not defined. Appendix A: Glossary..................................................................................................................21 Appendix B: Analysis Models .....................................................................................................21 Appendix C: Issues List ...............................................................................................................21

Revision History
Name Date Reason For Changes Version

It Reduce the response time due to the effective transfer of Information. 3. 5.SoftwareRequirements Specification for <EMAAN ERP> Page 1 1.Dependency o UI.Security Requirements . It helps in quick and vital decision making in an organization. All Business processes and sub-processes are integrated into a single unified system. o BR. An ERP system allows you to streamline most of your functions performed by your organization as a whole. 2. efficiency.User Documentation o AS – Assumption o DE. An ERP provides you Productivity.Software Interface o CI-Communication Interface o PE. 1.1 Purpose The Purpose of an EMAAN ERP system comes from some of its advantages below: 1. Introduction 1. The document follows the following convention while it is being written. 4.2 Document Conventions This SRS is developed by adapting templates derived from IEEE Standard 830-1998B which is highly recommended by IEEE to Practice software requirement specification document. effectiveness in Business plans.User Interface o HI – Hardware Interface o SI.Business Rule o FE – Feature o UC – Use Case o CO – Design and Implementation Constraint o UD. ocument will be incorporated by the System.Performance Requirements o SA.Safety Requirements o SE.

―once an invoice is created its content should never be modified‖. External requirement. Based on Great Abyssinia P. 2. and . The SRS is developed to create a common understanding between all stakeholders.SoftwareRequirements Specification for <EMAAN ERP> Page 2 1. For example. Non functional requirements.C business process the following modules of EMAAN ERP are found mandatory for facilitating the Enterprise Activities. For developer we suggest to start reading from overall description section. GRV. 3. The module handles the purchase order. 2. Non functional requirements.4 Project Scope The scope of this project is limited to the following modules of the EMAAN ERP Subsystems. 2.3 Intended Audience and Reading Suggestions This document is divided into three portions in a way that it can briefly state what will be implemented while the software is developed. 3. This module is also responsible for creating sales related vouchers and support all required operations on those vouchers. Start from reading purpose. Inventory Subsystem This subsystem will have two major modules – Supplier Management Module (SMM) and Inventory Management Module (IMM). It is also responsible for the generation of reports. System features short overview. This module is responsible for keeping rules related with sales transactions and make sure that the rules are applied properly. SMM is responsible for maintaining supplier information and handles reports that are related to suppliers or vendors. For user we will provide a manual along with our software which describe user how to use our software. 4. The enterprise needs the following subsystem modules 1.  Developers& Tester 1. 1. scope and product features.L.  Users 1. External requirement.  Marketing staff 1. Sales management module (SMM) is responsible to keep track of information related with sales persons and sales transaction. Sales Subsystem The sales subsystem will have two major modules.

Store Return. It includes the account receivables. Supplier Scheduling. It manages the preparation of credit sales invoice. Account Payable Management Module (APMM). IMM is responsible to keep track of information related with inventory transaction. Production Subsystem This subsystem is developed for maintaining products. which are obtained mainly from sales revenue collection.Supply Chain Management Inventory. to prepare journal reports.SoftwareRequirements Specification for <EMAAN ERP> Page 3 suppliers return activities that are related to the supplier. Items Transfer and Supplier Return and support all required operations on those vouchers. Supply Chain Planning. This module is also used to edit journals. 3. production process and Production voucher. this module prepares its own vouchers such as BPV. and Journal Management Module (JMM) ARMM is responsible for maintaining income related transactions that result for increasing in the proprietorship asset. 4. Disposal. and to control whether accounting journal principles are respected or not. Accounts Payable. Claim Processing. 5. Inspection of goods. It is also responsible to provide various reports related to the supplier. Fixed Assets . Accounting Subsystem This subsystem will have three major modules – Account Receivable Management Module (ARMM).Financials General Ledger.JMM is responsible for posting journal voucher source documents to the appropriate journals. The system will have a capacity for facilitating a production process from raw material to finished process. Purchasing. GRV. APMM is responsible to keep track of information related with expense transactions. This module is responsible for keeping rules related to the inventory transactions and controls the proper implementation of the rules. Cash Management. It is also responsible to provide various reports related to the income transactions. Order Entry. In addition to the documents it receives mainly from sales and inventory subsystem. and PCPV. It is also responsible for the generation of various reports. Accounts Receivable. This module is responsible for creating inventory related vouchers such as SIV. cash sales invoice and cash receipts. Commission Calculation 6.

5 References    SAP ERP From www. Customer Contact 1.org/wiki/Enterprise_resource_planning 2. Billing.Human Resources Human Resources. Implementing a EMAAN ERP Solution Manager solution at the enterprise level allows organizations to get rid of standalone computer systems in Accounts. Time & Attendance 9.1 Product Perspective ERP is the acronym for Enterprise Resource Planning. The key difference is that now Inventory Management and Purchase & Pre-Purchase Module can look into the Material Management Module and check if the pending orders from a day before have been processed or not. Overall Description 2. Commissions.google.com From http://en. We are analysis on ERP Scenario from last 2months in which we gathered all information regards ERP Solution for Middle Sized Industries and we design our ERP on OOP concept based in order to fulfill all Clients requirements. Activity Management 8. Payroll & HR. In our EMAAN ERP Solution Manager we introduce SMS Management System. an ambitious term that in reality attempts to integrate all departments and functions across a company onto a single computer system. Data Backup Management on . Like METRO.SoftwareRequirements Specification for <EMAAN ERP> Page 4 7. Time and Expense. This allows inter-departmental monitoring of business processes while allowing the management to correlate reports that provide a clearer picture of the enterprise as information is being used from across all levels and departments of the organization.Projects Costing. IMTIAZ. Payroll. MAKRO.wikipedia. AFROZE TEXTILE MILLS etc. EMAAN ERP Solution Manager provides the complete solution for Mid-Sized Industries and Organizations. Material Management and the Inventory Management and replaces them with a software solution with individual sub modules for each department. Service.Customer Relationship Management Sales and Marketing.

Day by Day Data Synchronization. Automatic SMS to Mobile Phone B. System Automated Back Office Reports . Automatic Email Alerts And Stock Budget Threshold And Task Assignment & Notifications Module Hardware Interface Module A. We offer complete services from consulting. Our EMAAN ERP Solution Manager Solutions: Our ERP solutions can be purchased by as a complete package or by module. Barcode and Online Attendance System (Optional) Security Module Accounts Module – General Ledger Accounts EMAAN ERP SOLUTION MANAGER OVERALL SYSTEM DIAGRAM Material Management (MM) Module A. Window Services (Automated). implementation and user training for ERP systems.SoftwareRequirements Specification for <EMAAN ERP> Page 5 Hourly Basis. requirement analysis to development. and Employee Attendance by Scanning Thumb Punch (Optional) features. Day by Day Data Synchronization. Data Backup Management.2Product Features           Payroll and HR Module Integrate Financial Information Integrate Customer Order Information and Store Customer History Streamline the manufacturing process Standardizing HR Information Store and Analyze productivity information for employees and facilities Allow inter-departmental process monitoring and reporting Reports with data from across the organization Allow Management to monitor and analyze all stages required to provide the clients with the client with products and services Allow users limited and monitored access to data across the organization according to needs Data Backup Management on Hourly Basis . System Automated Back Office Reports. Inventory Management Business Process Module B. Purchase & Pre-Purchase Module E-Business Website Module Sales Module (Shipping) 2.

Net. Crystal Report.  Managers will allow to access according to their destination. Purchase & Pre-Purchase Module). Android Technology (Optional) Hardware GSM Device Scanner NIL NIL 2.Automatic Email Alert (This modules is used for generating Automatic Email according to the conditions of record). Inventory Management Business Process Module B. Payroll and HR (It is used for making Employee Payroll or Pay Slip and Attendance).3 User Classes and Characteristics User classes of security level will be used to restrict the access according to the destination. Ado. Sales (It links to Customer to differentiate Customer on Sales basis and provide special facilities to Regular Customer).Net . Java Scripting. Asp. Html. The designing of ERP having ten modules namely Security (Multi-level security based on User Group and User Level).4 Operating Environment Programming Languages Operating Systems Databases Others Technologies Software Vb. and Material Management (This includes the following Business Processes: A. . Accounts (It relates to Accounts of Company). In this phase the Implementation of the Designing Phase will mainly occur these modules.SoftwareRequirements Specification for <EMAAN ERP> Page 6     Day by Day Data Synchronization Windows Services (Automated) System Automated Back Office Reports SMS Management System. Ajax.  Security level  Top management will be given full access. E-Business (A web based development require to show some database information like price list and product list). For the implementation of this system we will use Visual Studio 2008 by using Vb. Visual Studio 2008. 2.5 Design and Implementation Constraints This phase contains the designing and implementation.Net and Microsoft SQL Server 2005 for Database. C# Windows Operating System Sql Server 2005 Uml.Net. Hardware Interface Module (This module uses GSM Technology for SMS on Mobile Phone to facilitates our Customer) and Employee Attendance by Scanning Thumb Punch(Optional) and Data Backup Management Module (This module is used for Data Backup and its management on Hourly Basis).  Employeeswill be given limited access according to their job. 2.

The new system will improve productivity by reducing traveling time.SoftwareRequirements Specification for <EMAAN ERP> Page 7 2. AS_1 AS_2 AS_3 AS_4 AS_5 Great Abyssinia P. The ERP system eliminates a time misuse and over production in the enterprise.7 Assumptions and Dependencies An assumption is a statement that is believed to be true in the absence of proof or definitive knowledge. Simple Accounting transactions such as Journal will be easily navigated/ populated out of the System. improved customer service/ short response time/ and cost reduction/ saves time and money/. checking balance etc…. better communication. 2.making journal. The ERP system must able to be utilized in a Dial up connection with on way bandwidth All stakeholders will be trained to use the system with reliable affection. The system ease the workload in the enterprise employees for counting . AS_6 AS_7 DE_1 DE_2 3.6 User Documentation We will provide user manual along with the EMAAN ERP software for the help of our client and user which explain them how to use our ERP.1System Features System features are defined below and a use case diagram is shown here to show the system features. week and days. They can compare the market request based on months. As well dependencies are the projects external factors outside its control. Up to Date information will be retrieved by the stakeholders The System enables the managers to see the competitiveness of their product in the market.C shall make ready a networked LAN Environment in all office that utilizes the ERP System. .L.

SoftwareRequirements Specification for <EMAAN ERP> Page 8 .

this Feature is implemented as high priority.1. System Features of warehouse subsystem 3.1. Management to make a store request approval any time when a request comes from store personnel. Therefore. 3. this Feature in the sales system is taken as high priority. This Feature will be done every other day. This Feature is a high priority for the fact that there exists a chance for sales return.1. This Feature is also a medium priority for the System.1. 3. Description and priority The system enable a sales person to receive sales payments in two kinds of invoices namely cash and credit invoices.3 Prepare consignment sales note Description and Priority The system enables the sales person to prepare a consignment sales note for every product given with a consignment.2 Enable to perform store Request approval Description and Priority The system enable authorized personal. 3.SoftwareRequirements Specification for <EMAAN ERP> Page 9 3.2.2. This Feature is taken as a high priority for the fact the store shall be guaranteed to request a product which has demand by the market but not found in its limited value at the store.4 Prepare sales return invoice Description and priority The system enables the sales person to prepare a consignments sales return invoice whenever a sale that is made with consignment is returned from the consignee. 3.2 Enable users to receive sales pay with different sales invoices.1 Enable the user to prepare a sales order Description and priority .The system enables the sales person to prepare a sale order based on the request form any client.1.2. 3. This Feature is implemented as a medium priority. Perform a store request Description and Priority The system enables store personnel to prepare a store request when ever a store passes its minimum limit to hold the product.1. Therefore. This feature implementation is also a high priority. .5Prepare sales return invoice Description and Priority The system enables the sales person to prepare a sales return invoice to its client whenever the return is approved by authorized personnel. For every sales that is made every other day there exists either a cash sales or credit sales payment. 3.

multitasking ERP software.3 Functional Requirement Functional requirement is as follows: EMAANERP SOLUTION MANAGER Software Scope details for Manufacturing Business and for MidSized Industries and Organizations: LIST OF EMAANERP SOLUTION MANAGER MODULES The following are some key business processes (or procedures) which can be managed using ERP software. A store issue voucher will be prepared whenever a store is requested for any product or raw material.2. Multi-level security based on User Group and User Level.2.1. SECURITY MODULE 1. 3. 1.4. 1. This Feature is taken as a high priority. The ERP user gets a set of pre-mapped best business practice solutions for their particular industry. This Feature is taken as a high priority. Create Login id and password for each user.5.6Enable to prepare a store issue voucher Description and Priority . . modules may be applicable in your organization. Some of these. 1. Work done by individual users can be easily tracked because all transactions capture the users name automatically.2.The system enables a store keeper to prepare a store issue voucher.SoftwareRequirements Specification for <EMAAN ERP> Page 10 3. management to approve a purchase request that is requested by the Store keeper. 1. This is a general list of major Input and Output.6. In ERP parlance.1. 3.1.3Enable to prepare a purchase request form Description and Priority The system enables the store personnel to prepare a purchase request form.2. depending on the business requirements. Audit trail: ERP ensures accountability of users.2. they are referred as ERP modules. MIS (Management Information System) reports are shown for each module.1. We have successfully deployed the following modules and procedures at various manufacturing companies. 3. Assign permissions. Masters: 1. 1. 1. Map each user with menu / submenu. Restricting user access with login and password. 3. or all of these.3. User Manager. 1. This Feature is taken as high priority for the fact that there always exists a purchase request whenever a product in the ware house is limited.4Enable to prepare Purchase order Description and Priority the System also enables the store personnel to prepare a purchase order whenever there exist a need for a purchase. User group master.5Enable to make a Purchase order approval Description and Priority the system enables authorized personnel. Role based access & password.7.2. ERP Features: ERP is multi user. 1.

Bank. Bank Book (supports multiple banks) with receipts.1.3. Bank payment voucher.3.14. Key MIS Reports: 2. 2.17. ERP gives factory wise or branch wise plus consolidated for the head office.5. 2.5.4.15. 2.8. Service-tax payment (for excise link). such as .ACCOUNTS MODULE – GENERAL LEDGER ACCOUNTS 2.16.2.2. 2.2.4. ERP will create a JV automatically.7.1. 2. 2. 2. 2. Each menu and submenu can be locked (allow / deny) including MIS (Management Information System) reports to individual user in a very user friendly screen with tree structure and check box facility.8.2. 2. 1.6. 2.2. Option of various kinds of formatting.GL wise Tr.6.2. Contra-entry voucher. 2. Adjust unlink receipt with open sales invoice. Rate of depreciation (as per company act).2. Credit Note.2.2.g.1.2. 2. Journal Voucher.5. 2.9. 2. (For asset register and deprecation register).1. 2. 2. Narration Master.10. Trial Balance. Group and GL wise Tr. Automatic Audit Trail helps top management to know who has updated Masters or transaction and when. (Supplier / customer). . Masters: 2.2.2. TDS (Tax Deducted at Source) and % fields in the supplier / address (TP) masters. 2. 2. Asset installations slip. payments & contra filters. Transactions: 2.2. 2.2. 2. Group and sub-group wise Tr. Balance. Balance. Sub-ledger trial balance. Balance. 2. Cash payment voucher.1.12. Asset sale transaction. and GL accounts). (Option of T. 2.3.1.2.3.3. Rate of depreciation (as per I-Tax act).2. 2. 2.11.13. Expense voucher (for service provider bill booking). Sub-group wise Tr. 2. creditor. Cash receipt voucher. Cash Book. Debit Note.2. 2. Balance. E.3. General Ledger Account Head Master with Tax. Expense PO (for service provider. Consolidated reports of multiple locations for one company in Accounts Module.4. Automatic posting in GL.2.1.3. 2.9.2. Closing balance for master data (debtor. Detail Account Master. Account Group Master.2.2.18.1.2. Adjust unlink payment with open GRN (Purchase bill / expense bill).1.3. optional).SoftwareRequirements Specification for <EMAAN ERP> Page 11 1. Cash bifurcation.format = only closing balance). 2. Subgroup Master. 2.3.1. Bank receipt voucher.

3. from goods inward and sales invoice. Balance Sheet.14. 2. Fixed Asset register. Depreciation schedule (as per company act).1. Bank reconciliation statement.3. Automatic posting in respective G.1. 3. 3.11.3. 2. etc. Credit note register.3. shop floor) and subcontractor location.3. Profit & Loss account. TDS procedure takes care of automatic TDS posting.1.3.17.16. sales.4. (GL wise and sub-group wise).1. General Ledger.15.3. Help of Standard Narration master saves time to enter voucher.3. ERP Features: 2. Main Location Master – (sub-contractor location). Service tax procedure takes care of automatic posting in related excise ledger. 2.1.1. 2. All reports with drill down facility down to transaction level. bank balance.9. Purchase & Pre-Purchase Module A. 2.4. Filter available for amounts < than.4. 2. 3. 2. MATERIAL MANAGEMENT (MM) MODULE This includes the following business processes A.1. 3. Inventory Management Business Process Module 3.13. Expense voucher register.4.2.10. 2. money payable. Unit-of-Measurement (UOM) Master. 3. > than and =. 3.2. Sub-location master (stores. 3. Finished Goods Item Master and list.3. . Inventory Management Business Process Module B. 2. purchase. Masters: 3. Packing Material Item Master and list.1. 2.4.3.SoftwareRequirements Specification for <EMAAN ERP> Page 12 2.5.3. L.1.8.1. (Account head wise or all accounts with details under General Ledger). Depreciation schedule (as per Income Tax act). Factory Made (SFG or Semi-Finished) Material Item Master and list for WIP inventory. etc. Raw Material (Bought out) Item Master and list.2.1. 2.3.3. 2..4. (GL wise and sub-group wise). 2.4.5.6.3. Debit note register. Journal Voucher register.3.3.4. 3. Item Master. money receivable. Exceptional MIS Reports: Dash Board: This will give at a glance the highlights of certain figures to the top management viz.3. 2.1.12. For multi-location user can make consolidated P & L report. 2. 2.7.4.3. Contra-entry register. Category Master / Subcategory Master / Sub-group master.3.3.1.

3.2.3. 3.9. With quantity (location wise and category wise filters). 3. .2. . SAN (Stock adjustment note) register. This will debit the supplier in supplier ledger.e. item under inspection.3. 3. 3. 3.7. sub-category.5. (Location wise).1. 3. 3. 3.2. 3.2. 3. Conversion process Purchase return for non-excisable goods or Return to Supplier.3. Item ledger summary gives the stock of material at all locations – Drill down to ledger for any given location.4.6.3. 3. Physical stock and system stock (book stock) variance report.2. Or User may create Tax Invoice (sales -for excisable goods) 3. List of category. Key MIS Reports: 3.10.4. 3. MIN (Material issue note) register. Stores and Rejection location. GRN or Goods Receipt Note. Payment UOM and Payment conversion factor. QC person can login and enter Accepted / Rejected Quantity to transfer material to Stores. Various cost rate stored on Item master if required.4.5. ISO 9000 Facility to keep material in HOLD location – i.3. 3. 3.7.4. Physical stock slip to enter actual stock in a given location.4. 3.2.6.material issued to shop floor link to the Work Order as per BOM. This transaction is useful to get match physical inventory with stock reports. (With option to select any or all fields from item master).JPEG file). 3. 3.3.3. such as Weighted Average Rate.3. 3.2.4.3.6. ERP Features: 3. (With option to generate WAR – weighted average rate).1.2. With quantity and Rate (location wise and category wise filters). Stock Valuation report. GRN register (list) of items under “inward inspection".2.3. 3.3. 3.1.Filter provided for ‘normal’ STC and STC with Work Order.3. 3.3.3.3. Item List. Stock Statement for all types of material as well as WIP. Linked to Stores as well as creditor accounts. With quantity and Rate (location wise and category wise filters).8. Optional hyperlink with an AutoCAD drawing. (Location wise). 3. 3.3. a given period.4.SoftwareRequirements Specification for <EMAAN ERP> Page 13 3. Stock Transfer Challan register (STC) .1. and sub-group. Item Ledger (location wise) 3.2. For transferring material from one location to another location. With quantity (location wise and category wise filters).1. last pure purchase rate.7. Conversion Factor (relation between Purchase UOM and Issue UOM).8. (Optional).5. Transactions: 3.4.3. Optional Online link with picture of an item (.3.7. Separate ledger shows item in Hold. Stock Adjustment (SAN) to increase or reduce stock from a given location.6. This is linked with the material received and accounts entries are automatically generated by ERP. RTV.11.3. one time entry). Material Issue Note (MIN) to consume / material from a ‘given’ location. Closing balance master entry (as of cut-off date. Stock Transfer Challan . etc.2. 3. 3.4.2.3. RTV Register (Return to supplier – non-excisable items). 3. Stock Transfer Challan.2.2.7.

Lot number / Batch number / Serial number / heat number tracking of inventory.6.8.4.4.7.13. (Optional). (Optional). Purchase Order Register. Purchase enquiry. Supplier Type Master.7.11. Supplier Master (Supplier List). 3. Purchase quotation.7.4.15.2.8.10.14.3.16.2.Purchase & Pre-Purchase Module 3. B.4. 3. Purchase Requisition (Linked further to Purchase enquiry).1.6. 3. Auto transfer of Rejected Quantities to rejection stores location.6.7. 3. 3. 3. ERP Features: 3.7. 3.4. 3.12. Preparing Purchase Order.5. Just-in-time (JIT) inventory management by linking the MRP (material requirement planning) module and inventory module.SoftwareRequirements Specification for <EMAAN ERP> Page 14 3. Item wise consumption. Item specification document as per ISO 9000 requirements can be linked to PO (.3.6.4. P. This can be saved as . Purchase Order status Register with optional alert flag – when delivery period elapsed. (Optional).7.7. . Automatic calculation of landed-cost of item received and updating the same on master for valuation purpose.2. 3. being highlighted. etc. 3.4.4.8. delivery 3. For FMCG products user can store Inner Box / Outer Box data for shipping.6. can be shown automatically.9.PDF file and email to Supplier. Key MIS Reports: 3.2.1. 3.4. applicable flag in Item Master 3. Transactions: 3. Creditor Ledger. Serial No.4. Purchase requisition Register.7. 3. 3.7.6. Expiry / Near Expiry inventory for perishable goods.8.5. 3. Pending list of returnable items . Masters: 3.pdf) file.O. Drawing number. Supplier master list.RTV (return to Supplier with auto debit feature).3. Calling a given item by different name (alias) because different customers call with different name.8. Link to payment voucher with required validation to the GRN (Goods Receipt Note). 3. Warning letter generation based on poor performance/service. 3. 3. Supplier Performance Rating / Supplier Rating based on quality. 3.1. 3.5. (Optional). 3. or volume / weight of the box on item master.17. PFD (Process Flow Diagram) selection in Item Master.7. 3. 3.4.5.4. 3. Branch wise / Location wise / Plant wise / wise Stock status.4.1.6. 3. Excess material received can be accepted (Percentage tolerance given in subcategory master).3.

4.SoftwareRequirements Specification for <EMAAN ERP> Page 15 3. Transfer Invoice register (Optional).1. Invoice register – Product (item) details. 4.2. franchises. Sales Invoice. Scrape sales Invoice.3. Automatic Inspection Report (QC) for finished goods along with sales invoices (ISO 9000).4. G. 4. Key MIS Reports: 4. 4.6.2. 4.9. Make Similar Purchase Order. 4.2. Purchase Indent ‘Automatic’ alert to Purchase Department. 4.2.1.1. 4.2. such as branch. (Optional) 4.1. ‘Repairing Invoice’ (Sales bill towards repair service charges). 4. One Purchase Order – Multiple GRNs.8.11.1. 4.1.1. 4. etc.8.2. inventory (dispatch) and sales accounting.2. Replacement Challan non-excisable (linked to sales and RGN).2. Trading Invoice register (optional).). Complementary.8.5. 4.8. Purchase return invoice.5.3.1. Masters: 4.1. Invoice register – Customer details.1.(SHIPPING) F. Item 'accept / reject' quantity to be put by a separate password .2.2. Enquiry type master.1. Purchase Order Expiry Provision (Option).4. Purchase officer can make PO based on Material Requirement Planning report.8.3.3. Purchase Order ‘short-closed’ facility.3.2.2.6. 3.6.8. Goods returned from Customer.by QC person. Trading Invoice. Tax Invoice (Domestic). Officer Master (engineer or staff name can be attached to customer. or based on ROL based report. Customer Master. Commercial Invoice 4. Sales coordinator master. Customer Type Master. Sales Return transaction.3.10. 3.8.12.2. 4.2.4. 3.8. Preparing Challan cum Sales Invoice (CCI) 4. 3. 3. Invoice with zero sales value (free samples).3.2. (For excisable material returned to supplier). Stock Transfer Invoice. 4.2. Capturing of Excise.8.5. 4.8.3. RGN (Return Goods Note) register. 4.2. Packing Slip 4. Delivery mode master.1.7.2. 3.5.2.7.2. (To transfer material to own stock locations. (Amendment). .SALES MODULE .2.8. 4. Cess and S & H Education Cess information 3. Transactions: 4. 4.3. 4.4. Link to Order Receipt Information (ORI)/Internal ORI (Projection ORI for stocking) 4. 3. Purchase Order Revision Provision.1.2.3.2. 4. 4.

Information about the Contact details such as multiple contact person names. ERP Features: 4. Sales Invoice Link with sales order (ORI) to ensure accurate and fast billing preparation. for Customer.3.5. Classification of customer Geographically (Region. Multiple Delivery sales schedule (Sales Order) Report. Attendance Bonus setting 5. and Inventory. 4.4.4. City master 5. 4. Product wise invoice list. for preferential treatment as part of CRM (Optional).) 5.1.9.9. Replacement management – linked with inventory and sales accounting. Country). 4. while preparing sales invoice.4. Bank master 5. 80 U.2.g. Designation master 5. PAYROLL AND HR 5. email id. VAT / Sales Tax.5.1.3.3. 4. Customer ledger.2.5.1. etc. select customer name. to prepare phone book.11.4.5.1. phone number.1.1.1.10. Automatic pop-up based on link with credit limit of Customers and outstanding amount. User can select fields to prepare excel file. Employee master 5.8. 4. 5.6. Bank-Branch master 5.1.3. Segment wise. Capturing CT 3 information (Optional). Ledger.6. 15(2) (V) etc.2.14.4.7. state. Income Tax – Earning and deductions (Section 80C. ‘Repairing Invoice’ Register.SoftwareRequirements Specification for <EMAAN ERP> Page 16 4..9. 4.3. Excise Books.1.4. Department master (Cost Center) 5.4.4. 4. e.3.6. Credit control. Income Tax – Form 16.1. Sales Returned Goods Note (RGN) for item received back.1. Customer Master List. GL account Master 5.4. Master: 5. 4.Singing authority master .4. 4.13.4. 4.7. 4.4.1.8.1. Credit Limits for the customer.1. (Debtor Ledger). Price List – with filter to select a given category or subcategory. Grade master 5.3.3.4.5. 4.1. Automatic posting to Customer Account. 4.12. Sales invoice link to sales schedule (for OEM).10. 80D.7. telephone numbers.1. city. Age wise overdue report 4.1. Customer grading.1. 4. Bank-Branch master 5. Income Tax – Bank master 5. Age wise outstanding report 4.3.8. Bank master 5.3. 4.1. 4.1.5.3. email id. link to sales account and excise.4.

Employee type – manager. Every Report can be easily transferred to Excel. etc.4. Income Tax Monthly Challan Entry 5. 5.8.1.11. State Master 5. PF statement 5.4.3. Labor Welfare Fund master (LWF) 5.3.16.3. Earning head wise register 5. Modify all the transaction as many times as needed.3.3. Automatic calculation of income tax in pay-slip every month based on Earning and Deduction feed into the system.1.SoftwareRequirements Specification for <EMAAN ERP> Page 17 5.2. Attendance – The number of days present by an employee will have to be punched in the system by the concerned official of the HR Department.3. Employee resignation 5.2.5. Loans and advances to employees 5. 5. Transactions: 5. Form 16 5.15.13. Daily wages. 5. operator.3. ESI Report 5. (After this no Modification is allowed.5. monthly wages – salary calculations. Loan register 5.4.2. once one Account have audited.4.3.7.4.3. 5. 5.3.2.1. unpaid leave.9. . 5.8.Earning heads & deduction heads Master 5.4.4. User Matrix – By which each user is given/denied access to particular Report/Transaction resulting is high Security and blocking un-authorized access.3.14.4.9. Salary Heading .2. Bank Statement 5. 5.3.12.5. Reports: 5.15.3.4.3. Employee list 5. Pay Slip 5.3.3.18.3.3.2.2.1.10. Income Tax Yearly Report Per Employee wise (Automated) 5. Gratuity register 5. Attrition Report 5.2. Salary lock. ERP Features: 5.10. Pay slip 5. paid leave.6.4.4.15. Employee Joining Report 5. Leave Encashment Statement 5. etc. 5.3.15.1. Attendance Register 5.3. Very User Friendly GUI and Easy to understand Procedures which require minimum Training.4.16.6.7. 5.3.3. Attendance types – absence. Professional Tax [Professional Tax] Statement 5. Deduction head wise register 5.1. Payroll Register 5. 5. Monthly Deductions. Income TAX Quarterly Acknowledgement Entry 5.4.2.4.

SYSTEM AUTOMATED BACK OFFICE REPORTSAUTOMATIC EMAIL ALERTS AND STOCK BUDGET THRESHOLDAND TASK ASSIGNMENT & NOTIFICATIONS MODULE 8.2. User can restrict some web pages for internal use (Extranet / Intranet). Email id Master for sending auto emails 8. E-Catalogue. 8. Barcode Reader and Employee Attendance by Scanning Thumb Punch (Optional) 7. 6. ERP Database contains various information such as 'Product List' or 'Price List'.2. All Finished Goods for Sales are scanned by Bar Coder Scanning.4. 8.9. 7. Pending Purchase Order since defined days.8. as per the work sheet column data.E-BUSINESS 6. 8.1. WINDOW SERVICES (AUTOMATED). This module does not include website creating and design. 7.4.2. Day by Day Data Synchronization 8. 7. E-Business is the most significant area of the new ‘Digital Economy’.1.3. Data Backup Management on Hourly Basis 8. Alerts user for items falling below Re Order Level (ROL) 8. System Automated Back Office Reports 8. the same can be then published to the World Wide Web. channel partners (dealer) FG item master can be synchronized with the FG being shown on the e-commerce website for the shopping cart or while booking sales order (with option of showing stock).1. Leave allotment master 6. but SMS text can change dynamically. The rapid development of B2B and B2C e-Business shows that the internet is not just a new place to do business but constitutes a completely new method for commerce. Automatic SMS to Mobile Phone by Using GSM Technology. Order received but dispatch pending alert. DAY BY DAY DATA SYNCHRONIZATION.2. HARDWARE INTERFACE 7.2. B2B or B2C communication anywhere anytime from ERP. 6. 7.5.2. For instance. Once you have ERP database in place.3.1. For example.SoftwareRequirements Specification for <EMAAN ERP> Page 18 5. DATA BACKUP MANAGEMENT.7.1. 7.3.2. .1. Pending customer Bills since defined days/Months. 6. Employee Attendance by Scanning Thumb Punch.4. Show stock position online. Windows Services (Automated) 8. This can be now uploaded to a Website.6.11. ERP prepares reports instantly which can be exported to MS Excel file. SMS Gateway is designed to integrate seamlessly with ERP. Now this excel file can be sued to send SMS to mobile directly.1. 7. ORI pending since defined days.1. etc. *Note: Expected apply Windows Phone Technology some Functionality (Optional). we can prepare an active website.

12. External Interface Requirements a. Software Interfaces Software interfaces are as follows:    Programming language(VB. 8. Hardware Interfaces EMAAN ERP uses two hardware interfaces:   GSM device Scanner(Optional) c.NET.10. b. Non-Moving Items. Daily Sales to TOP Management. User Interfaces This is a similar ERP which gives you idea about our EMAAN ERP style to be followed. C#) Operating system(Windows operating system) Database(SQL Server 2005) . Bank balance going below defined amount. 8. 4.SoftwareRequirements Specification for <EMAAN ERP> Page 19 8.11.

Effectively track production performance and procedures with statistical process control tools and provide exactly the data that vendors are looking for when reporting back to them on the quality of their products. Asp.Net. Other Nonfunctional Requirements a. This is to protect the integrity of data integrated into the system. . application access system functions. the security of data backup and archiving. Html. network equipment. 4. Disaster may affect system but we will recover system. Java Scripting. and so on. to work-in-process. Crystal Report. Top-quality equipment leads to easier modification and updates in a frequent manner.Net. to customer returns. intrusion monitoring. Easily track defective materials and assign them for return to vendor. Upgrade the security systems when necessary. Safety Requirements   System crash cause damage or harm to ERP system. data access. Security Requirements System security includes: operating system. Ado. This is also to ensure unauthorized access and manipulation of process will not take place. Communications Interfaces For communication purpose we will use GSM device to communicate. Low-standard facilities that do not meet the standards demanded by ERP software and application will cause several problems. access. Performance Requirements  Make sure IT facilities used in the company meet international standards. scrap.SoftwareRequirements Specification for <EMAAN ERP> Page 20  Other technologies(Uml. security management regulations of the host room. virus prevention. Visual Studio 2008. Android Technology (Optional)) d. The increased quality of products and the efficiency of operations will significantly contribute to a more satisfied customer base. tracking data changes. Software Quality Attributes Maintain a high-level of product quality with complete inspection procedures—from raw materials. c.  b. authorization. Ajax. the system the administrator's supervision. d. or rework.

Technology used for mobile sms system will be windows 7.net.Data Flow Diagram Appendix B: Analysis Models Appendix C: Issues List   Programming languages that are used namely C# and VB.SoftwareRequirements Specification for <EMAAN ERP> Page 21 Appendix A: Glossary SRS------------------------System requirement specification ERP------------------------.Enterprise Resource Planning DFD------------------------. .

Sign up to vote on this title
UsefulNot useful