Design Phase of an Automatic payroll system

DesignPhase of an Automatic payroll system

Thedesign phase entails the production of technical and the visualprototype. The stage contains various non-technical aspects such asthe gathering of the web content. In the case of the server-sideprogramming and other numerous technical aspects entailed in thedesign, the emphasis is put on the design concepts such as efficientmodularity, stepwise elaboration, and information hiding (Connolly,et al. 2005).

Thesoftware is built using the Virtual Basic, and it typically runs onthe computers that have the .NET Framework installed. Basically, thewhole process can be primarily divided into five modules that includeemployee data, rates, payroll records, help, and ledger. When thedata is saved, it is written to an XML file. In ensuring that thesoftware platform remains independent, XML is an extremelyplatform-independent format for the storage of data. All the data ofthe employees along with their monthly payroll will be saved herehiding (Connolly,et al. 2005).

Thedesign process can be divided into three chief stages: logical,conception and the physical database design. The primary task of theconceptual database design is to simplify the design to be moremanageable, by evaluating the perspectives of the system. Therefore,the local conceptual data model is made complete and accuraterepresentation of the company as seen by the various users. Thelogical database design is capable of constructing a model of theinformation used in a system based on a particular data model, forinstance, the relational model, but it always independent of aparticular DBMS. The logical database design entails an EntryRelationship diagram, a relational schema, and other supportingdocumentation. The production of a logical data model entailsnormalization, and the aim of normalization is to eliminateparticular characteristics from the database design. It gets rid ofdata redundancy and in turn prevents the update anomalies. Typically, it helps to increase the clarity of this data model.

Themost vital modules of the design are payroll records, entity data,and the rates. In the case of the employee data module, the designerhas to keep track of the name, identification number, pension planagreement, union membership status and payroll of an employee. Thepayroll system has to link these to the general module that will holdthe other workers. Additionally, the design has to cater for themeans of storing the data, retrieving them, deleting and adding datawithout creating any errors.

Employees

_employees: Employee ()

Employees (): Employee ()

()

addEmployee ()

editEmployee ()

deleteEmployee ()

findEmployee ()

Payroll

_hoursWorked: double

_month: string

_year: string

_rate: Rate

hoursWorked: double

monthy(): string

year():string

rate(): Rate

()

addRate(): Rate

findRate(): Rate

()

federalDues(): double

stateDues(): double

unionDues(): double

pensionDues()

grossPy():double

netPay():double

Rate

_hourlyRate: double

_federalTax: double

_stateTax: double

_unionTax: double

_pensionPlan: double

hourlyRate(): double

federalTax():double

stateTax(): double

unionTax(): double

pensionPlan(): double

Employee

_id: string

_name: string

_unionMember: Boolean

_pensionplan: Boolean

_payrolls: Payroll()

Id() : string

Name(): string

unionMember() :boolean

pensionPlan():boolean

payrolls(): Payroll()

()

addPayroll(): Payroll

findPayroll():Payroll

Thefigure shows a demonstration of the automated payroll system in itsoriginal design.

Fromthe demonstration of the design shown above, the software will acceptemployee data in different capacities and then stores the data in anXML file. It then computes that data depending on the rates anddeductions that have been specified for the specific employee. Thissystem is automated, and that new employees can be added to thesystem at any time they come to the company. For this automatedsystem, an employee data can be modified or removed at any time fromthe list hiding (Connolly,et al. 2005).

References

Connolly,T. M., &amp Begg, C. E. (2005).&nbspDatabasesystems: a practical approach to design, implementation, andmanagement.Pearson Education.