Deployment software

For any application, the software used for model deployment is quite different than the software used for model development. This is because deployment software has a very different function, and thus very different reqnirements, than development software. Whereas development software requires flexibility and nser-friendliness, deployment software requires long-term stability, reliability, and accessibility to critical on-line data. The following are questions that reflect some conunon deployment software issues in a PAT project  

Many of these issnes are bom of the fact that, nnlike development software, deployment software must be an integral part of a much larger data handling and process control system. 

---

Does the deployment software snpport the model and preprocessing types specified for a given method ... 

Who is responsible for long-term snpport of the deployment software ... 

To develop an ability to design algorithms, implement programs, and deploy software... 

The SSR should have the ability to deploy software on newly constructed machines and network nodes, and to bring up the network and verify it as part of starting up the daughter SSR system (including its underlying communication network) as a preparatory step in the SSR division phase. 

Despite its weaknesses (such as described in the 1975 collection of essays The Mythical Man Month [11]), the traditional software development life cycle (collect requirements, design, implement, test, deploy, maintain) has remained the standard framework for software development. However, in recent years it has become clear that the life cycle is not well suited to applications that are experimental in nature (i.e., where there is no precedent for the particular kind of application) or that exist in rapidly changing environments. This has led to the development of agile methodologies (also known as lightweight... 

Whether life sciences informatics software ultimately becomes a commodity, with the commercial rewards for software companies being in packaging, integration, support, and deployment (in a similar way to the Linux community), and what impact the open source movement will have. In bioinformatics and chemoinformatics, open source, free software, and shareware are increasing in quantity, and it is becoming common for smaller software companies at least to release reduced-functionality versions of their software into the public domain at no cost. 

To combat attacks with fast-acting agents in the terminals, continuous visual surveillance of densely populated areas and observation of behavior patterns may be as useful as any detector. The TSA should study the feasibility of the widespread deployment of surveillance cameras in populated areas, coupled with behavioral-pattern-recognition software, as an alternative to chemical agent detectors. Such cameras could also provide a dual-use value in improving the overall security environment. In addition, many critical nodes in the air transportation system (control rooms, emergency-response centers, and so on) are supplied with air that is recirculated from publicly accessible areas this makes them vulnerable to being disabled by the release of... 

Flexibility means the ability not only to change quickly but also to provide several variants at the same time. A bank may deploy the same basic business system globally but needs to be able to adapt it to many localized rules and practices. A software product vendor cannot impose the same solution on every customer nor develop a solution from scratch each time. Instead, software developers prefer to have a configurable family of products. 

The term domain or business covers all concepts of relevance to your clients and their problems—that is, the environment in which any target software will be deployed. If you are designing a multiplexor in a telecommunication system, your users are the designers of the other switching components, and the business model will be about things such as packets, addresses, and so on. If you are redesigning the ordering process of a company, the business model is about orders, suppliers, people s roles, and so on. 

Distribution Software components, processes, hardware Deployed on or runs on CPU, can dynamically move to, network protocols... 

Deployment of software is shown here against this physical model, with different software components shown on different hardware nodes for example, the software components in the four-tier system are shown in Figure 12.5. Note that software component requirements, such as memory and storage space, can be modeled as attributes and matched against the corresponding attributes of the hardware. If needed, you can also explicitly specify the effect of actions, such as node failures (failover requirements) or network load, against such a model. 

Scalability Can the system as designed and deployed be scaled up to handle greater usage demands (volume of data, numbers of users, rate of requests) Scalability is achieved primarily by repheating resources—processors, memory, storage media—and their software processing counterparts. Component-based designs in which the components can be deployed on separate processors, and where the overhead of cross-component coordination is proportionately small, enhances scalability. 

Business collaboration Identifies the actors in the domain and their interactions (the actions, or use cases, and information exchanged). The actors typically represent the roles of people (such as buyer) or software systems (such as inventory system). The as-is and to-be versions form the basis of deployment and transition plans for the systems. 

Deployment It is in this phase that the business or domain makes its transition to the to-be model, adopting new processes, hardware, and software. It involves things such as software and hardware installation, tools to upgrade or migrate to new releases, documentation, acceptance testing, and user and administrator training. Note that user docu-... 

Typical cycles in software development might include feasibility study, GUI mock-up, requirements analysis and prototype, single-user, single-machine vertical incremental slices, tightening of relations between documentation layers, distribution across hosts, and multiuser deployment. A typical 10-person software development might use cycles ranging from two to six weeks. 

Although the SIMCA method is very versatile, and a properly optimized model can be very effective, one must keep in mind that this method does not use, or even calculate, between-class variability. This can be problematic in special cases where there is strong natural clustering of samples that is not relevant to the problem. In such cases, the inherent interclass distance can be rather low compared to the mtraclass variation, thus rendering the classification problem very difficult. Furthermore, from a practical viewpoint, the SIMCA method requires that one must obtain sufficient calibration samples to fully represent each of the J classes. Also, the on-line deployment of a SIMCA model requires a fair amount of overhead, due to the relatively large number of parameters and somewhat complex data processing instructions required. However, there are several current software products that facilitate SIMCA deployment. 

Can the software be run off-line, to allow piloting/testing of models before deployment ... 

Key words Drug discovery, chem-informatics, molecular design, combinatorial chemistry, combinatorial library, synthesis protocol, PGVL, reactant, product, enumeration, filtering integration, workflow, streamline, desktop tool, software deployment. 

---