This document provides a data dictionary for a payroll management system. It defines 17 tables used to store payroll data including employee salary setup, pay scales, bonuses, allowances, deductions and payment information. For each table, the document lists field names, data types, descriptions and whether each field is a primary or foreign key. It is version 1.0 of the data dictionary drafted on January 31, 2015.
Hi! This is a slide show that make me feel to upload that, in our college the final year project assignment has been adopted from this slide. So you guys really feel that this slide is a great one to download and have a look exactly whats are in a Hospital management system has.
The Hospital is an Institute which provides to people best health services.
That Provides Facility for hospitalization.
The patient is admitted in hospital with the exception that he or she will be in the
hospital for more Than 24 hours.
The Patient is assigned a room /bed.
The Hospital Provide Medical care.
This is Just an overview how to present those slides which Describes Software Working....
its a General way of Representation....
Don't worry About Forms Shown inside...
Hi! This is a slide show that make me feel to upload that, in our college the final year project assignment has been adopted from this slide. So you guys really feel that this slide is a great one to download and have a look exactly whats are in a Hospital management system has.
The Hospital is an Institute which provides to people best health services.
That Provides Facility for hospitalization.
The patient is admitted in hospital with the exception that he or she will be in the
hospital for more Than 24 hours.
The Patient is assigned a room /bed.
The Hospital Provide Medical care.
This is Just an overview how to present those slides which Describes Software Working....
its a General way of Representation....
Don't worry About Forms Shown inside...
Here is the easy presentation of Software Requirements Specification Model on "Payroll Management System" for employees of a company. It is important for Developing the software for mentioned system. More information you can find after opening the document.
Restaurant Management System
Our main goal of this project is to create such a restaurant management software or system which will save time of both customers & restaurant management team.
Normally Use Case Diagrams are used but the pictorial information in it is so small that an MS Word Table is sufficient. What is more it can also provide space for "Use Case Goal" which is very important for Use Case Modeling.
Tables are quick and easy to create and edit. No need to waste time to draw and label diagrams. One can still do it if necessary after creating the Use Case TABLE. Try.
A Use Case Table can spill over into multiple pages but a diagram cannot!
UML 2.5 allows TABLES to be used for diagrams. So, there is no compulsion to create diagrams spending a lot of time.
Here is the easy presentation of Software Requirements Specification Model on "Payroll Management System" for employees of a company. It is important for Developing the software for mentioned system. More information you can find after opening the document.
Restaurant Management System
Our main goal of this project is to create such a restaurant management software or system which will save time of both customers & restaurant management team.
Normally Use Case Diagrams are used but the pictorial information in it is so small that an MS Word Table is sufficient. What is more it can also provide space for "Use Case Goal" which is very important for Use Case Modeling.
Tables are quick and easy to create and edit. No need to waste time to draw and label diagrams. One can still do it if necessary after creating the Use Case TABLE. Try.
A Use Case Table can spill over into multiple pages but a diagram cannot!
UML 2.5 allows TABLES to be used for diagrams. So, there is no compulsion to create diagrams spending a lot of time.
A data dictionary is a “virtual database” containing metadata (data about data). Data dictionary holds information about the database and the data that it stores.
College Stationery Management System VB 6.0 and Microsoft Access ProjectTushar Soni
Here's a project on College Stationery Management System. The front end of this application is made on Visual Basic 6.0 and back end is Microsoft Access 2007. You can refer this project to develop your own projects as well. Extremely easy Graphical User Interface. Students pursuing BCA, BSc(IT). BSc(CS), B.Tech and other related courses can refer this project. You can visit www.CodingAlpha.com to view the source code. Alternatively, Mail me on tushar.soni@outlook.com if you need the source code.
Please Comment or Like if you find this project interesting. Thanks.
The objective of Student information System is to allow the administrator
of any organization to edit and find out the personal details of a student and
allows the student to keep up to date his profile .It’ll also facilitate keeping
all the records of students, such as their id, name, mailing address, phone
number, DOB etc. So all the information about an student will be available
in a few seconds.
Overall, it’ll make Student Information Management an easier job for the
administrator and the student of any organization. The main purpose of this SRS document is to illustrate the requirements of the project Student information System and is intended to help any organization to maintain and manage its student’s personal data.
The SlideShare 101 is a quick start guide if you want to walk through the main features that the platform offers. This will keep getting updated as new features are launched.
The SlideShare 101 replaces the earlier "SlideShare Quick Tour".
Collateral: Loans are secured by collateral, which is property in which a security interest is granted to secure repayment of the loan. The loan collateral may include business assets, stocks, bonds, certificates of deposits, or personal assets. Consider (1) the value of the loan collateral must be equal to or greater than the amount of the loan, (2) expected economic life of collateral will be considered by the Bank in evaluating the collateral offered for the loan, (3) formal collateral appraisals may be required, and (4) a pledge of personal assets may be required as additional collateral for the business loan requested.
Guarantors: For incorporated borrowers, guarantees of owner(s) is usually required, unless secured by Bank deposits or marketable collateral. If personal assets are in joint names, a sole proprietorship, and/or partnership, the Bank may require all parties to pledge collateral.
on SQL Managment studio(For the following exercise, use the Week 5.pdfformaxekochi
on SQL Managment studio
(For the following exercise, use the Week 5 DB Design Excel file. Place the completed file in the
zip folder with your .sql files)
A landscaping firm has tasked you with developing a database for their company. You have
gathered requirements and have come up with the following list of data elements to construct a
basic data structure:
Client name Invoice number Equipment description
Invoice date Job description Payment total
Client city Equipment purchase date Employee name
Invoice total Client address
Client phone Employee payrate
Client zip code Client state
a. Using the DB Design Excel file, do the following:
Name the tables using the drop down menu above each table grid
Add the appropriate fields to each table using the drop down menus within the fields of each
table
Choose the correct data type for each field using the drop down menus within the data type
column next to the field.
Example:
(Vendors) (Invoices) (InvoiceLineItems) VendorID InvoiceID InvoiceSequence
VendorName VendorID (FK to Vendors) InvoiceID (FK to Invoices)
VendorAddress InvoiceDate InvoiceLineItemAmount
VendorAddress2 InvoiceTotal
VendorCity
New Database:
Create a new database named Finances.
Write a script that creates the following tables with the listed attributes. Reference foreign keys
where indicated. Be sure to create the tables in order of their dependencies (if you attempt to
create a table with a reference to another table that hasn’t been created, the script will fail).
Register table
RegisterID INT PK IDENTITY NOT NULL
TransactionID
Transactions table INT FK NOT NULL
TransactionID INT PK IDENTITY NOT NULL
AccountID VARCHAR(25) FK NOT NULL
TransactionDate SMALLDATETIME NOT NULL
TransactionAmount
Account table MONEY NOT NULL
AccountID VARCHAR(25) PK NOT NULL
AccountName VARCHAR(50) NOT NULL
AccountAddress VARCHAR(30) NULL
AccountCity VARCHAR(25) NULL
AccountState CHAR(2) NULL
AccountZip VARCHAR(10) NULL
AccountPhone VARCHAR(14) NULL
Create a database diagram of the Finances database. Take a screenshot of the diagram and save
it as a png file.
if you receive an error message informing you that you don’t have permission for the database,
run the following query:
ALTER AUTHORIZATION ON DATABASE::Finances TO sa
GO
Write a script that creates non-clustered indexes on the foreign keys in the Register and
Transactions tables.
Write an ALTER TABLE statement that adds check constraints to the following columns (use
NOCHECK):
AccountPhone (NOT NULL)
TransactionAmount ( > 0 )
Write an ALTER TABLE statement that adds the follow columns to these tables:
Register table:
ReferenceNo
Transactions table: VARCHAR(15) NULL
TransactionType VARCHAR(15) NOT NULL
TransactionCredit BIT NULL
In the Object Explorer, do the following
Expand the Finances database
Expand the Tables folder
Expand each table
Expand the Columns folder for each table
Expand the Constraints folder for the Account and Transactions tables
Expand the Indexes folder for the Register and Tr.
1. Appendix-A
Data Dictionary of
Payroll Management System
Version No.: 1.0 Draft 1.0
Date of Release: 31 January, 2015
Copy No.:
Daffodil Software Limited (DSL)
Dhaka, Bangladesh
3. DD for Inventory module
A. Documen t Release History
Sl.
No.
Versio
n No.
Releas
e Date
Prepared
By
Reviewed
By
Approve
d By
Reason
s for
New
Release
1 1.0
Draft
1.0
DSOFT/BERP/D/DD Version 1.0 Page 3 of 13
4. DD for Inventory module
B. Circular Details
Copy No. Designation of Copy Holder Location of the Copy
1 PM DSOFT Project Folder
DSOFT/BERP/D/DD Version 1.0 Page 4 of 13
5. DD for Inventory module
C. List of Amend me n ts Done on the Previous Version No.
Sl.
No.
Section
No. /
Page No.
Descriptio n of
the
Amend me n t
Approved
By
Change Request
No. & Date
DSOFT/BERP/D/DD Version 1.0 Page 5 of 13
6. DD for Inventory module
Table List with Description:
Table name Description
PAY_ALLOWANCE_DEDUCTION
Contains information regarding
Allowance or Deduction description
PAY_BONUS
Contains information regarding bonus
description
PAY_BONUSEMPLOYEEMAPPING
Contains information regarding
Employee bonus Mapping
PAY_DISBURSEMAIN
Contains information regarding
disbursement of the employee
PAY_DISBURSESDATA UPDATION
USER ID
Contains information regarding
disbursement
of the employee
PAY_EMP_SALARY_SETUP
Contains information regarding
employee
salary setup
PAY_SALARY_SHEET_INTERMEDIAT
E
Contains information regarding
employee
salary sheet
PAY_SALARY_SHEET_MAIN
Contains information regarding
employee salary sheet
PAY_SALARY_SHEET_SDATA
UPDATION USER ID
Contains information regarding
employee salary sheet
PAY_SCALE_DETAIL
Contains information regarding pay
scale
PAY_SCALE_MASTER
Contains information regarding pay
scale
PAYMENTMAIN
Contains information regarding
payment
description
PAYMENTMETHOD
Contains information regarding
payment
method
PAYMENTMETHOD_GL_MAPPING
Contains information regarding
payment
method and mapping
PAYMENTSDATA UPDATION USER ID
Contains information regarding
payment
related description
PAYMENTSDATA UPDATION USER
IDSDATA UPDATION USER ID
Contains information regarding
payment
related description
PAYMENTTERM
Contains information regarding
payment
related description
DSOFT/BERP/D/DD Version 1.0 Page 6 of 13
7. DD for Inventory module
Data Dictionary
1. Table Name: PAY_ALLOWANCE_DEDUCTION
Purpose:
2. Table Name: PAY_Bonus
Purpose:
DSOFT/BERP/D/DD Version 1.0 Page 7 of 13
Field Name Data Type Size Is
Required/Not
Key Description
[ALLOW_DEDUC_ID] [int] NOT NULL Allowance and Deduction id
[ALLOW_DEDUC_NAME] [varchar50)
NULL
Allowance and deduction name
[DESCRIPTION] [varchar50) NULL
Description of the Allowance
and Deduction
[AllowanceDeductionType] [varchar10)
NULL
Allowance and deduction type
[APPLICABLE] [bit] NULL
Allowance or Deduction is
applicable or not
[VW_ORDER] [int] NULL Vworder
[CreatedBy] [int] NULL Data Creation User ID
[CreatedDate] [datetime] NULL Data Creation Date
[UpdateBy] [int] NULL Data Updating User ID
[UpdateDate] [datetime] NULL Data Updating Date
Field Name Data Type Size Is Required/Not Key Description
[BonusId] [int] NOT NULL ID of the Bonus
[BonusName] [varchar50) NOT NULL Name of the Bonus
[ALLOW_DEDUC_ID] [int] NOT NULL
Allowance and
Deduction id
[CompanyId] [int] NULL Company Id
[CalculationId] [int] NULL Calculation Id
[CreatedBy] [int] NULL
Data Creation User
ID
[CreatedDate] [datetime] NULL Data Creation Date
[UpdateBy] [int] NULL
Data Updating User
ID
[UpdateDate] [datetime] NULL Data Updating Date
8. DD for Inventory module
Table Name: PAY_BonusEmployeeMapping
Purpose:
3. Table Name: PAY_DisburseMain
Purpose:
4. Table Name: PAY_DisburseSData Updation User ID
Purpose:
DSOFT/BERP/D/DD Version 1.0 Page 8 of 13
Field Name Data Type Size Is Required/Not Key Description
[MappingId] [int] NOT NULL ID of the Mapping
[MappingType] [varchar20) NULL Mapping Type
[MappingRefId] [varchar30) NULL Mapping Reference ID
[BonusId] [int] NULL Bonus Id
[BranchId] [nvarchar4) NULL Branch Id
[CreatedBy] [int] NULL Data Creation User ID
[CreatedDate] [datetime] NULL Data Creation Date
[UpdateBy] [int] NULL Data Updating User ID
[UpdateDate] [datetime] NULL Data Updating Date
Field Name Data Type Size Is Required/Not Key Description
[DisburseId] [bigint] NOT NULL ID of the Disburse
[DisburseDate] [datetime] NULL Disburse Date
[VoucherNo] [varchar30) NULL Voucher No
[BranchId] [nvarchar4) NULL ID of the Branch
[CreatedBy] [int] NULL Data Creation User ID
[CreatedDate] [datetime] NULL Data Creation Date
Field Name Data Type Size Is Required/Not Key Description
[DisburseId] [bigint] NOT NULL ID of the Disburse
[EmployeeId] [int] NOT NULL ID of the employee
[PaymentMethod] [varchar50) NOT NULL Payment Method
[Amount] [decimal18 2) NOT NULL Disburse Amount
[ReferenceId] [nvarchar50) NULL Reference ID
[BankAccountSerialNo] [int] NULL
Bank Account Serial
No.
9. DD for Inventory module
5. Table Name: PAY_EMP_SALARY_SETUP
Purpose:
6. Table Name: PAY_SALARY_SHEET_Intermediate
Purpose:
DSOFT/BERP/D/DD Version 1.0 Page 9 of 13
Field Name Data Type Size Is Required/Not Key Description
[EmployeeId] [int] NOT NULL ID of the employee
[ALLOW_DEDUC_ID] [int] NOT NULL
Allowance and
Deduction id
[DESCRIPTION] [varchar200) NULL
Description of the
Salary Setup
[CreatedBy] [int] NULL
Data Creation User
ID
[CreatedDate] [datetime] NULL Data Creation Date
Field Name Data Type Size Is Required/Not Key Description
[Id] [int] NOT NULL ID of the salary
[Salary_Sheet_Id] [bigint] NOT NULL
ID of the salary
sheet
[GenerationNo] [int] NOT NULL Generation No.
[EmployeeId] [int] NOT NULL ID of the employee
[DisburseId] [bigint] NULL ID of the Disburse
[GenerationType] [varchar20) NULL Type of Generation
[PaymentMethod] [varchar20) NULL Payment Method
[ReferenceId] [varchar50) NULL ID of Reference
[BankBranchId] [int] NULL
ID of the Bank
Branch
[BankAccountSLNo] [int] NULL Cell number
[IsRequestForWithdraw] [bit] NULL
Bank account serial
No.
[RequestDate] [datetime] NULL Request Date
[RecommendBy] [int] NULL
Recommend by
user
[RecommendDate] [datetime] NULL Recommend date
10. DD for Inventory module
7. Table Name: PAY_SALARY_SHEET_MAIN
Purpose:
8. Table Name: PAY_SALARY_SHEET_SDATA UPDATION USER ID
Purpose:
9. Table Name: PAY_SCALE_DETAIL
Purpose:
DSOFT/BERP/D/DD Version 1.0 Page 10 of 13
Field Name Data Type Size Is Required/Not Key Description
[SALARY_SHEET_ID] [bigint] NOT NULL
ID of the Salary
Sheet
[SALARY_YEAR] [int] NOT NULL SALARY YEAR
[SALARY_MONTH] [int] NOT NULL Salary Month
[VARIFIED_BY] [varchar50) NULL Verified by User
[APPROVED_BY] [varchar50) NULL Approved by User
[VARIFIED_DATE] [datetime] NULL Verified Date
[APPROVED_TIME] [datetime] NULL Approval Time
[BranchId] [nvarchar4) NULL ID of the Branch
[CreatedBy] [int] NULL
Data Creation User
ID
[CreatedDate] [datetime] NULL Data Creation Date
Field Name Data Type Size Is Required/Not Key Description
[IntermediateId] [int] NOT NULL ID of the employee
[ALLOW_DEDUC_HEAD] [int] NOT NULL
Head of the
Allowance or
Deduction
[AMOUNT] [decimal18 2) NOT NULL
Amount of the pay
salary
[BonusId] [int] NULL ID of the Bonus
Field Name Data Type Size Is Required/Not Key Description
[GRADE] [varchar10) NOT NULL
Grade of the Pay
Scale
[ALLOW_DEDUC_ID] [int] NOT NULL
ID of the Allowance
and Deduction
[BASIC_PERCENT] [decimal18 0) NULL
Percentage of the
basic Salary
[TOTAL] [decimal18 2) NULL
Total amount of
salary
11. DD for Inventory module
10.
11. Table Name: PAY_SCALE_MASTER
Purpose:
12. Table Name: PaymentMain
Purpose:
DSOFT/BERP/D/DD Version 1.0 Page 11 of 13
Field Name Data Type Size Is Required/Not Key Description
[GRADE] [varchar10) NOT NULL
Grade of the Pay
Scale
[BASIC] [decimal18 0) NULL Basic Salary
[EB1_RATE] [decimal18 0) NOT NULL Increment Rate
[EB1_MAX_TIMES] [int] NOT NULL
Increment Rate
times
[EB2_RATE] [decimal18 0) NOT NULL Increment Rate
[EB2_MAX_TIMES] [int] NOT NULL
Increment Rate
times
[DESCRIPTION] [varchar100) NULL Description
[CreatedBy] [int] NULL
Data Creation User
ID
[CreatedDate] [datetime] NULL Data Creation Date
[UpdateBy] [int] NULL
Data Updating User
ID
[UpdateDate] [datetime] NULL Data Updating Date
Field Name Data Type Size Is Required/Not Key Description
[PaymentId] [nvarchar16) NOT NULL ID of the payment
[PaymentDate] [datetime] NOT NULL Payment Date
[BranchId] [char4) NOT NULL ID of the Branch
[SupplierId] [int] NOT NULL ID of the Supplier
[Amount] [decimal18 2) NOT NULL
Amount of the
payment
[CashAmount] [decimal18 2) NOT NULL
Cash Amount of the
payment
[ChequeAmount] [decimal18 2) NOT NULL
Cheque Amount of
the payment
[CreatedBy] [int] NOT NULL
Data Creation User
ID
[CreatedDate] [datetime] NOT NULL Data Creation Date
[UpdateBy] [int] NOT NULL
Data Updating User
ID
[UpdateDate] [datetime] NOT NULL Data Updating Date
12. DD for Inventory module
13. Table Name: PaymentMethod
Purpose:
14. Table Name: PaymentMethod_GL_Mapping
Purpose:
15. Table Name: PaymentSData Updation User ID
Purpose:
DSOFT/BERP/D/DD Version 1.0 Page 12 of 13
Field Name Data Type Size Is Required/Not Key Description
[MethodId] [int] NOT NULL ID of the Method
[MethodName] [nvarchar50) NOT NULL Name of the Method
[GLCode] [varchar10) NULL Code of the GL
[SelectedGLCode] [varchar50) NULL
Code of the
Selected GL
[BankChargeInPercentage] [decimal6 2) NULL
Percentage of the
Bank Charge
[IsCreditCard] [int] NULL
Credit Card have or
not
[UpdateBy] [int] NOT NULL
Data Updating User
ID
[UpdateDate] [datetime] NOT NULL Data Updating Date
Field Name Data Type Size Is Required/Not Key Description
[PaymentMethodId] [int] NOT NULL
ID of the Payment
Method
[SelectedGLCode] [varchar50) NOT NULL
Code of the
Selected GL
[BranchId] [char4) NOT NULL ID of the Branch
[CreatedBy] [int] NOT NULL
Data Creation User
ID
[CreatedDate] [datetime] NOT NULL Data Creation Date
[UpdateBy] [int] NOT NULL
Data Updating User
ID
[UpdateDate] [datetime] NOT NULL Data Updating Date
Field Name Data Type Size Is Required/Not Key Description
[PaymentId] [nvarchar16) NOT NULL ID of the Payment
[BillId] [nvarchar16) NOT NULL ID of the Bill
[PaidAmount] [decimal18 2) NOT NULL Paid amount
[CreatedBy] [int] NOT NULL
Data Creation User
ID
[CreatedDate] [datetime] NOT NULL Data Creation Date
[UpdateBy] [int] NOT NULL
Data Updating User
ID
[UpdateDate] [datetime] NOT NULL Data Updating Date
13. DD for Inventory module
16. Table Name: PaymentSData Updation User IDSData Updation User ID
Purpose:
17. Table Name: PaymentTerm
Purpose:
* P: Primary Key; U: Unique Key; FK: Foreign Key
DSOFT/BERP/D/DD Version 1.0 Page 13 of 13
Field Name Data Type Size Is Required/Not Key Description
[PaymentId] [nvarchar16) NOT NULL ID of the Payment
[PaymentMethodId] [int] NOT NULL
Method of the
Payment
[GLCode] [varchar50) NOT NULL Code of the GL
[Amount] [decimal18 2) NOT NULL Payment Amount
[RefNo] [varchar15) NULL Reference No.
[RefDate] [datetime] NULL Reference Date
[BankBranchId] [varchar4) NULL
ID of the Bank
Branch
[CreatedBy] [int] NOT NULL
Data Creation User
ID
[CreatedDate] [datetime] NOT NULL Data Creation Date
[UpdateBy] [int] NOT NULL
Data Updating User
ID
[UpdateDate] [datetime] NOT NULL Data Updating Date
[VoucharNo] [varchar50) NULL Vouchar No.
Field Name Data Type Size Is Required/Not Key Description
[TermId] [int] NOT NULL ID of the Term
[TermDescription] [nvarchar150) NOT NULL
Description of the
term
[UpdateBy] [int] NOT NULL
Data Updating User
ID
[UpdateDate] [datetime] NOT NULL Data Updating Date