3.

Project Estimation and Plan

Depending on the results of the initial investigation the survey is now expanded to a
more detailed feasibility study. FEASIBILITY STUDY is a test of system proposal
according to its workability, impact of the organization, ability to meet needs and
effective use of the resources. It focuses on these major questions:

1. What are the users demonstrable needs and how does a candidate system meet them?

2. What resources are available for given candidate system?

3. What are the likely impacts of the candidate system on the organization?

4. Whether it is worth to solve the problem?

During feasibility analysis for this project, following primary areas of interest are to be
considered. Investigation and generating ideas about a new system does this.

Steps in feasibility analysis

Eight steps involved in the feasibility analysis are:

1. Form a project team and appoint a project leader.

2. Prepare system flowcharts.

3. Enumerate potential proposed system.

4. Define and identify characteristics of proposed system.

5. Determine and evaluate performance and cost effective of each proposed system.

6. Weight system performance and cost data.

7. Select the best-proposed system.

8. Prepare and report final project directive to management.

1
3.1) Technical feasibility

A study of resource availability that may affect the ability to achieve an

acceptable system. This evaluation determines whether the technology needed
for the proposed system is available or not.

Can the work for the project be done with current equipment existing
software technology & available personal?

Can the system be upgraded if developed?

If new technology is needed then what can be developed?

This is concerned with specifying equipment and software that will successfully
satisfy the user requirement. The technical needs of the system may include:

Front-end and back-end selection

An important issue for the development of a project is the selection of suitable
front-end and back-end. When we decided to develop the project we went
through an extensive study to determine the most suitable platform that suits the
needs of the organization as well as helps in development of the project

The aspects of our study included the following factors :

2
FRONT-END SELECTION:

1. It must have a graphical user interface that assists employees that are not
from IT

background.

2. Scalability and extensibility.

3. Flexibility.

4. Robustness.

5. According to the organization requirement and the culture.

6. Must provide excellent reporting features with good printing support.

7. Platform independent.

8. Easy to debug and maintain.

9. Event driven programming facility.

10. According to the above stated features we Android Studio for developing
our project.

Android Studio is now the official IDE for Android, so you should
migrate to Android Studio to receive all the latest IDE updates

At the core of Android Studio is an intelligent code editor capable of

advanced code completion, refactoring, and code analysis.

3
BACK-END SELECTION:

1. Multiple user support.

2. Efficient data handling.

3. Provide inherent features for security.

4. Efficient data retrieval and maintenance.

5. Stored procedures.

6. Popularity.

7. Operating System compatible.

8. Easy to install.

9. Various drivers must be available.

10. Easy to implant with the Front-end.

According to above stated features we selected Oracle 10g xe as the backend.

The technical feasibility is frequently the most difficult area encountered at this
stage. It is essential that the process of analysis and definition be conducted in
parallel with an assessment to technical feasibility. It centers on the existing
computer system (hardware, software etc.) and to what extent it can support the
proposed system.

4
3.2) Economical feasibility

Economic justification is generally the Bottom Line consideration for most

systems. Economic justification includes a broad range of concerns that
includes cost benefit analysis. In this we weight the cost and the benefits
associated with the candidate system and if it suits the basic purpose of the
organization i.e. profit making, the project is making to the analysis and design
phase.

The financial and the economic questions during the preliminary investigation
are verified to estimate the following:

The cost to conduct a full system investigation.

The cost of hardware and software for the class of application being
considered.

The benefits in the form of reduced cost.

The proposed system will give the minute information, as a result the
performance is improved which in turn may be expected to provide increased
profits.

This feasibility checks whether the system can be developed with the
available funds.

The Application does not require enormous amount of money to be developed.

This can be done economically if planned judicially, so it is economically
feasible. The cost of project depends upon the number of man- hours required.

3.3) Operational Feasibility

5
It is mainly related to human organizations and political aspects. The points to
be considered are:

What changes will be brought with the system?

What organization structures are disturbed?

What new skills will be required? Do the existing staff members have
these skills? If not, can they be trained in due course of time?

The Application is operationally feasible as it very easy for the End users to
operate it. It only needs basic information about Android platform.

3.4) Schedule feasibility

Time evaluation is the most important consideration in the development of project. The time schedule
required for the developed of this project is very important since more development time effect
machine time, cost and cause delay in the development of other systems.

A reliable movie ticket booking application can be developed in the considerable amount of time.

6
4. SDLC
(Software Development life
cycle)

4.1 PHASES:-

4.1.1 INITIAL PHASE:

The initiation of a system begins when a business need or opportunity is
identified. A project manager should be appointed to manage the project. This
business need is documented in concept proposal. After the concept proposal is
approved, the system concept development phase begins.

4.1.2 SYSTEM CONCEPT DEVELOPMENT PHASE:

