Computer science

Starfleet

Design philosophy

• 24th century computer programming seemingly built modularly rather than low-level coding for 99% of design
  • Individual modules known as "subroutines", hard-built functions with specific input and output hooks
  • Can be individually enabled/disabled
    • When disabled, message-passing simply passes through rather than interrupting program flow
  • Manipulating functionality of an existing program thus consists of adding, deleting, enabling, or disabling individual subroutines rather than engaging in raw code
    • Possibly a factor of code density and/or safety? By using individual, expansively complex modules that have been formally verified, code errors can be reduced to a minimum
    • New subroutines could still be designed as needed (and described), inserted, but with potentially less effectiveness or errors
    • On many occasions, due to complexity of overall system, individual subroutines will be installed on individual removable storage elements, allowing for quick coding of new subroutines to replace existing in order to modify overall functioning (TNG: "The Naked Now")

History

S/COMS

• First major iteration of Starfleet operating system (ENT)
  • Short for "Spacecraft Operating & Management System" (Star Trek Encyclopedia)
  • Originates from Earth Starfleet software
• In use throughout Earth Starfleet vessels by 2140s (ENT: "First Flight")

PCAP-SYS

• Second major iteration of Starfleet operating system (Star Trek, Star Trek: Into Darkness)
• Largely a re-implementation of S/COMS for duotronic hardware, with associated UI modifications (TNG Novel: Immortal Coil; S31 Novel: Control)
  • Software directly ported where possible (TNG Novel: Immortal Coil; S31 Novel: Control)

LCARS

• Third major iteration of Starfleet operating system (Star Trek V: The Final Frontier; TNG; DS9; VOY)
  • Short for "Library Computer Access and Retrieval System"
• Largely a re-implementation of PCAP-SYS to properly take advantage of isolinear functionality, with associated UI modifications (TNG Novel: Immortal Coil; S31 Novel: Control)
  • Software directly ported where possible (TNG Novel: Immortal Coil; S31 Novel: Control)
• First Starfleet implementations deployed mid-2340s
  • Presumptive given lack of usage on Enterprise-C per "Yesterday's Enterprise"
  • Civilian version released by mid-2350s (VOY: "The Raven")