SRS(software requirement specification)
55 likes43,024 views
The document defines an SRS as the official statement of what system developers should implement, providing a complete description of the system behavior. An SRS precisely defines the software product and is used to understand requirements to design the software. It includes the purpose, product scope, features, interfaces, and other functional and non-functional requirements. The SRS benefits include establishing agreement between customers and suppliers, reducing development effort, and providing a baseline for validation.
1 of 12
Ad
Recommended
Requirement specification (SRS)
Requirement specification (SRS)kunj desai This document provides an overview of a requirements specification (SRS) for a software engineering project. It defines what an SRS is, its purpose, types of requirements it should include, its typical structure, characteristics of a good SRS, and benefits of developing an SRS. The SRS is intended to clearly define the requirements for a software product to guide its design and development.
Software requirement specification
Software requirement specificationshiprashakya2 Software Requirement Specification is a most important topic asked in exams and for presentations in B.Tech comp. engg. This presentation contains all the important topic and deep knowledge of SRS.It includes definition, scope, role, how to write srs, template and template description. It tells how to build SRS and also includes examples for ease.
Software Requirement Specification
Software Requirement SpecificationVishal Singh The document discusses requirements analysis, which involves understanding customer needs and expectations for a proposed system. Requirements analysis is necessary to ensure projects align with business goals and specifications. The requirements analysis process includes identifying system boundaries, customers, eliciting requirements through stakeholder interviews, analyzing requirements, documenting requirements in a specification, and managing evolving requirements. An effective software requirements specification establishes agreement between customers and developers on system functionality.
Software requirement specification
Software requirement specificationAmit Gandhi This document provides a software requirements specification (SRS) for an office automation system. It describes the purpose of the system as automating processes in a college office such as managing student, employee, and transaction data. The SRS outlines functional requirements for modules including attendance, courses, fees, donations, exams, profiles, and reports. It also provides technical requirements for the system such as the needed software (VB.NET and SQL Server), hardware specifications, and user characteristics. Diagrams are included showing the login process and main navigation levels of the system.
software engineering
software engineeringAzad public school The document discusses the origins and drivers of software engineering as a discipline. It arose in response to frequent software project failures in the late 1960s, termed the "software crisis". Key points:
- Software engineering aims to apply systematic and quantifiable principles to software development and maintenance to improve quality, productivity and job satisfaction.
- It draws on computer science, management science, economics and other fields. Processes and models help manage complex software projects.
- Early process models included waterfall and prototyping. Later agile models like spiral emphasize iterative development and risk management over rigid phases.
Requirement engineering process
Requirement engineering processDr. Loganathan R The document discusses requirements engineering processes. It describes the main activities as feasibility studies to determine if a project is worthwhile, elicitation and analysis to discover requirements, specification to formalize requirements, and validation to check requirements. It discusses techniques for eliciting requirements including interviews, scenarios, use cases and viewpoints to represent different stakeholder perspectives. The goal is to create and maintain requirements documents through these iterative processes.
Software requirements
Software requirementsDr. Loganathan R The document discusses software requirements and requirements engineering. It introduces concepts like user requirements, system requirements, functional requirements, and non-functional requirements. It explains how requirements can be organized in a requirements document and the different types of stakeholders who read requirements. The document also discusses challenges in writing requirements precisely and provides examples of requirements specification for a library system called LIBSYS.
Smart contracts
Smart contractsremoved_5ef8f4100b1d7e8bfe3d2dc557fe10d0 This document provides an introduction to smart contracts. It defines a smart contract as a program whose execution is autonomous and transparent, cannot be reverted, and has a public and immutable trace. Smart contracts can send, receive, and store money, and interact with other smart contracts or internet-connected systems. Bitcoin is described as the first smart contract, as it operates through an autonomous program on a decentralized network with public, immutable transactions. Ethereum is presented as an platform that allows for more complex smart contracts through a Turing-complete programming language. Examples of potential smart contract applications include sales contracts, decentralized DNS, autonomous companies, insurance, and inheritance. Challenges mentioned include scalability, privacy vs criminality, bugs, and
Formal Specification in Software Engineering SE9
Formal Specification in Software Engineering SE9koolkampus This document discusses formal specification techniques for software. It describes algebraic techniques for specifying interfaces as abstract data types and model-based techniques for specifying system behavior. Algebraic specifications define operations and their relationships, while model-based specifications represent the system state using mathematical constructs like sets and sequences. Formal specification finds errors earlier and reduces rework, though it requires more upfront effort. The document also provides an example of formally specifying an air traffic control system and insulin pump.
ppt on sOFTWARE DEVELOPMENT LIFE CYCLE
ppt on sOFTWARE DEVELOPMENT LIFE CYCLESwarnima Tiwari The document discusses the software development life cycle (SDLC). It describes the typical phases of SDLC including problem definition, program design, coding, debugging, testing, documentation, maintenance, and extension/redesign. It also covers different SDLC models like waterfall, prototyping, and agile development. The SDLC process is best for structured environments while iterative models work better for web and e-commerce projects where frequent stakeholder feedback is needed.
Staffing level estimation 
Staffing level estimation kavitha muneeshwaran The document discusses staffing level estimation over the course of a software development project. It describes how the number of personnel needed varies at different stages: a small group is needed for planning and analysis, a larger group for architectural design, and the largest number for implementation and system testing. It also references models like the Rayleigh curve and Putnam's interpretation that estimate personnel levels over time. Tables show estimates for the distribution of effort, schedule, and personnel across activities for different project sizes. The key idea is that staffing requirements fluctuate throughout the software life cycle, with peaks during implementation and testing phases.
Unified process model
Unified process modelRyndaMaala The Unified Process (UP) is a popular iterative software development framework that uses use cases, architecture-centric design, and the Unified Modeling Language. It originated from Jacobson's Objectory process in the 1980s and was further developed by Rational Software into the Rational Unified Process. The UP consists of four phases - inception, elaboration, construction, and transition - and emphasizes iterative development, architectural drivers, and risk-managed delivery.
Lecture 12 requirements modeling - (system analysis)
Lecture 12 requirements modeling - (system analysis)IIUI This document discusses requirements modeling in software engineering. It covers creating various models during requirements analysis, including scenario-based models, data models, class-oriented models, flow-oriented models, and behavioral models. These models form the requirements model, which is the first technical representation of a system. The document provides examples of writing use cases and constructing a preliminary use case diagram for a home security system called SafeHome. It emphasizes that requirements modeling lays the foundation for software specification and design.
Software Process Models
Software Process ModelsHassan A-j This document discusses different process models used in software development. It describes the key phases and characteristics of several common process models including waterfall, prototyping, V-model, incremental, iterative, spiral and agile development models. The waterfall model involves sequential phases from requirements to maintenance without iteration. Prototyping allows for user feedback earlier. The V-model adds verification and validation phases. Incremental and iterative models divide the work into smaller chunks to allow for iteration and user feedback throughout development.
Software Engineering Layered Technology Software Process Framework
Software Engineering Layered Technology Software Process FrameworkJAINAM KAPADIYA Software engineering is the application of engineering principles to software development to obtain economical and quality software. It is a layered technology with a focus on quality. The foundation is the software process, which provides a framework of activities. This includes common activities like communication, modeling, planning, construction, and deployment. Additional umbrella activities support the process, such as quality assurance, configuration management, and risk management.
Use Case Diagram
Use Case DiagramKumar The document discusses use case diagrams in object oriented design and analysis. It defines use cases as descriptions of system functionality from a user perspective. Use case diagrams depict system behavior, users, and relationships between actors, use cases, and other use cases. The key components of use case diagrams are described as actors, use cases, the system boundary, and relationships. Common relationships include association, extend, generalization, uses, and include. An example use case diagram for a cellular telephone is provided to illustrate these concepts.
Software development process models
Software development process modelsMuhammed Afsal Villan Software development process models
Rapid Application Development (RAD) Model
Evolutionary Process Models
Spiral Model
THE FORMAL METHODS MODEL
Specialized Process Models
The Concurrent Development Model
Software Engineering ppt
Software Engineering pptshruths2890 The document describes an online railway reservation system project submitted by students. It discusses software engineering principles and methods used to develop the system. It includes UML diagrams like use case, class, sequence, and activity diagrams that were created as part of the analysis and design of the system. It also describes testing done on the project in the form of alpha testing.
Analysis modeling & scenario based modeling 
Analysis modeling & scenario based modeling Benazir Fathima The document discusses requirements modeling and analysis modeling in software engineering. It provides information on:
1) The different types of models that can be created during requirements modeling, including requirements models, design models, scenario-based models, data models, class-based models, flow-oriented models, and behavioral models.
2) The purposes of requirements modeling, which include representing customer requirements, gaining a better understanding of the system, and providing information to help with system design and development.
3) Key principles of requirements modeling, such as representing the information, functional, and behavioral domains of the system and partitioning models in a layered/hierarchical way.
4) Specific modeling techniques like scenario-based modeling, data
Software testing ppt
Software testing pptHeritage Institute Of Tech,India Testing is the process of identifying bugs and ensuring software meets requirements. It involves executing programs under different conditions to check specification, functionality, and performance. The objectives of testing are to uncover errors, demonstrate requirements are met, and validate quality with minimal cost. Testing follows a life cycle including planning, design, execution, and reporting. Different methodologies like black box and white box testing are used at various levels from unit to system. The overall goal is to perform effective testing to deliver high quality software.
Language and Processors for Requirements Specification
Language and Processors for Requirements Specificationkirupasuchi1996 This document discusses several languages and processors that have been developed for requirements specification in software development. It describes Problem Statement Language (PSL) and its processor, the Problem Statement Analyzer (PSA), which were developed to allow concise statement and automated analysis of requirements. It also discusses the Requirements Statement Language (RSL) and Requirements Engineering Validation System (REVS). Finally, it provides a brief overview of Structured Analysis and Design Technique (SADT), including its data and activity diagram components.
Command center processing and display system replacement (ccpds-r) - Case Study
Command center processing and display system replacement (ccpds-r) - Case StudyKuppusamy P This document describes a case study of the Command Center Processing and Display System - Replacement (CCPDS-R) project led by TRW Space and Defense for the U.S. Air Force. The CCPDS-R was developed to replace the primary missile warning system at Cheyenne Mountain and included a 48-month development schedule using Ada. Key aspects of the CCPDS-R project included: 1) Developing a common subsystem with six software components, 2) Using an incremental design and development approach split into builds, and 3) Conducting demonstrations at major milestones to assess requirements and architectural risks. The project was completed on time and within budget to customer satisfaction.
software project management Artifact set(spm)
software project management Artifact set(spm)REHMAT ULLAH This document discusses software project management artifacts. Artifacts are organized into management and engineering sets. The management set includes artifacts like the work breakdown structure, business case, and software development plan. The engineering set includes requirement, design, implementation, and deployment artifact sets. Each set captures information through various notations and tools to manage the software development lifecycle.
Software Development Life Cycle
Software Development Life CycleManohar Prasad, PfMP®, PgMP®, PMP®, RMP®, ACP®, CAL®, ACC®, CSP® SDLC is the acronym of Software Development Life Cycle. It is also called as Software development process. The software development life cycle (SDLC) is a framework defining tasks performed at each step in the software development process.
Type Checking(Compiler Design) #ShareThisIfYouLike
Type Checking(Compiler Design) #ShareThisIfYouLikeUnited International University The purpose of types:
To define what the program should do.
e.g. read an array of integers and return a double
To guarantee that the program is meaningful.
that it does not add a string to an integer
that variables are declared before they are used
To document the programmer's intentions.
better than comments, which are not checked by the compiler
To optimize the use of hardware.
reserve the minimal amount of memory, but not more
use the most appropriate machine instructions.
Software development life cycle (SDLC)
Software development life cycle (SDLC)Simran Kaur The document defines the software development life cycle (SDLC) and its phases. It discusses several SDLC models including waterfall, prototype, iterative enhancement, and spiral. The waterfall model follows sequential phases from requirements to maintenance with no overlap. The prototype model involves building prototypes for user feedback. The iterative enhancement model develops software incrementally. The spiral model is divided into risk analysis, engineering, construction, and evaluation cycles. The document also covers software requirements, elicitation through interviews and use cases, analysis through data, behavioral and functional modeling, and documentation in a software requirements specification.
Software myths | Software Engineering Notes
Software myths | Software Engineering NotesNavjyotsinh Jadeja This document discusses common myths held by software managers, developers, and customers. It describes myths such as believing formal standards and procedures are sufficient, thinking new hardware means high quality development, adding people to late projects will help catch up, and outsourcing means relaxing oversight. Realities discussed include standards not being used effectively, tools being more important than hardware, adding people making projects later, and needing management and control of outsourced projects. Developer myths like thinking the job is done once code runs and quality can't be assessed until code runs are addressed. The document emphasizes the importance of requirements, documentation, quality processes, and addressing change impacts.
Formal Approaches to SQA.pptx
Formal Approaches to SQA.pptxKarthigaiSelviS3 The document discusses formal approaches to software quality assurance (SQA). It states that SQA can be improved through software engineering practices like technical reviews, multi-tiered testing, controlling work products and changes, and following standards. It also argues that a more rigorous mathematical approach is needed for SQA since programs can be viewed as mathematical objects with rigorous syntax and semantics defined for languages, allowing proofs of correctness.
Sonet
SonetAkash Kumar Dhameja SONET and SDH are standardized protocols that transfer multiple digital bit streams synchronously over optical fibre using lasers. SONET is used in North America while SDH is used globally. The document discusses the architecture of SONET systems including signals, devices, and connections. It also covers the SONET frame format, layers, and how SONET networks can be configured in linear, ring, or mesh topologies to provide bandwidth and protection.
Software requirements specification
Software requirements specificationKrishnasai Gudavalli This document provides a summary of requirements for a Library Management System. It includes 3 sections:
1. Introduction - Defines the purpose, scope and intended audience of the system which is to manage library processes like book borrowing online.
2. Overall Description - Outlines key product functions for administrators and users, the operating environment, user characteristics and design constraints.
3. External Interfaces - Specifies the user interface requirements including login, search and categories. Hardware and software interfaces are also listed.
The document provides a high-level overview of the essential functions, behaviors and non-functional requirements for the library management software.
Ad
More Related Content
What's hot (20)
Formal Specification in Software Engineering SE9
Formal Specification in Software Engineering SE9koolkampus This document discusses formal specification techniques for software. It describes algebraic techniques for specifying interfaces as abstract data types and model-based techniques for specifying system behavior. Algebraic specifications define operations and their relationships, while model-based specifications represent the system state using mathematical constructs like sets and sequences. Formal specification finds errors earlier and reduces rework, though it requires more upfront effort. The document also provides an example of formally specifying an air traffic control system and insulin pump.
ppt on sOFTWARE DEVELOPMENT LIFE CYCLE
ppt on sOFTWARE DEVELOPMENT LIFE CYCLESwarnima Tiwari The document discusses the software development life cycle (SDLC). It describes the typical phases of SDLC including problem definition, program design, coding, debugging, testing, documentation, maintenance, and extension/redesign. It also covers different SDLC models like waterfall, prototyping, and agile development. The SDLC process is best for structured environments while iterative models work better for web and e-commerce projects where frequent stakeholder feedback is needed.
Staffing level estimation
Staffing level estimation kavitha muneeshwaran The document discusses staffing level estimation over the course of a software development project. It describes how the number of personnel needed varies at different stages: a small group is needed for planning and analysis, a larger group for architectural design, and the largest number for implementation and system testing. It also references models like the Rayleigh curve and Putnam's interpretation that estimate personnel levels over time. Tables show estimates for the distribution of effort, schedule, and personnel across activities for different project sizes. The key idea is that staffing requirements fluctuate throughout the software life cycle, with peaks during implementation and testing phases.
Unified process model
Unified process modelRyndaMaala The Unified Process (UP) is a popular iterative software development framework that uses use cases, architecture-centric design, and the Unified Modeling Language. It originated from Jacobson's Objectory process in the 1980s and was further developed by Rational Software into the Rational Unified Process. The UP consists of four phases - inception, elaboration, construction, and transition - and emphasizes iterative development, architectural drivers, and risk-managed delivery.
Lecture 12 requirements modeling - (system analysis)
Lecture 12 requirements modeling - (system analysis)IIUI This document discusses requirements modeling in software engineering. It covers creating various models during requirements analysis, including scenario-based models, data models, class-oriented models, flow-oriented models, and behavioral models. These models form the requirements model, which is the first technical representation of a system. The document provides examples of writing use cases and constructing a preliminary use case diagram for a home security system called SafeHome. It emphasizes that requirements modeling lays the foundation for software specification and design.
Software Process Models
Software Process ModelsHassan A-j This document discusses different process models used in software development. It describes the key phases and characteristics of several common process models including waterfall, prototyping, V-model, incremental, iterative, spiral and agile development models. The waterfall model involves sequential phases from requirements to maintenance without iteration. Prototyping allows for user feedback earlier. The V-model adds verification and validation phases. Incremental and iterative models divide the work into smaller chunks to allow for iteration and user feedback throughout development.
Software Engineering Layered Technology Software Process Framework
Software Engineering Layered Technology Software Process FrameworkJAINAM KAPADIYA Software engineering is the application of engineering principles to software development to obtain economical and quality software. It is a layered technology with a focus on quality. The foundation is the software process, which provides a framework of activities. This includes common activities like communication, modeling, planning, construction, and deployment. Additional umbrella activities support the process, such as quality assurance, configuration management, and risk management.
Use Case Diagram
Use Case DiagramKumar The document discusses use case diagrams in object oriented design and analysis. It defines use cases as descriptions of system functionality from a user perspective. Use case diagrams depict system behavior, users, and relationships between actors, use cases, and other use cases. The key components of use case diagrams are described as actors, use cases, the system boundary, and relationships. Common relationships include association, extend, generalization, uses, and include. An example use case diagram for a cellular telephone is provided to illustrate these concepts.
Software development process models
Software development process modelsMuhammed Afsal Villan Software development process models
Rapid Application Development (RAD) Model
Evolutionary Process Models
Spiral Model
THE FORMAL METHODS MODEL
Specialized Process Models
The Concurrent Development Model
Software Engineering ppt
Software Engineering pptshruths2890 The document describes an online railway reservation system project submitted by students. It discusses software engineering principles and methods used to develop the system. It includes UML diagrams like use case, class, sequence, and activity diagrams that were created as part of the analysis and design of the system. It also describes testing done on the project in the form of alpha testing.
Analysis modeling & scenario based modeling
Analysis modeling & scenario based modeling Benazir Fathima The document discusses requirements modeling and analysis modeling in software engineering. It provides information on:
1) The different types of models that can be created during requirements modeling, including requirements models, design models, scenario-based models, data models, class-based models, flow-oriented models, and behavioral models.
2) The purposes of requirements modeling, which include representing customer requirements, gaining a better understanding of the system, and providing information to help with system design and development.
3) Key principles of requirements modeling, such as representing the information, functional, and behavioral domains of the system and partitioning models in a layered/hierarchical way.
4) Specific modeling techniques like scenario-based modeling, data
Software testing ppt
Software testing pptHeritage Institute Of Tech,India Testing is the process of identifying bugs and ensuring software meets requirements. It involves executing programs under different conditions to check specification, functionality, and performance. The objectives of testing are to uncover errors, demonstrate requirements are met, and validate quality with minimal cost. Testing follows a life cycle including planning, design, execution, and reporting. Different methodologies like black box and white box testing are used at various levels from unit to system. The overall goal is to perform effective testing to deliver high quality software.
Language and Processors for Requirements Specification
Language and Processors for Requirements Specificationkirupasuchi1996 This document discusses several languages and processors that have been developed for requirements specification in software development. It describes Problem Statement Language (PSL) and its processor, the Problem Statement Analyzer (PSA), which were developed to allow concise statement and automated analysis of requirements. It also discusses the Requirements Statement Language (RSL) and Requirements Engineering Validation System (REVS). Finally, it provides a brief overview of Structured Analysis and Design Technique (SADT), including its data and activity diagram components.
Command center processing and display system replacement (ccpds-r) - Case Study
Command center processing and display system replacement (ccpds-r) - Case StudyKuppusamy P This document describes a case study of the Command Center Processing and Display System - Replacement (CCPDS-R) project led by TRW Space and Defense for the U.S. Air Force. The CCPDS-R was developed to replace the primary missile warning system at Cheyenne Mountain and included a 48-month development schedule using Ada. Key aspects of the CCPDS-R project included: 1) Developing a common subsystem with six software components, 2) Using an incremental design and development approach split into builds, and 3) Conducting demonstrations at major milestones to assess requirements and architectural risks. The project was completed on time and within budget to customer satisfaction.
software project management Artifact set(spm)
software project management Artifact set(spm)REHMAT ULLAH This document discusses software project management artifacts. Artifacts are organized into management and engineering sets. The management set includes artifacts like the work breakdown structure, business case, and software development plan. The engineering set includes requirement, design, implementation, and deployment artifact sets. Each set captures information through various notations and tools to manage the software development lifecycle.
Software Development Life Cycle
Software Development Life CycleManohar Prasad, PfMP®, PgMP®, PMP®, RMP®, ACP®, CAL®, ACC®, CSP® SDLC is the acronym of Software Development Life Cycle. It is also called as Software development process. The software development life cycle (SDLC) is a framework defining tasks performed at each step in the software development process.
Type Checking(Compiler Design) #ShareThisIfYouLike
Type Checking(Compiler Design) #ShareThisIfYouLikeUnited International University The purpose of types:
To define what the program should do.
e.g. read an array of integers and return a double
To guarantee that the program is meaningful.
that it does not add a string to an integer
that variables are declared before they are used
To document the programmer's intentions.
better than comments, which are not checked by the compiler
To optimize the use of hardware.
reserve the minimal amount of memory, but not more
use the most appropriate machine instructions.
Software development life cycle (SDLC)
Software development life cycle (SDLC)Simran Kaur The document defines the software development life cycle (SDLC) and its phases. It discusses several SDLC models including waterfall, prototype, iterative enhancement, and spiral. The waterfall model follows sequential phases from requirements to maintenance with no overlap. The prototype model involves building prototypes for user feedback. The iterative enhancement model develops software incrementally. The spiral model is divided into risk analysis, engineering, construction, and evaluation cycles. The document also covers software requirements, elicitation through interviews and use cases, analysis through data, behavioral and functional modeling, and documentation in a software requirements specification.
Software myths | Software Engineering Notes
Software myths | Software Engineering NotesNavjyotsinh Jadeja This document discusses common myths held by software managers, developers, and customers. It describes myths such as believing formal standards and procedures are sufficient, thinking new hardware means high quality development, adding people to late projects will help catch up, and outsourcing means relaxing oversight. Realities discussed include standards not being used effectively, tools being more important than hardware, adding people making projects later, and needing management and control of outsourced projects. Developer myths like thinking the job is done once code runs and quality can't be assessed until code runs are addressed. The document emphasizes the importance of requirements, documentation, quality processes, and addressing change impacts.
Formal Approaches to SQA.pptx
Formal Approaches to SQA.pptxKarthigaiSelviS3 The document discusses formal approaches to software quality assurance (SQA). It states that SQA can be improved through software engineering practices like technical reviews, multi-tiered testing, controlling work products and changes, and following standards. It also argues that a more rigorous mathematical approach is needed for SQA since programs can be viewed as mathematical objects with rigorous syntax and semantics defined for languages, allowing proofs of correctness.
Viewers also liked (20)
Sonet
SonetAkash Kumar Dhameja SONET and SDH are standardized protocols that transfer multiple digital bit streams synchronously over optical fibre using lasers. SONET is used in North America while SDH is used globally. The document discusses the architecture of SONET systems including signals, devices, and connections. It also covers the SONET frame format, layers, and how SONET networks can be configured in linear, ring, or mesh topologies to provide bandwidth and protection.
Software requirements specification
Software requirements specificationKrishnasai Gudavalli This document provides a summary of requirements for a Library Management System. It includes 3 sections:
1. Introduction - Defines the purpose, scope and intended audience of the system which is to manage library processes like book borrowing online.
2. Overall Description - Outlines key product functions for administrators and users, the operating environment, user characteristics and design constraints.
3. External Interfaces - Specifies the user interface requirements including login, search and categories. Hardware and software interfaces are also listed.
The document provides a high-level overview of the essential functions, behaviors and non-functional requirements for the library management software.
E bidding presentation
E bidding presentationPrabin Tandan E-bidding is the process of bidding through electronic medium and is one of the three stages of e-procurement along with e-execution and e-payment. It provides a more transparent bidding process and promotes free and fair competition to save government resources. The e-bidding module has components for the site administrator, buyers, bidders, and general viewers. It facilitates tender notices, bid submission and modification, and secure storage of submitted bids. Fully implementing e-bidding in Nepal requires addressing issues like training manpower, unreliable power supply, and internet connectivity problems.
Auction presentation
Auction presentationtechmodi_India An auction is a process of buying and selling goods or services through competitive bidding. Traditionally, auctions were conducted live by auction houses, but now most occur online. The key aspects of an auction are multiple interested buyers bidding against each other, with the item going to the highest bidder. Common types of auctions include English, Dutch, sealed-bid, and Vickrey auctions. Industries that commonly use auctions include antiques, real estate, automobiles, commodities, and various business assets. Online auction platforms like eBay have made auctions more accessible globally.
Software requirement and specification
Software requirement and specificationAman Adhikari The document discusses software requirements and specifications. It explains that requirements engineering is the process of establishing customer requirements for a system. Requirements can range from high-level abstract statements to detailed functional specifications. Both types of statements may be called requirements. The document also discusses different types of requirements like user requirements, system requirements, functional requirements, and non-functional requirements. It provides examples and explanations of each. The structure and intended users of a requirements document are also covered.
SRS on Online Blood Bank Managment system... 
SRS on Online Blood Bank Managment system... GCWUF This document outlines the requirements for an online blood bank management system. The system will allow administrators to register blood donors and enter new blood details. It will track blood stock levels and facilitate blood sales and purchases. The system aims to automate the tracking of blood products from initial ordering through administration and updates to medical records. It will support routine transfusions as well as special cases and emergencies. The system requirements include specifications for hardware, software, databases, and functional modules for administrators, donors and acceptors.
Business requirement analysis session 5
Business requirement analysis session 5sampad_senapati This document discusses requirement specification and the software requirement specification (SRS) document. It covers the purpose and content of an SRS, including describing the system functionality, interfaces, performance, and attributes. It also discusses organizing requirements and avoiding common mistakes like ambiguity. An SRS is intended to communicate requirements to stakeholders and serve as a contract between clients and developers. It should describe what the system needs to do without including design or implementation details.
Beit 381 se lec 15 - 16 - 12 mar27 - req engg 1 of 3
Beit 381 se lec 15 - 16 - 12 mar27 - req engg 1 of 3babak danyal The document provides an overview of requirements engineering as the first stage of the software development process. It discusses how requirements are initially vague and ill-defined, and must be precisely defined to guide implementation. Requirements engineering involves elicitation, analysis, and specification, with the output being a Software Requirements Specification document. The document outlines key aspects that should be included in an SRS, such as functional requirements, data requirements, performance requirements, design constraints, and guidelines. It also discusses techniques for requirements analysis like use case modeling and data flow diagrams.
Sample business-plan
Sample business-planShafiqul Islam Touhid NewAge BIOTECH, Inc. was formed in XXXX to develop, market, and license its patented zinc peptide technology. The company has seen total revenue grow from $2.7 million in XXXX to an estimated $11.1 million in 200B. Although NewAge BIOTECH experienced a net loss of $4.5 million in XXXX, profit of $500,000 is projected in 200B. In 200A, the company’s revenue grew by 40 percent to $6.6 million from $4.7 million the prior year, while operating expenses increased by only 6.7 percent to $7.45 million from $6.98 million. Overall, the company is approaching profitability, and the zinc peptide technology is proving to be a significant platform from which to launch additional product lines.
Online auction system for art work
Online auction system for art workMorine Gakii This document proposes developing an online auction system for artworks at Taita Taveta University College. It discusses problems with existing manual auction systems, including security issues and limitations on access. The objectives are to study auction experts' role in market efficiency, determine art price factors, develop a prototype online auction system, and test its usability. A literature review covers factors influencing art prices, the impact of expert appraisals, and prototypes for online auction systems. If implemented, the proposed system could address security concerns, provide broader access to auctions, and help auction houses operate more efficiently.
Software Requirement Specification
Software Requirement SpecificationDr Sukhpal Singh Gill This document provides a template and guidelines for creating a Software Requirements Specification (SRS). It includes sections for an introduction, general description, specific requirements, and appendix. The specific requirements section breaks down high-level functional requirements into detailed child requirements and includes examples of formatting for non-functional and design requirements. Guidelines are provided on attributes of a good SRS such as requirements being correct, necessary, unambiguous and verifiable.
Presentation of project on e auction with dotnet
Presentation of project on e auction with dotnetSunanda Chakraborty this is a presentation on online auction or e-Auction, a project of DOTNET done by me and presented in a seminar at GLOBSYN,KOLKATA
Analysis concepts and principles
Analysis concepts and principlessaurabhshertukde Software requirement engineering bridges the gap between system engineering and software design. It involves gathering requirements through elicitation techniques like interviews and facilitated application specification technique (FAST), analyzing requirements, modeling them, specifying them in documents like use cases, and reviewing the requirements specification. Quality function deployment translates customer needs into technical requirements. Rapid prototyping helps validate requirements by constructing a partial system implementation using tools like 4GLs, reusable components, or formal specification languages. The software requirements specification document is produced at the end of analysis and acts as a contract between developers and customers.
Biomedical waste managment
Biomedical waste managmentADESH MEDICAL COLLEGE The document discusses biomedical waste management. It defines biomedical waste and notes that improper management poses health risks. The rules for management in India are outlined, including categories of waste and treatment methods like incineration and autoclaving. Proper procedures for storage, transportation, and disposal are important to implement the rules and prevent health and environmental issues.
Ch9-Software Engineering 9
Ch9-Software Engineering 9Ian Sommerville Software evolution involves making ongoing changes to software systems to address new requirements, fix errors, and improve performance. There are several approaches to managing software evolution, including maintenance, reengineering, refactoring, and legacy system management. Key considerations for legacy systems include assessing their business value and quality to determine whether they should be replaced, transformed, or maintained.
Incometax E-Filinf System
Incometax E-Filinf Systemvivek shah This document provides an overview and specifications for an Income Tax E-Filing System (IEFS) developed by Vivek Shah and Deven Sorthiya. The 3-sentence summary is:
The Income Tax E-Filing System (IEFS) allows users to manage their PAN information online, download tax return preparation software to fill out returns offline, and register and e-file their completed returns along with tracking the status of their account. Key features of IEFS include PAN lookup, registration for PAN allocation, downloading the ITR utility, validating and generating an XML return file, e-filing the return, and tracking the status of the filing. The system has modules for home page,
Artefacto SRS Especificaciones Suplementarias del Sistema
Artefacto SRS Especificaciones Suplementarias del SistemaIleana Garza Ibarra Artefacto SRS,Especificaciones Suplementarias del Sistema para el Sistema de Control de Producción para maquiladora del giro textil, versión 1.0
Performance Appraisal of Square Pharmaceutical ltd
Performance Appraisal of Square Pharmaceutical ltdShakhawatul Islam SaaGooR This document discusses Square Pharmaceuticals Ltd (SPL), a leading pharmaceutical company in Bangladesh. Some key points:
- SPL was established in 1958 and has grown to become the largest pharmaceutical company in Bangladesh.
- It has achieved several milestones over the decades including technical collaborations with international companies and being the first Bangladeshi company to export pharmaceutical products.
- SPL's vision is to use business as a means to improve material and social well-being. Its mission is to produce quality healthcare for people while maintaining high ethical standards.
- The company aims to conduct transparent business within legal frameworks to achieve its mission and vision. Its goals include increasing market share and offering manufacturing services internationally.
Ad
Similar to SRS(software requirement specification) (20)
SRS- Software Requirement Management
SRS- Software Requirement ManagementMuhammadAhmad1135 SRS is the official statement of what the system developers should implement.
SRS is a complete description of the behavior of the system to be developed.
Software Requirement Specification
Software Requirement SpecificationKishan Kaushik In this presentation, we delve into the crucial world of Software Requirement Specification (SRS). We explore the significance of a well-defined SRS in software development, covering its purpose, key components, and best practices. Discover how an effective SRS can streamline project management, enhance communication, and ensure successful software delivery.
software requirement specifcation.pptx
software requirement specifcation.pptxSACHINMAURYA57 The document provides an overview of requirements for developing a software system specification (SRS), including:
1) Identifying and specifying requirements is difficult, especially for large scale systems, and involves understanding user needs and precisely stating what the future system will do.
2) An SRS is needed to establish agreement between users and developers on what the system should do, provide a reference for validation, and help reduce costs.
3) Key components of an SRS include an introduction describing purpose, scope, and organization, as well as sections for overall description, specific requirements, external interfaces, functions, and performance requirements.
Introduction to Requirement engineering
Introduction to Requirement engineeringNameirakpam Sundari Requirement engineering is the process of understanding a client's needs, documenting software requirements, and ensuring the final product meets the client's expectations. It involves eliciting requirements from stakeholders, analyzing and specifying the requirements, and managing changes. The key outputs are a software requirements specification document that formally defines functional and non-functional requirements, and a common understanding between developers and clients.
Lec srs
Lec srshuzaifa tariq The document discusses the Software Requirements Specification (SRS), which precisely defines the software product to be built. The SRS includes user and system requirements, and fully describes what the software will do and how it will perform. It has a standard structure including an introduction, overall description of functions and constraints, and specific requirements for interfaces, performance, and design. An effective SRS is correct, unambiguous, complete, consistent, verifiable, modifiable, and traceable.
Software requirements specifications documents pdf
Software requirements specifications documents pdfNothing807440 The document discusses the structure and contents of a good Software Requirements Specification (SRS) document. It explains that an SRS should include sections for an introduction, general description, functional requirements, interface requirements, performance requirements, design constraints, non-functional attributes, schedule and budget, and appendices. It provides details on the purpose and contents of each section to fully specify the requirements for a software system.
Writing software requirement document
Writing software requirement documentSunita Sahu The document discusses the purpose and contents of a software requirements specification (SRS). An SRS defines what functionality a software system should have and describes both functional and non-functional requirements. It serves as an agreement between developers and customers about what will be delivered. Writing requirements documents helps ensure agreement on scope and prevents misunderstandings, guiding development and testing.
Writing software requirement document
Writing software requirement documentSunita Sahu The document discusses the purpose and contents of a software requirements specification (SRS). An SRS defines what functionality a software system should have and describes both functional and non-functional requirements. It serves as an agreement between developers and customers about what will be delivered. Writing out requirements helps ensure agreement on scope and prevents misunderstandings, guiding development and testing.
Requirement Analysis
Requirement Analysissslovepk The document discusses the importance of software requirements specification (SRS) in software project management. An SRS describes what a software system should do without describing how it will be implemented. It establishes agreement between clients and developers on system functionality and provides a reference for validation. Key components of an SRS include functional requirements, performance requirements, design constraints, and external interface requirements.
2nd MODULE Software Requirements _ SW ENGG 22CSE141.pdf
2nd MODULE Software Requirements _ SW ENGG 22CSE141.pdfJayanthi Kannan MK SOFTWARE ENGINEERING
Course Code: 22CSE141
Module 2: Software Requirements
•SOFTWARE ENGINEERING
Course Code: 22CSE141
Module 2: Software Requirements,
•Functional and nonfunctional requirements,
•User requirements,
•Software requirements Document,
•Requirement Engineering Process,
•Feasibility studies,
•Requirements elicitation and analysis,
•Requirements validation
•System models:
•Context Models,
•Behavioral models,
•Data models,
•Object models,
•structured methods.
•User requirements,
•Software requirements Document
•Requirement Engineering Process
•Feasibility studies,
•Requirements elicitation and analysis,
•Requirements validation
•System models:
•Context Models,
•Behavioral models,
•Data models,
•Object models,
•structured methods.
Lecture 2 & 3.pptx
Lecture 2 & 3.pptxRaoShahid10 The document discusses software requirements specifications (SRS), which describe the functional and non-functional requirements for a software system. An SRS includes contents like the system's purpose, scope, users, and features. It also distinguishes between functional requirements, which specify what a system should do, and non-functional requirements, which relate to attributes like performance and security. The document provides examples of different types of requirements and discusses challenges in requirements engineering.
Soft requirement
Soft requirementRishav Upreti The document discusses software requirement analysis and specification. It describes determining user and stakeholder needs, defining functional and non-functional requirements, and requirement types like performance and quality attributes. Requirements must be testable and related to business needs. The analysis process involves defining user and stakeholder profiles, environments, and use cases. Common techniques for organizing requirements include functional hierarchies, data flow diagrams, and use case diagrams. The software requirements specification fully defines system behavior.
Software Requirements Specification concept in Software Engineering
Software Requirements Specification concept in Software EngineeringMrSKamalakannanVelsU1 "SRS" can have two main meanings depending on the context: Software Requirements Specification and Supplemental Restraint System (SRS).
Sofyware Engineering
Sofyware EngineeringAmberSinghal1 The document discusses software requirement specifications (SRS), including what an SRS is, when it is useful, and an outline for an SRS template. Some key points:
- An SRS formally defines the requirements for software that is to be developed. It serves as a contract between developers and customers.
- The SRS describes functional and non-functional requirements, interfaces, design constraints, and other aspects of the software without specifying solutions.
- A good SRS template includes sections for introduction, overall description, specific requirements, and appendices. It provides a standardized way to document requirements.
Requirement and Specification
Requirement and Specificationsarojsaroza The presentation discusses software requirements and specifications. It defines user requirements as more abstract statements of what services the system should provide, while system requirements provide more detailed descriptions of the system's functions and constraints. Functional requirements describe what the system will do, including inputs, outputs, and business rules. Non-functional requirements describe emergent system properties like performance, availability, and security. Finally, a software requirements document formally specifies both the user and system requirements and serves as an agreement between developers and customers.
chapter_3_8 of software requirements engineering
chapter_3_8 of software requirements engineeringJavedKhan524377 Software requirements engineering slides
Software project management requirements analysis
Software project management requirements analysisAntony Alex The document discusses requirements analysis for software engineering. It provides 3 key points:
1. Requirements analysis bridges the gap between system requirements engineering and software design by providing a model of the system's information, functions, and behavior to guide design.
2. The purpose is to obtain a thorough understanding of business needs and break them down into clearly defined and agreed upon requirements. This establishes the framework to guide future design and development.
3. The primary goal is to create a detailed functional specification defining all system capabilities and accompanying data and process models, illustrating information managed and processes supported by the new system.
Ad
Recently uploaded (20)
DATA-DRIVEN SHOULDER INVERSE KINEMATICS YoungBeom Kim1 , Byung-Ha Park1 , Kwa...
DATA-DRIVEN SHOULDER INVERSE KINEMATICS YoungBeom Kim1 , Byung-Ha Park1 , Kwa...charlesdick1345 This paper proposes a shoulder inverse kinematics (IK) technique. Shoulder complex is comprised of the sternum, clavicle, ribs, scapula, humerus, and four joints.
Compiler Design Unit1 PPT Phases of Compiler.pptx
Compiler Design Unit1 PPT Phases of Compiler.pptxRushaliDeshmukh2 Compiler phases
Lexical analysis
Syntax analysis
Semantic analysis
Intermediate (machine-independent) code generation
Intermediate code optimization
Target (machine-dependent) code generation
Target code optimization
Data Structures_Searching and Sorting.pptx
Data Structures_Searching and Sorting.pptxRushaliDeshmukh2 Sorting Order and Stability in Sorting.
Concept of Internal and External Sorting.
Bubble Sort,
Insertion Sort,
Selection Sort,
Quick Sort and
Merge Sort,
Radix Sort, and
Shell Sort,
External Sorting, Time complexity analysis of Sorting Algorithms.
"Boiler Feed Pump (BFP): Working, Applications, Advantages, and Limitations E...
"Boiler Feed Pump (BFP): Working, Applications, Advantages, and Limitations E...Infopitaara A Boiler Feed Pump (BFP) is a critical component in thermal power plants. It supplies high-pressure water (feedwater) to the boiler, ensuring continuous steam generation.
⚙️ How a Boiler Feed Pump Works
Water Collection:
Feedwater is collected from the deaerator or feedwater tank.
Pressurization:
The pump increases water pressure using multiple impellers/stages in centrifugal types.
Discharge to Boiler:
Pressurized water is then supplied to the boiler drum or economizer section, depending on design.
🌀 Types of Boiler Feed Pumps
Centrifugal Pumps (most common):
Multistage for higher pressure.
Used in large thermal power stations.
Positive Displacement Pumps (less common):
For smaller or specific applications.
Precise flow control but less efficient for large volumes.
🛠️ Key Operations and Controls
Recirculation Line: Protects the pump from overheating at low flow.
Throttle Valve: Regulates flow based on boiler demand.
Control System: Often automated via DCS/PLC for variable load conditions.
Sealing & Cooling Systems: Prevent leakage and maintain pump health.
⚠️ Common BFP Issues
Cavitation due to low NPSH (Net Positive Suction Head).
Seal or bearing failure.
Overheating from improper flow or recirculation.
Process Parameter Optimization for Minimizing Springback in Cold Drawing Proc...
Process Parameter Optimization for Minimizing Springback in Cold Drawing Proc...Journal of Soft Computing in Civil Engineering In tube drawing process, a tube is pulled out through a die and a plug to reduce its diameter and thickness as per the requirement. Dimensional accuracy of cold drawn tubes plays a vital role in the further quality of end products and controlling rejection in manufacturing processes of these end products. Springback phenomenon is the elastic strain recovery after removal of forming loads, causes geometrical inaccuracies in drawn tubes. Further, this leads to difficulty in achieving close dimensional tolerances. In the present work springback of EN 8 D tube material is studied for various cold drawing parameters. The process parameters in this work include die semi-angle, land width and drawing speed. The experimentation is done using Taguchi’s L36 orthogonal array, and then optimization is done in data analysis software Minitab 17. The results of ANOVA shows that 15 degrees die semi-angle,5 mm land width and 6 m/min drawing speed yields least springback. Furthermore, optimization algorithms named Particle Swarm Optimization (PSO), Simulated Annealing (SA) and Genetic Algorithm (GA) are applied which shows that 15 degrees die semi-angle, 10 mm land width and 8 m/min drawing speed results in minimal springback with almost 10.5 % improvement. Finally, the results of experimentation are validated with Finite Element Analysis technique using ANSYS.
RICS Membership-(The Royal Institution of Chartered Surveyors).pdf
RICS Membership-(The Royal Institution of Chartered Surveyors).pdfMohamedAbdelkader115 Glad to be one of only 14 members inside Kuwait to hold this credential.
Please check the members inside kuwait from this link:
https://www.rics.org/networking/find-a-member.html?firstname=&lastname=&town=&country=Kuwait&member_grade=(AssocRICS)&expert_witness=&accrediation=&page=1
Lidar for Autonomous Driving, LiDAR Mapping for Driverless Cars.pptx
Lidar for Autonomous Driving, LiDAR Mapping for Driverless Cars.pptxRishavKumar530754 LiDAR-Based System for Autonomous Cars
Autonomous Driving with LiDAR Tech
LiDAR Integration in Self-Driving Cars
Self-Driving Vehicles Using LiDAR
LiDAR Mapping for Driverless Cars
Avnet Silica's PCIM 2025 Highlights Flyer
Avnet Silica's PCIM 2025 Highlights FlyerWillDavies22 See what you can expect to find on Avnet Silica's stand at PCIM 2025.
Artificial Intelligence (AI) basics.pptx
Artificial Intelligence (AI) basics.pptxaditichinar its all about Artificial Intelligence(Ai) and Machine Learning and not on advanced level you can study before the exam or can check for some information on Ai for project
some basics electrical and electronics knowledge
some basics electrical and electronics knowledgenguyentrungdo88 This chapter discribe about common electrical divices such as passive component, the internaltional system unit and international system prefixes.
π0.5: a Vision-Language-Action Model with Open-World Generalization
π0.5: a Vision-Language-Action Model with Open-World GeneralizationNABLAS株式会社 今回の資料「Transfusion / π0 / π0.5」は、画像・言語・アクションを統合するロボット基盤モデルについて紹介しています。
拡散×自己回帰を融合したTransformerをベースに、π0.5ではオープンワールドでの推論・計画も可能に。
This presentation introduces robot foundation models that integrate vision, language, and action.
Built on a Transformer combining diffusion and autoregression, π0.5 enables reasoning and planning in open-world settings.
fluke dealers in bangalore..............
fluke dealers in bangalore..............Haresh Vaswani The Fluke 925 is a vane anemometer, a handheld device designed to measure wind speed, air flow (volume), and temperature. It features a separate sensor and display unit, allowing greater flexibility and ease of use in tight or hard-to-reach spaces. The Fluke 925 is particularly suitable for HVAC (heating, ventilation, and air conditioning) maintenance in both residential and commercial buildings, offering a durable and cost-effective solution for routine airflow diagnostics.
IntroSlides-April-BuildWithAI-VertexAI.pdf
IntroSlides-April-BuildWithAI-VertexAI.pdfLuiz Carneiro ☁️ GDG Cloud Munich: Build With AI Workshop - Introduction to Vertex AI! ☁️
Join us for an exciting #BuildWithAi workshop on the 28th of April, 2025 at the Google Office in Munich!
Dive into the world of AI with our "Introduction to Vertex AI" session, presented by Google Cloud expert Randy Gupta.
Structural Response of Reinforced Self-Compacting Concrete Deep Beam Using Fi...
Structural Response of Reinforced Self-Compacting Concrete Deep Beam Using Fi...Journal of Soft Computing in Civil Engineering Analysis of reinforced concrete deep beam is based on simplified approximate method due to the complexity of the exact analysis. The complexity is due to a number of parameters affecting its response. To evaluate some of this parameters, finite element study of the structural behavior of the reinforced self-compacting concrete deep beam was carried out using Abaqus finite element modeling tool. The model was validated against experimental data from the literature. The parametric effects of varied concrete compressive strength, vertical web reinforcement ratio and horizontal web reinforcement ratio on the beam were tested on eight (8) different specimens under four points loads. The results of the validation work showed good agreement with the experimental studies. The parametric study revealed that the concrete compressive strength most significantly influenced the specimens’ response with the average of 41.1% and 49 % increment in the diagonal cracking and ultimate load respectively due to doubling of concrete compressive strength. Although the increase in horizontal web reinforcement ratio from 0.31 % to 0.63 % lead to average of 6.24 % increment on the diagonal cracking load, it does not influence the ultimate strength and the load-deflection response of the beams. Similar variation in vertical web reinforcement ratio leads to an average of 2.4 % and 15 % increment in cracking and ultimate load respectively with no appreciable effect on the load-deflection response.
15th International Conference on Computer Science, Engineering and Applicatio...
15th International Conference on Computer Science, Engineering and Applicatio...IJCSES Journal #computerscience #programming #coding #technology #programmer #python #computer #developer #tech #coder #javascript #java #codinglife #html #code #softwaredeveloper #webdeveloper #software #cybersecurity #linux #computerengineering #webdevelopment #softwareengineer #machinelearning #hacking #engineering #datascience #css #programmers #pythonprogramming
Process Parameter Optimization for Minimizing Springback in Cold Drawing Proc...
Process Parameter Optimization for Minimizing Springback in Cold Drawing Proc...Journal of Soft Computing in Civil Engineering
Structural Response of Reinforced Self-Compacting Concrete Deep Beam Using Fi...
Structural Response of Reinforced Self-Compacting Concrete Deep Beam Using Fi...Journal of Soft Computing in Civil Engineering
SRS(software requirement specification)
- 1. SRS(Software Requirement Specification) By: Akash Kumar Dhameja, K12270, BCA, IV Sem.
- 2. Index • Definition • Purpose of SRS • SRS Format • Types of reader for requirement specification • Characteristics of SRS • Importance of SRS
- 3. What is an SRS ? • SRS is the official statement of what the system developers should implement. • SRS is a complete description of the behaviour of the system to be developed. • SRS should include both a definition of user requirements and a specification of the system requirements. • The SRS fully describes what the software will do and how it will be expected to perform.
- 4. Purpose of SRS • The SRS precisely defines the software product that will be built. • SRS used to know all the requirements for the software development and thus that will help in designing the software. • It provides feedback to the customer.
- 5. SRS Format Introduction • Purpose • Document Conventions • Product Scope • Reference Overall Description • Product Perspective • Product Functions • User Classes and Characteristics • Operating Environment • Design and Implementation Constraints • User Documentation • Assumptions and Dependencies External Interface Requirements • User Interfaces • Hardware Interfaces • Software Interfaces • Communications Interfaces
- 6. Continue… System Features •System Feature 1 •System Feature 2 (and so on) Other Nonfunctional Requirements • Performance Requirements • Safety Requirements • Security Requirements • Software Quality Attributes • Business Rules Other Requirements •Appendix A: Glossary •Appendix B: Analysis Models
- 7. Types of reader for requirement specification System Customers Specify the requirements and read them to check that they meet their needs. Customer specify changes to the requirements . Managers Use the Requirements Document to plane a bid for the system and to plan system development process. System Engineers Use the requirements to understand what system is to be deployed.
- 8. Continue… System test engineers Use the requirements to develop validation tests for the system System Maintains engineers Use the requirements to understand the system and the relationship between its parts
- 9. Characteristics of SRS • Correct : Every requirement given in SRS is a requirement of the software. • Unambiguous: Every requirement has exactly one interpretation. • Complete: Includes all functional, performance, design, external interface requirements; definition of the response of the software to all inputs. • Consistent: Internal consistency. • Ranked importance: Essential vs. desirable.
- 10. Continue… • Verifiable: A requirement is verifiable if and only if there exists some finite cost effective process with which a person or machine can check that the SW meets the requirement. • Modifiable: SRS must be structured to permit effective modifications (e.g. don’t be redundant, keep requirements separate) • Traceable: Origin of each requirement is clear.
- 11. what are the benefits of a great SRS? 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. • Reduce the development effort. • Provide a basis for estimating costs and schedules. • Provide a baseline for validation and verification. • Serve as a basis for enhancement.