Castle Zeek Systems

Architecture

Castle Zeek uses certain technology approaches and languages.  Like so many other disciplines, expertise comes from focus.  Here we describe our standard architectural approach for each of the Engagement Levels we provide.

1. Engagement Level 1
   These are the "Brochure" types of static sites.  These involve HTML, CSS, and Javascript.
   • User Interfaces are developed using FireFox and then "quirkmode"-amended for non-standard browsers like Microsoft Internet Explorer.  Multi-browser testing is standard.  See TOS for version compatibilities.
   • HTML DOCTYPE STRICT is used to enforce standards to the extent possible.
   • Best practices observed such as image caching, separate CSS and JS files, and usability guidelines.
   • Castle Zeek understands Section 508 usability.  If this is a specific requirement, please let us know.
2. Engagement Level 2
   These are the "Information Websites" that have certain subscription-based server functionalities.  Here, we only describe the user interface aspect since the server engine architecture itself is not relevant to the kinds of customization inherent to this type of website.
   • All aspects of User Interface construction from Engagement Level 1 apply.
   • AJAX used for Administrative Panels to interact with server application.
3. Engagement Level 3
   This level of engagement is the introductory through mid-level Zeek Engine Web Application type project.  Level-3 engagements introduce hardware procurement in conjunction with the development and deployment.
   • Zeek Engines are written in Java 5. Migration to later Java versions is in the pipeline.
   • Deployment platforms: Linux OS such as Fedora 8, RHEL, and also Solaris 10.
   • Tomcat 5.5+ Servlet Container is used.
   • MySQL Database using InnoDB transactional engine, normalized at Domain/Key Normal Form.  The relational schema of all ZeekEngines is part of the system.  There are no direct integrations of the application stack to any pre-existing schemas the client may already implement.
   • All relevant design patterns per GoF, and derivatives thereof, are adhered to - as applicable to N-Tier, MVC-2 (Struts controller), Enterprise Web Application development.  Also see Sun BluePrints for Enterprise Architecture precepts observed by Castle Zeek.  Also see ITIL for business architecture precepts relevant to Castle Zeek business solution consulting.
   • Engagement Level 3 entails a non-clustered Zeek Engine Web Application deployed at the client site with a pre-configured server, or else at a remote dedicated hosting facility.  In the case of client site deployments, final system testing and acceptance are done onsite, and considerations for client-site hosting are considered case by case in the course of the engagement.
   • Engagement Level 3 does not include extrinsic integrations.  For example, integrating with PeopleSoft's PIA API is outside the scope of a Level 3 Engagements.
4. Engagement Level 4
   This level of engagement is for advanced Zeek Engine deployments.  These systems may be clustered if necessary.  A note on owning and operating a Zeek Engine system of this size: Castle Zeek does expect your organization has its own IT Team at this level.
   • Java 5, Linux/Solaris Platform, and design pattern adherence, per Level 3 Engagement.
   • MySQL preferred unless throughput and performance mandate Oracle 10g.
   • Integrations (if approved by Castle Zeek) are done via Web Service - SOA approaches.  If there are any preexisting relational schemas forming part of the integration architecture, there will be no direct ODBC/JDBC connections directly from the Zeek Engine.  Such integrations will require a suitable and approved application stack to also provide a web service layer abstraction from the external EIS.
   • In cases of overlap to a preexisting EIS tier with the new Zeek Engine Web Application, then a migration approach is preferred, and is generally so - as opposed to the SOA integration approach noted above.