Software Requirements Specification - Will Hardy

1 Software Requirements SpecificationBusiness Accounting and PayrollAnita Kotagiri (kot) and Will Hardy (wehardy)September 24, 2007 AbstractThis document contains the Software Requirements specification for the BusinessAccounting System. The goal of this document is to clearly specify the requirementsfor the system to be .. client .. development team .. and acronyms and abbreviations .. of general terms .. Resource Identifiers ..32 Overall context .. systems .. system .. Software .. source Software .. System .. Functionality .. Concepts .. is accounting? .. of accounting information .. double-entry system .. accounting equation .. statements ..133 Functional .. Requirements ..154 Functional Requirements .

2 16[FR-1]Undo [FR-2]Audit [FR-3] [FR-4]Localisation [FR-5]Internationalisation Requirements ( BSB).. lengths ..17[FR-6] [FR-7] [FR-8]Generic field [FR-9]Number field [FR-10]Comment [FR-11]Currency / output ..19[FR-12]Copy and [FR-13]Import file [FR-14]Export file [FR-15]Backup Guidelines ..20[FR-16] [FR-17] [FR-18]Spell [FR-19] [FR-20]Date ..22[FR-21]Help entry ..22[FR-22]Auto ..23[FR-23]Searching [FR-24]Expert [FR-25]Global [FR-26]Natural language ..25[FR-27]Tax Functional Requirements : Company Details ..26[FR-28]Company [FR-29]Company details [FR-30]GST [FR-31]GST registration [FR-32]Custom company of Accounts ..28[FR-33]Account [FR-34]Create new [FR-35]Special [FR-36]Special [FR-37]Account [FR-38]Edit account [FR-39]Account [FR-40]Account [FR-41]Account [FR-42]Edit [FR-43]Edit accounts [FR-44]View chart of accounts [FR-45]User Accounts & Categories.

3 32[FR-46]Default [FR-47]Default [FR-48]Default accounts for a service [FR-49]Default accounts for a wholesale ..35[FR-50]Multiple list ..36[FR-51]Import customer [FR-52]Import customer list list ..36[FR-53]Import supplier [FR-54]Import supplier list General ..37[FR-55] [FR-56] [FR-57]Tax transaction [FR-58]General Journal Functional Requirements : ..40[FR-59]Debtor [FR-60]Add new debtor [FR-61]Add new debtor [FR-62]Update existing debtor [FR-63]Inactive [FR-64]List of debtors [FR-65]List of debtors interface:..43[FR-66]Balance of all accounts receivable [FR-67]Delete debtor [FR-68]Relinking debtor [FR-69]Delete debtor ..45[FR-70]Quote [FR-71]Quote [FR-72]Quote orders ..46[FR-73]Sales order [FR-74]Sales order [FR-75]Sales order.

4 47[FR-76]Invoice [FR-77]Invoice [FR-78]Credit sales [FR-79]Cash sales [FR-80]Invoice payments from debtors ..49[FR-81]Receive Payment [FR-82]Record debtor payment [FR-83]Payment notes ..51[FR-84]Credit note [FR-85]Credit note [FR-86]Credit note deposits ..51[FR-87]Customer deposit [FR-88]Customer deposit [FR-89]Receipt of Functional Requirements : details ..53[FR-90]Creditor [FR-91]Add new creditor [FR-92]Add new creditor [FR-93]Update existing creditor [FR-94]Inactive [FR-95]List of creditors [FR-96]List of creditors [FR-97]Balance of all accounts payable [FR-98]Delete creditor [FR-99]Relinking creditor [FR-100]Delete creditor order ..57[FR-101]Purchase order [FR-102]Purchase order [FR-103]Purchase order ..59[FR-104]Bill [FR-105]Bill [FR-106]Credit purchase [FR-107]Cash purchase [FR-108]Bill [FR-109]List of [FR-110]List of bills payments to creditors.

5 64[FR-111]Make payment [FR-112]Creditor payment [FR-113]Make payment [FR-114]Print details of [FR-115]List payment [FR-116]List payment history Functional Requirements : accounts ..67 CONTENTS viii[FR-117]Bank [FR-118]Bank account [FR-119]Institution [FR-120]Institution details [FR-121]List of bank accounts [FR-122]List of bank accounts [FR-123]List of [FR-124]List of transactions reconciliation ..70[FR-125]Reconciliation [FR-126]Reconciliation with multiple [FR-127]Reconciliation [FR-128]Reconciliation opening [FR-129]Separation of transaction [FR-130]Reconciled [FR-131]Additional [FR-132]Final [FR-133]Reconciliation [FR-134]Post [FR-135]Reconciliation [FR-136]Reconciliation Functional Requirements : Balance sheet ..75[FR-137]Balance sheet [FR-138]Balance sheet Profit and loss statement.

