CCMAS Course Search

Students are attached to private and public organisations for a period of three months during the second year session long break with a view to making them acquire practical experience and to the extent possible, develop skills in all areas of Cybersecurity. Students are supervised during the training period and shall be expected to keep records designed for the purpose of monitoring their performance. They are also expected to submit a report on the experience gained and defend their reports.

Students are attached to private and public organisations for a period of three months during the second-year session long break with a view to making them acquire practical experience and to the extent possible, develop skills in all areas of Data Science. Students are supervised during the training period and shall be expected to keep records designed for the purpose of monitoring their performance. They are also expected to submit a report on the experience gained and defend their reports.

Students are attached to private and public organisations for a period of three months during the second-year session long break with a view to making them acquire practical experience and to the extent possible, develop skills in all areas of Computer Science. Students are supervised during the training period and shall be expected to keep records designed for the purpose of monitoring their performance. They are also expected to submit a report on the experience gained and defend their reports.

Students are attached to private and public organisations for three months to make them acquire practical experience and to the extent possible, develop skills in all areas of computing. Students are supervised during the training period and shall be expected to keep records designed to monitor their performance. They are also expected to submit a report on the experience gained and defend their reports.

Requires 3 months of Industrial Training after the completion of 300 Level. Students’ experience will be documented and presented in a Seminar.

Students are attached to private and public organisations for a period of three months during the third year session-long break with a view to making them acquire additional practical experience in all areas of Cybersecurity over and above what is gained in CYB 299. Students are supervised during the training period and shall be expected to keep records designed for the purpose of monitoring their performance. They are also expected to submit a report on the experience gained and defend their reports.

Students are attached to private and public organisations for a period of three months during the second-year session long break with a view to making them acquire practical experience and to the extent possible, develop skills in all areas of Computer Science. Students are supervised during the training period and shall be expected to keep records designed for the purpose of monitoring their performance. They are also expected to submit a report on the experience gained and defend their reports.

An in-depth look at software design. Continuation of the study of design patterns, frameworks, and architectures. Survey of current middleware architectures. Design of distributed systems using middleware. Component based design. Measurement theory and appropriate use of metrics in design. Designing for quality attributes such as reliability, performance, safety, security, reusability, etc. Measuring internal qualities and complexity of software. Evaluation and evolution of designs. Lab Work: Practical demonstration of the use of design patterns, frameworks and architectures. Practical simulation of distributed systems. Illustration of component based design. Working with software design software. Use of software metrics measuring software.

Management of the software configuration management process – organisation context for software configuration management, constraints and guidance for software configuration management process. Planning for software configuration management, software configuration management plan, and surveillance of software configuration management. Software configuration identification and software library. Software configuration control – requesting, evaluating and approving software changes, implementing software changes, and deviations and waivers. Software configuration status accounting – software configuration status information and reporting. Software configuration auditing. Key issues in software maintenance – technical issues, management issues, maintenance cost estimation, and software maintenance measurement. Maintenance process – maintenance processes and activities. Techniques for maintenance – program comprehension, re-engineering, reverse engineering, migration, and retirement. Lab Work: Practical demonstration of software configuration management processes. Working with software configuration management software. Illustration of software maintenance processes and activities. Working with software maintenance software. Illustration of software re-engineering and reverse engineering techniques.

Definition of Software Construction; Its importance; Key construction decisions – choice of programming language, selection of major construction decisions. Design in construction – Key design concepts, levels of design, design heuristics. Abstract Data Types (ADTs). Working Classes. High Quality Routines. The Pseudo Code Programming Process. Fundamental Data Types – Numbers, Characters and Strings, Boolean Variables, Arrays, Tables. Types of Statements – Straight Line Code, Loops, Control Structures; Developer Testing and Debugging. Software Craftsmanship – Layout and Style, Documentation, Personal Character. Lab Work: Practicals on the most common tools to ensure good software construction. The features include static code analysers to check that code follows coding conventions, special code searching and editing, collaboration support to allow multiple programmers working simultaneously, support for proper code documentation. Practice with IDEs (such as Visual Study Code, NetBeans and Eclipse) on debugging, compilation, running of code, auto completion and version control.