Software development process programming

The term software architecture is defined as a description of the structure of the components of a program/system (and) their interrelationships [331, 686[. This description serves different purposes, e.g. for analyzing certain software qualities, such as adaptability, maintainability, or portability, or managing the software development process [536]. 

Requirements criticality analysis is used to identify program requirements that affect safety. This is where safety-critical subsystems are often first determined. All items listed as safety-critical are then tracked through the entire software development process. 

Tools such as the compiler, test tools, editors and the chosen programming language (including limitations for its use) will be framework conditions, which also influence the software development process. 

Build refers to a version of software that meets a specified subset of the requirements that the completed software will meet. Typically during program development, several software builds are developed to incorporate changes, fixes, updates, and new requirements. Different builds are differentiated by a build number, which is established by the program s software development process. 

It should be noted that SwS is not the same as software reliability or SQA, and it cannot be achieved solely through these processes. The SwS methodology involves an independent stand-alone process that must be integrated with the software development process. The SwS process should be established at the start of a project and be documented in the SwSPP. The SwS program implements the SwSPP and carries out the SwS process. 

Humans should use computers to do functional work for them in the most efficient manner possible. However, we must not delude ourselves into thinking that the mere use of a computer to analyze adverse events will magically analyze these events in a systematic, efficient way. Computers do not automatically produce coherent, auditable results that can be subsequently reproduced with ease. Computers must be actively programmed through an iterative process involving tight communication between analysts and software developers until these processes are totally functional. 

FieldNotes user verification can be conducted by following the SOP written by Astrix, which can be downloaded from the Astrix Web site. The SOP contains a script that is typed into the computer system. If the printout matches the SOP script, then verification is complete. A record of this must be placed in the facility archive. This verification process takes 1 h or less. For FieldNotes, calculations are not verified at the field site since the manufacturer feels that the software developer and the sponsors have performed adequate validation of these calculations previously. This may, therefore, require a visit to the sponsor or to the manufacturer to confirm that this important step of the validation process has been completed and is adequately documented. By following the Astrix SOP, the user is simply ensuring that the program operates on their system(s). The SOP script must be typed in exactly as written in order to confirm the printout accuracy. QA must ensure that the verification documentation is properly archived. Just as with any other SOP, this SOP must be approved in writing by field site management to comply with GLP. 

A large number of chemical/biological processes will be presented, modeled and efficient numerical techniques will be developed and programmed using MATLAB 2. This is a sophisticated numerical software package. MATLAB is powerful numerically through its built-in functions and it allows us to easily develop and evaluate complicated numerical codes that fulfill very specialized tasks. Our solution techniques will be developed and discussed from both the chemical/biological point of view and the numerical point of view. 

---