6 76[FR-139]Profit and loss [FR-140]Profit and Loss Functional Requirements : Taxes ..78[FR-141]Australian [FR-142]Updating tax [FR-143]Updating tax tables from a [FR-144]Tax reporting [FR-145]International Tax Reports ..80[FR-146]GST [FR-147]GST report [FR-148]GST report [FR-149]BAS [FR-150]BAS report [FR-151]BAS report Additional Customers ..82[FR-152]Delete [FR-153]Delete quote [FR-154]Delete sales [FR-155]Delete sales order [FR-156]Delete [FR-157]Delete invoice [FR-158]Credit note Non-Functional Installation ..84 CONTENTSx[NFR-1]Windows packaged [NFR-2]Linux and Mac packaged [NFR-3]Installation [NFR-4] Performance ..85[NFR-5]Fast [NFR-6]Reporting results from [NFR-7] Security ..85[NFR-8]Zero tolerance data [NFR-9] Platform.

7 86[NFR-10]Windows [NFR-11]Apple OS X [NFR-12]Future Apple OS X [NFR-13]Linux [NFR-14]Future Linux Minimum Hardware Requirements ..87[NFR-15]Minimum Hardware Extensibility ..88[NFR-16] Custom report modules ..88[NFR-17]Basic reporting [NFR-18]Interpreted reporting [NFR-19]End user report Environment ..89[NFR-20]Multiple [NFR-21] [NFR-22]Peer to Licence ..89[NFR-23] ..90[NFR-24]Back-end language [NFR-25] [NFR-26] formats ..90[NFR-27]File ..91[NFR-28]Chosen development [NFR-29]Acceptable [NFR-30]Database transaction [NFR-31]Database Use Small business supplier .. Lessor .. Bulk data entry .. Process .. of data Acceptance SRS Acceptance .. Product Acceptance .. Product Deliverables ..9616 Client Changing Requirements .

8 SRS change management .. SRS Sign-off Iteration 1 .. SRS Sign-off Iteration 2 .. Product Acceptance ..99 Appendix A Requirement Ranking100 Appendix B Glossary101 LIST OF TABLES xiiiList of Tables1 Acronyms used in this document ..22 Definitions of general terms ..3 List of Figures1 document Hierarchy ..11 INTRODUCTION11 PurposeThis document will define an agreement between the client Cybersource and the developersTeam Chilli, by formally outlining the functional Requirements and non-functional require-ments (performance constraints) for the Business Accounting System. These requirementsform boundaries and constraints for the project s design process as well as providing areference for the development of a test document also provides the design team with informative context, drawn from thedomain experience of various contributors.

9 In doing this, the SRS will house all domainknowledge required for the development of the final 1 shows the hierarchy of documents descending from this 1: document HierarchyThe intended readers of this Software Requirements Specification are Cybersource, TeamChilli and the Team Chilli Supervisor Chris ScopeThis Software Requirement Specification outlines the functional and non-functional re-quirements and constraints of the system, ranking them asessential, does not provide any design specifications, except for constraints explicitly requested bythe ProductThe proposed product will referred to in this document as the Business Accounting SystemProduct or the The clientThe client for this project is:CybersourceLevel 4, 10 Queen StreetMelbourne 3000 AustraliaPH: (03) 9621 2377 The contacts for Cybersource are Steven D Aprano, and Con The development team Will Hardy Andrew Homer Anita Kotagiri Derek Lee Hon Chong Chin Yee Lee Lisa Luu Goran Stefkovski Sreedhar Valicherla Ronald Siswara Wong Alex Wong Tchen Ee Dennis Guang Definitions and acronyms and AcronymsCLOC lient Liaison OfficerIEEEI nstitute of Electrical and Electronic EngineersSDDS oftware Design DocumentSPMPS oftware Project Management PlanSQAPS oftware Quality Assurance PlanSRSS oftware Requirements SpecificationTPTest PlanUDUser DocumentationTable 1.

10 Acronyms used in this document1 Definition of general termsTermDefinition433-440 The forth year Software Engineering Project sub-ject taught by the University of Melbourne. TheBusiness Accounting System project is being un-dertaken as part of this client for this project is Cybersource. SeeSection deliverable to the Client at the comple-tion of the Project, known as Business AccountingSystem. See section for a list of project as a whole, including the Product, pro-cesses and any relevant documentation to the de-velopment of the product. The project in this sensewill cease on completion of the subject system as a whole, including the Software andany surrounding processes that integrate the soft-ware into the business SupervisorChris Edwards. His role and responsibilities canbe found in the 2: Definitions of general Universal Resource Identifierssvn:/Repositorywiki:/Wikigrou p:/CSSE group directoryshare:/chilliShare directorywww:/Group Std.