2. explain how to implement big bang model.

- Core Principles:

 Minimal Planning: There's little to no upfront planning regarding

requirements, design, or testing.
 Agile Development: Development happens iteratively based on what
emerges during the process.
 Focus on Coding: Coding commences right away with minimal
specifications.

-Implementation Steps(not recommended for real projects):

1. Gather Basic Requirements: Identify the general purpose of the system

without delving into specifics.
2. Start Coding: Developers begin working on the core functionalities based on
initial understanding.
3. Continuous Refinement: As development progresses, requirements and
functionalities are further defined and incorporated "on the fly."
4. Testing: Testing occurs sporadically throughout the process to identify and fix
bugs.

3. explain freeware, shareware, licensed tool in SAD

[3m]
Freeware:

 Cost: No upfront cost involved.

 Usage: Can be used indefinitely for free, often with full functionality.
 Distribution: Freely distributed by the developer.
  Source Code: Typically closed-source, meaning users cannot access or
modify the underlying code.
Freeware tools in SAD could include diagramming tools like Draw.io,
communication tools like Slack, or development environments like Eclipse.

Shareware:

 Cost: Free for a limited trial period, then requires purchase for continued use.
 Usage: Users can experience a restricted set of features during the trial.
 Distribution: Freely distributed by the developer.
 Source Code: Usually closed-source.

Shareware tools in SAD might include trial versions of software used for system modeling or
project management, where users can evaluate the tool before deciding to purchase it.

Licensed Tools:

 Cost: Requires a paid license for usage, with varying pricing models
(subscriptions, perpetual licenses).
 Usage: Full functionality is unlocked with a valid license.
 Distribution: Controlled by the developer or vendor.
 Source Code: Almost always closed-source.
licensed tools could include enterprise-level modeling tools like Microsoft Visio,
project management software like Microsoft Project, or database management
systems like Oracle or SQL Server.

5. explain V model.

The V-model is a type of SDLC model where the process executes

sequentially in a V-shape. It is also known as the Verification and Validation
model. It is based on the association of a testing phase for each corresponding
development stage. The development of each step is directly associated with
the testing phase. The next phase starts only after completion of the previous
phase i.e., for each development activity, there is a testing activity
corresponding to it.

 Gather & Analyze Requirements: Define what the software needs to do.
 Design: Plan the system's architecture and components.
 Implementation: Build the software based on the design.
 Testing: Verify the software meets requirements and functions correctly.
 Deployment: Release the software for use.
 Maintenance: Address issues and keep the software functioning.
4. Explain prototyping mode.

Prototyping Model is a software development model in which

prototype is built, tested, and reworked until an acceptable prototype is
achieved. It also creates base to produce the final system or software. It
works best in scenarios where the project’s requirements are not known
in detail. It is an iterative, trial and error method which takes place
between developer and client..
1. Requirement Gathering and Analysis: Initial phase involves
gathering user expectations and system requirements.
2. Quick Design: Second step focuses on basic design for a quick
overview of system requirements.
3. Build a Prototype: Creation of an actual prototype based on design
knowledge.
4. Initial User Evaluation: Preliminary testing to gather user feedback
on prototype performance.
5. Refining Prototype: Incorporating user feedback to improve
prototype design and functionality.
6. Implement Product and Maintain: Final phase involves testing,
distribution, and ongoing maintenance of the approved system to
prevent failures.

Types of prototyping model:

 Rapid Throwaway: Quick, basic prototypes for initial validation (discarded

later).
 Evolutionary: Continuously refined prototypes based on user feedback
(evolves into final system).
 Incremental: Prototyping individual modules for complex systems (integrated
later).
 Extreme: Rapidly built, low-fidelity prototypes for early UI exploration and
feedback.

6. Advantages and disadvantages of waterfall model.[3m]

7. Advantages of Waterfall Model:
 Clear Structure: Well-defined phases with specific deliverables ensure a
systematic approach to development.
  Easy to Manage: Defined milestones and deliverables simplify project
tracking and resource allocation.
 Focus on Requirements: Early emphasis on requirement gathering helps
maintain a clear vision throughout development.
 Suited for Simple Projects: Works well for projects with stable requirements
and limited complexity.
Disadvantages of Waterfall Model:
 Inflexible: Difficult to accommodate changes in requirements during later
stages, leading to rework and delays.
 Limited User Involvement: Focuses less on continuous user feedback,
potentially resulting in a system that doesn't fully meet user needs.
 Testing Delays: Integration and system testing occur at the end, leading to
potential rework if major issues arise.
 High-Risk: Unforeseen changes or defects discovered late can be expensive
and time-consuming to fix.

8. Difference between freeware and shareware [3m]

Freeware software is Shareware software is provided to its

