CERN Accelerating science

This website is no longer maintained. Its content may be obsolete. Please visit for current CERN information.

LSA [LHC Software Architecture] Controls Project 

The project aims to provide homogenous application software to operate the SPS, its transfer lines, and the LHC. It is using object oriented analysis and design, and Java based development  for implementation. Philosophy.   Scope

[Key technology in use: Java, Spring, Oracle, CVS, JUnit, Eclipse IDE]



LSA Requirements Planning
Team Members  SPS requirements - Overview Work packages Q1 2008
Application deployment LHC requirements - LHC software analysis
LSA DEV CENTRE TI8 requirements  
LSA Products Injection test/first turn requirements  
LSA Wiki LHC commissioning with beam requirements
Optics measurements
Commissioning phases

LSA review June 08

Brief LSA review November 2007 Meeting 34 of the LHCCWG



Milestones 2007
Deployment 2007
Workpackages second half 2007
Workpackages first quartrer 2007


2005:  Objectives 2005  Issues Q4 2005   Issues Q3 2005   Issues Q1 2005

2004:  TI8 Test  Issues Q3 2004    Issues Q2 2004     Issues Q1 2004    Goals 2004    

2003:  Milestones first half 2003   Ongoing 2003 (excel)    TT40 extraction test  

2002:   First half 2003    Second half 2002    First half 2002  Activities 2002  

Reviews & recent presentations


Applications & Issues




LSA philosophy

here are certain characteristics that are common to all clean, well-architected applications. Features such as modular design, good separation of concerns, loose coupling, and high cohesion � behaviour in one and only one place within an application � are all well-established best practices. Writing applications with testability in mind tends to lead to systems that display these characteristics. For instance, focusing on the ease of black- and white-box testing of individual modules is a sure-fire way to generate cleanly separated functional units. Saying that a module is easy to unit test is the same as saying we know exactly what the module should d, under what circumstances, and that we know (and can prove) its boundary behaviour. Saying that a module is easy to integration tests implies that it is easy to deploy and configure. .

--Dan North, Java Developer's Journal, January, 2004, p. 36

Spring and the English Archer