EUS-1: connect a student design to its evidence

Egyptian Universities Satellite 1, or EUS-1, appears in a Benha University faculty CV as a 2017 undergraduate design-and-development graduation project involving three students. This is direct evidence of academic work under that name. The January 2019 document does not report a launch, so the introduction treats EUS-1 as a documented development project rather than assigning it an unsupported orbital history.

This limited record still opens a useful engineering question: what must a student project hand over to become part of a larger mission? A design can be valuable before flight, but the recipient needs to know which configuration — open definition was built, which requirements were tested and which assumptions remain. A project title identifies an effort; it is not a substitute for those technical records.

Imagine an invented interface — open definition that accepts a component between 99.5 and 100.5 millimetres in width. A drawing specifies 100.0 millimetres. A manufactured example measures 100.7 millimetres, with measurement uncertainty — open definition small compared with the 0.2-millimetre excess. The drawing meets the nominal target, but the measured example lies outside the allowed interval. The team must investigate the hardware and measurement instead of reporting the drawing as the test result.

The acceptance decision also depends on a stated measurement procedure. Where was the width measured, at what condition and with which instrument? If the uncertainty were large enough to cross the limit, the simple pass-or-fail conclusion would require more care. This example is not an EUS-1 specification. It illustrates why design intent and evidence from a particular manufactured item must remain linked but distinct.

A drawing is not a measurement

An illustrative student handover might include the design revision, parts list, interface description, test setup and unresolved issues. A new team should be able to identify which result belongs to which item. If a board is replaced after testing, preserve the earlier results and record the change; then determine which tests remain applicable. Pretending the configuration never changed would make the evidence difficult to trust.

Likewise, historical reporting needs a trail from each claim to an appropriate source. A graduation-project record supports the existence and academic setting of design work. A launch-provider record would address launch, and operations records would address later behavior. These stages can be connected when evidence exists. Keeping them distinct recognizes student engineering without exaggerating its demonstrated outcome or dismissing useful work solely because flight is not established here.