The System Anatomy1968 - 1983 Developer Methods and Tools Ericsson AB 1983 - 1989 Line manager CAD...

22
The System Anatomy Lars Taxén, Linköping University [email protected] www.neana.se www.neana.se

Transcript of The System Anatomy1968 - 1983 Developer Methods and Tools Ericsson AB 1983 - 1989 Line manager CAD...

  • The System AnatomyLars Taxén, Linköping University

    [email protected]

    www.neana.sewww.neana.se

  • 1968 - 1983 Developer Methods and Tools Ericsson AB1983 - 1989 Line manager CAD Transmission Ericsson AB1989 - 1990 Department Spec. CAD Transmission Ericsson AB1990 - 1990 Project Manager VHDL Pilot project Ericsson AB1990 - 1994 Process Designer HW Ellemtel AB1994 - 1995 Technical Manager HW Ellemtel AB1995 - 1996 Process Designer SW & HW Ellemtel AB1996 - 1998 Method Developer SW Ericsson AB1998 - 2000 Technical Manager PLM Ericsson AB2001 - 2002 Information System Coordinator Ericsson AB

    Who am I?

    34 yrs

    2001 - 2002 Information System Coordinator Ericsson AB2002 - 2003 Process Developer PLM Ericsson AB-----------------------------------------------------------1998 - 2003 PhD studies Linköping University2003 - 2007 Associated Senior researcher Linköping University2007 - Associate professor Linköping University--------------------------------------------------------------------2003 - Consultant, Lars Taxén Consulting AB

    Siemens, Sandvik, Huawei, and others

    13 yrs

    8 yrs

  • Motivation for the System

    AnatomyAnatomy

  • Project failures

    “About 20 percent of IT projects are canceled

    before completion and less than a third are

    finished on time and within budget with

    expected functionality” (Standish Group,2004)

    “If failure teaches more than success, then the

    IT profession must be developing an army of IT profession must be developing an army of

    brilliant project managers” (Nelson, 2007)

    “Insanity: doing the same thing over and over

    again and expecting different results.” —Albert

    Einstein

  • The system to be to be

    developed is invisible!

    • ….• Design/ Build Hubble Window• Construct Hardware• Design / build Mission Control Table• ….

  • The System Anatomy

    - Visualizing contemporary “mammoths”- Visualizing contemporary “mammoths”

  • What capabilities are needed

    and how do they depend on each other ?and how do they depend on each other ?

  • Some examples from Ericsson

  • The telecom network

    Network AccessPoints

    Wide-bandBackbone

    LAN

    ServiceProviders

    LAN

    ExchangeExchange

    Router

  • DCHMulti code

    DCHPower control

    DCH Synchronization

    DCH User data process

    Cell capacitysupervision

    DCH connectionsupervision

    SW upgradeduring traffic

    Soft handover

    SMSbroadcast

    Fast congestioncontrol

    Hard handover

    Softerhandover

    RACH Transportchannel

    FACH/RACHconnection

    FACHProcess user data

    FACH Ack.

    Traffic connection

    Call path tracing

    Fast power control

    Single DCHradio link

    DCHSingle code

    PCH Power control

    PCH User data processBCCH User

    data process

    Multi DCH Radio link

    AAL5/IP packaging and encapsulating

    IP support

    HW/SW info

    Start MMI

    Element managementplatform

    Operation and Management

    Java executionplatform

    FACH Power control RACHsetup/release

    Iub data stream setup/release

    BCCH Power control

    FACHsetup/release

    FMsupport

    Node connection control

    PM support

    Distributed OS

    SW keyhandling

    AAL5 layer

    AAL2 networkconnection control

    SAAL layer

    De-block HW(incl. Self test)

    RX diversion

    PCH setup/release

    System upgrade

    Scalableexecution

    LED handling

    Power on

    Application hookLocal execution platform

    CMsupport

    DCHsetup/release

    AAL2 layer

    Network synch.incl. Distr.

    Cell processing setup/release

    Resource autoconfiguration

    Physicalline

    termination

    ApplicationSW load

    PCH Power control

    Cell measurementreport to RNC

    Nodesynch.

    BCCH setup/release

    Setup of RBS/RNC control link

    BCCH Power control

  • DCHMulti code

    DCHPower control

    DCH Synchronization

    DCH User data process

    Cell capacitysupervision

    DCH connectionsupervision

    SW upgradeduring traffic

    Soft handover

    SMSbroadcast

    Fast congestioncontrol

    Hard handover

    Softerhandover

    RACH Transportchannel

    FACH/RACHconnection

    FACHProcess user data

    FACH Ack.

    Traffic connection

    Call path tracing

    Fast power control

    Single DCHradio link

    DCHSingle code

    PCH Power control

    PCH User data processBCCH User

    data process

    Multi DCH Radio link

    AAL5/IP packaging and encapsulating

    IP support

    HW/SW info

    Start MMI

    Element managementplatform

    Operation and Management

    Java executionplatform

    FACH Power control RACHsetup/release

    Iub data stream setup/release

    BCCH Power control

    “The most important thing when

    working with complex system is

    to manage dependencies”

    Jack Järkvik

    FACHsetup/release

    FMsupport

    Node connection control

    PM support

    Distributed OS

    SW keyhandling

    AAL5 layer

    AAL2 networkconnection control

    SAAL layer

    De-block HW(incl. Self test)

    RX diversion

    PCH setup/release

    System upgrade

    Scalableexecution

    LED handling

    Power on

    Application hookLocal execution platform

    CMsupport

    DCHsetup/release

    AAL2 layer

    Network synch.incl. Distr.

    Cell processing setup/release

    Resource autoconfiguration

    Physicalline

    termination

    ApplicationSW load

    PCH Power control

    Cell measurementreport to RNC

    Nodesynch.

    BCCH setup/release

    Setup of RBS/RNC control link

    BCCH Power control

  • Anatomy for one node in the 3G mobile network

  • How to use the System Anatomy

  • Example: Local bus card reader

    Sell tickets Registrer travel

    Chose ticket

    Display

    Show balance

    User buttons

    Originator:

    Kristian Sandahl, Linköping University

    Power supply

    Read RFID

    Check balanceCheck validity

    Communicate

    with server

    Deduct money

  • Integration plan

    Sell tickets Registrer travel

    Chose ticket

    Display

    Read RFID

    Show balance

    User buttons

    Services

    User interface

    Read RFID

    Check balance

    Check validity

    Communicate

    with server

    Deduct money

    Power supply

    Server functions

    Communication

    Hardware and supply

  • Twist the figure for a development plan

    Sell tickets

    Chose ticket

    Read RFIDCheck balance

    Communicate

    with serverDeduct moneyPower supply

    User buttons

    Services User interface Server functionsCommunicationHardware

    and supply

    Registrer travel

    DisplayCheck validity

    with server

    Show balance

    User buttons

    Time

    Administra

    tive info

  • Use color code for progress tracking

    Sell tickets Registrer travel

    Chose ticket

    Display

    Read RFID

    Show balance

    User buttons

    Delivered

    On track

    At risk

    LateRead RFID

    Check balance

    Check validity

    Communicate

    with server

    Deduct money

    Power supply

    Late

    Not started

  • 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 capabilities

    • Brainstorm with yellow stickers• Brainstorm with yellow stickers

    • One sheet-of-paper => 30-60 anatoms

    • Check soundness

    Originators:

    Joachim Pilborg, KnowIT

    Erik Lundh, Compelcon AB

  • So, what is a system anatomy?

    • An image of a system

    • A common understanding of a large and complex 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

  • For the curious

    To be published on June 6th

    INCOSE “tour” autumn 2011-Lund

    -Linköping-Linköping

    -Göteborg

    -Stockholm

    More info to come at http://www.incose.se/

    Lars Taxén: [email protected]

    Jens Fredholm: [email protected]