软件工程复习
![软件工程复习_第1页](https://file7.zhuangpeitu.com/fileroot7/2023-10/28/ae3a4b37-d279-4b70-948a-f916d17d445d/ae3a4b37-d279-4b70-948a-f916d17d445d1.gif)
![软件工程复习_第2页](/images/s.gif)
![软件工程复习_第3页](/images/s.gif)
《软件工程复习》由会员分享,可在线阅读,更多相关《软件工程复习(24页珍藏版)》请在装配图网上搜索。
1、,单击此处编辑母版标题样式,单击此处编辑母版文本样式,第二级,第三级,第四级,第五级,*,*,Software Engineering Review,2021 Autumn,1,Why Software Engineering?,What is software engineering?,Solving problems,Where does the software engineer fit in?,How successful have we have?,What is good software?,The quality of the product,The quality of the
2、 process,CMM,ISO 9000,SPICE,Quality in the context of the business environment,ROI(return on investment),2,Why Software Engineering?,Who does software engineering?,Customer,user,and developer,A system approach,What is a system?,The elements of a system,Relationships and the system boundary,An engine
3、ering approach,Building a system,Members of the development team,The roles of the development team,3,Modeling the Process and Life Cycle,The meaning of process,What is a process,a life cycle,and a software life cycle?,Understanding the concept of a process,Software process models,The reasons to mode
4、l the process,Several typical software process models description,the model,advantages and disadvantages,examples,Waterfall model,V model,Prototyping model,Phased development:increments and iterations,Spiral model,Agile methods,4,Planning and Managing the Project,Tracking progress,What is a project
5、schedule,an activity,and a milestone,Work breakdown and activity graphs,4 parameters to describe an activity:precursor,duration,due date,and endpoint,Activity graph,Estimating completion,CPM(Critical Path Method),(*),Slack time for an activity,Tools to track progress,Gantt chart,5,Planning and Manag
6、ing the Project,Project personnel,Staff roles and characteristics,Work styles,Project organization,Depend on three factors,Chief programmer team,Egoless approach,Effort estimation,Can not produce accurate estimates,Risk management activities,What is a risk?,Steps in risk management,Hoe to reduce ris
7、k?,The project plan,6,Capturing the Requirements,The requirements process,What is a requirement?,Requirements elicitation,Who are stakeholders?,The means of eliciting requirements,Types of requirement,Functional requirements,Quality requirements/nonfunctional requirements,Design constraint,Process c
8、onstraint -the above are 4 types of requirements,Resolving conflicts priority,Two kinds of requirements documents,Requirements definition,Requirements specification,7,Capturing the Requirements,Characteristics of requirements,Correct,Consistent,Unambiguous,Complete,Feasible,Relevant,Testable,traceab
9、le,8,Capturing the Requirements,Modeling notations,Entity-relationship diagrams,Definition,Three elements,Properties/application,UML class diagrams,Event traces,Definition,Properties/application,UML sequence diagrams,State machines,Definition,Two elements,Properties/application,UML statechart diagra
10、ms,9,Capturing the Requirements,Modeling notations,Data-flow diagrams(DFD),Definition,Four elements,Properties/application,UML use case diagrams,Functions and relations,Decision table,(*),How to build a decision table?,10,Capturing the Requirements,Prototyping requirements,Rapid prototyping,Throwawa
11、y prototyping,Evolutionary prototyping,Prototyping vs.modeling,Requirements documentation,Requirements definition,Requirements specification,11,Designing the System,What is a design?,Conceptual design/system design,Technical design,Decomposition and modularity,High level lower level,Modular decompos
12、ition,Data-oriented decomposition,Event-oriented decomposition,Outside-in design,Object-oriented design,Modules/components,12,Designing the System,Architectural styles and strategies,Three design levels:architecture,code design,and executable design,Architectural styles description,properties,and ex
13、amples,Pipes and filters,Object-oriented design,Layering,Repositories,Interpreters,C/S,B/S,Issues in design creation,Modularity and levels of abstraction,Collaborative design,Concurrency,13,Designing the System,Characteristics of good design,Component independence,Why component independence?,Couplin
14、g uncoupled,data coupling,stamp coupling,control coupling,common coupling,and content coupling,Cohesion coincidental,logical,temporal,procedural,communicational,sequential,functional,Exception identification and handling,Typical exceptions,Handling strategies,Fault prevention and fault tolerance,14,
15、Testing the Programs,Software faults and failures,Types of faults,Testing issues,Test opinions,Test organization -testing steps,Module testing,component testing,or unit testing,Integration testing,System testing function test,performance test,acceptance test,and installation test,Testing techniques,
16、Black box,White box,15,Testing the Programs,Unit testing,Examining the code,Code walkthroughs,Code inspections,Success of the code reviews,Test thoroughness,Logic flow,(*),Integration testing,Bottom-up integration,Top-down integration,Big-bang integration,Sandwich integration,Comparison of the strategies,16,Testing the System,Principles of system testing,Sources of software faults,System testing process,Configuration management,Versions and releases,Regression testing,Deltas,separate files,and c
- 温馨提示:
1: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。图纸软件为CAD,CAXA,PROE,UG,SolidWorks等.压缩文件请下载最新的WinRAR软件解压。
2: 本站的文档不包含任何第三方提供的附件图纸等,如果需要附件,请联系上传者。文件的所有权益归上传用户所有。
3.本站RAR压缩包中若带图纸,网页内容里面会有图纸预览,若没有图纸预览就没有图纸。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 装配图网仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对用户上传分享的文档内容本身不做任何修改或编辑,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。