DOC PREVIEW
Toronto CSC 340 - Software Requirements Specification for EZ-LAW

This preview shows page 1-2-3-20-21-22-41-42-43 out of 43 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 43 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 43 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 43 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 43 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 43 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 43 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 43 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 43 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 43 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 43 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Table of ContentsRequirements AnalysisAppendices1.1 Purpose1.2 Background1.3 Scope1.4 Definitions, acronyms, and abbreviations1.5 References1.6 Overview2.1 Product Perspective2.2 User Characteristics2.3 ConstraintsCriticality of the application - This application is not considered to be critical software as defined by IEEE Std 610.12-1990 (Standard Glossary of Software Terminology) as follows:2.4 Assumptions and Dependencies3.1 Product FunctionsActor 2: Billable EmployeeActor 3: System AdministratorActor 4: StaffActor 5: Copitrak System3.2 Use Cases3.2.1 User Class: BookkeeperUse Case 12: Add New Employee3.2.2 User Class: Billable Employee3.2.3 User Class: System Administrator3.2.4 User Class: Staff3.3 Data Input and Output3.4 Data to be Maintained by the System4.1 External Interface Requirements4.1.1 User InterfacesMain Program InterfaceTime Tracking InterfaceAccounting InterfaceSystem Administrator InterfaceReport Generator Interface4.1.2 Hardware Interfaces4.1.3 Software InterfacesCopitrak System Interface4.1.4 Communications Interfaces4.2 Performance RequirementsTime/Space Bounds & EfficiencyException HandlingTesting Requirements4.3 Design Constraints4.4 Software System AttributesCorrectnessInteroperabilityMaintainabilityPortabilityReliabilitySecuritySurvivabilityUsability4.5 Other RequirementsPhysical ConstraintsDocumentationLifecycleEconomicInterview with Senior Partner:General InformationBilling SystemBackupsArchivingSecurityCurrent SystemBilling Rate InformationInterview with BookkeeperGeneral InformationGeneral System QuestionsInvoicing QuestionsAccounts Receivable QuestionsInterview with Associate LawyerGeneral InformationSystem QuestionsSecond Interview with Senior Partner:General Requirements QuestionsBusiness Rules QuestionsUse Case DiagramsThis appendix contains the use case diagrams for each actor. These diagrams demonstrate the interaction between the actors and the system. The following table is a brief summary of the use cases. For a full description of each use case, see Section 3.Use Cases for BookkeeperUse Cases for StaffAccess ControlAccess LevelAccounting ManagerBackupClientDisbursementDisbursement InterfaceEmployeeBillable EmployeeExpenseFirm AccountGeneral AccountTrust AccountInterface to Copitrak SystemInvoice/Statement GeneratorLoginMain Program InterfaceMatterPayroll DetailsPayroll ManagerPrintReport GeneratorReport Generator InterfaceTime EntryTime Tracking InterfaceTime SheetSequence DiagramsOn the following pages are sequence diagrams for most of the use cases. For purposes of simplicity, the manager objects, as defined in the Class Diagram, have been left out. These objects are Accounting Manager, Billing Manager, Payroll Manager. TheySequence Diagram for Add Client use caseState DiagramsGoldman Greenberg AssociatesTeam MeetingsNote on group meetings: Due to the very tight time constraints of this project (2 weeks) the group communication as much through email and online chat as in meetings. Those communications are not reflected here.Team Meeting #1Team Meeting #2Team Meeting #3HVK SolutionsSoftware Requirements Specification forEZ-LAWTable of ContentsRequirements Analysis1. Introduction ............................................................................................................................... 11.1 Purpose..................................................................................................................... 11.2 Background ............................................................................................................... 11.3 Scope ......................................................................................................................... 41.4 Definitions, acronyms, and abbreviations .................................................................. 61.5 References................................................................................................................. 61.6 Overview ....................................................................................................................62. Overall Description.................................................................................................................... 72.1 Product Perspective................................................................................................... 72.2 User Characteristics................................................................................................... 92.3 Constraints .................................................................................................................92.4 Assumptions and Dependencies ............................................................................... 103. Functional Requirements ......................................................................................................... 113.1 Product functions ....................................................................................................... 113.2 Use Cases.................................................................................................................. 143.2.1 User Class: Bookkeeper ............................................................................ 153.2.2 User Class: Billable Employee................................................................... 223.2.3 User Class: System Administrator ............................................................. 233.2.4 User Class: Staff ........................................................................................ 253.3 Data Input and Output to System............................................................................... 273.4 Data to be Maintained by the System........................................................................ 304. Non-Functional Requirement .................................................................................................... 304.1 External Interface Requirements ............................................................................... 304.1.1 User Interfaces........................................................................................... 304.1.2 Hardware Interfaces................................................................................... 364.1.3 Software Interfaces .................................................................................... 364.1.4 Communications Interfaces ....................................................................... 374.2 Performance


View Full Document

Toronto CSC 340 - Software Requirements Specification for EZ-LAW

Documents in this Course
Scoping

Scoping

10 pages

Load more
Download Software Requirements Specification for EZ-LAW
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Software Requirements Specification for EZ-LAW and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Software Requirements Specification for EZ-LAW 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?