The applications architecture is built upon the implementation of agile software development principles. IT practices at HBS include phasing projects with frequent deliverables and partnering with end-users to determine requirements while allowing those to change appropriately throughout the project timeline. This approach keeps the IT development team flexible and adaptable to changing priorities, and means they are able to react quickly to project demands because projects are kept small, end-users stay involved, and priorities are reviewed regularly.
The HBS custom applications environment features a three-tiered Web architecture: Oracle at the data layer, Java on WebLogic at the application layer, and any Web browser on any platform at the client layer. All HBS Web applications are built upon an internally developed object-relational mapping tool, HBSCommon Access Classes. An intranet authentication system, also developed in-house, customizes and controls access to content based on each user's unique login information.
A centrally managed Oracle enterprise-wide database provides information to all HBS applications. Developed in-house, a series of Oracle databases track a vast range of information related to faculty, staff, students, alumni, and other constituents of the School. "Enterprise data" ranges from contact information to academic content, student grades, alumni activities, recruiting and other company contacts, information about campus facilities and social events, and more. Data flows seamlessly between databases, making information available in any format needed. As a result, the IT group can create easy-to-use Web-based applications that draw upon any combination of this data to dynamically generate targeted views based on specific needs.
An MBA Student Information System (SIS) already allows the MBA Program to capture new types of data, manage it more efficiently, and leverage it in unprecedented ways. A single student record integrates academic data—from course schedules and assignments to surveys and exercises—along with administrative data, such as financial aid and recruiting, and selected personal information (from work experience to personal interests) to help students connect with faculty and each other.
Eventually, we'll be able to expand each student record to include areas such as:
We'll be able to follow a student through her entire HBS experience: from her first visit to the HBS Web site, through her application to the School, through her preparation and time on campus, and after she returns to the business world. And, as we share data carefully yet more fluidly, analyze it in new ways, and create long-term profiles of the student experience, we'll form valuable "learning loops" that will help us:
