[论文解读] Apache Web Server Execution Tracing Using Third Eye

Raimondas Lencevicius, Alexander Ran+1 more|arXiv (Cornell University)|Jan 1, 2000

Engineering and Information Technology参考文献 5被引用 1

一句话总结

本文提出 Third Eye，一种利用领域特定事件和形式化约束来追踪和验证软件系统的灵活框架。通过将 Apache Web Server 的访问策略建模为可追踪事件并强制执行架构约束，该框架能够检测执行违规，证明其作为复杂、基于组件的软件系统开发流程中实用补充的有效性。

ABSTRACT

Testing of modern software systems that integrate many components developed by different teams is a difficult task. Third Eye is a framework for tracing and validating software systems using application domain events. We use formal descriptions of the constraints between events to identify violations in execution traces. Third Eye is a flexible and modular framework that can be used in different products. We present the validation of the Apache Web Server access policy implementation. The results indicate that our tool is a helpful addition to software development infrastructure. Nowadays, many software-intensive systems such as personal communication devices or communication network elements integrate many dozens of software components that are designed to run on different types of hardware, to interoperate with different environments and to be configurable for different modes of operation and styles of use. The situation is further complicated by a fact that these components are often developed by geographically distributed teams, using different programming languages, development tools and even different design and development methodologies. All this makes complete testing of these systems in a lab very hard. In the Third Eye project [4], we focused on abstract representation of software - its architecture. We have defined a methodology for tracing execution of software by reporting events meaningful in the application domain or essential from the implementation point of view. Many ideas incorporated in the Third Eye framework were inspired by the Logic Assurance system [5] and work on enforcing architectural constraints [2]. In Third Eye, we have used different technologies to make the framework more extensible, to allow its integration with other trace analysis tools and specification languages. The implemented portable prototype of the Third Eye framework includes reusable software components for event definition and reporting and stand-alone tools for storage and query of event traces, constraint specification and trace analysis. 2 THIRD EYE ARCHITECTURE A central decision of Third Eye framework is what information from the execution state of the program is traced. We decided to trace occurrences of events (Figure 1). Events cross the boundary between the application and implementation domains allowing abstract specifications that use event properties and a simple representation in the implementation domain. Such representation helps to produce traces without introducing new errors. “Event” in this case is a qualitative change in the state of an entity either meaningful in the application domain or significant architecturally. In Third Eye framework, events are typed objects. Event type has a name, a list of named and typed properties, and the type constructor. Third Eye event types are similar to classes in programming languages although the only method associated with the event type is its constructor. We allow event type inheritance. To report an event, developers specify the type of the event and set values of the event properties. Developers need to set only the properties that were not set already by the event constructor. Events in Third Eye are characterized by the time and location of their occurrence. Correct behavior specifications define constraints on the properties of the events, their sequence, location, and timing. We use formal descriptions of the constraints between events to identify violations in execution traces.

研究动机与目标

• 解决具有地理分布团队和异构技术的复杂、基于组件的软件系统测试挑战。
• 通过使用应用领域事件而非底层实现细节的基于追踪的验证，降低测试开销。
• 提供一个模块化、可扩展的框架，用于在运行时根据形式化的架构约束验证系统行为。
• 在真实系统上评估该框架的有效性，具体为 Apache Web Server 的访问策略实现。
• 证明基于事件的追踪结合形式化约束检查，可在软件开发生命周期早期检测行为违规。

提出的方法

• 使用带命名、类型化属性及继承关系的类型化事件来建模应用领域状态变化。
• 通过在运行时报告事件来捕获执行追踪，包括时间与位置元数据以支持追踪分析。
• 定义对事件序列、时间、属性和位置的形式化约束，以指定正确的系统行为。
• 将事件追踪存储在持久化存储库中，以便使用专用查询工具进行后续分析。
• 集成约束规范语言和追踪分析工具，以验证是否符合架构规则。
• 使用该框架分析 Apache Web Server 的执行追踪，检查是否存在访问策略约束违规。

实验结果

研究问题

• RQ1 基于事件的追踪结合形式化约束是否能有效检测复杂、基于组件的软件系统中的违规行为？
• RQ2 Third Eye 的模块化架构在多大程度上支持与现有软件开发和测试基础设施的集成？
• RQ3 Third Eye 在具有分布式开发团队和异构组件的系统中，能在多大程度上降低测试复杂性？
• RQ4 Third Eye 在验证真实世界系统策略（如 Apache Web Server 访问控制）方面的实际有效性如何？
• RQ5 与低层级的仪器化相比，使用领域特定事件在提升可追踪性并减少错误引入方面有何优势？

主要发现

• Third Eye 成功利用形式化约束检查，在 Apache Web Server 访问策略执行追踪中识别出违规行为。
• 该框架基于事件的方法实现了清晰、有意义的追踪表示，且未引入实现层面的错误。
• 模块化与可扩展的设计使得其能无缝集成至现有的追踪分析与规范工具中。
• 形式化约束建模有效捕捉了架构与策略层面的需求，提升了验证的精确度。
• 原型在复杂软件开发环境中作为传统测试的补充，展现出实际应用价值。
• 事件继承与类型化属性增强了追踪模型的表达力与可维护性。