http://www.icast.org.tw/info/announcements-information/2007-03-21-icast-project-number-hierarchy/

iCAST Project Number Hierarchy

Michael

2007/6/21 - updated

As DT suggested, we will apply this new number hierarchy to all projects from the 2^nd project year. In other words, as shown in the following table, the 1^st digit of the project ID represents for its organization, the 2^nd one its research area (group), and the 3^rd one for its project number.

2007/3/21 - initiated

After almost one year, project numbers, 101, 201 … 401, are well accepted and become part of our project. I invented it, but I have to break, actually modify, it now. To deliver a consolidate outputs and outcomes with an integrated view at the end of project; we have to continuously review and revise our projects as needed. From the second year, the 300 series projects will be divided into three groups based on their major research areas:

(1).     Authentication, Vulnerability Analysis and Verification

(2).     Wireless and Sensor Security

(3).     Intrusion Detection and Management

Here I propose to use project numbers 310, 320, and 330 to represent these three groups correspondently, and 311, 312, 321, 322 … to represent those individual project or tasks as shown in the attached table.

In the meantime, we are designing and developing an enhanced database for iCAST website to support the iCAST multi-project and multi-year structure, as well as a view for iCAST users to easily access and follow the project developing and details. We will also include an automatic project number conversion to reflect the project number modification history and bring users to the corresponding projects when crossing the project years.