Professional Documents
Culture Documents
Unit : 01
Introduction to
Software and
Software Engineering
Outline
Software, Characteristics of Software, Software Application Domains
Software Engineering, Software Engineering Layered Approach
Software Process, Process Framework Activities , Umbrella Activities
Software Myths
• Management Myth
• Customer Myth
• Practitioner's/Developer Myth)
Software Process Models
• The Waterfall Model
• Incremental Process Model
• Prototyping Model, Spiral Model
• Spiral Model
• Rapid Application Development Model (RAD)
Component based Development
WHY SOFTWARE ENGINEERING
Why to Study Software Engineering?
1 2 3 4 5
How the How the How the How the How the
Customer Project System Programmer Business
Explains Leader Analyst Works Consultant
Requirement understand it design it on it describe it
4
Why to Study Software Engineering?
6 7 8 9 10
5
Why to Study Software Engineering?
7
Definition of Software Engineering
Definition
software engineering is defined as a process of analyzing user
requirements and then designing, building, and testing
software application which will satisfy those requirements.
EVOLVING ROLE OF SOFTWARE
What is Software?
Software is
1)Computer program that when executed provide desired features, function & performance
2)Data Structure that enable programs to easily manipulate information
3)Descriptive information in both hard and soft copy that describes the operation and use of
programs
Thus we can define Software as a combination of computer program , Data Structure &
Descriptive information
Computer
+ Data
+ Documents
Program Structure Soft & Hard
10
Characteristics of Software
Software is developed or engineered
It is not manufactured like hardware
Manufacturing phase can introduce quality problem that are nonexistent (or easily
corrected) for software
Both requires construction of “product” but approaches are different
Software doesn’t “wear-out” Change
Increate failure rate due to
side effect
Infant
“Wear out”
Failure Rate
Failure Rate
morality
Actual Curve
Idealized Curve
Time Time
12
Software Application Domains
• Artificial intelligence
Software Product line Embedded
Software Software
13
Cont…
System Software : System Software is necessary to manage the computer resources and
support the execution of application programs. Software like operating systems,
compilers, editors and drivers, etc., come under this category
Scientific Software : Scientific and engineering software satisfies the needs of a scientific
or engineering user to perform enterprise-specific tasks. Examples are software like
MATLAB, AUTOCAD, PSPICE, ORCAD, etc.
14
Cont…
Product Line Software :It focuses on limited application but mass consumer
market for example word processing, spreedsheets , computer graphics,
multimedia, entertainment, databases etc.
15
Cont…
16
SOFTWARE CRISIS ON THE
HORIZON & SOFTWARE MYTHS
Software Myths
Most, experienced experts have seen myths or superstitions
(false beliefs) or misleading attitudes which creates major
problems for management and technical people.
These types of software-related myths are listed below.
Management Myths
Myth 1:
We have all the standards and procedures available for software development.
Fact:
Software experts do not know all the requirements for the software development.
Myth 2:
The addition of the latest hardware programs will improve the software
development.
Fact:
The role of the latest hardware is not very high on standard software
development; instead Engineering tools help the computer, they are more
important than hardware to produce quality and productivity.
Management Myths
Myth 3:
With the addition of more people and program planners to Software
development can help meet project deadlines (If lagging behind).
Fact:
If software is late, adding more people will merely make the problem
worse. This is because the people already working on the project now
need to spend time educating the newcomers
Customers Myths
Myth 1:
A general statement of intent is enough to start writing plans (software development)
and details of objectives can be done over time.
Fact:
Official and detailed description of the database function, ethical performance,
communication, structural issues and the verification process are important.
Unambiguous requirements (usually derived iteratively) are developed only through
effective and continuous
communication between customer and developer.
Customers Myths
Myth 2:
Software requirements continually change, but change can be easily accommodated because
software is flexible
Fact:
It is true that software requirements change, but the impact of change varies with the time at
which it is introduced. When requirements changes are requested early (before design or code
has been started), the cost impact is relatively small. However, as time passes, the cost impact
grows rapidly—resources have been committed, a design framework has been established, and
change can cause upheaval that requires additional resources and major design modification.
Practitioner’s Myths
Myths 1:
They believe that their work has been completed with the writing of the plan.
Fact:
It is true that every 60-80% effort goes into the maintenance phase (as of the latter software release). Efforts are
required, where the product is available first delivered to customers.
Myths 2:
There is no other way to achieve system quality, until it is “running”.
Fact:
Systematic review of project technology is the quality of effective software verification method. These updates are
quality filters and more accessible than test.
Practitioner’s Myths
Myth 3:
An operating system is the only product that can be successfully exported project.
Fact:
A working system is not enough, the right document brochures and booklets are also required to provide guidance &
software support.
Myth 4:
Engineering software will enable us to build powerful and unnecessary document & always delay us.
Fact:
Software engineering is not about creating documents. It is about creating a quality product. Better quality leads to
reduced rework. And reduced rework results in faster delivery times
Software Engineering
Software Engineering is the science and art of building (designing and writing programs) a
software systems that are:
1) on time
2) on budget
3) with acceptable performance
4) with correct operation
25
Software Engineering Layered Approach
Quality
Main principle of Software Engineering is Quality Focus.
An engineering approach must have a focus on quality.
Total Quality Management (TQM), Six Sigma, ISO 9001, ISO 9000-3, CAPABILITY MATURITY
MODEL (CMM), CMMI & similar approaches encourages a continuous process
improvement culture
Process Layer
It is a foundation of Software Engineering, It is the glue the holds the technology layers
together and enables logical and timely development of computer software.
It defines a framework with activities for effective delivery of software engineering technology
It establish the context in which technical methods are applied, work products (models,
documents, data, reports, forms, etc.) are produced, milestones are established, quality is
ensured, and change is properly managed.
27
Software Engineering Layered Approach Cont.
Method
It provides technical how-to’s for building software
It encompasses many tasks including communication, requirement analysis, design
modeling, program construction, testing and support
Tools
Software engineering tools provide automated or semiautomated support for the process
and the methods
Computer‐aided software engineering (CASE) is the scientific application of a set of tools
and methods to a software system which is meant to result in high‐quality, defect‐free,
and maintainable software products.
CASE tools automate many of the activities involved in various life cycle phases.
28
Software Process
A process is a collection of activities, actions and tasks that are performed when some work product is to be created
A process is not a rigid prescription for how to build the software, rather it is adaptable approach that enables the
people doing the work to pick and choose the appropriate set of work actions and tasks
An activity is applied regardless of the application domain, size of the project, complexity of the effort, or degree
of accuracy with which software engineering is to be applied.
An action (e.g., architectural design) encompasses a set of tasks that produce a major work product (e.g., an
architectural design model).
A task focuses on a small, but well-defined objective (e.g., conducting a unit test) that produces a noticeable
outcome.
Each of these activities, actions & tasks reside within a framework or model
29
Software Process Software Process Framework
Figure represents “The Software Process” Process framework
Each framework activity is populated by Umbrella activities
Software Process
Work tasks
defined by a task set that identifies work … Work products
to be completed, product to be … Quality assurance points
33
Umbrella Activities Cont.
Reusability management: it defines criteria for work product reuse (including software
components) and establishes mechanisms to achieve reusable components.
Work product preparation and production: it encompasses (includes) the activities
required to create work products such as models, documents, logs, forms and lists.
34
Software Myths Beliefs about software and the process used to build it.
Management
Myths
Customer Myths
“Misleading Attitudes
that cause serious Practitioner's
(Developer)
problem” are myths. Myths
35
Management myth - 1 & 2
Reality Reality
Are software practitioners aware of It takes much more than the latest
standard’s existence? model computers to do high-quality
Does it reflect modern software software development.
engineering practice? Computer-aided software engineering
(CASE) tools are more important than
Is it complete?
hardware.
Is it streamlined to improve time to
delivery while still maintaining a focus on
quality?
In many cases, the answer to all of these
questions is "no.“ 36
Management myth - 3 & 4
38
Practitioner's (Developer) myth – 1 & 2
Once we write the program, our job I can’t access quality until it is
is done. running.
Reality Reality
Experts say "the sooner you begin 'writing One of the most effective software
code', the longer it will take you to get quality assurance mechanisms can be
done." applied from the beginning of a project
- the technical review.
Industry data indicates that 60 to 80 %
effort expended on software will be after it Software reviews are more effective
“quality filter” than testing for finding
is delivered to the customer for the first
software defects.
time.
39
Practitioner's (Developer) myth – 3 & 4
Reality Reality
A working program is only one part of a Software engineering is not about
software configuration. creating documents. It is about creating
A variety of work products (e.g., models, a quality product.
documents, plans) provide a foundation Better quality leads to reduced rework.
for successful engineering and, more And reduced rework results in faster
delivery times.
important, guidance for software support.
40
Software Process Models The process model is the abstract representation of process.
Size of team
42
Different Process Models
Process Models
43
TYPES OF PROCESS MODEL
44
Classic life cycle or linear sequential model
The Waterfall Model
Communication
• Project initiation
• Requirements
Planning
gathering • Estimating
• Scheduling
Modeling
• Tracking • Analysis
• Design
Construction
• Coding
• Testing
Deployment
• Delivery
• Support
• Feedback
When requirements for a problems are well understood then this model is used
in which work flow from communication to deployment is linear
45
The Waterfall Model
When to use ? Advantages
Requirements are very well known, clear Simple to implement and manage
and fixed
Product definition is stable Drawbacks
Technology is understood Unable to accommodate changes at later
There are no ambiguous (unclear) stages, that is required in most of the
cases.
requirements
Working version is not available during
Ample (sufficient) resources with
development. Which can lead the
required expertise are available freely
development with major mistakes.
The project is short
Deadlock can occur due to delay in any
step.
Not suitable for large projects.
No parallism
46
Evolutionary Process Models
When a set of core product or system requirements is well understood but the details of product or
system extensions have yet to be defined. (Customers have general objectives of software but do not
have detailed requirements for functions & features ).
In this situation there is a need of process model which specially designed to accommodate product that
evolve with time.
Evolutionary Process Models are specially meant for that which produce an increasingly more complete
version of the software with each iteration.
They are characterized in a manner that enables you to develop increasingly more complete versions of
the software.
48
PROTOTYPE MODEL
When the requirement are not clear then prototype model is used to finalize the
requirement.
In the early stage of the development SRS document contain the limited set of the
document.
In this model developer will prepare quick design, build prototype ( WORKING MODEL) and
then take feedback from customer.
49
Prototyping model cont.
It works as follow
Communicate with stockholders &
define objective of Software
Deployment & Communication
Feedback Identify requirements & design quick plan
If the customer feedback does not contain any additional set of requirements then the
corresponding sample product ( PROTOTYPE MODEL) SRS document will be finalized.
After finalizing the sample model or prototype model two kinds of prototype model is used.
51
Prototyping model cont.
Problem Areas
Customer demand that “a few fixes” be applied to make the prototype a working
product, due to that software quality suffers as a result
Developer often makes implementation in order to get a prototype working quickly;
without considering other factors in mind like OS, Programming language, etc.
Advantages
Users are actively involved in the development
Since in this methodology a working model of the system is provided, the users get a
better understanding of the system being developed
Errors can be detected much earlier
52
RAD (RAPID APPLICATION DEVELOPMENT)
RAD is used when the requirement is more clear and the schedule is very sort.
In the RAD model to develop the operational final product in less time, there is a need of
modularity design.
Modularity design is a decomposition(means break) technique that means divide the project
into sub modules, develop them simultaneously or parallelly.
Before Approaching to the modularity design there is a need of considering the man power
requirement.
53
CONT...
When the organization contain efficient man power then divide the man power into teams
and assign the independent modules into teams to develop simultaneously.
54
Rapid Application Development Model (RAD) It is a type of
incremental model in
Team - 1 which; components or
Communication functions are
Modeling developed in parallel.
Construction
Planning • Integration
• Delivery Rapid development
Team - 2 • Feedback is achieved by
• Business
Modeling Modeling
component based
• Data Deployment construction
Modeling Construction
• Process
Modeling This can quickly
Team - 3 • Component
Reuse give the customer
Modeling • Automatic something to see
Code
Construction Generation
and use and to
• Testing provide feedback.
55
Rapid Application Development Model (RAD) Cont.
Communication This phase is used to understand business problem.
Modeling Construction
Business Modeling: Information flow among the It highlighting the use of pre-
business. existing software component.
Ex. What kind of information drives (moves)?
Who is going to generate information? Deployment
From where information comes and goes?
Integration of modules
Data Modeling: Information refine into set of developed by parallel teams,
data objects that are needed to support delivery of integrated software
business. and feedback comes under
Process Modeling: Data object transforms to deployment phase.
information flow necessary to implement
business. 56
Rapid Application Development Model (RAD) Cont.
When to Use?
There is a need to create a system that can be modularized in 2-3 months of time.
High availability of designers and budget for modeling along with the cost of automated
code generating tools.
Resources with high business knowledge are available.
Advantages Drawback
Reduced development time. For large but scalable projects, RAD requires
sufficient human resources.
Increases reusability of components.
Projects fail if developers and customers are
Quick initial reviews occur. not committed in a much shortened time-
Encourages customer feedback. frame.
Integration from very beginning Problematic if system can not be modularized.
solves a lot of integration issues. Not appropriate when technical risks are high
(heavy use of new technology). 57
EVOLUTIONARY PROCESS MODEL
BY USING the evolutionary process model, we can develop the product functionality part by
part or release by release or category by category.
After the same iteration the final product will be available in the customer place.
58
Incremental Process Model or Iterative Enhancement Model
Incremental means MODULE BY MODULE.
There are many situations in which initial software requirements are reasonably well
defined, but the overall scope of the development effort prevent a purely linear process.
In such cases, there is a need of a process model that is designed to produce the software in
increments.
59
Software Functionality & Features
Incremental Process Model
The incremental model combines elements of linear and parallel process flows.
This model applies linear sequence in a iterative manner.
Initially core working product is delivered.
Each linear sequence produces deliverable “increments” of the software.
60
Incremental Process Model
e.g. word-processing software developed using the incremental model
It might deliver basic file management, editing and
document production functions in the first
increment Advantages
more sophisticated editing in the second increment; Generates working software quickly
spelling and grammar checking in the third and early during the software life
increment; and cycle.
advanced page layout capability in the fourth It is easier to test and debug during
increment. a smaller iteration.
When to use ? Customer can respond to each built.
When the requirements of the complete Lowers initial delivery cost.
system are clearly defined and understood but Easier to manage risk because risky
staffing is unavailable for a complete pieces are identified and handled
implementation by the business deadline. during iteration.
61
SPIRAL MODEL
Spiral model is continuous improvement process model.
This model is suitable to develop the complex systems because continuous qualitatively
feedback is accepted from the customer to improve the product functionality.
In this model the product development is started from the core product to more
sophisticated(COMPLEX) product. LIKE BANKING SOFTWARE.
62
CONT...
IN THIS MODEL WE CONSIDER 6 ACTIVITIES
Customer Communication
Planning
Risk Analysis
Engineering
Construction and release
Customer Evaluation (Qualitatively feedback from the customer)
63
The Spiral Model
66
Component based Development
Component based development incorporates the following steps
1. Available component-based products are researched & evaluated for software
development.
2. Component integration issues are considered.
3. A software architecture is designed to accommodate the components.
4. Components are integrated into the architecture.
5. Testing is conducted to insure proper functionality.
Advantages
It leads to software reuse.
It reduces development cycle time.
Reduction in project cost.
67
Product & Process
If the process is weak, the end product will suffer. But more confidence on process is also
dangerous.
People gain more satisfaction from the creative process as they do from the end product.
Like an artist enjoys the brush strokes as much as the framed result.
A writer enjoys the search for the proper metaphor (comparison) as much as the finished book.
As software professional, you should also derive as much satisfaction from the process as
the end product.
The duality (contrast) of product and process is one important element in keeping creative
people engaged as software engineering continues to evolve.
68
Thank You…