provided to its users free users free for a limited period of time
of cost. after which software needs to be paid.

The source code of the The source code of the software is not
software is not available available to its users.
to its user.

All the features of this Some features of shareware software are

software are available to not available to the users.
its users.

The distribution of these The distribution of these softwares might

softwares can be done be restricted.
free of cost.

These software's are This software are be freely available for a

available freely without short period of time after which it is paid.
any limit.
Some examples are Adobe Some examples are WinZip, Adobe Photoshop.
PDF, Google Chrome, Skype.

9. Win runner and load runner sad

10. WinRunner Overview: WinRunner was a software testing tool developed by

Mercury Interactive, later acquired by Hewlett Packard Enterprise (HPE).
11. Role in SAD: WinRunner was used during the testing phase of the System
Analysis and Design (SAD) process.
12. Automation Capabilities: It allowed testers to automate testing processes by
recording and replaying user interactions with software applications.
13. Improving Efficiency: By automating repetitive testing tasks, WinRunner
increased efficiency and accuracy in identifying software defects and issues.
14. Ensuring Quality: WinRunner helped ensure that software met specified
requirements and functioned correctly, contributing to overall software
quality.
15. Discontinuation: It's important to note that WinRunner is no longer actively
developed or supported, as HPE has discontinued it in favor of other testing
tools.

Load runner

1. **Purpose**: LoadRunner assesses software performance and scalability.

2. **Simulated User Behavior**: It mimics real user actions for testing.

3. **Load Generation**: LoadRunner creates virtual users for load scenarios.

4. **Protocol Support**: It covers various protocols like HTTP, HTTPS, SAP GUI.

5. **Components**: LoadRunner includes VuGen, Controller, Analysis.

6. **Scripting**: Test scripts are made in VuGen using different languages.

7. **Scenarios**: Different tests like load, stress, endurance are conducted.

8. **Monitoring and Analysis**: It monitors metrics and analyzes results.

9. **Integration**: LoadRunner integrates with CI/CD pipelines and other tools.

10. **Benefits**: Enhances reliability, meets performance requirements.

 9. iterative model [3m]

In this Model, you can start with some of the software specifications and develop the
first version of the software. After the first version if there is a need to change the
software, then a new version of the software is created with a new iteration. Every
release of the Iterative Model finishes in an exact and fixed period that is called
iteration.

The Iterative Model allows the accessing earlier phases, in which the variations made
respectively. The final output of the project renewed at the end of the Software
Development Life Cycle (SDLC) process.

10. waterfall model [5m]

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.

Phases:
1. **Requirements**: Gather and analyze stakeholder requirements to understand project scope.

2. **Design**: Create detailed design document outlining software architecture and components.

3. **Development**: Implement software based on design specifications, including unit testing.

4. **Testing**: Test software to ensure it meets requirements and is defect-free.

5. **Deployment**: Deploy tested and approved software to production environment.

7. **Maintenance**: Fix post-deployment issues and ensure software continues to meet

requirements over time.

11. spiral model

The Spiral Model is a Software Development Life Cycle (SDLC) model that
provides a systematic and iterative approach to software development. In its
diagrammatic representation, looks like a spiral with many loops. The exact number
of loops of the spiral is unknown and can vary from project to project. Each loop of
the spiral is called a Phase of the software development process.
1. Planning
The first phase of the Spiral Model is the planning phase, where the scope of the
project is determined and a plan is created for the next iteration of the spiral.
2. Risk Analysis
In the risk analysis phase, the risks associated with the project are identified and
evaluated.
3. Engineering
In the engineering phase, the software is developed based on the requirements
gathered in the previous iteration.
4. Evaluation
In the evaluation phase, the software is evaluated to determine if it meets the
customer’s requirements and if it is of high quality.
5. Planning
The next iteration of the spiral begins with a new planning phase, based on the
results of the evaluation.
12. big bang model:

The Big bang model is an SDLC model that starts from nothing. It is the simplest
model in SDLC (Software Development Life Cycle) as it requires almost no
planning. However, it requires lots of funds and coding and takes more time. The
name big bang model was set after the “Great Big Bang” which led to the
development of galaxies, stars, planets, etc. Similarly, this SDLC model combines
time, efforts, and resources to build a product. The product is gradually built as the
requirements from the customer come, however, the end product might not meet the
actual requirements.
Pros of Big Bang Model :
 There is no planning required for this.
 Suitable for small projects
 Very few resources are required.
 As there is no proper planning hence it does not require managerial staffs
 Easy to implement
 It develops the skills of the newcomers
 Very much flexible for the developers working on it
Cons of Big Bang Model :
 Not suitable for large projects.
 Highly risky model and uncertain
 Might be expensive if requirements are not clear
 Poor model for ongoing projects