SELECTION OF AN
APPROPRIATE
PROJECT APPROACH
MEMEBERS
ROLL NO:
16
17
18
19
20
INTRODUCTION •
This chapter is concerned with how the characteristics of a project environment
and the application to be delivered influence the shape of the plan of a project. •
Introduction to most common process models and selection of the most
appropriate of them for a project is also a part of this chapter.
BUILD OR BUY?
In-house: means that the developers and the users of the software in the
same organization. – often the methods to be used dictated by organizational
standards
• Outsourced:
means that the developers and the users of the software in the different organization. –
need for tailoring as different customers have different needs •
Off-the-shelf: means, a ready-made software product that is purchased.
Analysis of project characterstics:
Identify project as either objective driven and product driven
• Analyze other project characteristics
• Identify high level project risks •
Take into account user requirement concerning implementation
Objective driven or product driven.
• Product-driven project: – a project will be to create a product. – The details of the
product is provided by the client. • Objective-driven project: – A project is to meet an
objective. – The Client may have a problem and asks a specialist to recommend solutions.
ANALYZE OTHER PROJECT CHARACTERISTICS
• IS THE SYSTEM TO BE CREATED SAFETY CRITICAL?
• IS THE SYSTEM DESIGNED TO CARRY OUT PREDEFINED SERVICES OR TO BE ENGAGING AND
ENTERTAINING?
• WHAT IS THE NATURE OF THE HARDWARE/SOFTWARE ENVIRONMENT IN WHICH THE
SYSTEM WILL OPERATE?
SOFTWARE PROCESS MODEL
• A number of inter related activities have to be undertaken to create a final product.
These activities can be organized in different ways and we call these process models. • A
process model of a software product is a graphical or textual representation of its
lifecycle. Additionally a process model may describe the details of various types of
activities carried out during the different phases and the documents produced.
SOFTWARE PROCESS MODEL STRUCTURE VERSUS SPEED OF DELIVERY
• Two competing pressures – One is to make sure that the final product has a robust
structure which will be able to meet evolving needs. –
Other is to get the job done as quickly and as cheaply as possible.
SOFTWARE PROCESS MODELS
Waterfall Model.
V-process Model.
Spiral Model.
Software prototyping.
Phased Development Model.
• incremental development model.
• iterative development model.
Waterfall
Waterfall
Classical model of system development.
Called one-shot or once-through model.
limited scope of iteration. Is this a strength or a limitation??
This is a strength for the WF-model.
Because it is suitable for some projects especially for large projects, we want
to avoid reworking tasks that are thought to be completed.
Reworking tasks could result in late delivery.
Suitable for systems with well defined requirements.
Not suitable for systems of high uncertainty
V-PROCESS MODEL
An extension of the waterfall model.
V-process model expands the activity box “testing” in the waterfall model.
Each step has a matching validation process.
Validation process can cause a Loop back to the corresponding
stage and reworking the following steps in case of discrepancy.
V-PROCESS MODEL (CONT’D)
SPIRAL MODEL
A greater level of detail is considered at each stage of the project
Represented as a loop or a spiral where the system is
considered in more detail.
This means g reater confidence about the probability of
success.
Each sweep is terminated by an evaluation before the next
iteration is embarked upon.
SPIRAL MODEL (CONT’D)
Prototyping Model
Prototype is a working model of one or more aspects of
the projected system.
Goal
Gain knowledge
reduce risk and uncertainty
verify a design or implementation approach
The prototype is constructed and tested, quickly and
inexpensively to test assumptions.
PROTOTYPING MODEL
Benefits of Prototyping
Learning by doing.
Improved communication.
Improved user involvement.
Clarification of partially-known requirements.
Demonstration of the consistency and completeness of a
specification
Drawbacks of Prototyping
USERS SOMETIMES MISUNDERSTAND THE ROLE OF THE PROTOTYPE.
LACK OF PROJECT STANDARDS POSSIBLE.
LACK OF CONTROL.
ADDITIONAL EXPENSE.
MACHINE EFFICIENCY.
CLOSE PROXIMITY OF DEVELOPERS.
Forms of Prototypes
PARTIAL WORKING MODEL
VERTICAL:
only some features are fully prototyped
HORIZONTAL:
all featured are prototyped but not in detail.
Incremental Model
Break the system into small components.
Implement and deliver small components in sequence.
Every delivered component provides extra functionality to the user
ITERATIVE MODEL
Deliver full system in the beginning.
Enhance existing functionality in new releases.
ITERATIVE MODEL
