Development of an infrared imaging system for the surface tension driven convection experiment

An infrared imaging system is used to quantify the imposed surface temperature distribution along a liquid/gas free surface in support of the Surface Tension Driven Convection Experiment, a planned Space Transportation System flight experiment. For ground-based work a commercially available instrument was used to determine the feasibility of using the type of imaging system for this experiment. The ground-based work was used as a baseline for compiling specifications for a flight qualified imager to be designed, fabricated, tested and qualified for flight. The requirements and specifications for the flight model are given along with the reasons for departures from the ground-based equipment. The flight qualification requirements discussed are a representative sample of the necessary procedures which must be followed to flight qualify diagnostic equipment for use aboard the STS. The potential problems and concerns associated with operating an imaging system in orbit are also discussed

CVT/GPL phase 3 integrated testing

The hardware for 20 candidate shuttle program life sciences experiments was installed in the GPL and experiments were conducted during a 5-day simulated mission. The experiments involved humans, primates, rats, chickens, and marigold plants. All experiments were completed to the satisfaction of the experimenters. In addition to the scientific data gathered for each experiment, information was obtained concerning experiment hardware design and integration, experiment procedures, GPL support systems, and test operations. The results of the integrated tests are presented

Real world evaluation of aspect-oriented software development : a thesis submitted in partial fulfilment of the requirements for the degree of Master of Science in Computer Science at Massey University, Palmerston North, New Zealand

Software development has improved over the past decade with the rise in the popularity of the Object-Oriented (OO) development approach. However, software projects continue to grow in complexity and continue to have alarmingly low rates of success. Aspect-Oriented Programming (AOP) is touted to be one solution to this software development problem. It shows promise of reducing programming complexity, making software more flexible and more amenable to change. The central concept introduced by AOP is the aspect. An aspect is used to modularise crosscutting concerns in a similar fashion to the way classes modularise business concerns. A crosscutting concern cannot be modularised in approaches such as OO because the code to realise the concern must be spread throughout the module (e.g. a tracing concent is implemented by adding code to every method in a system). AOP also introduces join points, pointcuts, and advice which are used with aspects to capture crosscutting concerns so they can be localised in a modular unit. OO took approximately 20 years to become a mainstream development approach. AOP was only invented in 1997. This project considers whether AOP is ready for commercial adoption. This requires analysis of the AOP implementations available, tool support, design processes, testing tools, standards, and support infrastructure. Only when AOP is evaluated across all these criteria can it be established whether it is ready to be used in commercial projects. Moreover, if companies are to invest time and money into adopting AOP, they must be aware of the benefits and risks associated with its adoption. This project attempts to quantify the potential benefits in adopting AOP, as well as identifying areas of risk. SolNet Solutions Ltd, an Information Technology (IT) company in Wellington, New Zealand, is used in this study as a target environment for integration of aspects into a commercial development process. SolNet is in the business of delivering large scale enterprise Java applications. To assist in this process they have developed a Common Services Architecture (CSA) containing components that can be reused to reduce risk and cost to clients. However, the CSA is complicated and SolNet have identified aspects as a potential solution to decrease the complexity. Aspects were found to bring substantial improvement to the Service Layer of SolNet. applications, including substantial reductions in complexity and size. This reduces the cost and time of development, as well as the risk associated with the projects. Moreover, the CSA was used in a more consistent fashion making the system easier to understand and maintain, and several crosscutting concerns were modularised as part of a reusable aspect library which could eventually form part of their CSA. It was found that AOP is approaching commercial readiness. However, more work is needed on defining standards for aspect languages and modelling of design elements. The current solutions in this area are commercially viable, but would greatly benefit from a standardised approach. Aspect systems can be difficult to test and the effect of the weaving process on Java serialisation requires further investigation

Development of an infrared imaging system for the surface tension driven convection experiment

An infrared imaging system is used to quantify the imposed surface temperature distribution along a liquid/gas free surface in support of the Surface Tension Driven Convection Experiment, a planned Space Transportation System flight experiment. For ground-based work a commercially available instrument was used to determine the feasibility of using this type of imaging system for this experiment. The ground-based work was used as a baseline for compiling specifications for a flight qualified imager to be designed, fabricated, tested and qualified for flight. The requirements and the specifications for the flight model are given along with the reasons for departures from the ground-based equipment. The flight qualification requirements discussed are a representative sample of the necessary procedures which must be followed to flight qualify diagnostic equipment for use aboard the STS. The potential problems and concerns associated with operating an imaging system on orbit are also discussed

Application of Stochastic Reliability Modeling to Waterfall and Feature Driven Development Software Development Lifecycles

There are many techniques for performing software reliability modeling. In the environment of software development some models use the stochastic nature of fault introduction and fault removal to predict reliability. This thesis research analyzes a stochastic approach to software reliability modeling and its performance on two distinct software development lifecycles. The derivation of the model is applied to each lifecycle. Contrasts between the lifecycles are shown. Actual data collected from industry projects illustrate the performance of the model to the lifecycle. Actual software development fault data is used in select phases of each lifecycle for comparisons with the model predicted fault data. Various enhancements to the model are presented and evaluated, including optimization of the parameters based on partial observations

Test, Control and Monitor System maintenance plan

The maintenance requirements for Test, Control, and Monitor System (TCMS) and the method for satisfying these requirements prior to First Need Date (FND) of the last TCMS set are described. The method for satisfying maintenance requirements following FND of the last TCMS set will be addressed by a revision to this plan. This maintenance plan serves as the basic planning document for maintenance of this equipment by the NASA Payloads Directorate (CM) and the Payload Ground Operations Contractor (PGOC) at KSC. The terms TCMS Operations and Maintenance (O&M), Payloads Logistics, TCMS Sustaining Engineering, Payload Communications, and Integrated Network Services refer to the appropriate NASA and PGOC organization. For the duration of their contract, the Core Electronic Contractor (CEC) will provide a Set Support Team (SST). One of the primary purposes of this team is to help NASA and PGOC operate and maintain TCMS. It is assumed that SST is an integral part of TCMS O&M. The purpose of this plan is to describe the maintenance concept for TCMS hardware and system software in order to facilitate activation, transition planning, and continuing operation. When software maintenance is mentioned in this plan, it refers to maintenance of TCMS system software

Restructuring the Software Architecture: A Case Study of the CoolBiz Core Banking Platform

As the structural engineering underpins the resilience of a city built on an active geological fault, software architecture becomes crucial in an increasingly digital society. This paper investigates the challenges of rigid, low cohesion software structures through a detailed case study of the CoolBiz Platform, an integrated Core Banking solution. The platform currently faces significant issues in its service support framework, including low flexibility, unsatisfactory cohesion, non-adherence to SOLID principles, absence of unit tests, and lack of documentation. This study aims to describe the planning and implementation of a new event-driven architecture for the CoolBiz Platform. This architecture is expected to not only resolve current technical challenges but also bring significant business benefits, such as the implementation of language agnosticism, a strategy aimed at facilitating talent recruitment and retention by not limiting recruitment to expertise in a specific programming language