Software Engineering I

1
Software Engineering I

• Shyh-Kang Jeng
• Department of Electrical Engineering/
• Graduate Institute of Communication Engineering
• National Taiwan University

2
Additional Reading

• S. R. Schach, Classical and Object-Oriented
  Software Engineering, 4th edition, McGraw-Hill,
  1999.
• Sommerville, Software Engineering, 6th ed.,
  Addison-Wesley, 2000.

3
Software Engineering

• Development of large software system as an
  engineering process
• The problems are no more than enlarged versions
  of those faced when writing small programs
• Includes topics related to business management,
  such as personnel and project management

4
Software Engineering vs. Other Engineering Fields

• Building blocks
• Role of tolerances
• Metrics

5
Software Life Cycle
Development
Use
Modification
6
Development Phase
7
Development Models

• Waterfall
• Incremental
• Prototyping

8
Computer-Aided Software Engineering (CASE)

• Application of computer technology to the
  software development process itself
• Project planning tools
• Project management tools
• Documentation tools
• Prototyping and simulation tools
• Interface design tools
• Programming tools (e.g. code generator)

9
Structure Chart
10
Class Diagram
1
1
Player Record
Room
Is Currently In
11
Data Coupling
level
level
level
level
points
points
points
12
Collaboration Diagram
1. Pose problem
1
1
Player Record
Room
Is Currently In
2. Adjust score
13
Cohesion

• Logical cohesion
• Functional cohesion

14
OOP Cohesion
Room object
Display image
Pose problem
Evaluate response
15
Top-Down vs. Bottom-Up

• Top-down
• Hierarchical system
• Compatible with imperative paradigm
• Bottom-up
• Gained support recently
• Good for non-hierarchical systems
• More consistent with the building from off-shelf
  components concept

16
Dataflow Diagram
17
Entity-Relationship Diagram
Professor
Class
Teaches
Attends
Student
18
Data Dictionary

• Central depository of information about the data
  items appearing throughout the system
• Information
• Identifiers
• Valid entries
• Storage
• References

19
CRC Cards
Class Name WithdrawManager
Collaborators
Responsibilities Ask user for amount to
withdraw Verify amount with
AccountManager Tell CashDispenser to release
cash
AccountManager CashDispenser
20
Design Patterns

• Consists the statement of the problem
• Followed by a proposed solution
• The problems are intended to be universal
• The solutions are generic

21
Presentation of Data
22
Publisher-Subscriber Pattern
Subscriber
Subscriber
Publisher
Subscriber
Subscriber
Subscriber
23
Component-Container Pattern
Component
Container
Component
Container
Component
Container