《高级软件工程》学习资料(英文版)What about software

Problem Trends -e Why Hard? What about software Syllabus Too complex for complete analysis Separation into non-interacting subsystems distorts the results The most important properties are emergent Too organized for statistics Too much underlying structure that distorts the statistics Organized Complexity"(Weinberg) Copyright Nancy Leveson, Sept 1999
Problem Trends Why Hard? What about software? Slyllabus Too complex for complete analysis: Separation into non-interacting subsystems distorts the results. The most important properties are emergent. Too organized for statistics Too much underlying structure that distorts the statistics. "Organized Complexity" (Weinberg) Copyright c Nancy Leveson, Sept. 1999 �

Problem Trends Why Hard? Syllabus Large discrete state spaces Continuous vs discrete math acks repetitive structure found in computer circuitry Cannot test exhaustively Intangibility Invisible interfaces Hard to experiment with and manage Transient hardware faults vs. software errors Hard to diagnose problems Copyright ncy Leveson, Sept 1999
�� �� ������������������������ Problem Trends Why Hard? Slyllabus � Other Factors � � � � � � � � � � � � � � � � � � � � � � � �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� Large discrete state spaces Continuous vs. discrete math Lacks repetitive structure found in computer circuitry Cannot test exhaustively Intangibility � � Invisible interfaces Hard to experiment with and manage Transient hardware faults vs. software errors � � Hard to diagnose problems Copyright c Nancy Leveson, Sept. 1999 �

Problem Trends Why Hard? Syllabus And one more No historical usage information to allow measurement, evaluation and improvement of standard designs over time Always specially constructed Usually doing new things Copyright Nancy Leveson, Sept 1999
��������������������������� Problem Trends Why Hard? Slyllabus And One More � � � � � � � � � � � � � � � � � � � � � � � � � � � No historical usage information to allow measurement, evaluation, and improvement of standard designs over time. Always specially constructed. Usually doing new things. c Copyright Nancy Leveson, Sept. 1999 �

Problem Trends Why hard? Syllabus 1. Students will be able to evaluate software engineering techniques and approaches barefoot irreverance to their studies. They are here 2 It is important that students bring a certain ragamuffin not to worship what is known, but to question it. lacob Bronowski. The ascent of Man The developed theories .. have rarely been subjected to empirical testing and so their value remains unknown. They provide zealots with opportunities to market a rash of seminars the new technologies. When the theories are subjectto ing and courses and to flood the literature with papers advocating testing, what little evidence has been obtained sometimes suggests that the claimed benefits, in fact, may not exist. Vessey and weber Copyright ncy Leveson, Sept. 1999
������������������������������ ������������������������������ Problem Trends Why Hard? Slyllabus � Class Objectives � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 1. Students will be able to evaluate software engineering techniques and approaches. "It is important that students bring a certain ragamuffin barefoot irreverance to their studies. They are here not to worship what is known, but to question it." Jacob Bronowski, The Ascent of Man "The developed theories ...have rarely been subjected to empirical testing, and so their value remains unknown. They provide zealots with opportunities to market a rash of seminars and courses and to flood the literature with papers advocating the new technologies. When the theories are subjected to testing, what little evidence has been obtained sometimes suggests that the claimed benefits, in fact, may not exist. Vessey and Weber c Copyright Nancy Leveson, Sept. 1999 �

Proble Trends Why Ha Syllabus Class Objectives 2. Students will be able to exercise professional judgment in selecting an approach for a particular project based on an understanding of How the present state of software practice came about What was tried in the past What worked and what did not work Copyright Nancy Leveson, Sept 1999
������������������������������ Problem Trends Why Hard? Syllabus Class Objectives � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 2. Students will be able to exercise professional judgment in selecting an approach for a particular project based on an understanding of: How the present state of software practice came about What was tried in the past What worked and what did not work Why c Copyright Nancy Leveson, Sept. 1999 �

