Paschall's_9-1_Final
.docx
keyboard_arrow_up
School
Southern New Hampshire University *
*We aren’t endorsed by this school
Course
620
Subject
English
Date
Dec 6, 2023
Type
docx
Pages
17
Uploaded by jzpaschall
1
9-1 Final Project: Systems Engineering Case Study Report
James Z. Paschall
Global Campus, Southern New Hampshire University
EMA 610: System Thinking for Engineering
Professor Raymond Sheen
November 19, 2023
2
Case Study
The Hubble Case Study is the chosen subject for this analysis, providing an in-depth
exploration of the entire lifecycle and operational challenges experienced during the launch of
the Hubble Space Telescope (HST). The study delves into crucial aspects such as the required
support, both technical and physical, to ensure the telescope's successful operation within the
desired service timeframe. It highlights the benefits and significant contributions the Hubble
provided to humankind, along with the planning, validation, and risk management processes
involved.
The reason for selecting this particular case study stems from its departure from my usual
reading materials, offering a captivating exploration outside of my usual scope. Remarkably, it
evokes nostalgia and curiosity about the wonders of space, reminding me of a time when things
seemed effortless. Delving into the US government's management of a project of this magnitude,
and observing how they navigated failures while remaining dedicated to the project's ultimate
success, adds an additional layer of fascination.
Furthermore, this case study propels my interest in fully comprehending the significant
contributions the Hubble Telescope made to society. While most of us are familiar with the
telescope itself, understanding its development process and the groundbreaking discoveries it
enabled is a topic worth exploring. The final project aims to analyze the system's lifecycle,
elaborating on the development, deployment, and future prospects of the HST. Additionally, it
will examine the specific project requirements, including stakeholder input, elicitation methods,
engineering specifications, and project management, while also considering the tradeoffs
involved.
3
Systems Life-Cycle: Development
The development process of this project revolved around a set of key activities and
products. It all started with Process Inputs, which encompassed customer needs, objectives, and
requirements, as well as the existing Technology Base, output requirements from previous
development efforts, program decision requirements, and specifications and standard
requirements. This step played a crucial role in guiding the subsequent phases.
After gathering and analyzing the necessary inputs, the team proceeded with a Requirements
Analysis to determine the project's scope. This analysis helped them understand the various
components and functionalities that needed to be incorporated. Following this, a functional
analysis was conducted to delve deeper into the project's building structure. This analysis formed
the foundation for building the Hubble Space Telescope.
For a visual representation of the project's overall system, please refer to Figure 1.
Figure 1
4
With the high-profile nature of the project at hand, my expectations were set on an
extraordinary level of systems life-cycle planning. However, upon delving into the case study, I
discovered that even at the prestigious NASA level, they still adhere to the fundamental
principles. It became apparent to me that certain best practices were overlooked, such as a clear
team structure with well-defined product deadlines. Surprisingly, these crucial elements were
nowhere to be found in the case study, although one would assume they must have existed
considering the client involved. Another observation I made was the absence of the use of "shall"
or any other formal language in the defined requirements. It's possible that this was influenced
by the classification of the documents. As anticipated, the project emphasized the importance of
maintaining meticulous and comprehensive records.
Systems Life-Cycle: Deployment
As the Hubble telescope was being assembled, valuable lessons were learned along the
way. The process involved sub-assembling various components in different locations, which
were then brought together at the main site. However, the early stages of the program lacked
proper definition, and initially, the user community wasn't effectively engaged. (Mattice, 2005, p.
6). The Hubble project boasted a multitude of organizations providing funding and contributing
to its development. In such a complex endeavor, it was crucial to prioritize the technical aspects
over anything else. This led to the motto, "Keep it technical, stupid!" (Mattice, 2005, p. 6).
Despite the valuable experience gained from the Apollo program and the need for well-defined
collaboration, this lesson was unfortunately not fully implemented in the Hubble project. With
two main contractors involved, each brought their own expertise to the table. However, there
were instances where Lockheed, the primary contractor, relied too heavily on their own
knowledge, overlooking the valuable insights of Perkin-Elmer.
5
Systems Life-Cycle: Future
The United States Space Program has a rich history of launching shuttles into space for
various missions, including maintenance tasks on the iconic Hubble telescope. One of the most
memorable missions was the STS-61, where awe-inspiring spacewalks were televised for the
world to witness. During this mission, courageous astronauts skillfully replaced sensors and
electronic components, ensuring the Hubble's continued operation. While software diagnostics
and repairs can be conducted remotely from ground control using satellite communications,
certain damages require the expertise and resources of a shuttle launch. Interestingly, with the
recent surge in billionaire-backed ventures into space, such repairs are becoming less
extraordinary. This fascinating development signifies a shift in the landscape of space
exploration. The Hubble telescope has already surpassed its initial service target of 15 years,
thanks to the dedicated efforts of the shuttle missions to maintain and update its capabilities.
However, there will come a time when the Hubble will be decommissioned. In preparation for
this, NASA plans to deorbit and dispose of the telescope in a responsible manner. Considering
the rapid advancements in technology and our ever-growing curiosity about the vastness of
space, it is highly likely that a replacement for the Hubble will be designed and launched in the
not-too-distant future. However, the process of creating and deploying a new space telescope is
expected to undergo significant changes. The emergence of fierce competition among private
entities has transformed the landscape, turning it into another thrilling race to conquer the
cosmos.
Elicitation
Much to my surprise, the ambitious HST project faced a rocky start, with its success
hinging on input from political, governmental, and institutional figures. Just take a look at figure
6
one for a glimpse of the intricate program interfaces. According to Mattice (2005), in its early
stages, the program suffered from unclear mechanisms and a divided user community, leading to
a lack of engagement in defining and advocating for the program. Among the key players in the
HST program were astronomers and the Department of Defense (DOD). Initially, they held
vastly different perspectives on the project's needs and system requirements. It wasn't until
several months into the endeavor that they finally found common ground. According to Mattice
(2005), both parties shared a desire to harness cutting-edge technology to observe distant objects,
albeit with different intentions - one for exploring space and the other for wartime "spying." This
convergence laid the foundation for the project's objectives: a remarkable lifespan of 15 years,
punctuated by service intervals of 2.5 years. Throughout the years, the HST's lifecycle has been
extended through numerous enhancements installed in space, ensuring its continued impact.
Figure One: Program Interfaces
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help