Unit 1 Introduction to Software and Software Engineering

Define Software:
 Software can be defined as one of the following
o (1) Instructions (computer programs) that when executed provide desired function
and performance,
o (2) Data structures that enable the programs to adequately manipulate
information,
o (3) Documents that describe the operation and use of the programs.

Software Characteristics:
 The following are the characteristics of the software
o Software is developed or engineered; it is not manufactured in the classical
sense.
- In Software development and
Hardware manufacturing process,
there are some differences.
- Hardware Manufacturing process
produces “Quality Problems”, that
is nonexistent in Software.
- Software costs are concentrated in
engineering.
- This means that software projects
cannot be managed as if they were
manufacturing projects.
- The Fig is also known as “BathTub Curve”

o Software doesn't "wear out."

- As time passes, however, the
failure rate rises again as
hardware components suffer from
the cumulative affects of dust,
vibration, abuse, temperature
extremes, and many other
environmental maladies. Stated
simply, the hardware begins to
wear out.
- Software is not susceptible to the
environmental maladies that
cause hardware to wear out.

Prepared By: Prof. Arvind Meniya, Asst. Prof., SSEC, Bhavnagar Page 1
 Unit 1 Introduction to Software and Software Engineering

- In theory, therefore, the failure rate curve for software should take the
form of the “idealized curve”
- During its life, software will undergo change (maintenance).
- As changes are made, it is likely that some new defects will be introduced,
causing the failure rate curve to spike as shown in Figure.
- When a hardware component wears out, it is replaced by a spare part.
There are no software spare parts.
- Every software failure indicates an error in design or in the process
through which design was translated into machine executable code.
- Therefore, software maintenance involves considerably more complexity
than hardware maintenance.

o Although the industry is moving toward component-based assembly, most

software continues to be custom built.
- In the hardware world, component reuse is a natural part of the
engineering process.
- In the software world, it is something that has only begun to be achieved
on a broad scale.
- A software component should be designed and implemented so that it can
be reused in many different programs.
- Modern reusable components encapsulate both data and the processing
applied to the data, enabling the software engineer to create new
applications from reusable parts.
- The data structure and processing detail required to build the interface are
contained with a library of reusable components for interface construction.

Software Applications:
- The following software areas indicate the breadth of potential
applications:

System Software.

- System software is a collection of programs written to service other

programs.
- Some system software (e.g., compilers, editors, operating system
components, drivers).

Real-time software

- Software that monitors/analyzes/controls real-world events as they occur

is called real time.

Prepared By: Prof. Arvind Meniya, Asst. Prof., SSEC, Bhavnagar Page 2
 Unit 1 Introduction to Software and Software Engineering

- Elements of real-time software include

 Data gathering component -- Collect Information
 Analysis Component – Transform info as per the requirement of
application
 Control/Output Component - Responds to the external
environment
 Monitoring Component - coordinates all other components so
that real-time response can be maintained.

Business Software

- Business information processing is the largest single software application

area.
- Discrete "systems" (e.g., payroll, accounts receivable/payable, inventory)
have evolved into management information system (MIS) software that
accesses one or more large databases containing business information.

Engineering and scientific software

- Engineering and scientific software have been characterized by "number

crunching" algorithms.
- Applications range from astronomy to volcanology.
- However, modern applications within the engineering/scientific area are
moving away from conventional numerical algorithms.
- Computer-aided design, system simulation, and other interactive
applications have begun to take on real-time and even system software
characteristics.

Embedded Software

- Intelligent products have become commonplace in nearly every consumer

and industrial market.
- Embedded software resides in read-only memory and is used to control
products and systems for the consumer and industrial markets.
- Embedded software can perform very limited (e.g., keypad control for a
microwave oven) or provide significant function and control capability
(e.g., digital functions in an automobile such as fuel control, dashboard
displays, and braking systems).

Personal computer Software

- The personal computer software market has grown rapidly over the past two
decades.

Prepared By: Prof. Arvind Meniya, Asst. Prof., SSEC, Bhavnagar Page 3
 Unit 1 Introduction to Software and Software Engineering

- Word processing, spreadsheets, computer graphics, multimedia, entertainment,

database management, personal and business financial applications, external
network, and database access are only a few of hundreds of applications.

Web-based Software

- The Web pages retrieved by a browser are software that incorporates executable
instructions (e.g., HTML, or Java), and data.
- In essence, the network becomes a massive computer providing an almost
unlimited software resource that can be accessed by anyone with a modem.

Artificial intelligence Software

- Artificial intelligence (AI) software makes use of non numerical algorithms to

solve complex problems that are not willing to computation or straightforward
analysis.
- Expert systems, also called knowledge based systems, pattern recognition (image
and voice), and game playing are representative of applications within this
category.

Software Myths:
Management myths

Myth: We already have a book that's full of standards and procedures for building software,
won't that provide my people with everything they need to know?

Reality:

The book of standards may very well exist, but is it used? Are software practitioners
aware of its existence? Does it reflect modern software engineering practice? Is it
complete? 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."

Myth: My people have state-of-the-art software development tools; after all, we buy them the
newest computers.

