A CHARGE AS A SECURITY Act No. 89/2012 Coll., the New Civil Code (the "New Civil Code") has been in effect since 1 January 2014. The New Civil Code has substantially changed Czech civil law in many respects, including the rules governing the grant and enforcement of asset security. The following paper analyzes, inter alia, the changes to these rules brought about by the New Civil Code, and in particular seeks to evaluate them from a practical perspective, utilizing standard interpretative methodologies, as well as interpretation e ratione legis, and comparative law. Prior to adoption of the Act, rules governing security were unsatisfactorily derived from a number of legislative sources (Act No. 40/1964 Coll., the Civil Code, Act No. 513/1991 Coll., the Commercial Code and Act No. 591/1992 Coll., the Securities Act), and were relatively underdeveloped, such that some quite basic issues were left for the courts to decide. Both of these deficiencies have been addressed by the New Civil Code. The New Civil Code replaces the old Civil Code, the Commercial Code and the Securities Act, thus unifying the divergent rules on asset security, and develops these rules in greater detail. The New Civil Code has introduced new legal concepts and instruments to the asset security framework under Czech law. These...

Software development is a collaborative process where many developers come together and work on a project. To make things easy and manageable, software is developed on a version control system. A version control system is a centralized system which stores code and adds code from all other developers as an increment to the code base in the repository. Since multiple people work on the same code repository together, it is important to make sure that their contributions do not conflict with each other. It is important to maintain the quality and integrity of the repository. This is where the code review process comes into the picture. All the changes made to the repository by developers are reviewed by other, preferably senior developers, before it is integrated into the repository. This is done to maintain a high standard of development. The problem is that this is a manual and highly time consuming process. This research proposes a tool that tries to optimize the code review process. This is done by ranking the changes that the developers need to review: this makes it easier for the developer to decide which change he/she needs to review first. Also since every reviewer has their own preference and style, the tool takes feedback from the code reviewer after every change and readjusts the ranked change list according to his/her feedback. Adding to that, the tool classifies each change and tags it so that the code reviewers have a better understanding of the change that he/she is about to review. It also provides additional refactoring information about each change. Refactoring changes are very easy to miss, since they are not usually erroneous changes, but they erode the quality of the software overtime. The tool points out these changes so that these changes are not missed by the code reviewer. The research was evaluated on 7 open source project and a usability study was conducted which prove that this tool does have a positive impact on the code review process.