what is software Engineering ||

SOFTWARE
Computer applications
Set of instructions for desired output
Real time systems, information systems, games
Common characteristics
 Developed, not manufactured
 Does not “wear out”
 Custom built
2

SOFTWARE ENGINEERING
“Software engineering: (1) The application of a systematic, disciplined,
quantifiable approach to the development, operation, and maintenance
of software; that is, the application of engineering to software. (2) The
study of approaches as in (1).” [IEEE, 1993]
3

SOFTWARE MYTHS – MANAGEMENT MYTHS [1/2]
We already have a book that's full of standards and procedures for building
software. Won't that provide my people with everything they need to
know?
 Standards may exist
 Awareness & practice
 Complete & adaptable
4

MANAGEMENT MYTHS [2/2]
If we get behind schedule, we can add more programmers and catch up.
 Not a manufacturing process
 Need to trained people
 Communication problems
If I decide to outsource the software project to a third party, I can just relax
and left that firm build it.
 Organization needs good management skill
5

CUSTOMER MYTHS
A general statement of objectives is sufficient to begin writing programs –
we can fill in the details later.
 Ambiguous requirements: recipe of disaster
 Effective and continuous communication
Software requirements continually change, but change can be easily
accommodated because software is flexible.
 Time of change is important
6

PRACTITIONER’S MYTHS [1/2]
Once we write the program and get it to work, our job is done.
 60-80% of all effort expended after software delivery
Until I get the program "running" I have no way of assessing its quality.
 SQA practices from very beginning
7

PRACTITIONER’S MYTHS [2/2]
The only deliverable work product for a successful project is the working
program.
 Other work products
Software engineering will make us create voluminous and unnecessary
documentation and will invariably slow us down.
 It is not about documents only
 Creating quality products
 Ultimately reduced work and faster delivery time
8

THE CHAOS REPORT – STANDISH GROUP
1995
 365 managers, 8380 IT projects
 16.2 percent – success rate
 31 percent projects cancelled before completion
 $ 140 billion loss
2006
 35 percent – success rate
 19 percent projects cancelled
 $ 53 billion loss
9

INVESTMENT IN PROJECTS
IT projects
 $ 2.4 trillion in 2008
 8 percent increase from 2007
All projects
 $ 2.3 trillion every year in U.S.
 25% of U.S. GDP
 $ 10 trillion (the whole world)
10

WHAT IS THE LESSON?
Better project management
Project Management Institute (PMI)
 1969
 About 300,000 members / many from IT field
 IS Specific Interest Group
PMI Body of Knowledge (BOK) guide
 2008 edition
Project management certification
 PMP
11

PROJECT
Project is defined as “a temporary endeavor undertaken to create a unique
product, service, or result” [PMBOK® Guide, 2008]
Key attributes
 Unique purpose
 Temporary
 Progressive elaboration
 Various resources
 Primary customer/sponsor
12

FIRST MODERN PROJECT
Manhattan Project
 1946
 U.S. military project
 Development of atomic bomb
 Duration: 03 years
 Cost: $ 2 billion
13

TRIPLE CONSTRAINT
Competing goals
 Scope
 Cost
 Time
Trade-offs
Quadruple constraint
 Quality
14
Figure source: IT Project Management, K. Schwalbe, 6th ed., p. 9

PROJECT MANAGEMENT
It is “the application of knowledge, skills, tools and techniques to project
activities to meet project requirements.” [PMBOK® Guide, 2008]
Project managers strive
 To meet scope, time, cost, and quality goals
 Facilitate the entire process
 To meet needs and expectations of the stakeholders
15

PROJECT STAKEHOLDERS
People involved or affected
 Project sponsor
 Project team
 Support staff
 Customers
 Users
 Suppliers
 Opponents of project
16

PROGRAM
Program is "a group of related projects managed in a coordinated way to
obtain benefits and control not available from managing them
individually.” [PMBOK® Guide, 2008]
 Example: multiple applications development
Program manager
 Guide project managers
 Have review meetings
 Strong skills
17

PROJECT PORTFOLIO MANAGEMENT
Emerging business strategy
Previous projects and programs
Wise investment decisions
Portfolio manager
 No previous experience of project manager
 Strong financial and analytical skill
18

DIFFERENCE BETWEEN PROJECT MANAGEMENT AND
PORTFOLIO MANAGEMENT
19

PROJECT MANAGEMENT FRAMEWORK
20

PROJECT SUCCESS
To meet scope, time, and cost goals
Satisfied customers
To achieve main objectives
21

TOP FACTORS FOR PROJECT SUCCESS [CHAOS
REPORT, 2001]
Executive support
User involvement
Experienced project manager
Clear business objectives
Minimized scope
Standard software infrastructure
Firm basic requirements
Reliable estimates
Other criteria e.g. proper planning
22

SUCCESSFUL ORGANIZATIONS AND PROJECT
MANAGERS
Organizations
 Use of an integrated toolbox
 Project leaders growth
 Streamlined project delivery process
 Project metrics
Project managers
 Project management knowledge
 Performance competency
 Personal competency
 Understanding change
 Effective use of technology
23

SUGGESTED SKILLS FOR PROJECT MANAGERS
Project Management BOK
Application area knowledge, standards, and regulations
Project environment knowledge
General management knowledge and skills
Soft skills
24

IMPORTANCE OF PEOPLE AND LEADERSHIP SKILLS
A study conduced by Jennifer Krahn in 2006
 People skills
 Leadership
 Listening
 Integrity, ethical behavior, consistent
 Strong at building trust
 Verbal communication
 Strong at building teams
 Conflict management
 Critical thinking
25

SUMMARY
Software/ software engineering
IT project failure / investment
Project / program
Project and portfolio management
Project management framework
Project success factors
Successful organizations and managers
Suggested skills for project managers
26

what is software Engineering ||

More Related Content

What's hot (19)

Similar to what is software Engineering || (20)

Recently uploaded (20)

what is software Engineering ||