PPT-Software Requirements and Models

1 8312016 Topics covered Functional and nonfunctional requirements Requirements engineering processes Requirements elicitation Requirements specification Requirements validation Requirements change. Introduction. SRS is:. Requirements specification.  for a . software system. May . include a set of . use cases..  . Also . contains non-functional . requirements.. Topics. IEEE 830 format explored under 5 subtopics:. Machine Language (1. st. Gen). Assembly Language (2. nd. Gen). Third Generation Languages (FORTRAN, BASIC, Java, C++, etc.). CASE (4. th. Gen)?. IT System Complexity. Systems Analysis & Design. Recall Boehm’s paper. Why did they “invent” the waterfall model?. Distinction between programmer and user. Increased application, higher risks. Large systems: development is a group activity. Bring order to chaos:. Presented by. Vinay. . Gunnam. What is “Traceability” ?. The IEEE Standard Glossary of Software Engineering Terminology defines traceability as . “the degree to which a relationship can be established between two or more products of the development process, especially products having a predecessor-successor or master-subordinate relationship to one another.”. Lecture 5. André . van der . Hoek. Today’s Lecture. Requirements engineering. Requirements specification. Recurring, Fundamental Principles. Rigor and formality. Separation of concerns. Modularity. Lecture 1. 1. Chapter 2 Software Processes. Topics covered. Software process models. Process activities. Coping with change. The Rational Unified Process. An example of a modern software process. . 2. Understanding Requirements. Instructor Slides. Exercise Module Number: RM16. This course material was developed with NSF – TUES . a. ward # 1245036. Scenario. SoftRight. Inc., has outbid major competitors to build an Open Source Hospital Management System. This is a major software development project, totaling 3.5 million dollars in revenue, and it is the Product Manager’s (the leader of your team’s) first multi-million dollar project. She has handled many projects with lesser dollar amounts and feels that this project will not be that difficult. At the first brief meeting with the Director of Hospital Software Systems, the Product Manager is given a document consisting of a list of requirements. A sample of the given requirements are as follows:. 11. Review. Introduction to SDLC. Process Models. Waterfall. Evolutionary Development. Re-use Based Development. Generic Activities in ALL processes. Specification. Development. Validation. Evolution. Contract Cost Proposal Evaluation. . . October 18-20, 2016. Authors:. Wilson Rosa . Corinne Wallshein. Nicholas Lanham. Co-authors:. Barry Boehm, Ray Madachy, Brad Clark . Outline. Introduction. Stated and Implied Requirements. Instructor Slides. Exercise Module Number: RM13 . This course material was developed with NSF – TUES a. ward # 1245036. Task. Read the given stated need and suggest implied need(s).. Topics covered. Software processes and process models. Generic models:. Waterfall. i. ncremental development. Reuse-oriented software engineering. Basic process activities:. Specification. Development. LOS Testing. System Testing. Trends in Software Testing - 2018. Increasing Adoption of DevOps. More Utilization of Test Automation. Combining Manual and Automated Testing. Intelligent Test Automation and Analytics, Big Data Testing, Cloud Testing. 1. 8/31/2016. Topics covered. Functional and non-functional requirements. Requirements engineering processes. Requirements elicitation. Requirements . specification. Requirements validation. Requirements change. Software Requirements and Models 1 8/31/2016 Topics covered Functional and non-functional requirements Requirements engineering processes Requirements elicitation Requirements specification Requirements validation