VALLIAMMAI ENGINEERING COLLEGE S.R.M. Nagar, Kattankulathur DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING Sub Code: CP7007 Sub Name: SOFTWARE REQUIREMENTS ENGINEERING Branch / Year: ME CSE / I Year Staff in charge: Dr.M.Senthil Kumar 1. Define Requirement Engineering? QUESTION BANK UNIT- I -DOMAIN UNDERSTANDING PART - A 2. What are the different types of requirement? 3. State the difference between Functional and Non-functional requirements? 4. Define requirements specification? 5. Define elicitation? 6. What are the problems in Requirement analysis? 7. Define Ethnography? 8.Define Requirements checking? 9. Define Domain requirements? 10. What are the requirements validation techniques?
11. What is a test requirement? 12. Define Business modeling? 13. Define Use Case? 14. What is the use of Fish bone diagram? 15. Define User requirements? 16. Define Solution system Boundary? 17. Define UML activity diagram? 18. Differentiate Validation and verification? 19. What are the uses of Business Process modeling? 20. What is process mapping, Give its uses? PART-B 1.Explain in detail about Fish bone diagram with example? 2. Explain Business process modeling with the help of use cases and notations? 3. Discuss Requirements, design and there test cases in detail? 4. Explain verification and differentiate it with validation with example? 5. Describe about requirements engineering process and its types? 6. Explain Test case requirements by using example? 7. Structure Bank ATM use case diagram and explain it? 8. Explain UML Use case driven approach for requirements engineering? 9. Explain briefly test cases and procedures in requirements engineering? 10. Explain UML Activity diagram with an example in detail?
PART-C 1. Write a case study on the requirements engineering of the college automation software? 2. Do the Case study for the reason of more failures in the mathematics subject and draw the fishbone diagram with the cause and effects of the problem? 3. Do the Feasibility study for the automated traffic management and compare with the existing system? 4. Do the case study for finding the reason of downfall of self-financing engineering college in Tamilnadu and draw the IShakawa diagram for that.
1. What is stakeholder management? UNIT-II REQUIREMENTS ELICITATION PART-A 2. What are the building blocks in Stakeholder management? 3. Give some errors that might be in Questionnaires? 4. Write the elicitation techniques that followed in software requirements? 5. Give the types of Stakeholders? 6. What are the four phases followed in interviewing? 7. Define Brainstorming? 8. Define requirement elicitation? 9. What are the tools used to elicatate needs from clients? 10. What are tasks needed in stakeholder identification? 11. Define prototyping? 12. What are the advantages of prototyping? 13. What are the key components of an interview? 14. What is Goldsmith problem pyramid? 15. Give the basic rules for questionnaires? 16. Define Throwaway prototyping? 17. Define Evolutionary Prototyping? 18. What is the use of Nominal group technique in brainstorming? 19. What is Team idea mapping?
20. What is use of documenting stakeholder s needs? PART-B 1. Explain in detail about the Elicitation techniques and its advantages? 2.Explain, how the needs of stakeholders can be understood and documented in the library management system? 3. Briefly explain the difficulties involved in requirements elicitation and also suggest the solutions to overcome these difficulties? 4. Explain in detail about stakeholder expectations questionnaire with real time example? 5. Explain about interviews and questionnaires method in elicitation technique? 6. Explain about different types of stakeholders with suitable example? 7. Discuss about stakeholder analysis and their needs? 8. Explain about software Prototyping and its types in detail? 9. Briefly explain about documenting stakeholders needs in requirements process? 10. Explain about Workshop and brainstorming technique in elicitation process? PART-C 1. Do the Case study for elicitating requirements of automated health care system? 2. Explain the Scenario to be carried out, before the interview is conducted for getting the requirements from the stakeholders of the organization? 3. Do the Case study and prepare the questionnaire for elicitating needs for upgrading our college to university? 4. Do the Case study for brainstorming the students and teachers for the improvement of college learning system?
1. Define UML. 2. What are the Elements of a Use Case? UNIT-3 FUNCTIONAL REQUIREMENTS PART A 3. Differentiate include relationship and extend relationship. 5. What you meant by flow of controls. 6. Define Misuse case. 7. Write the System Description Document Template. 8. What are the questions to be answered before going for tool shopping? 9. What is National Widgets? 10. What are the types of Scenario in System development? 11. Draw the Order Processing Architecture. 12. Write the Flow of Events. 13. Define Alistair Cockburn Approach. 14. Define an Actor and give its types. 15. State Martin Fowler Approach. 16. What is Version Control? 17. Define Granularity and give its types. 18. What is SRS? 19. What is Control Hierarchy? 20. List out any four characteristics of good UML Diagram.
PART B 1. Explain Use Case based requirements with example? 2. Explain in detail about documenting use cases in Software Requirements engineering? 3. Explain about order processing system with the real time example? 4. Describe the features of Use cases and their scenarios? 5. Tabulate the SRS documents and explain in detail? 6. Draw the USE case diagram for Library management system 7. Explain the different types of Use cases in detail. 8. Explain the various applications of scenarios in system development? 9. Explain the Coleman s use case template in detail? 10. With help of USE Case diagram build Electricity Payment Systems. PART-C 1. Do the Case study for the Functional requirement of the smart phone needed by the college student. 2. Do the Case study of SRS document of the failure project and give the alternate solution to make the project as success. 3. Do the Case study for finding the impact of use case diagram in the success of the project. 4. Do the case study for the functional characteristics and non-functional characteristics of the student expected by the software company.
UNIT IV QUALITY ATTRIBUTES AND USER EXPERIENCE PART A 1. What are the benefits of CISCO Quality of Service? 2. Define QAW 3. List out the steps involved in QAW 4. What are the ways to specify UI design 5. Mention the important quality attributes for medical imaging system. 6. Name the common system quality attributes. 7. List out the quality attribute scenarios. 8. What are the elements of user experience design 9. Define process and product quality with example. 10. Define metrics and its types. 11. Give any four barriers in achieving quality. 12. What is Buildability. 13. What is usability and list out its factors? 14. What is Conceptual Integrity? 15. Define the term Availability. 16. What are the two types of Usability Requirements? 17. Define Quality? 18. What is the difference between Stimulus and Artifact? 19. What are the Barriers to Achieving Quality?
20. List some basic characteristics of The ISO/IEC 9126 Standard. PART B 1. Explain in detail about Quality attribute workshop (QAW). 2. Explain Quality of Service with real time example 3. Describe about Quality attributes in more detail. 4. Explain User Interface design in detail. 5. Briefly explain the quality attributes scenarios. 6. Explain the importance of Documenting quality attributes 7. Explain in details about elicitating and documenting usability requirements? 8. Explain the elements of User experience design attributes. 9. Explain the need of specifying UI design in the early phase of the project. 10. Explain the Usability requirements and its components in detail. PART-C 1. Do the Case study about the quality of the affiliated engineering college students and compare with the IIT students. 2. Do the Case study about the Quality Attribute Workshop conducting inside the software company. 3. Do the Case study about Usability requirements of the laptop required by the college student. 4. Do the Case study and create the User experience model for studying software courses in online.
1. What is Requirements Management? 2. List the Types of requirement. 3. Define software requirement metrics. 4. What is meant by managing changes? 5. Define Project Scope. 6. Define Product Scope. 7. Define Scope creep. 8. What is meant by Context Diagram? UNIT V MANAGING REQUIREMENTS PART A 9. List and explain two types of building blocks. 10. Write about Active and Passive external entities. 11. Define Cooperative and Autonomous. 12. Why is Requirements Management Important? 13. Write about Requirements Activities. 14. Define Investigation and Feasibility. 15. Define Traceability. 16. Define Product metric 17. Define the term Knot in a graph. 18. Give the Halstead s Product Metrics. 19. Why do Requirements change?
20. What are major steps of Requirements Management Process? PART B 1. Explain the Problem of project scope and scope prioritization techniques. 2. Explain in detail about context diagram and its alternatives. 3. a) Write a short notes on managing changes. b) Write a short note on Types of requirement. 4. Explain in detail about managing requirement. 5. Explain about software Requirements Properties. 6. Explain Traceability and its role in requirements engineering. 7. Explain generalized traceability model in detail. 8. Briefly explain the two factors affect the change in requirements. 9. Explain the attributes in SRS and their impact in the project. 10. Explain the Requirements Management tools in detail? PART-C 1. Do the Case study and find the solution to manage the change in requirements at the end of the development phase. 2. Do the Case study about traffic management in the city and draw the Context diagram. 3. Do the Case study to find the Quality metrics of the college which is helpful to the +2 student to choose the best college in the Counseling. 4. Do the Case study on traceability and explain the impact of it in the entire software development cycle.