Reality:

It takes much more than the latest model mainframe, workstation, or PC to do high-
quality software development. Computer-aided software engineering (CASE) tools are
more important than hardware for achieving good quality and productivity, yet the
majority of software developers still do not use them effectively.

Prepared By: Prof. Arvind Meniya, Asst. Prof., SSEC, Bhavnagar Page 4
 Unit 1 Introduction to Software and Software Engineering

Myth:

If we get behind schedule, we can add more programmers and catch up.

Reality:

Software development is not a mechanistic process like manufacturing.

In the words of: "adding people to a late software project makes it later."

However, as new people are added, people who were working must spend time
educating the newcomers, thereby reducing the amount of time spent on productive
development effort. People can be added but only in a planned and well-coordinated
manner.

Myth:

If I decide to outsource the software project to a third party, I can just relax and let that firm build
it.

Reality:

If an organization does not understand how to manage and control software projects
internally, it will invariably struggle when it outsources software projects.

Customer myths

Myth:

A general statement of objectives is sufficient to begin writing programs— we can fill in the
details later.

Reality:

A poor up-front definition is the major cause of failed software efforts. A formal and detailed
description of the information domain, function, behavior, performance, interfaces, design
constraints, and validation criteria is essential.

These characteristics can be determined only after thorough communication between customer
and developer.

Prepared By: Prof. Arvind Meniya, Asst. Prof., SSEC, Bhavnagar Page 5
 Unit 1 Introduction to Software and Software Engineering

Software Engineering Layers:

 Software engineering is a layered technology. Referring to Figure, any engineering

approach (including software engineering) must rest on an organizational commitment
to quality.
 Total quality management and similar philosophies foster a continuous process
improvement culture, and this culture ultimately leads to the development of increasingly
more mature approaches to software engineering.
 The bedrock that supports software engineering is a quality focus.
 The foundation for software engineering is the process layer.
 Process defines a framework for a set of key process areas (KPAs) that must be
established for effective delivery of software engineering technology.
 Software engineering methods provide the technical how-to's for building software.
 Methods encompass a broad array of tasks that include requirements analysis, design,
program construction, testing, and support.
 Software engineering tools provide automated or semi-automated support for the process
and the methods.
 When tools are integrated so that information created by one tool can be used by another,
a system for the support of software development, called computer-aided software
engineering (CASE), is established.

Umbrella activities in Software Engineering

 Software engineering is a collection of interconnected phases.
 These steps are expressed or available in different ways in different software process
models.
 Umbrella activities are a series of steps or procedures followed by a software
development team to maintain the progress, quality, changes, and risks of complete
development tasks.
 The activities in the software development process are supplemented by many general
activities.

Prepared By: Prof. Arvind Meniya, Asst. Prof., SSEC, Bhavnagar Page 6
 Unit 1 Introduction to Software and Software Engineering

 Generally, common activities apply to the entire software project and help the software
development team manage and track progress, quality, changes, and risks.

Umbrella activities consist of different tasks:

 Software Project Tracking and Control

 Formal Technical Reviews

 Software Quality Assurance

 SCM or Software configuration management

 Document Preparation and Production

 Re-usability Management

 Measurement and Metrics

 Risk Management

Prepared By: Prof. Arvind Meniya, Asst. Prof., SSEC, Bhavnagar Page 7
 Unit 1 Introduction to Software and Software Engineering

Waterfall Model – Design

 Waterfall approach was first SDLC Model to be used widely in Software Engineering to
ensure success of the project.
 In "The Waterfall" approach, the whole process of software development is divided into
separate phases.
 In this Waterfall model, typically, the outcome of one phase acts as the input for the next
phase sequentially.
The following illustration is a representation of the different phases of the Waterfall Model.

The sequential phases in Waterfall model are −

 Requirement Gathering and analysis − All possible requirements of the system to be

developed are captured in this phase and documented in a requirement specification
document.

 System Design − The requirement specifications from first phase are studied in this
phase and the system design is prepared. This system design helps in specifying hardware
and system requirements and helps in defining the overall system architecture.

 Implementation − With inputs from the system design, the system is first developed in
small programs called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality, which is referred to as Unit Testing.

 Integration and Testing − All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire system is
tested for any faults and failures.

Prepared By: Prof. Arvind Meniya, Asst. Prof., SSEC, Bhavnagar Page 8
 Unit 1 Introduction to Software and Software Engineering

 Deployment of system − Once the functional and non-functional testing is done; the
product is deployed in the customer environment or released into the market.

 Maintenance − There are some issues which come up in the client environment. To fix
those issues, patches are released. Also to enhance the product some better versions are
released. Maintenance is done to deliver these changes in the customer environment.

Waterfall Model - Application

Every software developed is different and requires a suitable SDLC approach to be
followed based on the internal and external factors. Some situations where the use of Waterfall
model is most appropriate are −

 Requirements are very well documented, clear and fixed.

 Product definition is stable.

 Technology is understood and is not dynamic.

 There are no ambiguous requirements.

 Ample resources with required expertise are available to support the product.

 The project is short.

Waterfall Model - Advantages

