CSC/ECE 517 Fall 2015/oss E1552 NRR

From Expertiza_Wiki
Revision as of 21:13, 31 October 2015 by Fvravani (talk | contribs)
Jump to navigation Jump to search

E1552 Refactoring dynamic_review_assignment_helper.rb and dynamic_quiz_assignment_helper.rb

Overview

Refactoring

Refactoring is the process of changing a software system in such a way that it does not alter the external behavior of the code yet improves its internal structure<ref>[1]</ref>. It is a disciplined way to clean up code that minimizes the chances of introducing bugs. In essence when you refactor you are improving the design of the code after it has been written. There are many benefits of refactoring as follows: <ref>[2]</ref>

  • Refactoring improves the design of software. Refactoring often cleans up codes by deleting duplicates, divides a big chunk of codes into several methods, and makes the program more understandable.
  • Because refactoring makes a design cleaner, it helps the programmers understand codes better and see things that may have not been seen before.
  • Refactoring helps spot bugs since it makes the software more comprehensible.
  • Refactoring turns an adverse design into a good design, which allows for rapid software development.

Peer Reviewing

It is the process of evaluating work done by an individual or team by another team of individual with expertise in the concerned area. Types of Reviewing Strategies in Expertiza:-

  • Instructor Selected Reviewing - Using this strategy the instructor assigns reviews to participant in the assignment. After selecting this strategy the instructor has the following two options -
    • Set number of reviews done by each student.
    • Set minimum number of reviews done for each submission.

Then the instructor can click on assign reviewers and map the students to the topics which should be reviewed by them.


References

<references/>

Retrieved from "https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/oss_E1552_NRR&oldid=97681"