软件架构实践01.ppt

课程内容的组织——每一章 概念介绍-1/3 案例分析-1/3 动手实践-1/3 装系统、工具（很多） 分析别人的代码（不少） 自己写代码 （不太多，但很关键） 课程目标检验 知道（你知道什么是“惯性”吗？） 领会（汽车转弯的时候身体倾斜是因为惯性作用） 应用（可以向反方向用力来抵消惯性） 实践课： 时间：16学时，实际可能远远不止 按照老师的“操作手册”上机 独立完成每个阶段的任务 得到开发结果，体验开发过程 软件： 老师提供部分软件（百度网盘上） 自己下载 自己编写 开发环境： 保存的问题（最好用自己的笔记本） 考试：笔试70%+平时成绩30% 笔试部分： 基本概念 基本方法 实践体会 平时成绩： 独立完成每次实践课的内容 平时作业、实验报告 上课提问 点名、签到 At level 1, the software process is an amorphous entity-a black box-and visibility into the project’s processes is limited. Since the staging of activities is poorly defined, managers have an extremely difficult time establishing the status of the project’s progress and activities. Requirements flow into the software process in an uncontrolled manner, and a product results. Software development is frequently viewed as black magic, especially by managers who are unfamiliar with software. At level 2, the customer requirements and work products are controlled, and basic project management practices have been established. These management controls allow visibility into the project on defined occasions. At level 3, the internal structure of the boxes, i.e., the tasks in the project’s defined software process, is visible. The internal structure represents the way the organization’s standard software process has been applied to specific projects, Both managers and engineers understand their roles and responsibilities within the process and how their activities interact at the appropriate level of detail. Individuals external to the project can obtain accurate and rapid status updates because defined processes afford great visibility onto project activities. At level 4, the defined software processes are instrumented and controlled quantitatively. Managers are able to measure progress and progress and problems. They have an objective, quantitative basis for making decisions. Their ability to predict outcomes grows steadily more precise as the variability in the process grows smaller. At level 5, new and improved ways of building the software