The Waterfall Model was the first Process Model to be introduced.

It is also
referred to as a linear-sequential life cycle model. It is very simple to
understand and use. In a waterfall model, each phase must be completed
before the next phase can begin and there is no overlapping in the phases.
The Waterfall model is the earliest SDLC approach that was used for software
development.
The waterfall Model illustrates the software development process in a linear
sequential flow. This means that any phase in the development process
begins only if the previous phase is complete. In this waterfall model, the
phases do not overlap.

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 sequential phases in Waterfall model are :
Requirement Gathering and analysis
System Design
Implementation
Integration and Testing
Deployment of system
Maintenance

Principles of User Interface Design

User Interface Design is the design of the interface or system which is
directly accessible by the user and they interact with in order to do a task. It
establishes the way with which the user will interact with the product.
Now let us discuss about the principles of user-interface design which are as
follows −
Minimize actions − Minimize action means steps per screen. The tasks and
actions are streamlined so that they can be done in as few steps as possible.
The interface should be designed keeping in mind to maintain the steps as
few as possible for performing any tasks.
Simplicity − The user interface should not be complex. It should always be
designed simple and elegant.
Consistent − The user interface should be consistent. The design should be
consistent. Increasing consistency increases the familiarity, and hence
increases the usability.
 Proving useful feedback − The user should be provided with feedback for
every action. This keeps the user informed and helps them to know whether
some action was successful or not.
Clarity − Content should provide the user with clarity. There should not be
anything which confuses the user, as it becomes an obstacle for the user in
interacting with the product.

What is Software Quality Management?

Software Quality Management ensures that the required level of quality is
achieved by submitting improvements to the product development process.
SQA aims to develop a culture within the team and it is seen as everyone's
responsibility.
Software Quality management should be independent of project management
to ensure independence of cost and schedule adherences. It directly affects
the process quality and indirectly affects the product quality.

Activities of Software Quality Management:

AD
Quality Assurance - QA aims at developing Organizational procedures
and standards for quality at Organizational level.
Quality Planning - Select applicable procedures and standards for a
particular project and modify as required to develop a quality plan.
Quality Control - Ensure that best practices and standards are
followed by the software development team to produce quality products

Quality Control Process:

The three class parameters that control software quality are:

Products
Processes
Resources
The total quality control process consists of:
Plan - It is the stage where the Quality control processes are planned
Do - Use a defined parameter to develop the quality
Check - Stage to verify if the quality of the parameters are met
Act - Take corrective action if needed and repeat the work

Quality Control characteristics:

Process adopted to deliver a quality product to the clients at best cost.
Goal is to learn from other organizations so that quality would be better
each time.
To avoid making errors by proper planning and execution with correct
review process.

What is System Testing?

System Testing (ST) is a black box testing technique performed to evaluate
the complete system the system's compliance against specified requirements.
In System testing, the functionalities of the system are tested from an end-to-
end perspective.
System Testing is usually carried out by a team that is independent of the
development team in order to measure the quality of the system unbiased. It
includes both functional and Non-Functional testing.

Types of System Tests:

What Is Verification and How Does It Work?
Verification is the process of reviewing the intermediate work products of a
software development lifecycle to ensure that we are on track to complete the
final result.
In other words, verification is a process of evaluating software mediation
products to see whether they meet the requirements set out at the start of the
phase.
The issue now is, what xactly are intermediate or mediator products?e
These may comprise documentation like requirements specifications, design
documents, database table design, ER diagrams, test cases, traceability
matrix, and so on that are created throughout the development stages.
We often overlook the necessity of examining these papers, but we should
remember that reviewing may uncover numerous hidden flaws that, if
discovered or addressed later in the development cycle, can be quite
expensive

What Is Validation and How Does It Work?

Validation is the process of assessing the completed product to see whether
it fits the business requirements. To put it another way, the test execution that
we undertake on a daily basis is essentially a validation activity that
comprises smoke testing, functional testing, regression testing, systems
testing, and so on.
Validation encompasses all types of testing that include interacting with the
product and putting it to the test.
The validation procedures are listed below −

What is CMMI?
The CMMI (Capability Maturity Model Integration) is a procedure and,
software developmental model. It assists in organizing and
streamlining the software development process. It advances and
boosts the development process and reduces threats in software and
system.
Established by the Software Engineering Institute at Carnegie Mellon
University, It was developed as a process enhancement tool for
software development. It is now managed by the CMMI Institute.
CMMI analyses your existing processes and classifies their flaws and
strengths. In the next steps, measures are taken to convert the
weaknesses into strength.

CMMI is both a process model and a behavioral model. It can be

used to manage the logistics of refining performance by creating
determinate standards; it can also develop a structure for boosting
prolific and effective behavior throughout the system.
To conclude, the CMMI model is a pool of dependable best practices
that helps in improving quality, standards, and efficiency of
the software development processes. It includes various process
areas like project planning, configuration management, etc.

 Testing for integration

 System Evaluation
 Acceptance Testing of Users

What is software reuse?

Software reuse is a term used for developing the software by using
the existing software components. Some of the components that
can be reuse are as follows;
 Source code
 Design and interfaces
 User manuals
 Software Documentation
 Software requirement specifications and many more.
What are the advantages of software reuse?
 Less effort: Software reuse requires less effort because many components
use in the system are ready made components.
 Time-saving: Re-using the ready made components is time saving for the
software team.
 Reduce cost: Less effort, and time saving leads to the overall cost reduction.
 Increase software productivity: when you are provided with ready made
components, then you can focus on the new components that are not
available just like ready made components.
 Utilize fewer resources: Software reuse save many sources just like effort,
time, money etc.
 Leads to a better quality software: Software reuse save our time and we can
consume our more time on maintaining software quality and assurance.

SPI……
Software Process Improvement (SPI) methodology is defined as a sequence
of tasks, tools, and techniques to plan and implement improvement activities
to achieve specific goals such as increasing development speed, achieving
higher product quality or reducing costs.

This definition is combined from [1][2]. SPI can be considered as process re-
engineering or change management project to detect the software
development lifecycle inefficiencies and resolve them to have a better
process. This process should be mapped and aligned with organizational
goals and change drivers to have real value to the organization.

SPI mainly consists of 4 cyclic steps as shown in the figure below, while these
steps can be broken down into more steps according to the method and
techniques used. While in most cases the process will contain these steps.