List view
Identify and address issues that could potentially be exploited by an attacker, and leveraged to the detriment of the end-user.
No due date•0/1 issues closedSimplify the way that users deploy and manage their DynamiteNSM deployments.
No due date•0/2 issues closedThe team has identified several items that are contributing to a significant amount of technical debt that is slowing development, especially in the realm of event normalization. The goal will be to shed this dead weight take a more thoughtful approach for future integrations, and align to well defined standards where possible.
No due date•1/3 issues closedDynamiteNSM development has outpaced our ability to effectively test the codebase manually. As a first step we will be requiring unit tests to be included with every service module. This is a far-cry from full code coverage, but offers a reasonable starting place.
No due date•1/3 issues closed- Single Responsibility Principle - a class should have only one job. So if a class has more than one responsibility, it becomes coupled. A change to one responsibility results to modification of the other responsibility. - Open-Closed Principle - Software entities(Classes, modules, functions) should be open for extension, not modification. - Liskov Substitution Principle - The main idea behind Liskov Substitution Principle is that, for any class, a client should be able to use any of its subtypes indistinguishably, without even noticing - Interface Segregation Principle - Make fine grained interfaces that are client specific Clients should not be forced to depend upon interfaces that they do not use. - Dependency Inversion Principle - Dependency should be on abstractions, not concretions. High-level modules should not depend upon low-level modules.
No due date•0/2 issues closed