目录

  • 1 Unit 1  Starting a Software Project
    • 1.1 Part1  Listening & Speaking
    • 1.2 Part 2  Reading and Translating
    • 1.3 Part 3  Simulated Writing: Memo
  • 2 Unit 2  Capturing the Requirements
    • 2.1 Part1 Listening & Speaking
    • 2.2 Part 2 Reading and Translating
    • 2.3 Part 3 Simulated Writing
  • 3 Unit 3 Planning the Project
    • 3.1 Part 1 Listening & Speaking
    • 3.2 Part 2 Reading and Translating
    • 3.3 Part 3 Simulated Writing
  • 4 Unit 4 Working in a Team
    • 4.1 Part1 Listening & Speaking
    • 4.2 Part 2 Reading and Translating
    • 4.3 Part 3 Simulated Writing: PowerPoint Presentation
  • 5 Unit 5  Designing the System
    • 5.1 Part1 Listening & Speaking
    • 5.2 Part 2 Reading and Translating
    • 5.3 Part 3 Simulated Writing: Software Design Specification
  • 6 Implementing the System
    • 6.1 Part1 Listening & Speaking
    • 6.2 Part 2 Reading and Translating
    • 6.3 Simulated Writing: Progress Report
  • 7 Testing the System
    • 7.1 Part1 Listening & Speaking
    • 7.2 Part 2 Reading and Translating
    • 7.3 Part 3 Simulated Writing: Software Test Specification
  • 8 Delivering the System
    • 8.1 Part1 Listening & Speaking
    • 8.2 Part 2 Reading and Translating
    • 8.3 Part 3 Simulated Writing: User Guide
Part 1 Listening & Speaking

第三单元  项目计划         用时:4学时

了解软件项目计划的基本概念、作用和主要目标;

了解项目计划的主要活动和主要方法;

了解软件项目中需要管理的变量要素及其之间的相互作用;

了解大数据的基本概念以及其应用;

掌握软件项目计划文档的写作方法




Dialogue:SoftwareProject Planning



Exercises: Work in pairs, and make up a similar conversation by replacing the statements with other expressions on the right side. 

[1]Indeed, planning for testing should start with the early stages of there quirement process, and test plans and procedures must be syste matically and continuously developed, and possibly refined, as development proceeds.

Replace with: 

Software design is an indispensable process which has a significant impact on the next processes in the entire development.

[2] Then, we must assign some management responsibilities to everyone.

Replace with:

1.database management

2.configuration management

3.risk management


Listening Comprehension: Software Project Planning

Listen to the article and the following 3 questions based on it. After you hear a question, there will be a break of 10 seconds. During the break, you will decide which one is the best answer amongthe four choices marked (A), (B), (C) and (D).



Questions:

1. How many kinds of planning philosophies are mentioned in the article?

(A)    Two

(B)   Three

(C)    Four

(D)   Five

2. How many questions are stated in  Boehm’s  principle for leading project planning?

(A)    Three

(B)    Five

(C)   Six

(D)   Seven

3. Which point of view is the most accordant  with the idea of this article on the project planning?

(A)   Planning every activities in the  projectas detailed as possible for their foreseeable ability

(B)   Carrying out as early as possible regardless of planning,because even the best planning can be obviated by uncontrolled change as the work proceeds.

(C)   Adjusting different levelof details for activities according to their different locations in the project timeline.

(D)   Making aperfectplan which can evade changes that may come about during thework.


Dictation:FourVariables in Projects

This article will be played three times.Listen carefully, and fill in the blanks with the words you have heard.





A project  is  a carefully  defined  setof         1   that  use resources to achieve        2        goals and objectives.  It is a      3        endeavor  having specific start and  completion dates as well as a  managed        4      having   range of         5      ,  budget  and   organizational  constraints.

It iusually considered that  there are four    6     variableswewill        7         in software projectscost,  time, scope,  and quality. These  four variables  affect  a  project together  by    8    with  each other:  increased  scope  typically  means  more time and    9    ,a   tight  time   stress  could  mean  stronger  finance  support and suffered               10         , too little money   couldn't  solve   the  customer's  business  problem       11        the scope, and a higher quality  might  deliver  longer developing     12            and  more  cost.

It seems that there is not a simple relationship between them. For example, you can't just get software  faster  by spending  more money. As the     13     goes,  “Nine  women cannot  make         14         in             one  month.”

In his book Extreme Programming Explained: Embrace Change, Kent Beck  says  that  the solution  ito  make  the four variables    15        .  If  everyone-programmers,customers,

and managerscanseeall   four  variables,  they can consciously        16      which  variables to control.  If   they   don't    like  the  result        17       for fourth  variable,  they   can   change theI8          ,  or they can     19          a different  three variables to  controlf or           20       ultimately  the project  objectives.