120 likes | 237 Views
What is a system anatomy ?. By Kristian Sandahl. Example: Local bus card reader. Sell tickets. Show balance. Registrer travel. Chose ticket. and. Capability , aka Anatom aka Function group. User buttons. Display. Read RFID. Check balance. Deduct money. Check validity.
E N D
What is a system anatomy? By Kristian Sandahl
Example: Local bus card reader Sell tickets Show balance Registrer travel Chose ticket and Capability, aka AnatomakaFunction group User buttons Display Read RFID Check balance Deduct money Check validity Communicate with server Dependency Power supply
Layout of an anatomy Sell tickets Show balance Registrer travel Chose ticket Functions to sell to the customer User buttons Display Read RFID You work your way up to the top Check balance Deduct money Check validity Communicate with server Most fundamentalcapability Power supply
What is a system anatomy? • A directed, acyclic graph of functional capabilities from a usage perspective • A common understanding of a large product • Aligns the co-workers’ inner pictures of the system • A means for communication • A means for decision making • A basis for integration planning • A basis for project planning • A social accomplishment • It is not an exact, unique, formal description • Works in both agile and stage-gate project models • Term coined by Jack Järkvik in early 1990’s
Example: Organic integration plan Sell tickets Show balance Registrer travel Chose ticket Services User buttons Display User interface Read RFID Check balance Deduct money Server functions Check validity Communicate with server Communication Hardware and supply Power supply
Example: Twist the figure for a development plan Hardware and supply Communication Services User interface Server functions Check balance Sell tickets Read RFID Communicate with server Deduct money Power supply Chose ticket User buttons Check validity Display Administrative info Show balance Registrer travel Time
Example: Use colour code for progress tracking Sell tickets Show balance Registrer travel Chose ticket Delivered On track User buttons Display At risk Read RFID Late Not started Check balance Deduct money Check validity Communicate with server Power supply
Anatomiför en telekom-processor SFC SW (33) MAS fault MAS Fault handling SFC handling SFC (HW) (SW) (33) (33) AXE Parameter MIP for SFC LA for SFC CPS - SW (20, 30, (33) (SW) (33) 33) MAS Fault handling capacity Serial RP bus at MIP I - test for (HW)(33) FC (20, 30, 33) SFC (33) SFC APS (33) No Stop Copy FCSUC with new AXE Parameter (20, 30) FURAX interface IPU HW for DBS - SW (20, 30, (20, 30, 33) SFC (33) Loading 33) Communication Communication functions buffer (Restart) buffer CPS - SW MAS fault handling (SW) (33) (30, 33) (20) capacity (SW) (33) MIP Support for No Backup in 212 Stop Copy (20) 33 SYREI, Initiated reload (30, 33) AXE Parameter Increase number of Parallel Start APS (20, 30, 33) blocks to 4K (SW) (33) APS Support for (30, 33) Communication Test/ Measurement buffer (20, 30, (SW) (33) 33) OCS over IPNA MAS CPT for (30, 33) capacity (33) IPNA Error handling (30, 33) CPS Kernel (SW) (33) MAS (SW) 100 Mbit Ethernet termination in 212 30 Start - Up , Single CP (33) CPT Initiate reload Initial load (33) (30, 33) MAS (SW) Increase of MIP Program store (30, 33) CP Reload from IPNA (30, 33) Originator: Lars TaxénLinköpings Universitet IPNA Load from AP (30, 33) Create Initial dump (33) MIP for Capacity De - Compress (33) dump in CP (20, 30, 33) MIP I - test for IPNA (30, 33) MIP I - test for IPNA Start Compress dump Capacity (33) DSU HW (30, 33) in I/O (IO 20, (30, 33) 30, 40) IPU HW for APG 40 Capacity (33)
How do we create an anatomy? • All participants bring functional requriement material • Work in teams of max 12 people, compare and negotiate results periodically • Identify function groups as anatoms • Brainstorm with yellow stickers • One sheet-of-paper => 30-60 anatoms • Check soundness Originator: Joakim Pilborg,KnowIT
Check soundness • Alignment with use-case model (if any) • Alignment with architecture • Money-making functions at top • Fundamental functions at bottom • Integration and test realistic • Some more notations: A Outstanding questionregarding dependency between A and B >=1 A B B A and B depends on each other OR-symbol
Grounding • Strong experience base • Theoretical evaluation in: Taxén, L. and Lilliesköld, J. (2008). Images as action instruments in complex projects, International Journal of Project Management, 26(5), 527-536. DOI: doi:10.1016/j.ijproman.2008.05.009