1 / 9

Illinois Institute of Technology

Illinois Institute of Technology. CS487 Software Engineering Midterm Review David Lash. What it covers . ~2 hours long A mixture of concepts and problem solving Covers material from the beginning of the course through this 7/3/01. What it covers . 1. What is SE Softw Lifecycle models

noreen
Download Presentation

Illinois Institute of Technology

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Illinois Institute of Technology CS487 Software Engineering Midterm Review David Lash

  2. What it covers • ~2 hours long • A mixture of concepts and problem solving • Covers material from the beginning of the course through this 7/3/01

  3. What it covers • 1. What is SE Softw Lifecycle models • Various models (waterfall, prototype, incremental, sprial evolutionary concurrent) • What are the advantages of … • What are the weaknesses … • Which model would you use if ... • 2. Requirements -> Requirements process, FAST, QFD, partitioning, • What is QFD? What is FAST

  4. What it covers • 3. Requirements II - several modeling techniques, use case, system context diagrams, Partitioning • Data Modeling - Entity-Relation - Data objects and their relationships • Information flow diagram - Data flow diagrams - how data transforms in system- how functions transform data • Control Specifications - State diagrams - how system behaves as result of external events . • Test example list HW

  5. What it covers • Consider the problem of designing the software system for an automatic teller machine (ATM). • The user puts his or her card into a slot, enters a four-digit PIN (personal identification number), and can then perform the following operations on different bank accounts: d • deposit any amount, • withdraw funds (the account may not be overdrawn), • determine account balance, or • transfer funds between two accounts. • Design the ATM system using a transaction-oriented analysis. Draw a data flow diagram (Level-0 and Level-1). Note: in this question you do not have to specify (e.g., using pseudo-code) processes, data flows, external entities, stores and modules

  6. What it covers

  7. What it covers

  8. What it covers • 4. More Requirements - Decision tables, • Like HW • 5. Design concepts - abstraction, cntrl hierarchy, struct programming, info hiding, coupling, cohesion • What is the problem with content coupling. • Suppose Module X and module Y both access the same global structure, what type of coupling is it? • List all types of module cohesion. For each type of module cohesion provide its description and an example of a module exhibiting that kind of cohesion.

  9. What it covers • 6. Architectural concepts - various types of architecture, DF oriented design • For a DF diagram with a transform flow, translate into one with none. • (transform and transaction flow) • Go to structure Chart. • 7. Low level design concepts - pseudo code, Struct programming • What is SP, what programming constructs does it require? • 8. OO software concepts - • What is the difference between inheritance and polymophism?

More Related