- In information technology, gap analysis is the study of the differences between

two different information systems or applications, often for the purpose of determining
how to get from one state to a new state. A gap is sometimes spoken of as "the space
between where we are and where we want to be." Gap analysis is undertaken as a means
of bridging that space. Among the various methodologies used to perform gap analysis is
IDEF, a group of methods used to create a model of a system, analyze the model, create a
model of a desired version of the system, and to aid in the transition from one to the
other.

Business Requirements Definition

At the core of any requirements process is the ability to get people to tell you what they
really need, rather than their perceived solution, or what they think you might be able to
deliver.

The Volere process (our preferred model) provides a well-defined structure and guide as
to which requirements content is appropriate for you. The process and template fit with
existing tools (Caliber, DOORS, Requisite, etc.) and methods. The process is based on
experience from worldwide business analysis projects, and is continually improved with
input from users.
DEFINITION: A functional specification (or sometimes functional specifications) is a
formal document used to describe in detail for software developers a product's intended
capabilities, appearance, and interactions with users. The functional specification is a
kind of guideline and continuing reference point as the developers write the programming
code. (At least one major product development group used …
Definition continues below.
FUNCTIONAL SPECIFICATIONS DEFINITION (continued): … a "Write the
manual first" approach. Before the product existed, they wrote the user's guide for a word
processing system, then declared that the user's guide was the functional specification.
The developers were challenged to create a product that matched what the user's guide
described.) Typically, the functional specification for an application program with a series
of interactive windows and dialogs with a user would show the visual appearance of the
user interface and describe each of the possible user input actions and the program
response actions. A functional specification may also …
Functional Specifications definition sponsored by SearchSoftwareQuality.com, powered
by WhatIs.com an online computer dictionary

Definitions of risk
There are many more and less precise definitions of risk; they depend on specific
applications and situational contexts. It can be assessed qualitatively or quantitatively.

Qualitatively, risk is considered proportional to the expected losses which can be caused
by an event and to the probability of this event. The harsher the loss and the more likely
the event, the greater the overall risk.
Frequently in the subject matter literature, risk is defined in pseudo-formal forms where
the components of the definition are vague and ill-defined, for example, risk is
considered as an indicator of threat, or depends on threats, vulnerability, impact and
uncertainty.

In engineering, the quantitative engineering definition of risk is:

.
risk analysis(business) is a technique to identify and assess factors that may jeopardize
the success of a project or achieving a goal. This technique also helps to define
preventive measures to reduce the probability of these factors from occurring and identify
countermeasures to successfully deal with these constraints when they develop to avert
possible negative effects on the competitiveness of the company.

One of the more popular methods to perform a risk analysis in the computer field is
called Facilitated Risk Analysis Process (FRAP).

Three of the most important risks a software company faces are unexpected changes in
revenue and costs from those budgeted and amount of specialization of the software
planned. Risks that affect revenues can be unanticipated competition, privacy, intellectual
property right problems, and unit sales that are less than forecasted; unexpected
development costs also create risk that can be in the form of more rework than
anticipated, security holes, and privacy invasions. [1]

Risk analysis’ is employed in its broadest sense to include:

Risk assessment
involves identifying sources of potential harm, assessing the likelihood that harm
will occur and the consequences if harm does occur.

Risk management
evaluates which risks identified in the risk assessment process require
management and selects and implements the plans or actions that are required to
ensure that those risks are controlled.

Risk communication
involves an interactive dialogue between stakeholders and risk assessors and risk
managers which actively informs the other processes.

Risk analysis = risk assessment + risk management + risk communication.

Prototype:
Definition: 1. original used as model: the original form of something, which has the
essential features and is the model for subsequent forms
2. full-size functional model: a first full-size functional model to be manufactured, e.g.
of a car or a machine
3. standard example: a standard example of a particular kind, class, or group
4. biology primitive form: a primitive form believed to be the original type of a species
or group, exhibiting the essential features of the later type

Mockup model is the best expression way of design language. Not only does it
offers the most vivid visual effects but the best feedback of designs and ideas, so
as to effectively cut the investment risk. We now possess 20 imported CNC
machining centres and more than 130 experienced mockup
engineers. Different materials such as ABS, PC, PP, PE, PU,
PA, POM,PMMA, etc. are applicable according to customers’
requirements, and high qualities like high surface gloss, high
rigidity, high temperature resistance, high extension, high
elasticity, etc. are achievable. Moreover, metal sheet
specimen such as aluminum alloy is also available. The
various mockup models made by our company can be
compared with the real product, and can meet different
requirements on product exterior, structure, marketing
potential, function testing, and so on.

A use case diagram is a type of behavioral diagram defined by the Unified Modeling
Language (UML) and created from a Use-case analysis. Its purpose is to present a
graphical overview of the functionality provided by a system in terms of actors, their
goals (represented as use cases), and any dependencies between those use cases.

The main purpose of a use case diagram is to show what system functions are performed
for which actors.
 Use Case Diagram
This diagram shows a system's functions from a user's point of view, which in this case is
pretty simple. All the following diagrams were created in the Telelogic Tau UML suite by
Telelogic for this same example. Five of the nine possible diagrams available in UML are
shown below. The Component Diagram (software module interaction), Deployment
Diagram (hardware nodes) and the Activity Diagram (tasks) are not included. The Object
Diagram (instantiations of classes) is rarely used. (All diagrams courtesy of Telelogic, AB,
www.telelogic.com)
Gap analysis
The process of determining, documenting, and approving the variance between business
requirements and system capabilities in terms of packaged application features and
technical architecture.