The Future of Software Engineering

Slides:



Advertisements
Similar presentations
Chapter 6 HCI in the software process. Software engineering and the design process for interactive systems Usability engineering Iterative design and.
Advertisements

The design process IACT 403 IACT 931 CSCI 324 Human Computer Interface Lecturer:Gene Awyzio Room:3.117 Phone:
HCI in the software process Chapter 6
CS3773 Software Engineering Lecture 01 Introduction.
May 2, May 2, 2015May 2, 2015May 2, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University, Azusa, CA.
The European Qualifications Framework for lifelong learning (EQF)
CMMI – Continuous as well as staged model CMMI capability levels – Incomplete, performed, managed, defined, quantitatively managed, optimized Example.
1 Computer Systems & Architecture Lesson 1 1. The Architecture Business Cycle.
Lecturer: Dr. AJ Bieszczad Chapter Reviewing Wasserman’s recommendations Abstraction Analysis and design notations User interface prototyping Software.
MCA –Software Engineering Kantipur City College. Topics include  Formal Methods Concept  Formal Specification Language Test plan creation Test-case.
Understanding Educational Innovation Professional Practice Module Dr Sue Wharton.
The design process z Software engineering and the design process for interactive systems z Standards and guidelines as design rules z Usability engineering.
Architecture Business Cycle
1 Chapter 5 Practice: A Generic View Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman.
Software Models (Cont.) 9/22/2015ICS 413 – Software Engineering1 -Component-based software engineering -Formal Development Model.
Planning and Writing Your Documents Chapter 6. Start of the Project Start the project by knowing the software you will write about, but you should try.
Chapter 2 소프트웨어공학 Software Engineering 임현승 강원대학교
The Future of Software Engineering 中国科学技术大学软件学院 孟宁 2010 年 12 月.
HCI in Software Process Material from Authors of Human Computer Interaction Alan Dix, et al.
1 5.1 Software Engineering Practice  Provide value to the user  KIS—keep it simple!  Maintain the product and project “vision”  What you produce,
1 Chapter 5 Software Engineering Practice. 2 What is “Practice”? Practice is a broad array of concepts, principles, methods, and tools that you must consider.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Coming up: Software Engineering: A Practitioner’s Approach, 6/e Chapter 5 Practice: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Delivering the System 中国科学技术大学软件学院 孟宁 2012 年 11 月.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
Methodology Matters: Doing Research in the Behavioral and Social Sciences ICS 205 Ha Nguyen Chad Ata.
Requirement Handling
Chapter 3: Software Project Management Metrics
Formal Specification and Analysis of Software Architectures Using the Chemical Abstract Machine Model CS 5381 Juan C. González Authors: Paola Inverardi.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 5 Practice: A Generic View Software Engineering: A Practitioner’s Approach, 6/e Chapter.
Ivar Jacobson, Grady Booch, and James Rumbaugh The Unified Software Development Process Addison Wesley, : James Rumbaugh's OOMD 1992: Ivar Jacobson's.
Chapter 22 Metrics for Process and Projects Software Engineering: A Practitioner’s Approach 6 th Edition Roger S. Pressman.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 9: Design Engineering Software Engineering: A Practitioner’s Approach, 6/e Chapter.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 1 Slide 1 Chapter 1 Introduction As modified by Randy Smith.
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
Development of Concepts for R&D Management R&D in an Individual Enterprise.
Stages of Research and Development
Chapter 33 Estimation for Software Projects
Innovation Management 2012 Stefan Wuyts
Chapter 7: Software Engineering
EI Architecture Overview/Current Assessment/Technical Architecture
Chapter 1- Introduction
Chapter 7: Software Engineering
Definition CASE tools are software systems that are intended to provide automated support for routine activities in the software process such as editing.
Presentation on Decision support system
Chapter 1- Introduction
Topic for Presentaion-2
The Systems Engineering Context
State of the art We still have problem using 3D – There are no standard of how to make the modelling, so we can’t benefit from each other. There are not.
Chapter 26 Testing Mobile Applications
Frequently asked questions about software engineering
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
HCI in the software process
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
Frequently asked questions about software engineering
HCI in the software process
For University Use Only
Chapter 33 Estimation for Software Projects
PPT1: Basics of software engineering
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Leadership Chapter 7 – Path-Goal Theory Northouse, 4th edition.
HCI in the software process
INFS 452 – Computer Ethics & Society
Human Computer Interaction Lecture 14 HCI in Software Process
Metrics for Process and Projects
Chapter # 7 Software Development
Professional Practice Framework for
ERP and Related Technologies
UML Design for an Automated Registration System
Presentation transcript:

