Selection of an Appropriate Software Project Approach

1. SOFTWARE PROJECT MANAGEMENT
Unit-2
Ch4: Selection of an Appropriate Project Approach
Reference: Bob Hughes

2. 1. Introduction
 Meaning of In-House software development.
 Decision making process of Individual
Project: Methodologies andTechnologies
 Project Analysis
 Technical Planning
 Method Engineering
 MethodTailoring
 Means end inversion
 Lightweight vs heavyweight Processes

3. Means End Inversion
 Developers focus on the means – the
procedures and the intermediate products of
a prescribed method- at the expense of the
‘end’, the actual required outcomes of the
work.

4. 2 Buid or Buy ?
 In- House Development
 Outsource Development

5. 3 Choosing Methologies and
Technologies
 Methodologies describes a collection of
Method.
 Techniques tend to involve the application of
scientific, mathematical or logical principles to
resolve a particular kind of problem.
 Method often involves creation of models.
 Model is a representation of a system which
abstracts certain features but ignores others.
E.g. ERD Model, DFD Model

6. 3 Choosing Methologies and
Technologies
 Project Analysis identifies appropriate
methodology( project approach) and
technology.
 Project Analysis selects appropriate
application building environment and the
methods within the methodology that are to
be deployed.

7. 3 Choosing Methodologies and
Technologies
3.1 Identify project as either
Objective-Driven or Product-Driven

8. 3 Choosing Methodologies and
Technologies
3.2 Analyse other project Other Charactristics:
E.g.
 Data Oriented(information sys) or Process
oriented(embedded sys) or Both
 General system(Exel ,word) or Application
System(Ticket Booking sys)
 Expert system needs Expert device
 Safety Critical System
 Different from Conventional i.e. Engaging and
Entertaining
 Nature of H/W or S/W environment.... E.g.
Embedded/ Desktop Application

9. 3 Choosing Methodologies and
Technologies
3.3 Identify high-level project risk:
 Product risk: changes in law , taxation or
market need or users need.
 Process risk: changes in methods or
modeling standard.
 Resource risk: personals, tools, infrastructure

10. 3 Choosing Methodologies and
Technologies
3.4 Take into account user requirements
concerning implementation.
 Ensure that unnecessary constraints are not
imposed on the way that a project’s
objectives are to be met.
 E.g. specify s/w supplier have:
 BS EN ISO 9001:2000 standard
 TickIT accreditation

11. 3 Choosing Methodologies and
Technologies
3.5 Select general life cycle approaches.
 Control Systems
 Information Systems
 Availability of users
 Specialized techniques
 Hardware environment
 Safety critical systems
 Imprecise requirements

12. 4 S/W Processes and Process
Models
 Expression of need for the product is Product
Inception.
 Identifiable Intermediate Developing stages
 Maintenance Stage
 Retirement Stage
 This set of identifiable stages through which a
product transits from inception to retirement form
the life cycle of the product.
 Referred as S/W development life cycle (SDLC) or
S/W Process.
 Graphical orTextual representation of life cycle of
s/w product is called Process Model .

13. 5 Choice of Process Models
 Process means idea of system in action. i.e. A
number of interrelated activities have to be
under taken to create a final product.
Organization of these activities can be done
in different ways using Process Models.
 StructureVs Speed of Delivery
 E.g.
 Waterfall model
 Spiral model
 Prototyping model
 Incremental

14. Choice of Process Models
 Atern / DSDM
 RAD
 JAD
 Agile
 XP
 Scrum
 LSD : Lean S/W Development
 Time Boxes

15. 19 Selection of the Most
Appropriate Process Model
 Construction Vs Installation.

16. Thank You