Software Engineering and Project Management: Drdivyasindhulekha Assistant Professor

Software Engineering and
Project Management
Dr D i v ya S i n dhu L e k h a
A s s i stant Pro fess or
CSE 312 SOFTWARE ENGINEERING AND PROJECT MANAGEMENT, ODD SEMESTER, 2021 1
A quick recap
Course outline
Software, Software vs. Hardware, Concerns and Challenges, Motivation for SE
Software applications – based on information content and determinacy
SE as a Layered Technology
tools
methods
process model
a “quality” focus
Software Engineering
Outline
▪Generic View of Software Engineering
▪Software Process
▪Software Process Maturity Levels
▪Software Process Models
Generic View of SE
Engineering?
Generic View of SE
Engineering?
Analysis, design, construction, verification, and management of technical entity.
Generic View of SE
Engineering?
General activities:
Generic View of SE
Engineering?
General activities :
1. Define the technical entity: characteristics
Generic View of SE
Engineering?
2. Construct the entity: Error-proof/ Fail-safe approaches
Generic View of SE
Engineering?
2. Construct the entity: Error-proof/ Fail-safe approaches
3. Support the entity over long term: in corrections, adaptations, and
enhancements.
Generic View of SE
Software Engineering?
Analysis, design, construction, verification, and management of software.
Generic View of SE
Software Engineering?
Analysis, design, construction, verification, and management of software.
3 generic phases:
1. Definition
2. Development
3. Support
Definition phase: Software engineer
attempts to identify
what information is to be processed,
what information is to be
processed,
what function and

performance are desired,
what information what system
is to be behavior can be
processed, expected,
what function
and performance
are desired,
what
information is what system
to be behavior can be
processed, expected,
what function what interfaces

and are to be
performance established,
are desired,
what
information what system what design
is to be behavior can constraints
processed, be expected, exist, and
what what
function and interfaces
performance are to be
are desired, established,
what
information is what system what design
to be behavior can be constraints
processed, expected, exist, and
what function what interfaces what validation

and are to be criteria are
performance established, required to
are desired, define a
successful
system.
Definition phase
what information is to what system behavior what design
be processed, can be expected, constraints exist, and
what function and what interfaces are to what validation criteria

performance are be established, are required to define
desired, a successful system.
3 major tasks:
1. System or information engineering
2. Software project planning
3. Requirements analysis
Development phase: Software
engineer attempts to define
how data are to be structured,
how data are to be

structured,
how function is to be
implemented within a
software architecture,
how procedural details
how data are to be are to be
structured, implemented,
how function is to be
implemented within a
how procedural
how data are to details are to be
be structured, implemented,
how function is to how interfaces

be implemented are to be
within a software characterized,
architecture,
how the design will
be translated into a
programming
how procedural language (or
how data are to be details are to be nonprocedural
structured, implemented, language), and
how function is to how interfaces are

be implemented to be
within a software characterized,
architecture,
how the design
will be translated
into a
programming
how procedural language (or
how data are to details are to be nonprocedural
be structured, implemented, language), and
how function is how interfaces how testing will

to be are to be be performed.
implemented characterized,
within a
software
architecture,
how the design will be
translated into a
programming language (or
how data are to be how procedural details nonprocedural language),
structured, are to be implemented, and
how function is to be how interfaces are to be how testing will be

implemented within a characterized, performed.
3 specific technical tasks:

1. Software design
2. Code generation
3. Software testing
Support phase
Focuses on
➢Change associated with error correction,
➢Adaptations required as the software's environment evolves, and
➢Changes due to enhancements brought about by changing customer
requirements.
Support phase
4 types of changes:
1. Correction
2. Adaptation
3. Enhancement
4. Prevention
Software Process
Common process framework
❑Framework activities and Umbrella activities
A framework activity
❑Activities applicable to all software projects
❑Regardless of size or complexity of software.
An Umbrella activity
❑Overlay the process model
❑Independent of any one framework activity and occur throughout the process.
❑E.g. software quality assurance, software configuration management, and measurement
Common process framework
A Task set
A collection of
❑ software engineering work tasks,
❑ project milestones,
❑ work products, and
❑ quality assurance points
Process Maturity Levels
Level 1: Initial.
❑ Process is characterized as ad hoc and occasionally even chaotic.
❑ Few processes are defined, and success depends on individual effort.
Level 2: Repeatable.
❑ Basic project management processes established.
❑ E.g. track cost, schedule, and functionality.
❑ The necessary process discipline is in place.
❑ Repeat earlier successes on projects with similar applications.
Process Maturity Levels
Level 3: Defined. – LEVEL 2 +
❑ The software process is documented, standardized, and integrated.
❑ Organization-wide software process
Level 4: Managed. - LEVEL 3+
❑ Measuring quality of the software process and product.
❑ Process and products are controlled using detailed measures.
Level 5: Optimizing. – LEVEL 4 +
❑ Continuous process improvement is enabled
❑ by quantitative feedback from the process and
❑ from testing innovative ideas and technologies
Process Maturity Levels – SEI CMM
❑To determine an organization’s current state of process maturity
❑Software Engineering Institute (SEI) Capability Maturity Model (CMM)
❑Uses an assessment that results in a five point grading scheme.
❑The grading scheme determines compliance with a capability maturity model (CMM)
❑CMM defines key activities required at different levels of process maturity
Additional Reads
SEI CMM Documentation:
https://resources.sei.cmu.edu/asset_files/MaturityModule/1995_008_001_16355.pdf

Software Engineering and Project Management: Drdivyasindhulekha Assistant Professor

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Engineering and Project Management: Drdivyasindhulekha Assistant Professor

Uploaded by

Copyright:

Available Formats

Software Engineering and

what information is to be processed,

what function and

what function what interfaces

what function what interfaces what validation

what function and what interfaces are to what validation criteria

how data are to be structured,

how data are to be

how function is to how interfaces

how function is to how interfaces are

how function is how interfaces how testing will

how function is to be how interfaces are to be how testing will be

3 specific technical tasks:

You might also like