Assessments
Peacekeeper Solutions works with your management and personnel to assess business application requirements and design appropriate architectures and implementations. We educate your team on the 8 fallacies of distributed computing and present customized solutions that maximize security, reliability, accessibility, performance, administration, data integrity, and cost. Our process includes addressing concurrency rules for database record conflict resolution based on user roles and various connectivity scenarios. When shared by key stakeholders, these artifacts often illuminate hidden concerns, leading to an improved understanding of the problem space. Peacekeeper’s procedures ensure the most accurate assessments and the best solutions.
Documentation
Documentation is provided using outlines, notes, reports, contracts, and diagrams. Diagrams are quite useful for stakeholders and decision-makers. Peacekeeper produces UML diagrams to clarify contracts, support collaboration, and enhance documentation. Entity Relationship Diagrams are generated to illustrate standardized business domain nomenclature, associations, and multiplicities. Activity and Sequence diagrams can be utilized to portray business processes. Class diagrams are crafted to represent class responsibility, design patterns, and object memory management. Deployment diagrams can portray hardware requirements. Component diagrams are constructed to depict the interfaces within Service-Oriented Architecture (SOA). Use Case diagrams are not typically used, as use cases are documented in plain English.
Recommendations
Peacekeeper provides detailed justification of all recommendations, including the specifications of those options deemed impractical or inappropriate as an implementation of a specific technology layer. Additionally, Peacekeeper produces comprehensive reports describing factors and scenarios which would justify choosing other technologies. Proven methods are suggested to address on-site and off-site data backup, system and disaster recovery, and edge case scenarios such as long-term power outages.
Peacekeeper often recommends N-tier domain-driven design, including Hexagonal, Onion, and custom architectures while employing persistence-ignorant business objects, defined abstractions, and inversion of control. Interfaces are utilized for defining business specifications to clarify intent for proper development, dependency injection, testing, and maintainability.
