Software Engineering: Understanding the Requirements Engineering and Analysis Gap - Prof. , Study notes of Computer Science

Download Software Engineering: Understanding the Requirements Engineering and Analysis Gap - Prof. and more Study notes Computer Science in PDF only on Docsity! Lecture 2: The Requirements/Design Gap Kenneth M. Anderson Object-Oriented Analysis and Design CSCI 6448 - Spring Semester, 2001 January 18, 2000 ' Kenn eth M. Anderson, 2001 2 Goals for this Lecture • Review definition of software engineering • Discuss requirements engineering • Discuss requirements analysis • Discuss requirements/design gap January 18, 2000 ' Kenn eth M. Anderson, 2001 3 What is “Software Engineering” • Software – Computer programs and their related artifacts • Engineering – The application of scientific principles in the context of practical constraints January 18, 2000 ' Kenn eth M. Anderson, 2001 4 A Definition (Daniel M. Berry) • Software engineering is that form of engineering that applies: – a systematic, disciplined, quantifiable approach, – the principles of computer science, design, engineering, management, mathematics, psychology, sociology, and other disciplines, • to creating, developing, operating, and maintaining cost-effective, reliably correct, high- quality solutions to software problems. January 18, 2000 ' Kenn eth M. Anderson, 2001 5 Engineers Build Machines • Software is intangible – Descriptions of a desired machine, written according to specific languages and notations • Computer is tangible – General-purpose description executor – Behaves as if it were the desired machine • Software engineers “build” descriptions – Organizing, structuring, and making complex assemblages of descriptions – Raw materials: languages and notations January 18, 2000 ' Kenn eth M. Anderson, 2001 6 Basic Software Engineering Activities • Create – Modeling • Record – Specification • Analyze – Verification & Validation • Configure – Selection, Translation, & Deployment January 18, 2000 ' Kenn eth M. Anderson, 2001 7 IEEE definition of requirement • A condition or capacity needed by a user to solve a problem or achieve an objective • A condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification or other formally imposed documents • A documented representation of a condition or capability as in 1 or 2 January 18, 2000 ' Kenn eth M. Anderson, 2001 8 Requirements Engineering • “The systematic process of developing requirements through an iterative cooperative process of analyzing the problem, documenting the resulting observations in a variety of representation formats, and checking the accuracy of the understanding gained.” – K. Pohl, 1993