The Python Lowracer is a bicycle project originally created by Jürgen Mages. The project is disseminated in an open source fashion through a web page (http://www.python-lowracer.de) a mailing list (http://www.freelists.org/list/python) and recently, a wiki (http://en.openbike.org/wiki/Main_Page).
Those resources include a list of individuals around the world that have created their own versions of the Python Lowracer. Many of those individuals have web pages describing their versions of the project (links available through the Python webpage).
The bicycle has many variations but there are some key features:
* Low seating position - user is seated at around the wheel axle height,
* Recumbent seating position - user's legs are forward and back is facing down,
* Front wheel drive,
* Center steering - the steering axle is behind the front wheel and below the rider,
* Negative trail - see Bicycle_and_motorcycle_dynamics, basically the wheel/steering axle relationship is opposite to that in a "standard" bicycle.
* Simplicity - linear frame joins the two wheels, drive train is very short, steering is performed by body motion
Those resources include a list of individuals around the world that have created their own versions of the Python Lowracer. Many of those individuals have web pages describing their versions of the project (links available through the Python webpage).
The bicycle has many variations but there are some key features:
* Low seating position - user is seated at around the wheel axle height,
* Recumbent seating position - user's legs are forward and back is facing down,
* Front wheel drive,
* Center steering - the steering axle is behind the front wheel and below the rider,
* Negative trail - see Bicycle_and_motorcycle_dynamics, basically the wheel/steering axle relationship is opposite to that in a "standard" bicycle.
* Simplicity - linear frame joins the two wheels, drive train is very short, steering is performed by body motion
Structure-Behavior Coalescence (SBC) architecture is the system architecture that demands the structure and behavior views must be integrated and coalesced. The core concept of SBC architecture is: “Architecture = Structure + Behavior.”
A system comprises multiple views such as planning, , design, implementation, deployment, structure, behavior, input data, and output data views. A system architecture is an integrated, holistic, united, coordinated, coherent, and coalescence system model of multiple views in which (A) a system comprises many components; (B) multiple views are derived from the interactions between these components; (C) multiple views are all contained in this model.
Since the structure and behavior views are the two most prominent ones among multiple views, integrating the structure and behavior views is the most appropriate method for integrating multiple views of a system. In other words, structure-behavior coalescence (SBC) results in integrating multiple views of a system.
SBC Architecture includes a) SBC architecture description language (SBC-ADL) and b) SBC architecture framework (SBC-AF).
Overview
A system comprises multiple views such as planning, requirement (analysis), design, implementation, deployment, structure, behavior, input data, and output data views. A system model is required to represent all these multiple views. The system model describes and represents the system multiple views possibly adopting two different approaches. The first one is the non-architectural approach and the second one is the architectural approach. The non-architectural approach respectively picks a model for each view. The architectural approach, also known as system architecture, instead of picking many heterogeneous and unrelated models, will use only one single coalescence model.
In general, multiple view coalescence (MVC) architecture is a synonym for system architecture. Since the structure and behavior views are the two most prominent ones among multiple views, integrating the structure and behavior views is the most appropriate method for integrating multiple views of a system. In other words, structure-behavior coalescence (SBC) results in the coalescence of multiple views. Therefore, SBC architecture is also a synonym for system architecture.
History
SBC architecture was created during the late-1980s by Dr. William S. Chao. The initial idea of SBC architecture comes from the calculus of communicating systems (CCS) and developed by Robin Milner.
Robin Milner used the CCS and <math>\pi</math>-calculus, mainly, for analyzing theoretical concurrency problems. Nevertheless, both CCS and <math>\pi</math>-calculus were magnificently appealing to Dr. Chao because of their superior ability to integrate the structure and behavior views of a system.
Since 1989, the year that the CCS book was published, Dr. William S. Chao has been working on a structure-behavior coalescence model which later successfully leads to the SBC architecture.
Topics in SBC architecture
Topics in SBC Architecture include a) SBC architecture description language (SBC-ADL) and b) SBC architecture framework (SBC-AF).
SBC Architecture Description Language (SBC-ADL)
SBC Architecture Description Language consists of six fundamental diagrams. These diagrams are: a) architecture hierarchy diagram, b) framework diagram, c) component operation diagram, d) component connection diagram, e) structure-behavior coalescence diagram, and f) interaction flow diagram.
Architecture Hierarchy Diagram
The architecture hierarchy diagram (AHD) enables architects to examine the multi-level decomposition and composition of a system. AHD is the first fundamental diagram to achieve structure-behavior coalescence.
Framework Diagram
The framework diagram (FD) enables architects to examine the multi-layer (sometimes referred to as multi-tier) decomposition and composition of a system. FD is the second fundamental diagram to achieve structure-behavior coalescence.
Component Operation Diagram
For a system, architects use the component operation diagram (COD) to display all components' operations. COD is the third fundamental diagram to achieve structure-behavior coalescence.
Component Connection Diagram
A component connection diagram (CCD) is utilized to describe how all components and actors are connected within a system. CCD is the fourth fundamental diagram to achieve structure-behavior coalescence.
Structure-Behavior Coalescence Diagram
The structure-behavior coalescence diagram (SBCD) enables architects to observe the integration of system structure and system behavior simultaneously. SBCD is the fifth fundamental diagram to achieve structure-behavior coalescence.
Interaction Flow Diagram
An interaction flow diagram (IFD) is utilized to describe each individual behavior of the overall system behavior. IFD is the sixth fundamental diagram to achieve structure-behavior coalescence.
SBC Architecture Framework (SBC-AF)
SBC Architecture Framework consists of: a) Two-Level SBC-AF for System Analysis and Design, and b) Multi-Level SBC-AF for General Purpose.
Two-Level SBC-AF for System Analysis and Design
In the two-level SBC-AF for system analysis and design, we categorize the system architecture into the following: a) owner’s architecture and b) designer’s architecture.
The owner’s architecture includes the owner’s six SBC fundamental diagrams. The designer’s architecture includes the designer’s six SBC fundamental diagrams.
Multi-Level SBC-AF for General Purpose
In the multi-level SBC-AF for general purpose, we categorize the system architecture into the following: a) planner’s architecture, b) owner’s architecture, c) designer’s architecture, and d) builder’s architecture.
The planner’s architecture includes the planner’s six SBC fundamental diagrams. The owner’s architecture includes the owner’s six SBC fundamental diagrams. The designer’s architecture includes the designer’s six SBC fundamental diagrams. The builder’s architecture includes the builder’s six SBC fundamental diagrams.
Applications of SBC architecture
Applications of SBC architecture include a) SBC hardware architecture, b) SBC software architecture, c) SBC enterprise architecture, d) SBC knowledge architecture, and e) SBC thinking architecture.
SBC Hardware Architecture
When applying SBC architecture to a hardware system, SBC architecture becomes the SBC hardware architecture.
SBC Software Architecture
When applying SBC architecture to a software system, SBC architecture becomes the SBC software architecture.
SBC Enterprise Architecture
When applying SBC architecture to an enterprise system, SBC architecture becomes the SBC enterprise architecture.
SBC Knowledge Architecture
When applying SBC architecture to a knowledge system, SBC architecture becomes the SBC knowledge architecture.
SBC Thinking Architecture
When applying SBC architecture to a thinking system, SBC architecture becomes the SBC thinking architecture.
A system comprises multiple views such as planning, , design, implementation, deployment, structure, behavior, input data, and output data views. A system architecture is an integrated, holistic, united, coordinated, coherent, and coalescence system model of multiple views in which (A) a system comprises many components; (B) multiple views are derived from the interactions between these components; (C) multiple views are all contained in this model.
Since the structure and behavior views are the two most prominent ones among multiple views, integrating the structure and behavior views is the most appropriate method for integrating multiple views of a system. In other words, structure-behavior coalescence (SBC) results in integrating multiple views of a system.
SBC Architecture includes a) SBC architecture description language (SBC-ADL) and b) SBC architecture framework (SBC-AF).
Overview
A system comprises multiple views such as planning, requirement (analysis), design, implementation, deployment, structure, behavior, input data, and output data views. A system model is required to represent all these multiple views. The system model describes and represents the system multiple views possibly adopting two different approaches. The first one is the non-architectural approach and the second one is the architectural approach. The non-architectural approach respectively picks a model for each view. The architectural approach, also known as system architecture, instead of picking many heterogeneous and unrelated models, will use only one single coalescence model.
In general, multiple view coalescence (MVC) architecture is a synonym for system architecture. Since the structure and behavior views are the two most prominent ones among multiple views, integrating the structure and behavior views is the most appropriate method for integrating multiple views of a system. In other words, structure-behavior coalescence (SBC) results in the coalescence of multiple views. Therefore, SBC architecture is also a synonym for system architecture.
History
SBC architecture was created during the late-1980s by Dr. William S. Chao. The initial idea of SBC architecture comes from the calculus of communicating systems (CCS) and developed by Robin Milner.
Robin Milner used the CCS and <math>\pi</math>-calculus, mainly, for analyzing theoretical concurrency problems. Nevertheless, both CCS and <math>\pi</math>-calculus were magnificently appealing to Dr. Chao because of their superior ability to integrate the structure and behavior views of a system.
Since 1989, the year that the CCS book was published, Dr. William S. Chao has been working on a structure-behavior coalescence model which later successfully leads to the SBC architecture.
Topics in SBC architecture
Topics in SBC Architecture include a) SBC architecture description language (SBC-ADL) and b) SBC architecture framework (SBC-AF).
SBC Architecture Description Language (SBC-ADL)
SBC Architecture Description Language consists of six fundamental diagrams. These diagrams are: a) architecture hierarchy diagram, b) framework diagram, c) component operation diagram, d) component connection diagram, e) structure-behavior coalescence diagram, and f) interaction flow diagram.
Architecture Hierarchy Diagram
The architecture hierarchy diagram (AHD) enables architects to examine the multi-level decomposition and composition of a system. AHD is the first fundamental diagram to achieve structure-behavior coalescence.
Framework Diagram
The framework diagram (FD) enables architects to examine the multi-layer (sometimes referred to as multi-tier) decomposition and composition of a system. FD is the second fundamental diagram to achieve structure-behavior coalescence.
Component Operation Diagram
For a system, architects use the component operation diagram (COD) to display all components' operations. COD is the third fundamental diagram to achieve structure-behavior coalescence.
Component Connection Diagram
A component connection diagram (CCD) is utilized to describe how all components and actors are connected within a system. CCD is the fourth fundamental diagram to achieve structure-behavior coalescence.
Structure-Behavior Coalescence Diagram
The structure-behavior coalescence diagram (SBCD) enables architects to observe the integration of system structure and system behavior simultaneously. SBCD is the fifth fundamental diagram to achieve structure-behavior coalescence.
Interaction Flow Diagram
An interaction flow diagram (IFD) is utilized to describe each individual behavior of the overall system behavior. IFD is the sixth fundamental diagram to achieve structure-behavior coalescence.
SBC Architecture Framework (SBC-AF)
SBC Architecture Framework consists of: a) Two-Level SBC-AF for System Analysis and Design, and b) Multi-Level SBC-AF for General Purpose.
Two-Level SBC-AF for System Analysis and Design
In the two-level SBC-AF for system analysis and design, we categorize the system architecture into the following: a) owner’s architecture and b) designer’s architecture.
The owner’s architecture includes the owner’s six SBC fundamental diagrams. The designer’s architecture includes the designer’s six SBC fundamental diagrams.
Multi-Level SBC-AF for General Purpose
In the multi-level SBC-AF for general purpose, we categorize the system architecture into the following: a) planner’s architecture, b) owner’s architecture, c) designer’s architecture, and d) builder’s architecture.
The planner’s architecture includes the planner’s six SBC fundamental diagrams. The owner’s architecture includes the owner’s six SBC fundamental diagrams. The designer’s architecture includes the designer’s six SBC fundamental diagrams. The builder’s architecture includes the builder’s six SBC fundamental diagrams.
Applications of SBC architecture
Applications of SBC architecture include a) SBC hardware architecture, b) SBC software architecture, c) SBC enterprise architecture, d) SBC knowledge architecture, and e) SBC thinking architecture.
SBC Hardware Architecture
When applying SBC architecture to a hardware system, SBC architecture becomes the SBC hardware architecture.
SBC Software Architecture
When applying SBC architecture to a software system, SBC architecture becomes the SBC software architecture.
SBC Enterprise Architecture
When applying SBC architecture to an enterprise system, SBC architecture becomes the SBC enterprise architecture.
SBC Knowledge Architecture
When applying SBC architecture to a knowledge system, SBC architecture becomes the SBC knowledge architecture.
SBC Thinking Architecture
When applying SBC architecture to a thinking system, SBC architecture becomes the SBC thinking architecture.
This page is dedicated to media related to Howling Bells, an indie rock band originally from Sydney, Australia, Made up of sister and brother Juanita Stein (vocals/rhythm guitar); and Joel Stein (lead guitar); Brendan Picchio (bass); and Glenn Moule (drums). Since their move to England in 2004 they have attained a level of moderate popularity, beginning with the release of their self-titled debut album, Howling Bells. Since that time they have released a second album, Radio Wars, and toured the world supporting platinum-selling artists including: The Editors; Placebo; The Killers; Snow Patrol; and Coldplay. Their third album is slated for release in 2011.
Television appearances (Australia)
* CD Live, Fox8 TV, Australia
:Live studio performance of Low Happening
:Broadcast 15th July 2006
Television appearances (UK)
* Album Chart Show, Channel 4 TV
:Filmed at KOKO, Camden, London, 23rd October 2006
:Broadcast 28th October 2006
* The JD Set, Channel 4 TV
:Filmed at The Cathouse, Glasgow, 8th December 2006
:Broadcast 17th February 2007
* 4-Play, Channel 4 TV
:Filmed at The Barfly, Camden, London, 23rd November 2006
:Broadcast 10th March 2007
* The JD Set, Channel 4 TV
:Filmed at The Cluny, Newcastle, 10th March 2009
:Broadcast 1st May 2009
Miscellaneous television
* Low Happening played on The OC, Season 3, Episode 13, 'The Pot Stirrer', track 6
* Various tracks from Radio Wars played on several episodes of Home and Away
* Juanita Stein appeared as a guest on Australian music-themed television quiz show Spicks and Specks, Episode 15, broadcast 16 May 2007
Live radio and web performances
* Live at Paradiso, Amsterdam, Netherlands, 1 April 2006, broadcast on 3voor12.vpro.nl (streaming feed)
* Live at Summer Sundae Festival, Leicester, UK, 12 August 2006, broadcast on BBC 6 Music, 2 October 2009
* Live at Summer Sundae Festival, Leicester, UK, 8 August 2008, broadcast on BBC 6 Music, 9 August 2008
* Live at Punk, Soho, London, UK, 7 March 2009, broadcast on NME Radio
Live radio and web sessions
UK
* BBC 6 Music with Gideon Coe, 1 December 2005
* BBC Radio 1 with Steve Lamacq, 10 April 2006
* XFM Radio, 23 April 2006
* BBC 6 Music with Tom Robinson, 18 May 2006
* Bradford Community Radio BCB 106.6FM with Albert Freeman, 9 August 2006
* BBC Radio 2 with Mark Radcliffe, 2 November 2006
* BBC 6 Music with Marc Riley, 8 March 2007
* BBC 6 Music with Marc Riley, 5 November 2008
* BBC 6 Music with Stephen Merchant, 7 December 2008
* BBC Radio 2 with Zoë Ball, 7 February 2009
* BBC 6 Music with George Lamb, 17 February 2009
* NME Radio, 10 March 2009
* Fly TV, 23 April 2009
Non-UK
* On The Pulse, Los Angeles, 5 October 2005
* 3voor12.vpro.nl, Behind Closed Doors, Amsterdam, 1 April 2006 .
* JTV, 31 March 2007
* Aligre FM Radio, Paris, 28 January 2009 .
* Today FM with Paul McLoone, Dublin, 10 July 2009 .
Radio and web interviews
* TripleJ (AUS, 2006).
* undercover.com.au (AUS, 2006).
* abc.net.au (AUS, 2006.
* Top Shelf TripleJ (AUS, 2006).
* In The Raw TV (AUS, 2007).
* videohits.com.au (AUS, 2007).
* rollingstone.com (USA, 2007)
* The Beat TV (AUS, 2007).
* fasterlouder.com.au (AUS, 2007).
* Music For Listeners (USA, 2007).
* fuzzed.tv (UK, 2008).
* rtrfm.com.au (AUS, 2009).
* QTheMusic.com (UK, 2009).
* nme.com (UK, 2009).
* futureradio 96.9FM (UK, 2009).
* The JD Set (UK, 2009).
* The Range on Radio Adelaide (AUS, 2009).
* Top Shelf TripleJ (AUS, 2009) .
* videohits.com.au (AUS, 2009).
* thecamdencrawl.com (UK, 2009).
* WTUL 91.5 New Orleans (USA, 2009) .
* youtellconcerts.com (USA, 2009) .
* musiomusic.com (UK, 2009) .
* rte 2FM (Ireland, 2009) .
* sapo.pt (Portugal, 2009) .
* Music For Listeners (USA, 2009).
* novaFM (AUS, 2009) .
* videohits.com.au (AUS, 2009) .
Television appearances (Australia)
* CD Live, Fox8 TV, Australia
:Live studio performance of Low Happening
:Broadcast 15th July 2006
Television appearances (UK)
* Album Chart Show, Channel 4 TV
:Filmed at KOKO, Camden, London, 23rd October 2006
:Broadcast 28th October 2006
* The JD Set, Channel 4 TV
:Filmed at The Cathouse, Glasgow, 8th December 2006
:Broadcast 17th February 2007
* 4-Play, Channel 4 TV
:Filmed at The Barfly, Camden, London, 23rd November 2006
:Broadcast 10th March 2007
* The JD Set, Channel 4 TV
:Filmed at The Cluny, Newcastle, 10th March 2009
:Broadcast 1st May 2009
Miscellaneous television
* Low Happening played on The OC, Season 3, Episode 13, 'The Pot Stirrer', track 6
* Various tracks from Radio Wars played on several episodes of Home and Away
* Juanita Stein appeared as a guest on Australian music-themed television quiz show Spicks and Specks, Episode 15, broadcast 16 May 2007
Live radio and web performances
* Live at Paradiso, Amsterdam, Netherlands, 1 April 2006, broadcast on 3voor12.vpro.nl (streaming feed)
* Live at Summer Sundae Festival, Leicester, UK, 12 August 2006, broadcast on BBC 6 Music, 2 October 2009
* Live at Summer Sundae Festival, Leicester, UK, 8 August 2008, broadcast on BBC 6 Music, 9 August 2008
* Live at Punk, Soho, London, UK, 7 March 2009, broadcast on NME Radio
Live radio and web sessions
UK
* BBC 6 Music with Gideon Coe, 1 December 2005
* BBC Radio 1 with Steve Lamacq, 10 April 2006
* XFM Radio, 23 April 2006
* BBC 6 Music with Tom Robinson, 18 May 2006
* Bradford Community Radio BCB 106.6FM with Albert Freeman, 9 August 2006
* BBC Radio 2 with Mark Radcliffe, 2 November 2006
* BBC 6 Music with Marc Riley, 8 March 2007
* BBC 6 Music with Marc Riley, 5 November 2008
* BBC 6 Music with Stephen Merchant, 7 December 2008
* BBC Radio 2 with Zoë Ball, 7 February 2009
* BBC 6 Music with George Lamb, 17 February 2009
* NME Radio, 10 March 2009
* Fly TV, 23 April 2009
Non-UK
* On The Pulse, Los Angeles, 5 October 2005
* 3voor12.vpro.nl, Behind Closed Doors, Amsterdam, 1 April 2006 .
* JTV, 31 March 2007
* Aligre FM Radio, Paris, 28 January 2009 .
* Today FM with Paul McLoone, Dublin, 10 July 2009 .
Radio and web interviews
* TripleJ (AUS, 2006).
* undercover.com.au (AUS, 2006).
* abc.net.au (AUS, 2006.
* Top Shelf TripleJ (AUS, 2006).
* In The Raw TV (AUS, 2007).
* videohits.com.au (AUS, 2007).
* rollingstone.com (USA, 2007)
* The Beat TV (AUS, 2007).
* fasterlouder.com.au (AUS, 2007).
* Music For Listeners (USA, 2007).
* fuzzed.tv (UK, 2008).
* rtrfm.com.au (AUS, 2009).
* QTheMusic.com (UK, 2009).
* nme.com (UK, 2009).
* futureradio 96.9FM (UK, 2009).
* The JD Set (UK, 2009).
* The Range on Radio Adelaide (AUS, 2009).
* Top Shelf TripleJ (AUS, 2009) .
* videohits.com.au (AUS, 2009).
* thecamdencrawl.com (UK, 2009).
* WTUL 91.5 New Orleans (USA, 2009) .
* youtellconcerts.com (USA, 2009) .
* musiomusic.com (UK, 2009) .
* rte 2FM (Ireland, 2009) .
* sapo.pt (Portugal, 2009) .
* Music For Listeners (USA, 2009).
* novaFM (AUS, 2009) .
* videohits.com.au (AUS, 2009) .
Joseph Marie Luguya is a Ugandan born accountant and author .
He is the author of Payment in Kind (1985) and The Gospel According to Judas Iscariot (2007) . This fictional work is a christian themed novel based on with themes dealing with Christianity and spirituality in Africa . Themes are drawn through a series of monologues that look at what Satan may have thought through the events surrounding the central character Mjomba. He has worked at the International Center for Research on Women and Cooperative Housing Foundation. He has lived and worked in Kenya, Uganda, Canada and now lives in the US.
Works
*Payment in Kind,novel (Kenya Literature Bureau) - 1985
He is the author of Payment in Kind (1985) and The Gospel According to Judas Iscariot (2007) . This fictional work is a christian themed novel based on with themes dealing with Christianity and spirituality in Africa . Themes are drawn through a series of monologues that look at what Satan may have thought through the events surrounding the central character Mjomba. He has worked at the International Center for Research on Women and Cooperative Housing Foundation. He has lived and worked in Kenya, Uganda, Canada and now lives in the US.
Works
*Payment in Kind,novel (Kenya Literature Bureau) - 1985