目录

  • 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
Part1 Listening & Speaking

第五单元   系统设计          用时:4学时

了解软件系统设计的基本概念、作用和主要目标;

了解软件设计阶段的主要活动和主要方法;

了解用户体验和用户界面设计的重要性;

了解社交网络的基本概念以及其应用;

掌握软件设计规格明书的写作方法


Dialogue:Software Design



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

[1] We will move from a “big picture” view of the software to a more narrow view that defines the details required to implement this system

Replace with: We peform the software design form a high level to more detailed levels step by step.

[2] we must be certain that each subsystem is functionally cohesive, and design subsystem interfaces first, and then allocate analysis classes or functions to each subsystem

Replace with: 

1. We must ensure that….

2. We must make sure that….


Listening Comprehension: Software Design

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



Questions:

1. Which description is not correctabout the design process?

(A)  The design process moves from a macro-view of software to a more microcosmic view.

(B)  Through  the  design  process, requirements  are translated into a ”blueprint"for construction.

(C)  The design process is represented from a high level of abstraction to lower levels step by step.

(D)   It  is reasonable  for the design process to create a  model of software with all  details directly.

2. How many different elements areencompassed in the design model according to this article?

(A)  Two

(B)  Three

(C)  Four

(D)  Five

3. Which statement is not correctabout the design concepts?

(A)  Design  concepts have been developing over  the first half-century of software engineering work

(B)  The  design  concepts  used  in different  projects  may  be inconsistent  because of  the  different  software  engineering  process  that  is chosen.

(C)  The design  methodapplied in the projects may  be different  in terms of the different software  engineering process  that is chosen.

(D)  Design concepts have evolved along  with  software    engineering.



Dictation:User Interface Design

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




When the concept of the interface first began to emerge, it was commonly understood as the hardware and software through which a human and a computer could communicate. So User Interface Design is also known as          I                  Interaction or HCI. As it has evolved, the concept has come to include the cognitive and emotional  aspects  of the user's      2             as well.

Many  technological  innovations        3             upon User Interface Design to elevate their  technical complexity to a          4                     product. Technology  alone may not  win  user  5                    

and  subsequent         6       . The User Experience, or how  the  user  experiences  the end  product, is the key to acceptance. And that is where User Interface Design enters thedesign                   7         . While product engineers     8                on  thetechnology,usability                     9            focus on the U1.  For greatest  efficiency   and cost  effectiveness,  this working       10                          should be maintained  from the start of a project to itsrollout.

UI affects the feelings, the emotions, and the mood of your users. If the UI is wrong and the user feels like they can't      11        your software,  they  literally  will  be angry and      12                          it

on your software.          13            , if  the UI  is  smart  and  things  work  the way the user expected    them to work, they  will  be cheerful as they manage to      14     small goals. Thus, the cardinal axiom of  all user interface design  is  that, a  UIis       15    when  the  program                 16         

exactly  how the  user  thought it would.

To  make  user  happy, you            have to         17        them in control of their environment. To do this, you  need to correctly interpret their actions. Additionally, you should  reduce  the  user's memory   18              and make the interface            19          . Those  three  points  above are considered    as

      20     and actually form the basis  for  a set of  user interface design  principles that guide

this important software design action.