41341490-assigsol-kumarkittmohan

7/28/2019 41341490-AssigSol-KumarKittMohan

1/10

Software RequirementsSpecification

for

Academic Payroll System

Version 0.1

Prepared by: Himanshu Kumar, Georgia Kitt & Monish Mohan

21/04/2009

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

This document has been modified for use in courses at AUT, February 2009.


2/10

SoftwareRequirements Specification for Page ii

Table of Contents

1. Introduction................................................................................................................................11.1 Purpose ............................................................................................................................................... 11.2 Intended Audience and Reading Suggestions..................................................................................... 1

1.3 Project Scope....................................................................................................................................... 21.4 References........................................................................................................................................... 3

2. Overall Description....................................................................................................................32.1 Product Perspective............................................................................................................................. 32.2 Product Features.................................................................................................................................. 42.3 User Classes and Characteristics........................................................................................................ 52.4 Operating Environment....................................................................................................................... 52.5 Design and Implementation Constraints............................................................................................. 52.6 User Documentation........................................................................................................................... 52.7 Assumptions and Dependencies......................................................................................................... 5

3. System Features......................................................................................................................... 6.................................................................................................................................................................. 63.1 Modify Payment Method ................................................................................................................... 7

4. External Interface Requirements ......................................................................................... 85. Other Nonfunctional Requirements......................................................................................... 8

6. Other Requirements.................................................................................................................. 86.1 Appendix A: Glossary......................................................................................................................... 8

Revision History

Name Date Reason For Changes Version

Maciaszek, LeszekA., RequirementsAnalysis andSystem Design

19/04/09

Documentation and System Features 3rd Edition


3/10

SoftwareRequirements Specification for Page 1

1. Introduction

1.1 Purpose

The scope of the project is computerizing a new Academic Payroll (AP) system for a university. It describes

a single subsystem of the AP System for full-time and casual academics to use.

1.2 Intended Audience and Reading Suggestions

The intended audience that the document is intended for is developers to implement the system, project

managers who design the system, users such as the full-time and casual employees who use the system

and anyone with interest to the system.

1.2.1 Business Requirements

1. Business categorizes employees into Full Time and Casual (Contractual).

2. Personnel Department maintains employees information.

3. The Academic payroll system maintains employees, manages leaves, and sick leaves.

4. Academic Kiosk (Web access) allows employees to maintain their information.

5. Academics are to be paid on Wednesday every fortnight.

6. Full time academics are paid on a flat salary and casual academics are paid on hourly rate.

7. Contracts Management System maintains the contract information.

8. Standard tax rates are deducted from full time academics.

9. Casual academics are given the choice of either to pay or not pay the tax.

10. The academics are either paid by mail (Cheques) or directly deposited into bank account.


4/10


1.3 Project Scope

The software being developed is an Academic Payroll (AP) System for a university. Its main purpose is to

pay salaries to the Full-time and Casual Academics which are currently being employed at the university.

Academic Payroll System has also links with other departments. AP System has full access Personnel

Department and Contract Management which it has access to all the personal and contract information for

all of its employees.

The Academic Payroll System enables university to achieve its business goal of payment to Full-time and

Casual Academics.


5/10


1.4 References

Not applicable to assignment.

2. Overall Description

2.1 Product Perspective

The product being developed is new for the university to achieve its Payroll System to pay salaries to the

Full-time and Casual Academics.

AP SystemPersonnelManagement

ContractManagement

Full-TimeAcademic

CasualAcademic


6/10


2.2 Product Features

Information Business processes Participants

Employee Personnel

information

Maintain Employee Information

Manage leave

Make payments(fortnight)

Add EmployeeDelete employee

Manage annual leave & sick leave

days

Paid Fortnightly

Mail (bank cheque) (postal address)

Direct deposit (bank ac.)

Automatic (every second wednesday)

Hourly rate

Request receiving payments

Full time academics

Casual academics

Accountants

Windows-based desktop

interface

FULL TIME ACADEMICS

View payments details

Fortnight payments

Total salariesYear to date tax

Leave balances

Personal information

Update (Web Based Access)

Flat salary

Web developers

Casual Contract information Contract information

Stores basic contract

information(Hourly rate)

Verification (Total Hours)

May elect to have no tax

deductions(university)

Fortnight payments

No leave entitlementNotification by email or mail


7/10


2.3 User Classes and Characteristics

User Classes categories end users of the new system in terms of their industry and IT skills, capabilities and

characteristics.

Type of users can be Direct (Employees maintaining the AP System) or Indirect (Full-time

academics accessing the system through Academic Kiosk). Frequency of use is both applicable to direct and Indirect users. Employees in Personnel

Department will be interacting with the AP System more frequently.

Subset of product functions allows both direct and indirect users to use same functions with

privileges and access.

Technical expertise refers to the direct users which will have full access to AP System plus

