Question

Analyze and compare at least three internet systems development software technologies for use at PVF.

Analyze how the selected internet systems development software technologies support PVF’s core business processes.

Answer 1

PVF - The program vulnerability factor has been defined as a metric to understand the impact of hardware faults on software.

Visual studio :

PVF projects are available in many language.The first time Visual studio is started it may display a list of default settings from which to choose.The visual studio IDE frequently uses the terms solutions and projects.

Comparison and contraction of Internet systems development software technologies.There are different types of internet system development technologies all which offer a guide to some of the main web technologies we use to develop accessibly. For example, Client-Side Technologies, Server-Side Technologies and Multimedia are some of the commonly used internet system development technologies.Client-side technologies include HTML and Cascading Style Sheets which are codes that run within a web browser. This means that the web browser temporarily downloads all the files from a web server and, in turn, displays a static web page which one would be able to view these file seven if one lost his or her internet connection as long as one left his or her web browser open.JavaScript and Action Script are the two most commonly used client-side scripts.

Console Application - An application (.exe) that runs in a console window, using

text input and output.

‣ Dynamic Library - A dynamically-linked library file (.dll) that provides routines

that can be loaded on-demand when called by the program that needs them.

‣ Static Library - An archive file (.lib) containing one or more object files that can be

linked to create an executable.

‣ Windows Application - An application (.exe) that supports a graphical user

interface that makes use of components like windows, dialog boxes, menus, and so

on. The name of the program entry point for such applications is WinMain.

‣ Empty Project - A skeletal project intended to allow migration of existing

applications to PVF. This project type does not include any source files. By default,

an empty project is set to build an application (.exe).

PVF Build Macros

PVF implements a subset of the build macros supported by Visual C++ along with a few

PVF-specific macros. The macro names are not case-sensitive, and they should be usable

in any string field in a property page. Unless otherwise noted, macros that evaluate to

directory names end with a trailing backslash ('\').

In general these items can only be changed if there is an associated PVF project or

file property.

• For example, $(VCInstallDir) cannot be changed, while $(IntDir) can be

changed by modifying the General | Intermediate Directory property.

For the names and descriptions of the build macros that PVF supports, refer to the ‘PVF

Build Macros’ section in the PGI Visual Fortran Reference Manual.

Functions and Subroutines

Fortran C, and C++ define functions and subroutines differently.

For a Fortran program calling a C or C++ function, observe the following return value

convention:

‣ When a C or C++ function returns a value, call it from Fortran as a function.

‣ When a C or C++ function does not return a value, call it as a subroutine.

For a C/C++ program calling a Fortran function, the call should return a similar type.

Fortran and C/C++ Data Type Compatibility, lists compatible types. If the call is

to a Fortran subroutine, a Fortran CHARACTER function, or a Fortran COMPLEX function,

call it from C/C++ as a function that returns void.