CHAPTER-THREE

PROCESS MODEL

3.1 OVERVIEW
This chapter elaborate the process model over which the project is based on. A process model is
a simplified representation of a software process. Each model represents a process from a specific
perspective. We’re going to take a quick glance about very general process models. These generic
models are abstractions of the process that can be used to explain different approaches to the
software development. They can be adapted and extended to create more specific processes.
3.2 PROCESS MODEL

This android application project is based on spiral model. The spiral model is similar to
the incremental model, with more emphasis placed on risk analysis. The spiral model has four
phases: Planning, Risk Analysis, Engineering and Evaluation. A software project repeatedly
passes through these phases in iterations. The baseline spiral, starting in the planning phase,
requirements are gathered and risk is assessed. Each subsequent spirals builds on the baseline
spiral. Its one of the software development models like Waterfall, Agile, V-Model.

Planning Phase : Requirements are gathered during the planning phase. Requirements like ‘BRS’
that is ‘Business Requirement Specifications’ and ‘SRS’ that is ‘System Requirement
specifications’.

Risk Analysis: In the risk analysis phase, a process is undertaken to identify risk and alternate
solutions.  A prototype is produced at the end of the risk analysis phase. If any risk is found
during the risk analysis then alternate solutions are suggested and implemented.

Engineering Phase: In this phase software is developed, along with testing at the end of the
phase. Hence in this phase the development and testing is done.

Evaluation phase: This phase allows the customer to evaluate the output of the project to date
before the project continues to the next spiral.

Advantages of Spiral model:

 High amount of risk analysis hence, avoidance of Risk is enhanced.

 Good for large and mission-critical projects.
 Strong approval and documentation control.
 Additional Functionality can be added at a later date.
 Software is produced early in the software life cycle.
Disadvantages of Spiral model:

 Can be a costly model to use.

 Risk analysis requires highly specific expertise.
 Project’s success is highly dependent on the risk analysis phase.
 Doesn’t work well for smaller projects.

3.3 PROJECT COST ESTIMATION MODEL

The process of project cost estimation is central to setting up the foundation for making key
decisions, taking initiatives, budgeting activities and controlling expenditures. Cost forecasts and
projections are used to establish a set of metrics against which project success will be measured,
and to communicate work progress to the stakeholders at any given point in time.
The necessity of calculating expenses consists in maintaining confidence and trust that project
activities are performed properly and as expected throughout the entire project life-cycle. Logical
and reasonable cost estimate will allow the team to make collaborative effort with a reduced
probability of risk occurrence and failure because the estimators use various efficient
methodologies to fight uncertainty, prevent performance bottlenecks, determine budget and
control spending.
The estimation process complies with a set of principles which act as a foundation for identifying
and calculating right project expenses.

Here are the key principles:

3.3.1 Integrity
Any cost estimate should be produced with a high standard of ethical integrity and by following
an open and transparent process. Any uncertainties and vagueness associated with the estimate
should be explained in an easy-to-understand manner and in laymen’s terms. This principle
allows avoiding false precision and rash decisions by integrating all people involved in the
process into a team which works as a single mechanism and uses the same sources of
information.

3.3.2 Information Accuracy and Relevance

The development of cost estimates should be based only on the best information available. When
a planner develops an estimate, engineering judgement and technical advice should be applied to
any assumption made at that estimate. By following this principle, all information used for
developing estimates can be thoroughly considered, filtered and refined in order to get the most
accurate and relevant pieces of that information.