answersLogoWhite

0


Best Answer

Historically, equity theory focused on distributive justice or "the perceived fairness of the amount and allocation of rewards among individuals." Equity should also consider procedural justice, "the perceived fairness of the process used to determine the distribution of rewards." The evidence indicates that distributive justice has a greater influence on employee satisfaction than procedural justice. Procedural justice tends to affect an employee's organizational commitment, trust in his or her boss, and intention to quit. By increasing the perception of procedural fairness, employees are likely to view their bosses and the organization as positive even if they are dissatisfied with pay, promotions, and other personal outcomes.

User Avatar

Wiki User

14y ago
This answer is:
User Avatar

Add your answer:

Earn +20 pts
Q: Contrast distributive and procedural justice What implications might they have for designing pay systems in different countries?
Write your answer...
Submit
Still have questions?
magnify glass
imp
Continue Learning about Law

Explain normalization with examples?

Normalization is the process of designing a data model to efficiently store data in a database. The end result is that redundant data is eliminated, and only data related to the attribute is stored within the table.For example, let's say we store City, State and ZipCode data for Customers in the same table as Other Customer data. With this approach, we keep repeating the City, State and ZipCode data for all Customers in the same area. Instead of storing the same data again and again, we could normalize the data and create a related table called City. The "City" table could then store City, State and ZipCode along with IDs that relate back to the Customer table, and we can eliminate those three columns from the Customer table and add the new ID column.Normalization rules have been broken down into several forms. People often refer to the third normal form (3NF) when talking about database design. This is what most database designers try to achieve: In the conceptual stages, data is segmented and normalized as much as possible, but for practical purposes those segments are changed during the evolution of the data model. Various normal forms may be introduced for different parts of the data model to handle the unique situations you may face.Whether you have heard about normalization or not, your database most likely follows some of the rules, unless all of your data is stored in one giant table. We will take a look at the first three normal forms and the rules for determining the different forms here.Rules for First Normal Form (1NF)Eliminate repeating groups. This table contains repeating groups of data in the Software column.Computer Software1 Word2 Access, Word, Excel3 Word, ExcelTo follow the First Normal Form, we store one type of software for each record.Computer Software1 Word2 Access2 Word3 Excel3 Word3 ExcelRules for second Normal Form (2NF)Eliminate redundant data plus 1NF. This table contains the name of the software which is redundant data.Computer Software1 Word2 Access2 Word3 Excel3 Word3 ExcelTo eliminate the redundant storage of data, we create two tables. The first table stores a reference SoftwareID to our new table that has a unique list of software titles.Computer SoftwareID1 12 22 13 33 13 3SoftwareID Software1 Word2 Access3 ExcelRules for Third Normal Form (3NF)Eliminate columns not dependent on key plus 1NF and 2NF. In this table, we have data that contains both data about the computer and the user.Computer User Name User Hire Date Purchased1 Joe 4/1/2000 5/1/20032 Mike 9/5/2003 6/15/2004To eliminate columns not dependent on the key, we would create the following tables. Now the data stored in the computer table is only related to the computer, and the data stored in the user table is only related to the user.Computer Purchased1 5/1/20032 6/15/2004User User Name User Hire Date1 Joe 5/1/20032 Mike 6/15/2004Computer User1 12 1What does normalization have to do with SQL Server?To be honest, the answer here is nothing. SQL Server, like any other RDBMS, couldn't care less whether your data model follows any of the normal forms. You could create one table and store all of your data in one table or you can create a lot of little, unrelated tables to store your data. SQL Server will support whatever you decide to do. The only limiting factor you might face is the maximum number of columns SQL Server supports for a table.SQL Server does not force or enforce any rules that require you to create a database in any of the normal forms. You are able to mix and match any of the rules you need, but it is a good idea to try to normalize your database as much as possible when you are designing it. People tend to spend a lot of time up front creating a normalized data model, but as soon as new columns or tables need to be added, they forget about the initial effort that was devoted to creating a nice clean model.To assist in the design of your data model, you can use the DaVinci tools that are part of SQL Server Enterprise Manager.Advantages of normalization1. Smaller database: By eliminating duplicate data, you will be able to reduce the overall size of the database.2. Better performance:a. Narrow tables: Having more fine-tuned tables allows your tables to have less columns and allows you to fit more records per data page.b. Fewer indexes per table mean faster maintenance tasks such as index rebuilds.c. Only join tables that you need.Disadvantages of normalization1. More tables to join: By spreading out your data into more tables, you increase the need to join tables.2. Tables contain codes instead of real data: Repeated data is stored as codes rather than meaningful data. Therefore, there is always a need to go to the lookup table for the value.3. Data model is difficult to query against: The data model is optimized for applications, not for ad hoc querying.


Related questions

Implications of value and assumptions in OD?

1.Implications For Dealing With Individuals 2.Implications For Dealing With Groups 3.Implications For Designing and Running Organization


What is Procedural models?

Procedural models are models generated by using an algorithm(s) to create the model, instead of a 3d graphic designing it in a program like Blender or 3D studio max.


Difference between procedural programming and modular programming?

Procedural programming is a computer programming technique in which the program is divided into modules like function or subroutine or procedure or subprograms, where as ... "Modular Programming" is the act of designing and writing programs as interactions among functions that each perform a single well-defined function, and which have minimal side-effect interaction between them. Put differently, the content of each function is cohesive, and there is low coupling between functions as happens in procedural programming.


What is two types of programming approaches?

Procedural programming, one that is made of one or more procedures and Object-oriented programming (O.O.P.) where a standard model is used for designing using real-world objects to express patterns, called classes in software.


Have you heard about Virtual Voyage World?

Yes this College is provide many Vocation Courses like fashion Designing, Interior Designing, Web Designing, Graphics Designing, and Multi Media Designing


5 factors in designing and receiving area?

Designing what?


Who is responsible in designing the accounting system?

designing of accounting system


When was Designing Heaven created?

Designing Heaven was created in 1996.


When was Designing Spaces created?

Designing Spaces was created in 2005.


What are the release dates for Designing Women - 1986 Designing Women 1-1?

Designing Women - 1986 Designing Women 1-1 was released on: USA: 29 September 1986


What are the release dates for Designing Women - 1986 Designing Women - 1.1?

Designing Women - 1986 Designing Women - 1.1 was released on: USA: 29 September 1986


What is the duration of Designing Woman?

The duration of Designing Woman is 1.97 hours.