1 / 23

Mine Pump Control

Mine Pump Control. TSW November 2009 Anders P. Ravn Aalborg University. OOAD Development steps. Problem Domain Analysis Application Domain Analysis Architectural Design Timing Analysis Detailed Design Implementation Validation. Problem Domain Analysis: Rich Picture.

ferdinand-reilly
Download Presentation

Mine Pump Control

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Mine Pump Control TSW November 2009 Anders P. Ravn Aalborg University

  2. OOAD Development steps • Problem Domain Analysis • Application Domain Analysis • Architectural Design • Timing Analysis • Detailed Design • Implementation • Validation

  3. Problem Domain Analysis:Rich Picture

  4. Problem Domain Analysis:Class Diagram AirQuality Pump WaterFlow Sump CO CH_4 AirFlow OperatorConsole WaterHigh WaterLow

  5. Problem Domain AnalysisBehaviours Pump (only non-trivial) off On Off off on on

  6. Problem Domain Analysis:Plant Structure • Water Level: dw = C_w  dt – C_p • Gas Level: If AirFlow then disappears after C_a time units • Water Flow: Must be on after C_f time units when (w > w_min) && (p == on)

  7. «interface» IO getCO() : bool getCH_4() : short getAirFlow(): bool getWF() :bool getWHigh() :bool getWLow() :bool setPump(on: bool) send(Event) Application Domain Analysis:Interfaces • CH_4 > 10 is high • Events: • pumpStopped • pumpUnsafe • pumpStarted • pumpFault (alarm) • WFflow • CH_4high (alarm) • CH_4error (alarm) • NoAirFlow (alarm) • COhigh (alarm)

  8. Application Domain Analysis:Functionality • Water Level is kept low unless CH_4 is to high (or pump stopped by operator). • Monitor gas levels and air flow. Report critical levels. • All critical events are sent to operator. • All system events are stored in a log.

  9. Application Domain:Timing Requirements • Pump must be shut off at high methane level within 200 ms • Operator must be informed within 1-3 seconds of critical events

  10. «component» Model «component» UserInterface «component» SubsystemInterface «component» OS «component» FileSystem «component» Function Design:Simple Generic Architecture «component» Interface «component» Platform ...

  11. Function Component CH_4 Monitor AirFlow Controller WaterLevel Monitor WaterFlow Monitor Data Logger CO Monitor Pump Controller Operator Console

  12. Model Component I Function Layer CH_4 Monitor WaterFlow Monitor Data Logger Pump Controller Operator Console WaterLevel Monitor Model Layer Log WL Command WF CH_4

  13. Model Component II Function Layer CH_4 Monitor Data Logger CO Monitor AirFlow Monitor Model Layer Log CH_4 CO AF

  14. Function Component CH_4 Monitor AirFlow Controller WaterLevel Monitor WaterFlow Monitor Data Logger CO Monitor Pump Controller Operator Console

  15. Functional Decomposition – RT_HOOD

  16. Interfaces

  17. PumpController

  18. WaterLevel Monitor

  19. Environment Monitor

  20. Priority Assignment

  21. Feasibility Check

  22. Detailed Design - Implementation • Programming Components • Synchronized / Atomic R/W • Environment Simulator • IO Interfaces for actual platform • OS Interfaces for actual platform

  23. Validation • Unit Test of Model Layer • Unit Test of IO Interfaces to Environment Simulator • Stepwise integration of Functions • Analysis/Measurement of C, D • Deployment on actual hardware • System Test

More Related