Project Conventions

<domain>-<sub domain/product name>-<project type>

Domain Type is related to the functional business areas that the project is associated with. Examples are, academic, admissions, sfs, admin and common.

Sub Domain or Product Type are the areas or products underneath the primary domain. For example, sub domains under "academic" are grading, advising, registration, scheduling. If a domain uses products instead of sub domains, then they would use the product name under the primary domain. For example, products under "admissions" are ectrack, "my.mit.edu" and stargate.

Project Type should be indicative of the function that the project is responsible for. For instance, if the project is a web application the project type should be "web". If the project provides business services, then the type should be "services". In the unique case of web services clients, the project type should be "client" or "service-client".

 The goal for naming projects as above is to modularize project functions. For example, the project academic-grading-services, should provide business services related to academic grades in a "jar" file. I can use this resulting "jar" in a variety of ways, I can include it in a web services application or I could use it within a local SAIS application. Here are the project types that SAIS supports: