Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
Transcript of Systems Architecture
Diagram Fault Handling Components Central Component Runtime Platform Model Distributed Vending Machine Restocking System Important! drivers... Keeping costs down
Prompt fault reporting
Redundancy 3G cheaper than
paying for the
@ each location Less downtime,
more profit!!! Two (or more)
is better than one the better one Summary We could
View Model 3G Load Balancing 5000 vending machines,
needs some clever
balancing act Just move the machine New machine? Moving machine? Just plug in the power Data
Replication In batches
Head office might not need all state office data instantly copy Architectural
Decisions Added more traceability so key diagrams/sections of the document would easily refer back to the requirements. Perhaps looked at existing 3rd party alternative solutions that would help with a certain component of our architecture such as data replication, fault handling Network Diagram Stock management components Sequence Diagram Architecture Overview State office Head office External Since our solution included the usage of pings to verify whether or not the machines were operational, there are room for inaccuracy or false positives Issues with the solution Lessons
Learned Why we need to design and document an architecture Traceability (blame) Risk management Communication
(still needs work!)