Report (M.S.)--Virginia Polytechnic Institute and State University. M.S. 1992. / Abstract. Includes bibliographical references (leaf 84). Also available via the Internet.

Thesis (M.S.)--Virginia Polytechnic Institute and State University, 1993. / Vita. Abstract. Includes bibliographical references (leaves 58-63). Also available via the Internet.

Thesis (M.S. in Astronautical Engineering)--Naval Postgraduate School, June 2010. / Thesis Advisor(s): Newman, James H. ; Romano, Marcello. "June 2010." Description based on title screen as viewed on July 14, 2010. Author(s) subject terms: 1U, COTS, CubeSat, CubeSat Kit, Falcon 1e, Integration, I-V Curve, NPS-SCAT, Naval Postgraduate School, P-POD, Printed Circuit Board, Satellite, Space Shuttle, Solar Cell, Solar Cell Array Tester, Space Systems, Sun Sensor, Systems Engineering, Temperature Sensor, Testing, Thermal Vacuum. Includes bibliographical references (p. 153-161). Also available in print.

Thesis (M.S. in Systems Engineering)--Naval Postgraduate School, March 2010. / Thesis Advisor(s): Goshorn, Rachel ; Goshorn, Deborah. Second Reader: Stevens, Mark. "March 2010." Description based on title screen as viewed on April 26, 2010. Author(s) subject terms: Systems Engineering, Facial Recognition, Force Protection, Pier Security, Mustering Includes bibliographical references (p. 77-79). Also available in print.

Thesis (Ph. D.)--University of Wisconsin--Madison, 1969. / Typescript. Vita. eContent provider-neutral record in process. Description based on print version record. Includes bibliographical references.

Thesis--Wisconsin. / Vita. Includes bibliographical references (leaves 187-191).

Thesis (M.S.)--University of Wisconsin--Madison. / Typescript. eContent provider-neutral record in process. Description based on print version record.

We have problem areas which are beyond the scope of a discipline, but we are generally educated in just a single discipline. I explored our philosophy of work to see how we became disciplinary, where the disciplines came from, what philosophy underlies our way of working, and what philosophy underpins work that is beyond the scope of a discipline. The underlying philosophy leads to the research question. My hypothesis is that a systems engineer can create a model which networks the disciplines using constructs from philosophy, the tiers of disciplines in transdisciplinarity, and systemic and holistic thinking. This will provide a way of working on problem situations which transgress the boundary of a discipline. Using constructs from philosophy, the methods of the philosophers, hermeneutics, systems thinking and soft systems methodology I proceeded to create a conceptual model and showed conceptual examples of how to use the model. The client for the model is the interdisciplinary researcher who is seeking a way of working to manage problem areas that transgress disciplinary boundaries. The recommendation is made for using critical, systemic and holistic thinking and a network model of disciplines to manage our approach to problem situations which are beyond the scope of a discipline. The model is developed in the incremental sequence: disciplinary, multidisciplinary, interdisciplinary, transdisciplinary and gets as far as catering for tiers of disciplines (one aspect of the large and complex field of transdisciplinarity). Therefore, the model is suitable for interdisciplinary research, but can be developed further in future projects. The importance of the model is that it provides a practical way of working to manage problem situations which transgress disciplinary boundaries whilst accessing the expertise of disciplined practitioners. The model can find wide applicability. It is not necessary for the user of the model to be comfortable with the abstract philosophy used to create it. Users will need the will for uncoerced mutual understanding or free communication, along with their disciplinary expertise. The reader of the dissertation however should be comfortable with abstractions such as ideas about reality and actuality, form and class, subject and object, truth and justice, truthfulness and functional fit. Future work may reduce the method to practice in the academy and extend the method to bridging silos in learning organisations in the workplace. The work was conducted independently, and an original model was created.

At the Boeing Satellite Development Center, all programs must follow the same test flow through the factory. First the units are built, tested, and delivered for sub system level integration. There are units built for the bus module and units built for the payload module. Both sub systems are built in different locations and have their own core teams. Once the sub systems are properly integrated, they will then travel to the next test phase of the factory which is known as Integrated Vehicle Testing (IVT). During IVT, both the bus and payload modules are integrated to make one system. This system will travel through the factory and will be tested to make sure that all requirements are met. Once all requirements are validated and verified, the spacecraft is now ready for launch and delivery to the customer. There are hundreds of tests that need to take place throughout the spacecrafts life in the factory. The purpose of these tests is to make sure that a requirement from the customer is met one way or another. Thousands of man hours are budgeted for testing the satellite during its journey through the factory. At an average engineering cost of $200 per hour, this total dollar value for requirements validation and verification can get very expensive. One of the tests in particular is called "Harness Shakedown." This test is conducted to make sure that all the harness wiring in the bus module is wired correctly per the released wire list. These wires can be used for telemetry and control, power to units, signal wires, etc. The way that the test is currently conducted is all done manually using break out boxes, break out cables, digital volt meters, and power supplies. This is an inefficient way of doing the test. This test can be leaned out using systems engineering practices and finding better ways for doing this test to bring value to the customer. The most expensive cost to a program is engineering labor. Systems engineering can help in this test by using the systems engineering process milstd- 499B. This will be used to ensure that the requirements are good and can be fulfilled through the new way of testing. Lean systems engineering will play a large role in finding waste in the test and how to eliminate this non-value added waste. Understanding risk that can occur and ways to manage that risk, is key when fulfilling these requirements. Performing trade studies on how to do this test will help in making the proper engineering decision for the best way of doing the test while again, focusing on added value to the program.

No description available.