Book Image

Sakai CLE Courseware Management: The Official Guide

Book Image

Sakai CLE Courseware Management: The Official Guide

Overview of this book

Sakai is a Collaboration and Learning environment that provides the means to manage users, courses, instructors, and facilities, as well as a spectrum of tools including assessment, grading, and messaging. Sakai is loaded with many handy features and tools, which make it uniquely the Learning system of the present as well as the future.This book is the officially endorsed Sakai guide and is an update to the previous book, Sakai Courseware Management: The Official Guide. From setting up and running Sakai for the first time to creatively using its tools and features, this book delivers everything you need to know.Written by Alan Berg, a Sakai fellow and former Quality Assurance Director of the Sakai Foundation and Ian Dolphin the Executive Director of the Sakai Foundation with significant contributions from the Sakai community, Sakai CLE Courseware Management: The Official Guide is a comprehensive study of how Sakai CLE should be used, managed, and maintained, with real world examples and practical explanations.The book opens with an overview of Sakai, its history and how to set up a demonstration version. Next, the underlying structures and tools are described. In using Sakai for Teaching and Collaboration, there is a detailed discussion of how to structure online courses for teaching and collaboration between groups of students, from creating course sites to understanding their use in different organizations around the world.
Table of Contents (27 chapters)
Sakai CLE Courseware Management
Credits
Foreword
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Terminology
Index

Automatic code analysis


Recognizing the ever-increasing cost in human resources of Quality Assurance as the code base expands, a refactoring of the Sakai code base is currently taking place. Roughly speaking, the project planners have separated the refactoring into two phases; the first phase is consolidation of core functionality, and the second is a significant overhaul of the underlying technologies. During both of these phases, the technical leads have placed emphasis on building in a significant degree of regression testing. If something gets broken during change, then the developers will find it before the Quality Assurance team.

A second line of defense is the automatic scrutiny of the main code base two to three times a day by the University of Amsterdam's QA server. The Amsterdam server automatically downloads the most current source and builds as shown:

Tools such as Findbugs (http://findbugs.sourceforge.net/) and PMD (http://pmd.sourceforge.net/) check the source code for bad...