UNIT1 SEMD
Uploaded by
NAMDEOUNIT1 SEMD
Uploaded by
NAMDEOUNIT 1:Introduction to Software
Engineering
• Nature of Software, Software Engineering, The
Software Process, Software Myths, A Generic Process
Model Vs Prescriptive Process Models: The waterfall
Model, Incremental Process Models, Concurrent
Models, The Unified Process , Agility Principles,
Extreme Programming(XP), SCRUM.
UNIT II:Requirement
Engineering
• Requirement Engineering, Collaborative Requirements
Gathering, Quality Function Deployment, Elicitation
Work Product, Developing use cases, Building the
requirement model, Validating requirements,
Analysis: Scenario Based Modeling, UML Models,
Class-Based Modelling, Requirements Modeling
Strategies: Flow oriented modelling, SRS plan, Case
study
UNIT III:Project Planning and Management
• The Management Spectrum, Software Scope, Problem
Decomposition, Process Decomposition, Process and
project metrics, Size-Oriented Metrics, Function-
Oriented Metrics, Software Process Reconciling LOC
and FP metrics, Object- Oriented Metrics, Integrating
metrics within the software project Estimation,
Decomposition, Process based Estimation, Estimation
with use cases Empirical Estimation Models, The
Structure of Estimation Models, The COCOMO II Model,
Scheduling: Tracking the Scheduling, Project Plan,
Application
UNIT IV: Introduction to Software Design
• Introduction to Software Design, design methods:
procedural/structural and object oriented,
Requirement Vs Analysis, Vs Architecture Vs Design
Vs Development 4+1 Architecture, case study of
transferring requirement to design, UP,COMET use
case based software life cycle, Introduction to UML-
Basic building blocks, Reusability, Use case
Modeling, Use case template.
UNIT V:Static Modeling
• Analysis Vs Design, Class diagram-Analysis-Object &
Classes finding analysis & Design-Design classes,
refining analysis relationships, Inheritance &
Polymorphism, Object diagram, Component
diagram-Interfaces & Components, deployment
diagram, Package diagram
UNIT VI:Dynamic Modeling
• Interaction & Interaction overview diagram,
Sequence diagram,
• Timing diagram,
• Communication diagram,
• Advanced state machine diagram,
• Activity diagram
Rubrics for the CIA Calculation
• CIA marks will be given based on NPTEL assignment
marks as follows.
• Average of best 6 assignments marks out of 12
assignments will be consider for CIA.
• No other rubrics is necessary to define for NPTEL
assignments.
• Additional weightage of 5 Marks will be given for
NPTEL Certification with limit to maximum 20 CIA
marks .
PROF. N. D. KAPALE
PROF. N. D. KAPALE
PROF. N. D. KAPALE
PROF. N. D. KAPALE
PROF. N. D. KAPALE
PROF. N. D. KAPALE
THANK YOU
PROF. N. D. KAPALE
N. D. KAPALE
N. D. KAPALE
N. D. KAPALE
N. D. KAPALE
N. D. KAPALE
N. D. KAPALE
N. D. KAPALE
N. D. KAPALE
N. D. KAPALE
N. D. KAPALE
N. D. KAPALE
N. D. KAPALE
N. D. KAPALE
N. D. KAPALE
N. D. KAPALE
N. D. KAPALE
• We can study the
political map which
focuses on the different
provinces, capital,
major cities, railway
road connectivity etc.
• You will look into the
physical map and try to
find out the vegetation,
the elevation of the
different places, rivers,
sea shore and etc.
Why to study Software Engineering
• To acquire skills to develop large programs.
-Handling exponential growth in complexity with size.
-Systematic techniques based on abstraction(modelling)and
decomposition
• Learn systematic techniques of.
-specification,design,user interface development,testing,project
management,maintenance, etc
-appreciate issues that aries in the team development.
• To acquire skills to be better programmer
-Higher Productivity
-Better quality programs
What is Software?
1) Instructions (programs) that when executed
provide desired function and performance.
2) Data structures that enable the programs to
adequately manipulate information.
3) Documents that describe the operation and
use of the programs.
4)A logical rather than physical system element.
Characteristics of Software
• Software is engineered/developed
• Software doesn’t wear out
• Software is custom built
• Software is complex
Failure (“Bathtub”) Curve for
Hardware
Failure Rate Infant
Wear
mortality
out
Time
Wear vs. Deterioration
increased failure
rate due to side effects
Failure
rate
change
actual curve
idealized curve
Time
Software
• System software
Applications
• Real-time software
• Business software
• Engineering/scientific software
• Embedded software
• PC software
• WebApps (Web applications)
• AI software
The Cost of
Change 60-100x
1.5-6x
1x
Definition Development After release
Software Poses
Challenges
How do we ensure the quality of the software that
we produce?
How do we meet growing demand and still
maintain budget control?
How do we upgrade an aging "software plant?"
How do we avoid disastrous time delays?
How do we successfully institute new software
technologies?
Software Myths
• Management
• We have books with standards & Procedures to
develop software.
• We have purchased new computers, software & tools.
• We’ll add more people/programmer to catch up
schedule.(Mangolian Horde Concepts)
• I outsourced it, I’m done and relaxed.
• Customer
• We have general objectives, let’s start.
• Change is easily accommodated, as software is
flexible.
• Practitioner
• Once we write program and be done.
• I can’t assess quality until it is running.
• I only need deliver working code.
• Software engineering is about meaningless
documents
A Layered
Technology
Software Engineering
- provide support for methods and
tools processes
methods - technical how to’s
-glue that holds layers together
process model
a “quality” focus - bedrock
Software Process Models/Software Life Cycle Model(SDLC)
• A life cycle is the set of stages through which something evolves.
• Descriptive and diagramatic model of software life cycle
• Identifies all activities undertaken during software product development
• Established precedence ordering amoungst various activities
• Divide life cycle in to phases
Why Life cycle Model
• Helps Common Understanding of activities among software developers.
• Helps to identify inconsistencies,redundencies and omission in the
development process.
• Helps in tailoring process model for specific project.
• Development team identify suitable life cycle model and adhere to it.
• Helps in developement of software in disciplined and systematic maner.
• Must be precise understanding among team members as to when to do
what.
• Project Manager can at any time accurately tell at which stage (Design,
coding, testing etc.) project is.
• Avoids 99% Complete syndrome.
Classical Waterfall Model
