Chapter 7 Software Engineering Pdf Software Development Process Chapter 7 software engineering, study guides, projects, research for software engineering. Software engineering chapter 7 free download as pdf file (.pdf), text file (.txt) or view presentation slides online. software engineering chapter 7.
Software Engineering Docsity This document discusses requirements engineering processes and activities. it describes the key activities in requirements engineering as requirements elicitation, analysis, validation, and management. This chapter discusses the essential principles and concepts of software design, emphasizing its role in software engineering. Software engineering software engineering concerns the overall process of software development and maintenance. n large software systems cost many man year’s efforts beyond the short term memory capability of the human mind. n the time span may exceed one’s lifetime to work on the whole system alone. n likewise, the increased complexity of. • incremental model – a simplified version of the final product, and then more features added in an incremental manner – prototyping (evolutionary vs. throwaway): build and evaluate prototypes (incomplete versions of the proposed system) copyright © 2012 pearson education, inc. publishing as pearson addison wesley 7 14 software engineering methodologies (cont.) • open source development (e.g., the linux operating system) – a single author writes an initial version and posts the source code and documentation on the internet – modified or enhanced by others – report these changed to the original author – further modifications • extreme programming (by kent beck in 1996) – developed incrementally by means of repeated daily cycles – characterized by flexibility compared with “waterfall” copyright © 2012 pearson education, inc. publishing as pearson addison wesley 7 15 modularity • modularity: the division of software into manageable units called modules • procedures imperative paradigm – structure charts • objects object oriented paradigm – collaboration diagrams • components component architecture copyright © 2012 pearson education, inc. publishing as pearson addison wesley 7 16 figure 7.3 a simple structure chart • imperative paradigm: begin by considering the actions that must take place • structure chart: procedures and procedure dependencies copyright © 2012 pearson education, inc. publishing as pearson addison wesley 7 17 figure 7.4 the structure of playerclass and its instances • there are two players that we should represent by two objects • the judge object, the score object copyright © 2012 pearson education, inc. publishing as pearson addison wesley 7 18 figure 7.5 a simple collaboration diagram copyright © 2012 pearson education, inc. publishing as pearson addison wesley 7 19 coupling • inter module coupling: the linkage between modules • goal: to maximize independence among modules or minimize the linkage between modules • control coupling: when a module passes control of execution to another • data coupling: sharing of data between modules – in the form of parameters – in the form of global data copyright © 2012 pearson education, inc. publishing as pearson addison wesley 7 20 figure 7.6 a structure chart including data coupling copyright © 2012 pearson education, inc. publishing as pearson addison wesley 7 21 cohesion • cohesion: the degree of relatedness of a module’s internal parts • goal: high intramodule cohesion • logical cohesion – the internal elements of a module perform activities logically similar • functional cohesion – all the parts of the module are focused on the performance of a single activity.
Software Engineering Docsity Software engineering software engineering concerns the overall process of software development and maintenance. n large software systems cost many man year’s efforts beyond the short term memory capability of the human mind. n the time span may exceed one’s lifetime to work on the whole system alone. n likewise, the increased complexity of. • incremental model – a simplified version of the final product, and then more features added in an incremental manner – prototyping (evolutionary vs. throwaway): build and evaluate prototypes (incomplete versions of the proposed system) copyright © 2012 pearson education, inc. publishing as pearson addison wesley 7 14 software engineering methodologies (cont.) • open source development (e.g., the linux operating system) – a single author writes an initial version and posts the source code and documentation on the internet – modified or enhanced by others – report these changed to the original author – further modifications • extreme programming (by kent beck in 1996) – developed incrementally by means of repeated daily cycles – characterized by flexibility compared with “waterfall” copyright © 2012 pearson education, inc. publishing as pearson addison wesley 7 15 modularity • modularity: the division of software into manageable units called modules • procedures imperative paradigm – structure charts • objects object oriented paradigm – collaboration diagrams • components component architecture copyright © 2012 pearson education, inc. publishing as pearson addison wesley 7 16 figure 7.3 a simple structure chart • imperative paradigm: begin by considering the actions that must take place • structure chart: procedures and procedure dependencies copyright © 2012 pearson education, inc. publishing as pearson addison wesley 7 17 figure 7.4 the structure of playerclass and its instances • there are two players that we should represent by two objects • the judge object, the score object copyright © 2012 pearson education, inc. publishing as pearson addison wesley 7 18 figure 7.5 a simple collaboration diagram copyright © 2012 pearson education, inc. publishing as pearson addison wesley 7 19 coupling • inter module coupling: the linkage between modules • goal: to maximize independence among modules or minimize the linkage between modules • control coupling: when a module passes control of execution to another • data coupling: sharing of data between modules – in the form of parameters – in the form of global data copyright © 2012 pearson education, inc. publishing as pearson addison wesley 7 20 figure 7.6 a structure chart including data coupling copyright © 2012 pearson education, inc. publishing as pearson addison wesley 7 21 cohesion • cohesion: the degree of relatedness of a module’s internal parts • goal: high intramodule cohesion • logical cohesion – the internal elements of a module perform activities logically similar • functional cohesion – all the parts of the module are focused on the performance of a single activity. This textbook is designed for undergraduate software engineering courses. additionally, it can be used by junior developers looking to consolidate their knowledge in the field. The requirements engineering process includes a feasibility study, requirements elicitation and analysis, requirements specification and requirements management. Download exercises software engineering: introduction to computing chapter 7 | alagappa university | a beginner level guide to computer science students. Software design is a creative activity in which you identify software components and their relationships, based on a customer’s requirements. implementation is the process of realizing the design as a program. sometimes there is a separate design stage, and this design is modeled and documented.
Chapter 7 Part 1 Pdf Software Testing Software This textbook is designed for undergraduate software engineering courses. additionally, it can be used by junior developers looking to consolidate their knowledge in the field. The requirements engineering process includes a feasibility study, requirements elicitation and analysis, requirements specification and requirements management. Download exercises software engineering: introduction to computing chapter 7 | alagappa university | a beginner level guide to computer science students. Software design is a creative activity in which you identify software components and their relationships, based on a customer’s requirements. implementation is the process of realizing the design as a program. sometimes there is a separate design stage, and this design is modeled and documented.
Comments are closed.