The Future of Software Engineering 东华理工大学软件学院 李祥

Contents 14.1 How have we done? 14.2 Technology transfer 14.3 Decision making in software engineering 14.4 The professionalization of software engineering: licensing, certification and ethics

Chapter 14 Objectives The Wasserman principles and how we have done Technology transfer How researchers provide evidence for technology adoption Decision making in software engineering Next step in research and practice

14.1 How Have We Done? Use complex languages Use patterns and abstractions Apply formal methods Build a vast array of tools

14.1 How Have We Done? Challenges Ahead Provide great accuracy in the large: we can tell when a space vehicle will reach Mars when a chemical reaction will reach a critical stage Do not have accuracy in small: we cannot tell precisely when a software product will fail again exactly how a user will exercise system’s function

14.1 How Have We Done? Wasserman’s Steps to Maturity Abstraction Analysis and design notations User interface prototyping Software architecture Software process Reuse Measurement Tools and integrated environments

14.1 How Have We Done? What Now? Should consider how well we move the new software engineering ideas into practice Must consider how well our research and practice support decision making about processes, resources, and products

14.2 Technology Transfer Producers: create and use new technologies Consumers: adopt and use new technologies in new products and services

14.2 Technology Transfer How We Make Technology Transfer Decision Now In the 1960s and 1970s, it took an average of 7.5 years for new technology to become widely available Because of time-to-market pressure, new technologies must prove themselves quickly

14.2 Technology Transfer Adopter Types Innovators Early adopters Early majority Late majority Laggards

14.2 Technology Transfer Evidence Supporting Technology Decisions Researchers: reproducible validation methods theoretical proof, static analysis, and simulation Practitioners: methods relevant to their environment case studies, field studies, and replicated controlled experiments

14.2 Technology Transfer Types of Evidence and Their Audiences What will you do for your new technology?

14.3 Decision-Making in Software Engineering Two points of view of decision-making Descriptive描述性的: provides evidence about how decisions are actually made Prescriptive说明性的: provides frameworks and methods to help decision-makers

14.3 Decision-Making in Software Engineering Roots of Decision Science

14.3 Decision-Making in Software Engineering Elements that Affect How We Make Decision

14.3 Decision-Making in Software Engineering Issues in Group Decision-Making

14.3 Decision-Making in Software Engineering Types of Decision Strategic decision: affects the well being and nature of the organization Tactical decision: affects pricing, employee assignment, customer interaction, or operations Routine decision: repetitive in nature, local in scope, and guided by organizational rules or policies

14.3 Decision-Making in Software Engineering How We Really Decide Bias Caused by Decision Context 背景偏见 stereotype threat 刻板印象威胁 status quo bias现状偏见 Individuals exhibit a marked preference for case-specific,or singular information个体对特定情况和单一信息由明显偏好 一个因素出现的越久远,回忆者降低其重要性的倾向就越高 Anchoring-and-adjustment锚定和调整 不愿表现的消极

14.3 Decision-Making in Software Engineering Example Used in Assessing Group Effects Condition Error rate Subject is alone 1% With one person who says A 3% With two people who say A 13% With three people who say A 33% With six who say A and one who say B 6%

Improve software engineering education 14.4 The Professionalization of Software Engineering: Licensing, Certification and Ethics Improve software engineering education Licensing or certification to improve process and product

谢谢大家! References 软件工程 - 理论与实践(第四版 影印版) Software Engineering: Theory and Practice (Fourth Edition),Shari Lawrence Pfleeger,Joanne M. Atlee ,高等教育出版社 软件工程 - 理论与实践(第四版) Software Engineering: Theory and Practice (Fourth Edition),Shari Lawrence Pfleeger,Joanne M. Atlee,杨卫东译,人民邮电出版社 软件工程—实践者的研究方法(Software Engineering-A Practitioner’s Approach); (美) Roger S. Pressman 著; 机械工业出版社ISBN:7-111-07282-0 http://code.google.com/p/advancedsoftwareengineering/