SoftWare NOTES

1) Compare Waterfall and spiral model

Ans:-
Q.2) You are appointed as scrum master , Explain your role for completing scrum
process. OR What is scrum process ? Explain life cycle of scrum proceess ?
Ans:- First of all what is scrum master - A Scrum Master is a key role in the Scrum
framework, The Scrum Master's primary responsibility is to facilitate and guide the Scrum
process. The Scrum Master acts as a coach.
What is scrum process - The Scrum process is an agile framework for managing and delivering
complex projects and products. It emphasizes collaboration, flexibility, and iterative
development. Scrum provides a structured yet adaptable approach to project management that
allows teams to work efficiently while responding to changing requirements and priorities. The
Scrum process is based on a set of roles and events that work together to facilitate the project's
success.

LifeCycle of Scrum process

LifeCycle of Scrum process -
 Sprint - A Sprint is a time-box of one month or less. A new Sprint starts immediately
after the completion of the previous Sprint.
 Release - When the product is completed, it goes to the Release stage.
 Sprint Review - If the product still has some non-achievable features, they will be
checked in this stage. The product is then passed to the Sprint Retrospective stage.
 Sprint Retrospective - In this stage, the quality or status of the product is checked.
 Product Backlog - The product is organized according to the prioritized features.
 Sprint Backlog - Sprint Backlog consists of two parts:

Product Assigned Features to Sprint: Features assigned from the Product

Backlog for the current Sprint.

Sprint Planning Meeting: Part of the Sprint Backlog, involves planning for
 the upcoming Sprint.

Q.3 Difference between functional and non-functional requirement ?

Ans:-
Q.4 With a suitable illustration explain evolutionary spiral model for software
Development ..?
Ans:-

1) The Spiral Model is a software development methodology that combines elements of both
iterative development and incremental development approaches. Introduced as an alternative to
the traditional Waterfall model.
2) The Spiral Model is particularly suited for projects that involve a high degree of risk and
uncertainty, The Spiral Model is a risk-driven model.
3) Each loop of the spiral is called a Phase of the software development process.
4) Each cycle in the spiral is divided into four parts:
 Objective Identification: Each cycle in the spiral starts with the identification of purpose
for that cycle, the various alternatives that are possible for achieving the targets, and the
constraints that exists.
 Risk Assessment and reduction: The next phase in the cycle is to calculate these various
alternatives based on the goals and constraints. The focus of evaluation in this stage is
located on the risk perception for the project.
 Development and validation: The next phase is to develop strategies that resolve
uncertainties and risks. This process may include activities such as benchmarking,
simulation, and prototyping.
 Planning: Finally, the next step is planned. The project is reviewed, and a choice made
whether to continue with a further period of the spiral. If it is determined to keep, plans are
drawn up for the next step of the project.
5) When deliverance is required to be frequent and When the project is large we should use spiral
model.
6) Risk handling ;- Risk handling in the Spiral Model involves identifying, assessing, and
mitigating risks at each spiral, ensuring that potential issues are addressed before they escalate.
Here's how risk handling is integrated into each phase of the Spiral Model.

Q.5 With is software requirement specification SRS , elaborate the content and
charcteristics of SRS ..?
Ans:- 1) SRS is a formal report, which acts as a representation of software that enables the
customers to review whether it (SRS) is according to their requirements.
2) It serves as a formal contract between the client or stakeholders and the development team,
providing a clear and detailed description of what the software is expected to do.
3) content ;-
 Category- what kind of application is your software will come here
 Purpose – describe the purpose of making the document
 Scope – defines the limit of the software
 Introduction – define existing & proposed system
 Advantage – define advantage of system
 Funtional and non-functional requirement
 Software tool – mention the tools to be used
 Deployment – Environment required to deploy
 Hardware specification – Hardware required to develop the system
 Gantt chart – chart to shiw the schedule of project
4) Characteristic ;-
 Clear and Unambiguous: The requirements should be expressed in clear and easily
understandable language.
 Complete: The SRS should cover all aspects of the software's functionality.
 Consistent: The requirements should be internally consistent.
 Verifiable: Each requirement should be testable, allowing for objective verification that
the software meets the specified criteria.
 Traceable: Each requirement should be traceable to its origin, whether it's a stakeholder's
need, a business goal, or another source.
 Feasible and Realistic: The requirements should be achievable within the project's
constraints, including time, budget, and available technology.
 Modifiable: The document should be designed for easy updates and changes as the
project progresses and new information becomes available.
Q.7 Constuct a DFD(Data Flow Diagram) for food ordering system upto level 1
Ans;-
Q.8 State and explain the methods for eliciting requirements..?
Ans:- 1) Eliciting requirements is the process of gathering information from stakeholders and
users to understand their needs, preferences, and constraints, which forms the foundation for
designing and developing a software system.
2) There are various methods for eliciting requirements, each suited to different situations and
stakeholders. Here are some common methods
 Interview: To understand the customer’s expectations from the software. Interviews,
Which maybe be open-ended or structured. In open-ended interviews there is no pre-set
agenda. Context free questions may be asked to understand the problem. In structured
interview, agenda of fairly open questions is prepared.
 Brainstorming Sessions: It is a group technique , It is intended to generate lots of new
ideas hence providing a platform to share views, A highly trained facilitator is required to
handle group bias and group conflicts.
 Surveys and Questionnaires: Distributing structured questionnaires to a large number of
stakeholders to collect their opinions and preferences. Useful for gathering a wide range of
perspectives quickly and efficiently.
 Observations: Observing users in their natural environment to understand their
workflows, pain points, and behaviors. Provides insights into actual user needs and context,
helping to identify hidden requirements.
 Prototyping: Creating a simplified version of the software or user interface to
demonstrate concepts and gather feedback. Helps stakeholders visualize the end product,
which can lead to better requirement definition.
 Document Analysis: Reviewing existing documents, such as user manuals, reports, and
business processes, to extract requirements. Useful for identifying explicit and implicit
requirements embedded in organizational artifacts.

Q.11 What is agile methodology ?

Ans:- 1) Agile methodology is a set of principles and practices for software development that
emphasizes flexibility, collaboration, incremental progress, and customer feedback.
2) It is a response to the limitations of traditional, linear approaches to software development,
such as the Waterfall model. Agile methodologies prioritize delivering functional software
quickly and continuously, while also accommodating changes and adjustments based on
evolving requirements.
3) To make a process Agile, the following principles need to be satisfied.
1. highest priority is to satisfy the client through early and continuous delivery of valuable
computer software.
2. Welcome dynamical necessities, even late in development. Agile processes harness
modification for the customer’s competitive advantage.
3. Deliver operating computer software often, from a pair of weeks to a couple of months,
with a preference to the shorter timescale.
4. Business individuals and developers should work along daily throughout the project.
5. The build comes around actuated people. offer them the setting and support they have,
and trust them to urge the task done.
6. the foremost economical and effective methodology of conveyancing info to and among a
development team is face-to-face speech.
7. working computer software is the primary live of progress.
8. Agile processes promote property development. The sponsors, developers, and users got
to be able to maintain a relentless pace indefinitely.
9. Continuous attention to technical excellence and smart style enhances nimbleness.
10. the most effective architectures, necessities, and styles emerge from self– organizing
groups.