Topics:

Topic 1: software quality attributes Topic 2: software development life cycle Topic 3:classical waterfall model
Presented by: Neha Rani B.Tech (CS) 6th Sem IIET
1

Software quality attributes

Definitions of software quality

It is the degree of excellence The quality of the software is based upon the customers needs. The right quality is not necessary best quality. It determine by the Cost of the product and the technical characteristics as suited to the Specific requirements

Software Quality Attributes

Quality attributes are the key factors in the success of any software system.
Also Quality attributes are important for the user of the software system to evaluate how good a system is. Software quality is measured by analyzing the various attributes that are significant to a certain domain or application .

Software Quality Attributes

Robustness Efficiency Reliability Testability Understandability

Usability

Software development lifecycle

Diagram for software development life cycle:

 software development life cycle is a series of identificable stages that a software development undergoes during its lifetime.

Phases of software development life cycle

There are 5 phases of software development life cycle and the Phases are also known as stages of software development life Cycle.
feasibility design coding

testing

maintenance

Feasibility study:
The main aim of feasibility study phase is to determine whether it Would be financially and technically feasible or not. The feasibility study also include analysis of problem and Collecting related information for the software.. In this phase we also prepare SRS(Software Requirement Specification ) to understand the need of the customer.

10

Design:
The goal of the design phase is to transfer the requirement Specified in the SRS document into a structure which is suitable For implementing in programming language. In technical word we can say: During the design phase the software architecture is derived From the SRS document.

11

Coding:
Coding phase sometimes known as the implementation phase.

In this phase we implemented the software architecture in workable Solution using some programming language and other.
In other words we can say : In coding phase the programmer developed a program to implement The software..

12

Testing:
Testing involves the software is ready according to the SRS Document or not..
Testing phase involves the conditions correct or not and Debugging of program. Testing phase include correct working of the individual modules.

13

Maintenance:
In this phase we focus on that whether the software is ready According to the need of the customer or not. Maintenance involves correcting errors that are not discovered During the software development phase.

Maintenance involves improving the implementation of the System and enhancing the functionalities of the system According to the customers requirement .

14

Software life cycle models:

15

 A software life cycle model is a descriptive and diagrammatic Representation of the software development life cycle. A life cycle model prescribes the different activities that Need to be carried out to develop a software and sequencing Of these activities.

16

Classical water fall model for software development:

The classical water fall model is the very simple way To develop a software. All other model is described from this model. It is the theoretical model of software development not practical. We study this model because all other life cycle models are Derived from this model.
17

Classical water fall model for software development contd..

18

Phases of classical water fall model:

maintenance

testing

effor ts

feasib ility

design coding

phases
19

Advantages:
It is very simple model for software development.
All other models are derived form this model..

20

disadvantages:
The classical water fall model is very simple model to development A software but not used for s/w development.
The classical water fall model is an idealistic model because it Assumes that no error is ever committed by engineers during any of The life cycle phase. Based on error correction not on error prevention. This model assume that all the requirements are defined correctly At the beginning of the project.

21

Thank you

22