-
Top Three Posts
Free updates by email
-
Recent Posts
Categories
- Agile
- API
- Architecture
- Automation
- AWS
- Booking Practice
- Business Rules
- Cloud
- Conferences
- Connectivity
- Continuous Integration
- Data Flow
- Data Mapping
- Databases
- Derivatives Industry
- DevOps
- Docker
- Domain Model
- EMIR
- Enterprise Integration
- Enterprise Wide Data
- Eurex 13
- FpML
- High Frequency Trading
- Home Computing
- Humour
- ISDA
- Jenkins
- JMeter
- Kanban
- MariaDB
- Message Queue Software
- Messaging
- Messaging Standards
- MiFID
- Models
- MTFs
- Music Production
- Oracle
- Orchestration
- Project Management
- Rapid Application Development
- Regression
- Regulatory Reporting
- Replay
- Risk Management
- Rogue Trader
- Routing Rules
- Rule Engines
- Scrum
- Security Exchanges
- Smoke Testing
- Static Data
- STP
- Test Automation
- Test Data
- Testing
- TICK
- Time Recording
- Trade Flow
- Trade Organisations
- Travel
- Uncategorized
- Vendors
- VirtualBox
- Virtualisation
- WaveMaker
Tags
- adapter framework
- agile
- Asynchronous
- AWS
- break
- CCP
- ClearVision
- Cloud computing
- Consolidated Tape
- Continuous Deployment
- Continuous Integration
- devops
- Docker
- EC2
- edge case
- Enterprise Integration
- Enterprise Integration Patterns
- eurex 13
- family
- FFastFill
- fpml
- Google App Engine
- HTTP API
- IDX
- infrastructure
- Jenkins
- logging
- Messaging Systems
- Middle Office
- OTC
- Post-Trade
- Project Scope
- regression test packs
- rules
- Rules engine
- screen time
- SEALS
- security
- sequencing
- static data
- STP
- SunGard
- testing
- use case
- workflow
Tag Archives: logging
Not modelling your workflow? Here there be monsters!
I wanted to share a recent project experience with you that further strengthened my belief that a picture paints a thousand words. It helped to identify the root cause of a show-stopping problem where other efforts to do so had … Continue reading
Posted in Business Rules, Data Flow, Domain Model, Messaging, Models, Replay, Risk Management, Routing Rules, Rule Engines, Smoke Testing, Trade Flow, Uncategorized
Tagged adapter, adapter framework, complex, conflict, deep dive, entry rule, exit rule, infrastructure, logging, Messaging Systems, refactor, regression test packs, root cause, Rules engine, test rig, testing rig, the code documents itself, trade capture system, upstream, walk through, walkthrough, workflow
Comments Off on Not modelling your workflow? Here there be monsters!