This slide will guide you towards basic concept of Software Management Approach

1. Chapter 10 : Project
Management Approach
Training Presentation

2. Topics
Project Management Approach.
Terminology related to project.
Key points while creating Software projects.
Demo project
Why project management ?

3. Project
Management

4. Why ??
Software
development is a
kind of all new stream
in world business and
there’s various
models that are
followed in building
software products.

5. Software Projects
A Software Project is the
complete procedure of
software development
from requirement
gathering to testing and
maintenance, carried out
according to the
execution
methodologies, in a
specified period of time
to achieve intended
software product.

6. Project management
Software project management comprises of a
number of activities, which contains planning of
project, deciding scope of software product,
estimation of cost in various terms, scheduling of
tasks and events, and resource management.
• Project Planning
• Scope Management
• Project Estimation

7. Purpose of project planning
The purpose of project planning is to identify the
scope of the project, estimate the work involved,
and create a project schedule. Project planning
begins with requirements that define the software
to be developed.
Different methodologies used while creating
projects:-

8. SRS

9. SRS
A software requirements
specification (SRS) is a
description of a software
system to be developed,
laying out functional and
non-functional
requirements, and may
include a set of use cases
that describe interactions
the users will have with
the software.

10. SRS
Software
Specification
depends on
many things.

11. DFD

12. DFD
It is a graphical representation
of the "flow" of data through an
information system, modelling
its process aspects. A DFD is
often used as a preliminary step
to create an overview of the
system, which can later be
elaborated.[2] DFDs can also be
used for the visualization of
data processing (structured
design).

13. DFD
It is a graphical representation
of the "flow" of data through an
information system, modelling
its process aspects. A DFD is
often used as a preliminary step
to create an overview of the
system, which can later be
elaborated.[2] DFDs can also be
used for the visualization of
data processing (structured
design).

14. ER
Diagrams

15. ER Diagrams
An entity–relationship model is the result of using a
systematic process to describe and define a subject area
of business data.
ERDs show entities in a database and relationships
between tables within that database.
It is essential to have ER-Diagrams if you want to create a
good database design.
The diagrams help focus on how the database actually
works.

16. Ex

17. JARVIS- Text to Speech Converter Application
DFD Level 0
JARVISUser ADMIN

18. Level 1 DFD
JARVIS
USER
Event
SELECTION
USER

19. All about E-R Diagrams
The original notation for ER-Diagrams uses rectangles
to represent entities, and diamonds to represent
relationships
There are three basic elements in ER-Diagrams:
Entities are the "things" for which we want to
store information. An entity is a person, place,
thing or event.
Attributes are the data we want to collect for an
entitiy.
Relationships describe the relations between the
entities.

20. Project DEMO

21. Project DEMO