You are on page 1of 11

EmployeeSetup Design Document

Date: Nov 13 , 2014

Address:

BizBites Technologies Pvt Ltd.,
Plot No.1, Survey No. 105/C
4th Floor, E. Malla Reddy Complex
Kompally, Hyderabad

India.

DOCUMENT REVISION HISTORY Revision/Date Issue/Date Version Author Changes Reviewer Approver Number 13/11/14 13/11/14 1 Murali .

.....Table of Contents TABLE OF CONTENTS..................................... SEARCH EMPLOYEE........................................................................................................... 4 2................................................................................. 6 3................ 3 1...................................................................................................................................................................................... ADD EMPLOYEE.. REPORT EMPLOYEE........................................................ 8 ................................

User Interface . and Save the details to the database after completing the validations. On Click [Edit] Data is filled in Form and ready to edit. and Delete the details from the database after confirm from User by Confirm Dialog Box.1. Navigation Add: People Resources->Employee->Add Action On Click [Save] Save the details to the database after completing the validations. On Click [Delete] Data is filled in Form and ready to Delete. Add Employee Screen Add/ Edit/ Delete Employee Screen Description This page allows the user to Create or Update or Delete Employee.

Employee. Stored Add/Edit: Procedures [HR]. Tables Referred HR.  If user clicks the delete button then system displays a confirm message like “Are you sure you want to delete”.Employee. + <Exception .[proc_UpsertEmployee] Delete: Validation Rules  If the save button is clicked data should be saved to the database after validating the mandatory fields.  If save is not successful display Employee Saving Failed.Message> Business Rules  Employee is used to login to the application.  If save is successful display “Employee Saved Successfully”.If Validation fails the System should highlight the mandatory fields.Tables Updated HR. Use Cases N/A Screen Field Database Data Control Remarks Table Field Validation Type .

Employee .FirstName FirstName nVarchar(256) TextBox Mandatory HR.

On Click [View All] Display the All Employees Data.HR.EmployeeOfficeDetails . On Click [Delete] Data is filled in Delte tab and ready to Delete. On Click [Edit] Data is filled in Edit tab and ready to Edit.DepartmentLanguage. Search Employee Screen Search Employee Screen Description This page allows the user to Search Employees By Keyword.2.Employee. Navigation Search: People Resources->Employee->Search Action On Click [Search] Search departname or description.JobTitleLanguage.HR. HR. User Interface Tables Updated N/A Tables Referred HR.

[proc_SearchEmployeesByCommonKeyword] Search: [HR].Employee Last Name LastName nVarchar(256) GridColumn N/A HR.EmployeeOf ficeDetails Age Age Int GridColumn N/A HR.Stored View All: Procedures [HR].it gives client side javascript validation.EmployeeOf ficeDetails Gender Gender nVarchar(256) GridColumn N/A HR.Department Name Name Language JobTitle JobTitle nVarchar(256) GridColumn N/A HR.Employee EmployeeCd EmployeeCd nVarchar(256) GridColumn N/A HR.it raises an validation message that “Please Select A Record” Business Rules N/A Use Cases N/A Screen Field Database Data Control Remarks Table Field Validation Type FirstName FirstName nVarchar(256) GridColumn N/A HR.Employee Middle Name MiddleName nVarchar(256) GridColumn N/A HR.Employee Address Address nVarchar(256) GridColumn N/A HR.  If the edit/delete button is clicked without selecting Employee .Employee .Employee Department Department nVarchar(256) GridColumn N/A HR.JobTitleLan guage Join Date Join Date DateTime GridColumn N/A HR.[proc_SearchEmployeesByCommonKeyword] Validation Rules  If the Search button is clicked without entring any data.

Report Employee Screen Report Employee Screen Description This page allows the user to Export Employee List.Employee Stored [HR]. Navigation Search: People Resources->Employee->Report Action On Click [Export] Exports the EmployeeList in Specified Format. User Interface Tables Updated N/A Tables Referred HR.[proc_GetAllEmployees] Procedures Validation RulesN/A Business Rules  Exports the Employee List as a Document in specified format.3. Use Cases N/A .

Employee Address Address nVarchar(256) GridColumn N/A HR.Screen Field Database Data Control Remarks Table Field Validation Type EmployeeName EmployeeNa nVarchar(256) GridColumn N/A HR.Department Name Name Language JobTitle JobTitle nVarchar(256) GridColumn N/A HR.Employee .EmployeeOf ficeDetails Age Age Int GridColumn N/A HR.Employee me EmployeeCd EmployeeCd nVarchar(256) GridColumn N/A HR.EmployeeOf ficeDetails Gender Gender nVarchar(256) GridColumn N/A HR.JobTitleLan guage Join Date Join Date DateTime GridColumn N/A HR.Employee Department Department nVarchar(256) GridColumn N/A HR.

. 28/11/14: Saving Detials of Employee (Personal Details.5\mssql2008r2). And Implemented Required Methods in BLL.168. Implemented Methods in BLL.DAL to Save Employee Details.Apprisal Details etc. 08/12/14: Implemented Roles. 05/12/14: Design the new Deisgn For Roles tab(Roles.Changelog Functionality for OfficeDetails while Editing.Privileges Windows) and worked on MemberShip Exception when Editing Existing Employee. 25/11/14: Changes Made in Code according to New Guidelines. 27/11/14: Changed UI Controls that Not Supported.1. 26/11/14: List User Control Removed and Search Functinality Added. 24/11/14: Designing New UI.) while Editing Existing Employee.Privileges Popup Windows in Roles tab accoring to New UI Requirements. 14/11/14: Moving the Design and Code from Kolerefactoring Application to KolmeERP_Solution..and related Methods.. 13/12/14: Implemented DashBoardAlerts.DAL.Developer Notes: 13/11/14: Copy the design KolmeRefactoring Application(with new DB connetion and DB name is KolmeRedesign from 192.Membership Details.