Once a business need is approved, the approaches for accomplishing the
concept are renewed for feasibility and appropriateness. The systems boundary
document identifies the scope of the system and requires senior official approval
and funding before beginning the planning phase.

4.1.3 PLANNING PHASE:

The concept is further developing to describe how the business will operate
once the approved system is implemented, and to assess how the system will
impact employee and customer privacy. To ensure the products and/or services
provide the required capability on time and within budget, project resources,
activities, schedules, tools and reviews are defined. Additionally, security
certification and accreditation activities begin with the identification of system
security requirements and the completion of high level vulnerabilities
assessment.

4.1.4 REQUIREMENTS ANALYSIS PHASE:

Functional user requirements are formally defined and delineate the
requirements in terms of data, system performance, system security and
7
maintainability requirements for the system. All requirements are defined to a
level of detail sufficient for system design to proceed. All requirements need to
be measurable and testable and relate to the business need or opportunity
identified in the initiation phase.

4.1.5 DESIGN PHASE:

Software design is a process through which the requirements are translated into
a representation of software. One of the software requirements have been
analyzed and specified, the software design involves three technical activities:
design, coding generation and testing. The design of the system is in modular
form i.e. the software is logically partitioned into components that perform
specific functions and sub functions. The design phase leads to modules that
exhibit independent functional characteristics.
It even leads to interfaces that reduce the complexity of the connections
between modules and with the external environment. The design phase is of
main importance because in this activity, decisions ultimately affect the success
of software implementation and maintenance.

4.1.6 DEVELOPMENT PHASE:

The development phase includes choosing of suitable software to solve the
particular problem given. The various facilities and the sophistication in the
selected software give a better development of the problem.

4.1.7 INTEGRATION AND TEST PHASE:

The code is tested at various levels in software testing. Unit, system and user
acceptance testing are often performed. This is a grey area as many different
opinions exist as to what the stages of testing are and how much, if any iteration
occurs. Iteration is not generally part of the waterfall model, but usually some
occur at this stage.
Testing is done in various ways such as testing the algorithm, programming
code; sample data debugging is also one of following the above testing.

4.1.8 IMPLEMENTATION PHASE:

8
The development phase includes choosing of suitable software to solve the
particular problem given. The various facilities and the sophistication in the
selected software give a better development of the problem.
4.1.9 OPERATION AND MAINTENANCE PHASE:
The deployment of the system includes changes and enhancements before the
decommissioning or sunset of the system. Maintaining the system is an
important aspect of SDLC. As key personnel change positions in the
organization, new changes will be implemented, which will require system.

4.2 SDLC OBJECTIVES:-

4.2.1 ENSURE HIGH QUALITY:

The SDLC must ensure that these objectives are well defined for each project
and used as the primary measure of success for the project and system.
The business objectives provide the contextual definition of quality. There is
also an intrinsic definition of quality. This definition of quality centres on the
characteristics of the system itself: is it zero defect, is it well-structured, it is
well-documented, functionally robust, etc. The characteristics are obviously
directly linked to the system's ability to provide the best possible ROI.
Therefore, the SDLC must ensure that these qualities are built into the system.
However, how far you go in achieving intrinsic quality is tempered by the need
to keep contextual quality (i.e., ROI) the number one priority. At times there are
trade-offs to be made between the two. Within the constraints of the business
objectives, the SDLC must ensure that the system has a high degree of intrinsic
quality.

4.2.2 PROVIDE STRONG MANAGEMENT CONTROL:

The essence of strong management controls is predictability and feedback.
Projects may last for many months or even years. Predictability is provided by
being able to accurately estimate, as early as possible, how long a project will
take, how many resources it will require and how much it will cost. This
information is the key to determining if the ROI will be achieved in a timely
manner or at all. The SDLC must ensure that such planning estimates can be put
9
together before there have been any significant expenditures of resources, time
and money on the project. The feedback process tells us how well we are doing
in meeting the plan and the project's objectives. If we are on target, we need that
verified. If there are exceptions, these must be detected as early as possible so
that corrective actions can be taken in a timely manner. The SDLC must ensure
that management has timely, complete and accurate information on the status of
the project and the system throughout the development process.

4.2.3 MAXIMIZE PRODUCTIVITY:

There are two basic definitions of productivity. One centres on what you are
building; the other is from the perspective of how many resources, how much
time and how much money it takes to build it. The first definition of
productivity is based on the return on investment (ROI) concept. What value is
there in doing the wrong system twice as fast? It would be like taking a trip to
the wrong place in a plane that was twice as fast. You might have been able to
simply walk to the correct destination. Therefore, the best way to measure a
project team's or system department's productivity is to measure the net ROI of
their efforts. The SDLC must not just ensure that the expected ROI for each
project is well defined. It must ensure that the projects being done are those
with the maximum possible ROI opportunities of all of the potential projects.

10
11