All about Project Management :)

1. A Seminar
on
Project
Management
Presented By Mr. Raviraj Solanki

2. Content
• What is Project?
• What is Management?
• What is Project Management?
• Project Environment
• Software Engineering
• Software development Models
• DFD
• Conclusion

3. What is Project?
• It is a sequence of tasks.
• It is planned from beginning to
end.
• It is bounded by time,
resources and required results.
• Defined outcome and
deliverables.
• It has deadline.
• It has limit number of people,
supplies and capital

4. What is Management?
• It is the process of dealing with or controlling things
or people.

5. What is Project Management?
• Project management is the application processes,
methods, knowledge, skills and experience to achieve
the project objectives.
• A project is a unique, undertaken to achieve planned
objectives, which could be defined in terms of outputs,
outcomes or benefits.

10. What is Software Engineering?
• There are two words ‘software’ and
‘engineering’.
• Engineering forces us to focus on
systematic, scientific and well defined
processes to produce a good quality
product.
• The application of a systematic,
disciplined, quantifiable approach to the
development, operation and maintenance
of software, and the study of these
approaches, that is, the application of
engineering to software.

12. SDLC
• SDLC provides a series of steps to be followed to
design and develop a software product efficiently.
• SDLC includes following steps
– Requirement gathering & Analysis
– System Design
– Coding
– Testing
– Deployment
– Maintenance

14. Requirement gathering
• Analysts and engineers
communicate with the
client and end-users to
know their ideas on what
the software should
provide and which features
they want the software to
include.

15. FEASIBILITY STUDY
• A description of the tasks the system is required to do.
• A feasibility is a study made before committing to a
project
• A feasibility study is carried out to select the best system
that meets performance requirements.
• The main aim of the feasibility study activity is to
determine whether it would be financially and
technically feasible to develop the product.
• A feasibility study leads to a decision:
– Go ahead
– Do not go ahead
– Think again

16. FEASIBILITY STUDY

17. Technical Feasibility
• Determine available hardware.
• Determine available computer with configuration.
• Determine available software.
• Find out technical feasibility required for proposed system
1) It mentions new hardware requirements of proposed system.
2) It Mentions Computer with new configuration requirements of
proposed system.
3) It mentions New software requirements of the proposed system.

18. Economical Feasibility
1) Feasibility study cost.
2) Cost converting existing system to proposed system.
3) Cost to remolding architecture of the office, machineries, rooms
etc.
4) Cost of hardware's.
5) Cost of operating Software’s.
6) Cost of Application software’s.
7) Cost of training.
8) Cost of documentation preparation.

19. Operational Feasibility (Behavioral feasibility)
• It find out whether the proposed System will be suitable using
three types of aspects;
• That are human, organizational, and political aspects.
• It finds out whether there is any direct-indirect conflict from the
user of this system or not?
• It finds whether the operations of proposed system is easy or not
as compare to existing system.
• It find out whether the user or customer of the system requires
extra training or not?
• It finds if any job reconstruction is required or not?
• Watches the feelings of the customers as well as user.
• System should provide right & accurate information to user or
customer at right place as well as at right time.

20. System Analysis
• System analysis includes Understanding of
software product limitations, learning system
related problems or changes to be done in
existing systems beforehand, identifying and
addressing the impact of project on
organization and personnel etc.
• The project team analyzes the scope of the
project and plans the schedule and resources
accordingly.
• Fact-Finding Techniques

21. System Designing
• System Design helps in
specifying hardware and
system requirements and
also helps in defining
overall system
architecture.
• The system design
specifications serve as input
for the next phase of the
model.
• For e.g.: DFD, UML

22. Implementation / Coding
• On receiving system design
documents, the work is divided
in modules/units and actual
coding is started.
• Since, in this phase the code is
produced so it is the main
focus for the developer.
• This is the longest phase of
the software development life
cycle.

23. Testing:
• After the code is developed it is
tested against the requirements to
make sure that the product is
actually solving the needs
addressed and gathered during the
requirements phase.
• During this phase all types of
functional testing like unit testing,
integration testing, system testing,
acceptance testing are done as
well as non-functional testing are
also done.

24. Deployment
• After successful testing the product is delivered /
deployed to the customer for their use.
• As soon as the product is given to the customers they will
first do the beta testing.
• If any changes are required or if any bugs are caught,
then they will report it to the engineering team.
• Once those changes are made or the bugs are fixed then
the final deployment will happen.

25. Maintenance
• Once when the
customers starts using
the developed system
then the actual problems
comes up and needs to
be solved from time to
time.

26. Software Development Models
• Waterfall Model
• V-Shaped Model
• Evolutionary Prototyping Model
• Spiral Method (SDM)
• Iterative and Incremental Method
• Extreme programming (Agile
development)

27. Waterfall model

28. V-Shaped Model

29. Evolutionary Prototyping Model

30. Spiral Method (SDM)

31. Iterative and Incremental Method

32. Extreme programming (Agile development)

33. Data flow diagram
• Data flow diagram is graphical representation of flow of
data in an information system.
• It is capable of Showing incoming data flow, outgoing
data flow and stored data.
• There is a prominent difference between DFD and
Flowchart.
• The flowchart depicts flow of control in program
modules.
• DFDs depict flow of data in the system at various levels.

34. DFD Notation

35. Levels of DFD
• Level-0
– It also known as
context level.
– Show the overview of
system.
– Only a Single Process
will be used in this
level.
– We can not use data
store symbol in it.

36. Level-1
–It gives details view of the system.
–We can use all symbols of dfd in it.
–Must have multiple entity and processes
and data stores in it.

39. Anything that can be measured,
…..can be improved