It is known as software engineering paradigms, where all the engineering concepts pertaining to the development of software are applied.

Includes identifying, estimating, and monitoring the technical feasibility and management risks

Helps developer to select a strategy to develop the software.

The team receives feedback about the product and works through the feedback.

The identified features are developed and verified through testing. The actual software is produced based on the feedback from the customer

It is easier to build a wall than to a house or building, likewise, as the size of software become large engineering must step to give it a scientific process

· This paradigm is a part of Software Development and includes –

Define the requirements.

· Implement the design into “Blank” through coding.

Developing products using well defined scientific principles and methods.

The team issues a product for the user's work environment.

Gathering all requirements for the software product's utility and features.

Emphasizes technical aspects over management in software development

A widely-used Agile process framework in software development.

This tells us how well software works in operations. It can be measured on:

Better process of software development provides better and quality software product.

As hardware industry has shown its skills and huge manufacturing has lower down, the price of computer and electronic hardware.

simplest model

This aspect is important when the software is moved from one platform to another:

If the software process were not based on scientific and engineering concepts, it would be easier to re-create new software than to scale an existing one.

You can use the user flow diagram or the high-level UML diagram to show the work of new features and show how it will apply to your existing system.

a German computer scientist.

· A subset of Software design paradigm.

An executable code

The tasks performed by the human components of the information system.

An engineering branch associated with development of software product using well-defined scientific principles, methods, and procedures. The outcome of software engineering is an efficient and reliable software product.

Meaningful data that the system stores and processes.

Writing and assembling the actual code based on design specifications.

a pioneer in the field, introduced a diagram outlining five sequential phases, which later became known as the waterfall model.

Evaluation of possible solutions and documentation of selected specifications

The Quality Assurance team examines the product's performance and looks for the bug.

The always growing and adapting nature of software hugely depends upon the environment in which user works.

A collection of executable programming code

Made for a specific requirement

Designers and developers start working on their project, which aims to deploy a working product.

The Customers evaluate the developed version of the software so far.

cyclic manner, · Consumes more resources, as defining iterations may require redefinition of the complete system.

o Gathering the business requirements in the baseline spiral. o Continuous communication between the customer and the system analyst.

Keeping the software available and running smoothly in the live environment.

· Combination of iterative development process model and sequential linear development model with a very high emphasis on risk analysis.

Refer to the methods and steps which are taken while designing the software.

Transferring the tested software to the live staging environment for user access.

Ensuring every component of the software functions as intended.

· Do not follow any specific process. · May or may not be as per customer requirement. · Requires very little planning. Even the customer is not sure about what exactly he/she wants · Beginning with nothing, a rapid growth and expansion of code will quickly emerge, thus producing a finished product in a mere instant · Produce a very high risk and uncertainty · Used as a learning aid for new comers or students, but not on complex or object-oriented projects.

A framework for 'just in time' work processes, originating from Toyota's factory floor

· Extension of the waterfall model · Every single phase in the development cycle, there is a directly associated testing phase. · Sequential type. · Not flexible to changes. · Not good for complex and object-oriented projects.

This aspect briefs about how well a software has the capabilities to maintain itself in the ever-changing environment: