1.

The analysis phase answers the questions of who will use the system, what the system will do, and
where and when it will be used. During this phase, the project team investigates any current
system(s), identifies improvement opportunities, and develops a concept for the new system. This
phase has three steps:
a. Analysis Strategy: Developed to guide the project team's efforts. Such a strategy usually
includes an analysis of the current system (as-is system) and its problems, and then ways
to design a new system (to-be system).
b. Requirements Gathering: The analysis of this information—in conjunction with input from
project sponsor and many other people—leads to the development of a concept for a new
system. The system concept is then used as a basis to develop a set of business analysis
models that describes how the business will operate if the new system were developed.
c. System Proposal: The analyses, system concept, and models are combined into a document
called the system proposal, which is presented to the project sponsor and other key decision
makers.

2. Polymorphism is the occurrence of something in various forms. . In object-oriented programming,

polymorphism refers to a programming language's ability to process objects differently depending
on their data type or class. More specifically, it is the ability to redefine methods for derived classes.
In a programming language that exhibits polymorphism, objects of classes belonging to the same
hierarchical tree (i.e. inherited from a common base class) may possess functions bearing the same
name, but each having different behaviors.

3.