Page 1

PLAGIARISM SCAN REPORT

Words 693 Date December 21,2020

Characters 4739 Exclude URL

25% 75% 9 27
Plagiarized
Plagiarism Unique Unique Sentences
Sentences

Content Checked For Plagiarism

Question1
a. Software requirements specification displays what the software is supposed to do as well as how it is supposed to
achieve. It is written down before the definite software development work starts.
The possible reader for the SRS in the company can be:-
Developers
Testers
Engineers
Reasons for them to read SRS:-
This gives the goal of the SRS document, not the software itself. It also states how much of the software is covered by
the document,
mainly saying whether it describes the whole software system or only a part of it. It similarly states the intended readers
of the document.
The software requirements specification (SRS) is a communication device between users and software designers. The
specific goals of the SRS are as follows:
Easing reviews
Telling the scope of work
Providing a reference to software designers (i.e. navigation aids, document structure)
Providing a system for testing primary and secondary use cases
Including features to client requirements
Providing a platform for continuing alteration
b. A well-designed, well-written SRS accomplishes four major goals:
It delivers feedback to the client. An SRS is the client’s assurance that the development organization comprehends the
matters to be solved and the software performance necessary to address those issues. Therefore, the SRS must be
written in natural language (versus a formal language, explained later in this article), in an explicit manner that may also
include charts, tables, data flow diagrams, decision tables, and so on.
It decomposes the problematic into component parts. The simple act of writing down software requirements in a well-
designed format classifies information, places borders around the problem, hardens ideas, and helps split the problem
into its component parts in an methodical manner.
It serves as an input to the design specification. As mentioned before, the SRS serves as the parent document to
subsequent documents, for instance the software design specification and statement of work.
Consequently, the SRS must comprise adequate detail in the functional system requirements so that a design solution
can be devised. It helps as a product validation check. The SRS also
It serves as the parent document for testing and validation strategies that will be applied to the requirements for
verification.
Software requirements specifications are usually developed during the first stages of “Requirements Development,”
which is the original product development pha
se in which information is collected about what requirements are needed–and not. This information-gathering stage can
contain onsite visits, questionnaires, surveys, interviews,
and possibly a return-on-investment (ROI) analysis or needs analysis of the customer or client’s current business
 Page
environment. The actual specification, then, is written
when the requirements have been gathered and examined.
c. The principles of agile methods have contributed to the accelerated development and deployment of software in the
following ways:
1. Incremental delivery: In this procedure, the software is provided in small increases to the client. Depends on the
customer response and requirements, the developers made the increments in the system. In every raise, the new
functionalities are established and deployed into the system.
2. Customer participation: The customers are involved in the development process of the system. The agile methods
involve consistent discussions with the client. As the development of the system is done in small increments, the
customer must involve in the development process to provide the requirements of the new features in the system.
3. People, not process: One of the significant principle to develop effective software is to distinguish the technical skill
of the people working in the development process of the system. It is essential to implement and provide the product
rapidly with high quality.
4. Embrace change: As technology is developing, the changes must be done to the current system. The system must
be designed as per the requirements of the changes to deploy the new features in the system.
5. Keep simplicity: As the changes in the system done regularly in small increases, the program used in the system
must be simple. If changes are obligatory for the system, the existing code must be restructured as per the
requirements of the changes. The uncomplicatedness of the code and the development process must be preserved
without any complication in the system.

Sources Similarity

The Importance Of Software Requirements Specification | Nascenia

it also states how much of the software is covered by the document, particularly saying whether it describes the entire
software system or only a part of it.this segment describes the software in brief. its purpose, objectives etc. it further 20%
states how the software ties into corporate aims and...

https://nascenia.com/the-importance-of-software-requirements-specification/

Software requirements specification - Wikipedia

the specific goals of the srs are as follows: facilitating reviews. describing the scope of work. providing a reference to
software designers (i.e. navigation aids, document structure). providing a framework for testing primary and secondary 10%
use cases.

https://en.wikipedia.org/wiki/Software_requirements_specification

13 a well designed well written srs accomplishes four

a well-designed, well-written srs accomplishes four major goals: it provides feedback to the customer .the ieee 830
standard defines the benefits of a good srs: establish the basis for agreement between the customers and the
suppliers on what the software product is to do.
7%
https://www.coursehero.com/file/p5idhl6/13-A-WELL-DESIGNED-WELL-WRITTEN-SRS-ACCOMPLISHES-
FOUR-MAJOR-GOALS-It-provides/

Writing Software Requirements Specifications (SRS) | TechWhirl

Technical writing guidance for technical writers and technical communicators on ... The simple act of writing down
software requirements in a well-designed format organizes information, places borders around the problem, solidifies 10%
ideas, and helps break down the problem into its component parts in an orderly fashion.

https://techwhirl.com/writing-software-requirements-specifications/

NGO Project Management SYstem-2

· it serves as an input to the design specification. as mentioned previously, the srs serves as the parent document to
subsequent documents, such as the software design specification and statement of work.
7%
http://ngomanagementsystem.blogspot.com/2012/12/ngo-project-management-system-2.html

Software Requirements Specification Amazing Lunch Indicator ...

... and possibly a return-on-investment( ROI) analysis or needs analysis of the customer or client's current business
environment. The actual specification, then, ... 4%
http://webxteam.info/Tutorials/1673763-software-requirements-specification-amazing-lunch-indicator-writing-
software-requirements-specifications

4%
Software Engineering module3-activity.docx - Course Hero
Software Engineering Module 2-Quiz Aubrey Joy U Gaffud BSIT-4A 1. Explain how the principles underlying agile Page
methods lead to the accelerated development ...

https://www.coursehero.com/file/68796171/Software-Engineering-module3-activitydocx/

Explain how the principles underlying agile methods lead to ...

The system must be designed as per the requirements of the changes to deploy the new features in the system. 5.
Maintain simplicity: As the changes in the system done frequently in small increments, the code used in the system 3%
must be simple.

https://cpentalk.com/430/principles-underlying-accelerated-development-deployment