Software reuirement elicitation in software engineering basics by ram k paliwal
Download as PPTX, PDF1 like325 views
The document outlines the necessity and process of requirement engineering in software development, emphasizing the identification and specification of user requirements. It details a four-step requirement engineering process consisting of feasibility study, requirement gathering, software requirement specification, and validation. Additionally, it discusses various requirement elicitation techniques such as interviews, brainstorming sessions, and form/interface analysis to effectively understand user needs.
Software reuirement elicitation in software engineering basics by ram k paliwal
- 1. Software Engineering- Unit 1 REQUIREMENT ELICITATION TECHNIQUE IN SOFTWARE ENGINEERING 8/31/2019 REQUIREMENT ANALYSIS AND SPECIFICATION IN SOFTWARE ENGINEERING - UNIT 1 - BY RAM K PALIWAL 1
- 2. Software Requirement The software requirements are description of features and functionalities of the target system. Requirements convey the expectations of users from the software product. The requirements can be obvious or hidden, known or unknown, expected or unexpected from client’s point of view. Requirement Engineering The process to gather the software requirements from client, analyze and document them is known as requirement engineering. The goal of requirement engineering is to develop and maintain sophisticated and descriptive ‘System Requirements Specification’ document. 8/31/2019 REQUIREMENT ANALYSIS AND SPECIFICATION IN SOFTWARE ENGINEERING - UNIT 1 - BY RAM K PALIWAL 2
- 3. Software Requirement Analysis Requirement Engineering Process It is a four step process, which includes ◦ Feasibility Study ◦ Requirement Gathering ◦ Software Requirement Specification ◦ Software Requirement Validation 8/31/2019 REQUIREMENT ANALYSIS AND SPECIFICATION IN SOFTWARE ENGINEERING - UNIT 1 - BY RAM K PALIWAL 3
- 4. Software Requirement Analysis Feasibility Study: Feasibility study establishes the basic business requirements and constraints associated with the application to be built and then assesses whether the application is a viable. It explores technical aspects of the project and product such as ◦ usability ◦ Maintainability ◦ productivity ◦ integration ability. 8/31/2019 REQUIREMENT ANALYSIS AND SPECIFICATION IN SOFTWARE ENGINEERING - UNIT 1 - BY RAM K PALIWAL 4
- 5. Software Requirement Analysis Requirement Gathering If the feasibility report is positive towards undertaking the project, next phase starts with gathering requirements from the user. Analysts and engineers communicate with the client and end-users to know their ideas on what the software should provide and which features they want the software to include. 8/31/2019 REQUIREMENT ANALYSIS AND SPECIFICATION IN SOFTWARE ENGINEERING - UNIT 1 - BY RAM K PALIWAL 5
- 6. Software Requirement Analysis Software Requirement Specification SRS defines how the intended software will interact with ◦Hardware ◦external interfaces ◦speed of operation ◦response time of system 8/31/2019 REQUIREMENT ANALYSIS AND SPECIFICATION IN SOFTWARE ENGINEERING - UNIT 1 - BY RAM K PALIWAL 6
- 7. Software Requirement Analysis Software Requirement Specification ◦ portability of software across various platforms ◦ Maintainability ◦ speed of recovery after crashing ◦ Security ◦ Quality ◦ Limitations etc. Note: SRS will be discussed in details in later chapters. 8/31/2019 REQUIREMENT ANALYSIS AND SPECIFICATION IN SOFTWARE ENGINEERING - UNIT 1 - BY RAM K PALIWAL 7
- 8. Software Requirement Analysis Software Requirement Validation Requirements can be checked against following conditions ◦ If they can be practically implemented ◦ If they are valid and as per functionality and domain of software ◦ If there are any ambiguities ◦ If they are complete ◦ If they can be demonstrated 8/31/2019 REQUIREMENT ANALYSIS AND SPECIFICATION IN SOFTWARE ENGINEERING - UNIT 1 - BY RAM K PALIWAL 8
- 9. Requirement Elicitation Techniques Requirements elicitation is perhaps the most difficult, most error-prone and most communication intensive software development. It can be successful only through an effective customer-developer partnership. It is needed to know what the users really need. Note: The success of an elicitation technique used depends on the maturity of the analyst, developers, users and the customer involved. 8/31/2019 REQUIREMENT ANALYSIS AND SPECIFICATION IN SOFTWARE ENGINEERING - UNIT 1 - BY RAM K PALIWAL 9
- 10. Requirement Elicitation Techniques Requirement Elicitation methods 1. Interviews 2. Brainstorming Sessions 3. Form Analysis/ Interface Analysis etc… 8/31/2019 REQUIREMENT ANALYSIS AND SPECIFICATION IN SOFTWARE ENGINEERING - UNIT 1 - BY RAM K PALIWAL 10
- 11. Requirement Elicitation Techniques 1. Interviews: Objective of conducting an interview is to understand the customer’s expectations from the software. It is impossible to interview every stakeholder hence representatives from groups are selected based on their expertise and credibility. ◦ Interviews 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. Sometimes a proper questionnaire is designed for the interview. 8/31/2019 REQUIREMENT ANALYSIS AND SPECIFICATION IN SOFTWARE ENGINEERING - UNIT 1 - BY RAM K PALIWAL 11
- 12. Requirement Elicitation Techniques 2. 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. ◦ Every idea is documented so that everyone can see it. ◦ Finally a document is prepared which consists of the list of requirements and their priority if possible. 8/31/2019 REQUIREMENT ANALYSIS AND SPECIFICATION IN SOFTWARE ENGINEERING - UNIT 1 - BY RAM K PALIWAL 12
- 13. Requirement Elicitation Techniques 3. Form Analysis/Interface analysis ◦Interfaces for a software product can be human or machine. Integration with external systems and devices is just another interface. ◦User centric design approaches are very effective at making sure that we create usable software. ◦Interface analysis – reviewing the touch points with other external systems is important to make sure we don’t overlook requirements that aren’t immediately visible to users. 8/31/2019 REQUIREMENT ANALYSIS AND SPECIFICATION IN SOFTWARE ENGINEERING - UNIT 1 - BY RAM K PALIWAL 13
- 14. References: https://www.tutorialspoint.com/software_engineering/software_requirements.htm?source=po st_page--------------------------- 7th edition Software Engineering A Practitioners Approach by Roger S. Pressman https://www.tutorialspoint.com/business_analysis/business_analysis_requirement_gathering_t echniques https://www.geeksforgeeks.org/software-engineering-requirements-elicitation/ 8/31/2019 REQUIREMENT ANALYSIS AND SPECIFICATION IN SOFTWARE ENGINEERING - UNIT 1 - BY RAM K PALIWAL 14
Editor's Notes
- #5: When the client approaches the organization for getting the desired product developed, it comes up with rough idea about what all functions the software must perform and which all features are expected from the software. Referencing to this information, the analysts does a detailed study about whether the desired system and its functionality are feasible to develop. This feasibility study is focused towards goal of the organization. This study analyzes whether the software product can be practically materialized in terms of implementation, contribution of project to organization, cost constraints and as per values and objectives of the organization. It explores technical aspects of the project and product such as usability, maintainability, productivity and integration ability. The output of this phase should be a feasibility study report that should contain adequate comments and recommendations for management about whether or not the project should be undertaken.
- #8: The requirements received from client are written in natural language. It is the responsibility of system analyst to document the requirements in technical language so that they can be comprehended and useful by the software development team. SRS should come up with following features: 1. User Requirements are expressed in natural language. 2. Technical requirements are expressed in structured language, which is used inside the organization. 3. Design description should be written in Pseudo code. 4. Format of Forms and GUI screen prints. 5. Conditional and mathematical notations for DFDs etc.
- #9: After requirement specifications are developed, the requirements mentioned in this document are validated. User might ask for illegal, impractical solution or experts may interpret the requirements incorrectly. This results in huge increase in cost if not nipped in the bud.