Abu bakar - jhjjjjjjjjjj PDF

Preview

Summary

jhjjjjjjjjjj...

Description

SOFTWARE ENGEERNING

Abu Bakar Asad

Question#1 Is there any difference between "system requirements specification" and” software requirement specification" if any describe in detail?

Figure 1



Systems usually comprise of 4 key elements: People, Process, Technology, and Partners.



Technology, in turn, contains aspects such as Hardware, Software, and Network. However, in many instances, the hardware and network may not be affected by the project and only software is affected. For example, we may add a new feature to an existing software solution. It may so happen that we do not affect people, process or partners. In this case, technology requirements equal software requirements and system requirements equal software requirements. However, for larger changes, typically software requirements will be the subset of solution requirements.

   

Software Requirements Specification: A software requirements specification (SRS) is a document that describes what the software will do and how it will be expected to perform. It also describes the functionality the product needs to fulfill all stakeholders (business, users) needs. Software Requirement specification describe the depth description of the software that will be developed. SRS is used by various individuals in the organization. System customers need SRS to specify and verify whether requirements meet the desired needs. In addition, SRS enables the managers to plan for the system development processes. System engineers need a requirements document to understand what system is to be developed. These engineers also require this document to develop validation tests for 1

the required system. Lastly, requirements document is needed by system maintenance engineers to use the requirement and the relationship between its parts.

Figure 2

The requirements document has diverse users. Therefore, along with communicating the requirements to the users it also has to define the requirements in precise detail for developers and testers. In addition, it should also include information about possible changes in the system, which can help system designers avoid restricted decisions on design. SRS also helps maintenance engineers to adapt the system to new requirements.

System Requirements Specification: System requirements specification collect the information on the requirement for a system. “Software” and “system” are sometimes used interchangeably as SRS. But a software requirement specification provides greater detail than a system requirements specification.

Figure 3

2

A System Requirements Specification is a structured collection of information that embodies the requirements of a system. A business analyst, sometimes titled system analyst, is responsible for analyzing the business needs of their clients and stakeholders to help identify business problems and propose solutions.

2- Enlist the basic purpose of SRS document, what to keep in mind while writing the document? The purpose of this Systems Requirements Specifications document (henceforth referred to as SRS) is to provide the guidelines necessary to design and implement software that fulfills all the requirements given. This SRS will be entirely designindependent, focusing only the end requirements that the final software must achieve. Furthermore, this document can be used by clients and stakeholders as a representation of their requirements for the software. Fulfilling all the requirements of the SRS will be in essence fulfilling the contract with the client. A requirements specification is necessary if you plan to create your own startup or build a software product. A good SRS is a reference point for everyone involved in the project. It's vital for software developers, designers, testers, operations and maintenance staff, and even investors. 

You can get an accurate estimate of the cost, risk and time costs.



The client will be able to form their vision of the project more clearly.



The customer and the contractor will have the same idea about the product.



It will help identify the optimal set of functions.



It serves as the basis for the formation of other technical documentation.



The development process will be optimized and time minimized.



There will be no duplication of tasks.



Allows you to structure problems to solve them easier and faster.

Save time Consider how many times you will have to explain your expectations to different web developers. It is much quicker to outline all your needs in one document. Moreover, an SRS document simplifies estimation and scheduling. It provides the basis for planning validation and verification, as well as enhancement of the system. An easyto-follow SRS speeds up the development process at all stages. 3

Save money Redesign or re-testing take effort. Unclear tech documentation means wasting time and having extra spending. Thanks to software requirement specification, the stakeholders will discuss and establish all nuances at the start of the project. An SRS will also make the system easier to update in the future.

Better cooperation with the development team The provider of web software development services needs to comprehend your demands. This way, you will get the product you expect and prevent misunderstandings. SRS improves communication in the team. It provides easy access to all product feature descriptions. Moreover, the new employees will learn the details of the project faster.

Mind Mapping to Develop an SRS Document? You can start with a brainstorming session that helps determine the product's major features and turn them into an actionable mind map. Here is a quick overview of the process: 1. Identify the users of your app and their problems using interviews. 2. Create a big-picture mind map to answer three questions. Who will enjoy your solution? Why do they need it? When will they use your product? 3. Develop user stories mind map. It will help you follow different scenarios and understand which features will meet the audience's needs. 4. Based on the user stories mind map, estimate the functional features, plan and prioritize their development. 5. Transfer the mind map data into an SRS document. The structured document can help you come up with new ideas. 6. Update and broaden the mind map as you develop a better understanding of user needs and requirements.

Figure 4: Mind Mapping

4

There is no need to waste days on drawing a complex mind map with detailed explanations for all features. Instead, focus on critical concepts and explain them in an SRS document that you will transfer to the chosen software development services provider. Your system requirement specification should be as detailed as possible. Include any constraints you deem necessary for the project, like budget and timeframe. If the app developer team can't complete the work on time or within the allotted sum, you might need to let go of non-essential features.

References: https://freshcodeit.com/freshcode-post/creating-srs-step-by-step-by-analyzingrequirements https://www.perforce.com/blog/alm/how-write-software-requirements-specification-srsdocument https://www.jamasoftware.com/blog/characteristics-of-excellent-requirements/ https://www.softwaretestingclass.com/software-requirement-specification-srs/

5...