Problem Why Hard? abus ■ Required Background ■ Assignments No programming Reading summaries Main ideas or themes Critical evaluation Any additional thoughts Some additional short assignments Copyright Nancy Leveson, Sept 1999
� � �� �� Problem Trends Why Hard? Syllabus Required Background Assignments No programming Reading summaries: Main ideas or themes Critical evaluation Any additional thoughts Some additional short assignments c Copyright Nancy Leveson, Sept. 1999 �

Problem Trends Why Hard? Reading: Both classic papers and new ones I would like to see computer science teaching set deliberately in a historica/ framework .. The absence of this element in their training causes people to approach every problem from first principles. They are apt to propose solutions that have been found wanting in the past. Instead of standing on the shoulders of their precursors, they try to go it alone Maurice Wilkes cy Leveson, Sept. 1999
Problem Trends Why Hard? Syllabus Reading: Both classic papers and new ones I would like to see computer science teaching set deliberately in a historical framework.... The absence of this element in their training causes people to approach every problem from first principles. They are apt to propose solutions that have been found wanting in the past. Instead of standing on the shoulders of their precursors, they try to go it alone. Maurice Wilkes c Copyright Nancy Leveson, Sept. 1999 �
按次数下载不扣除下载券;
注册用户24小时内重复下载只扣除一次;
顺序:VIP每日次数-->可用次数-->下载券;
- 《高级软件工程》学习资料(英文版)Is there a problem.pdf
- 《数据库原理》SS2K3AccessMeth.ppt
- 《数据库原理》第10章 数据库管理.doc
- 《数据库原理》第9章 数据库设计.doc
- 《数据库原理》第8章 数据依赖和关系模式规范化.doc
- 《数据库原理》第7章 数据库安全及完整性约束.doc
- 《数据库原理》第6章 事务管理.doc
- 《数据库原理》第5章 查询处理与优化.doc
- 《数据库原理》第4章 数据库管理系统引论.doc
- 《数据库原理》第4章(图4).doc
- 《数据库原理》第4章(图3).doc
- 《数据库原理》第4章(图2).doc
- 《数据库原理》第4章(图1).doc
- 《数据库原理》第3章 关系数据库语言SQL.doc
- 《数据库原理》查询课程信息.doc
- 《数据库原理》学生选课信息查询.doc
- 《数据库原理》SS2K3AccessMeth.ppt
- 《数据库原理》第2章 数据模型.doc
- 《数据库原理》第1章 绪论.ppt
- 哈尔滨工业大学:《智能建筑网络通信技术》讲义.ppt
- 《高级软件工程》学习资料(英文版)sept14.pdf
- 《高级软件工程》学习资料(英文版)sept221.pdf
- 《高级软件工程》学习资料(英文版)sept222.pdf
- 《高级软件工程》学习资料(英文版)oct13.pdf
- 《高级软件工程》学习资料(英文版)oct6.pdf
- 《高级软件工程》学习资料(英文版)sept29.pdf
- 《高级软件工程》学习资料(英文版)reviews.pdf
- 《高级软件工程》学习资料(英文版)oct20.pdf
- 《高级软件工程》学习资料(英文版)cots Reuse.pdf
- 《高级软件工程》学习资料(英文版)metrics2.pdf
- 《高级软件工程》学习资料(英文版)metrics1.pdf
- 《高级软件工程》学习资料(英文版)Can programming language influence correctness?.pdf
- 《高级软件工程》学习资料(英文版)A Model of Team development.pdf
- 《高级软件工程》学习资料(英文版)types of Characteristics.pdf
- 《高级软件工程》学习资料(英文版)Programming Languages.pdf
- 《高级软件工程》学习资料(英文版)Software System Safety.pdf
- 《Microsoft Project 2002 教学手册》讲义.pdf
- 《计算机软件技术基础》ppt电子课件.ppt
- 陕西国防学院:《电子商务概论》序言.pps
- 陕西国防学院:《电子商务概论》第二章 网络技术基础.pps