The Data Management Business Intelligence (DMBI) team endeavors to build data-intensive web applications in the same way every time. To make applications easy to create, similar in style and in code, and therefore easy for users and developers to learn, we use an evolving application skeleton, a user interface style guide, an interaction design pattern library, and a set of coding design patterns and conventions EVER TIME we create a new application. Since RAFT 3 was the first application we created using this skeleton methodology, and it evolved from a previous code base, it differs from subsequent applications and the current skeleton to some extent. Therefore, some of the following documentation must be RAFT specific or make mention of RAFT divergence from the general pattern.
For folks interested in how the application looks and acts to end users, please look at the:
For people who want to know how to build an MITBI-skeleton-based application, please look at the:
Why these standards matter
Setting these standards improves the reliability of a user interface by creating a consistent and predictable system for its end users. If buttons and links behave consistently from page to page, users know where to look and what to expect when navigating a system. This creates a positive user experience that in turn increases users’ efficiency using the system. Having a reliable library for developers also decreases development time for add-on features post launch because the need to figure things out (i.e., solving previously solved problems) is reduced.
Who this guide is for
Any internal MIT employees and external contractors engaged in the development or maintenance of the DM-BI applications should be familiar with this guide.
Who to contact for more information
Michael Berger, IS&T (mberger@mit.edu)