Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 1

Q2.

Generally, software requirements specifications (SRSs) describe what the software will do and how it
will perform. Furthermore, it defines what functionality the product must have to satisfy the
requirements of all stakeholders (business and users).

Q3. SDLC (Software Development Life Cycle) is a framework defining the activities carried out during a
software development cycle. The SDLC model consists of six phases. 1. Requirement: In this phase, all
the requirements are collected from the customer/client. They are provided in a document called
Business requirements specification (BRS) and System requirement specification (SRS). All the details are
discussed with the customer/client in detail. 2. Design: It has two steps: ❖ High-level design (HLD): It
describes the architecture of software products. ❖ Low-level design (LLD): It describes how each and
every feature in the product should work and every component. 3. Implementation: ❖ This is the
longest phase. ❖ This phase consists of the Front end + Middleware + Back-end. ❖ In front-end:
Development of coding is done even SEO settings are done. ❖ In Middleware: They connect both the
front end and back end. ❖ In the back-end, a database is created. 4. Testing: Testing is carried out to
verify the entire system. The aim of the tester is to find out the gaps and defects within the system and
also to check whether the system is running according to the requirement of the customer/client. 5.
Deployment: After successful testing, the product is delivered/deployed to the client, and even clients
are trained on how to use the product. 6. Maintenance: Once the product has been delivered to the
client a task of maintenance starts as when the client will come up with an error the issue should be
fixed from time to time.

Q4. ● The term project refers to a temporary undertaking by a company or organization (such as the
creation of a new product, service, or result). ● The concept of a program refers to a collection of
projects that have similar or related goals, and which are managed and coordinated as a group instead
of independently ● Portfolios are collections of related and unrelated programs and/or projects within
the same organization Q5 Difficult stakeholders are those stakeholders who could disrupt or even bring
an end to a project unless you manage them carefully. They might not be open and forthcoming in their
communications, or they may only offer negative feedback. Some stakeholders may be frustrated at the
progress of the project or may not seem to be very engaged in the work. Here are some strategies to
manage these stakeholders: 1. Identify your stakeholders 2. Categorize and prioritize them 3. Stay calm
4. Listen carefully 5. Understand their motivation 6. Be objective 7. Respond quickly to issues 8. Be firm,
if necessar

You might also like