Some of the major advantages of the Waterfall Model are as follows −

 Simple and easy to understand and use

 Easy to manage due to the rigidity of the model. Each phase has specific deliverables and
a review process.

 Phases are processed and completed one at a time.

 Works well for smaller projects where requirements are very well understood.

 Clearly defined stages.

 Well understood milestones.

 Easy to arrange tasks.

 Process and results are well documented.

Prepared By: Prof. Arvind Meniya, Asst. Prof., SSEC, Bhavnagar Page 9
 Unit 1 Introduction to Software and Software Engineering

Waterfall Model - Disadvantages

The major disadvantages of the Waterfall Model are as follows −

 No working software is produced until late during the life cycle.

 High amounts of risk and uncertainty.

 Not a good model for complex and object-oriented projects.

 Poor model for long and ongoing projects.

 Not suitable for the projects where requirements are at a moderate to high risk of
changing. So, risk and uncertainty is high with this process model.

 It is difficult to measure progress within stages.

 Cannot accommodate changing requirements.

 Adjusting scope during the life cycle can end a project.

 Integration is done as a "big-bang. at the very end, which doesn't allow identifying any
technological or business bottleneck or challenges early.

Prototype Model
 The prototype model requires that before carrying out the development of actual
software, a working prototype of the system should be built.
 A prototype is a toy implementation of the system.
 A prototype usually turns out to be a very crude version of the actual system, possible
exhibiting limited functional capabilities, low reliability, and inefficient performance as
compared to actual software.
 In many instances, the client only has a general view of what is expected from the
software product.
 In such a scenario where there is an absence of detailed information regarding the input
to the system, the processing needs, and the output requirement, the prototyping model
may be employed.

Prepared By: Prof. Arvind Meniya, Asst. Prof., SSEC, Bhavnagar Page 10
 Unit 1 Introduction to Software and Software Engineering

Steps of Prototype Model

1. Requirement Gathering and Analyst
2. Quick Decision
3. Build a Prototype
4. Assessment or User Evaluation
5. Prototype Refinement
6. Engineer Product

Advantage of Prototype Model

1. Reduce the risk of incorrect user
requirement
2. Good where requirement are
changing/uncommitted
3. Regular visible process aids
management
4. Support early product marketing
5. Reduce Maintenance cost.
6. Errors can be detected much earlier
as the system is made side by side.

Disadvantage of Prototype Model

1. An unstable/badly implemented prototype often becomes the final product.
2. Require extensive customer collaboration
3. Difficult to know how long the project will last.
4. Easy to fall back into the code and fix without proper requirement analysis, design,
customer evaluation, and feedback.
5. Prototyping tools are expensive.
6. Special tools & techniques are required to build a prototype.
7. It is a time-consuming process.

Prepared By: Prof. Arvind Meniya, Asst. Prof., SSEC, Bhavnagar Page 11
 Unit 1 Introduction to Software and Software Engineering

RAD (Rapid Application Development) Model

 The Rapid Application Development Model was first proposed by IBM in the
1980s.
 The critical feature of this model is the use of powerful development tools and
techniques.
 A software project can be implemented using this model if the project can be
broken down into small modules wherein each module can be assigned
independently to separate teams.
 These modules can finally be combined to form the final product.
 Development of each module involves the various basic steps as in the waterfall
model i.e analyzing, designing, coding, and then testing, etc. as shown in the figure.
 Another striking feature of this model is a short time span i.e the time frame for
delivery(time-box) is generally 60-90 days.

When to use RAD Model?

 When
o the customer has well-
known requirements,
o the user is involved
throughout the life cycle,
o the project can be time
boxed,
o the functionality
delivered in increments,
o high performance is not
required,
o low technical risks are
involved and the system can be modularized.

Advantages:

 The use of reusable components helps to reduce the cycle time of the project.
 Feedback from the customer is available at the initial stages.
 Reduced costs as fewer developers are required.
 The use of powerful development tools results in better quality products in
comparatively shorter time spans.
 The progress and development of the project can be measured through the various
stages.
 It is easier to accommodate changing requirements due to the short iteration time
spans.

Prepared By: Prof. Arvind Meniya, Asst. Prof., SSEC, Bhavnagar Page 12
 Unit 1 Introduction to Software and Software Engineering

Disadvantages:

o The use of powerful and efficient tools requires highly skilled professionals.
o The absence of reusable components can lead to the failure of the project.
o The team leader must work closely with the developers and customers to
close the project in time.
o The systems which cannot be modularized suitably cannot use this model.
o Customer involvement is required throughout the life cycle.
Applications:
1. This model should be used for a system with known requirements and requiring a
short development time.
2. It is also suitable for projects where requirements can be modularized and
reusable components are also available for development.
3. The model can also be used when already existing system components can be used
in developing a new system with minimum changes.
4. This model can only be used if the teams consist of domain experts. This is because
relevant knowledge and the ability to use powerful techniques are a necessity.
5. The model should be chosen when the budget permits the use of automated tools
and techniques required.

Prepared By: Prof. Arvind Meniya, Asst. Prof., SSEC, Bhavnagar Page 13