maintaining the AP System for the indirect user.

Security or privilege levels are very both important as indirect users will have high security and less

privilege in the AP System compared to direct users which will have full access to all the information

of the AP System.

Educational level or experience is less important to satisfy as it does not affect the AP System or the

users in any way.

2.4 Operating Environment


2.5 Design and Implementation Constraints

If the server for the web-based access is not running properly, full-time academics would not be able to

access the interface for viewing their payment details, leave balances and personal information. If the server

is down, the full-time academics would not be able to update their personal details and payment method.

Academic Kiosk would not be able to query the system about the full-time academics payment details. Also,

making sure that the payment is made securely to the Full-time academics bank account.

2.6 User Documentation


2.7 Assumptions and Dependencies

No Assumptions have been made during this project.


8/10


3. System Features

Payment Notification

MailE-mail

Tax Deduction

Payment By Mail(Bank Cheques) Payment By Direct Deposit

Submit Time Cards

Full-Time

Academics

Maintain Personal Information

Check Leave Balances

Modify Payment Method

Caasual

Academics

Verification of Total Hours Against

Contract

Salary Payment

Academmic

Kiosk

Peronnel

Department

Contract

Management

The Use case diagram above gives an overview of the complete Academic Payroll system. The Casual

academics submit timecards at the start at which it will be checked by the Contract Department who verifythe total hours worked against the hours agreed on the contract.

The time cards then will be passed on to the Personal Department, which processes the cards and make

salary payments to the academics via the chosen payment method.

The tax value can be deducted upon the choice of the academic. In addition, the casual academics have the

choice of receiving payment notifications by either mail or email. The full time academics are paid a flat

salary and therefore will be paid directly via the Personal Department to the academics with tax being

deducted.

The Full time academics have the option to view, edit personal details and payment method via the

Academic Kiosk.

Academic Payroll System


9/10


3.1 Modify Payment Method

3.1.1 Description and Priority

A full time academic change its payment method through Academic Kiosk whereas Casual Academic

has to notify Personnel Department to change their payment method.

3.1.2 Functional Requirements

Use CaseName:

Modify Payment Method

Scenario (ifapplicable):

A full time academic wants to change his payment method through Academic Kiosk.

TriggeringEvent (if applicable):

A Full time academic wants to change payment method.

BriefDescription:

If a Full Time academic wants to change his/her payment method, they can access

the Web-based interface(Academic Kiosk).

Actors: Full Time Academics, Academic Payroll System

Related UseCases:

Preconditions: A Full Time Academic needs to exist in the system and have a User ID andPassword. Also, Academic Kiosk needs to be in a good working condition.

Postconditions: Payment method successfully modified.

Basic Flow:Line Actor Action System Response1. Full Time Academic wants to change

his/her Payment Method.

2. Academic accesses the Web based

Interface.

The AP system asks the user to log in using

his/her User ID and Password.3. User enters his/her User ID and Password. System verifies the user login details with the

existing details in the database.

4. System loads the Home Page upon login by

default.

5. User accesses the Payment Method

webpage.

System displays the Payment Method webpage.

6. The academic then locates the modify

payment method option.

7. The academic changes his/her Payment

Method.

System updates his/her Payment Method.

8. Academic logs out of system. System logs out user.

Alternate Flow (AF1)If at line 3, this happens:Line Actor Action System Response3a If user enters invalid login details Invalid login message displayed and prompts to

re- enter details. It also prompts user to disable

Caps Lock.

5a The user refreshes the payment method

page.

Payment method page displays error message:

Page cannot be displayed.


10/10


4. External Interface Requirements


5. Other Nonfunctional RequirementsNot applicable to assignment.

6. Other Requirements

6.1 Appendix A: Glossary Personnel Department - The departments responsible for maintaining employees information,

manages leave, and makes payments.

Contract The agreement drawn up between the employer and the employee to confirm paymentterms, royalty, respective responsibilities etc

Entitlements An entitlement is a particular type of authorization

Contractual Relating to or be part of a binding legal agreement.

Academic Kiosk Provides web based access to full-time academics to view their payment details,

leave balances, and personal information.

Web-based access - Information and/or an application made available via the World Wide Web.

Windows-based desktop - Desktop that runs Windows based operations system.

Timecards - Records the dates and hours worked for a particular contract number.

Contracts Management System that maintains contract information.

Database - A Computer Database is a structured collection of records or data that is stored in a

computer system

Query A query is the primary means of viewing, changing, and analyzing data.

Bank Cheque - A cheque is a negotiable instrument instructing a financial institution to pay aspecific amount of a specific currency from a specific demand account held in the maker/depositor's

name with that institution. Both the maker and payee may be natural persons or legal entities

Appendix B: Analysis Models


Appendix C: Issues List


41341490-assigsol-kumarkittmohan

Documents