1. Structured design - 1 © Minder Chen, 1997-2002 Produce Paycheck Retrieve Employee Record Global Data Store Offpage Calling Module Called Module System Device Module Module Name Normal Procedure (Subroutine) Call Module Name Library(Predefined) Module Global Data Store Used by Page-Jones Offpage Used by Page-Jones Sender Receiver Control Flag Data Structure Chart Notations

2. Structured design - 2 © Minder Chen, 1997-2002 A A,1A,2A,3 Call A,1 Call A,2 Call A,3 Sequence Structured Chart Notations A A,4A,3A,2A,1 Call A,1 IF Tx-Code = “A” Then Call A,2 ELSE IF Tx-Code = “B” Then Call A,3 ELSE IF Tx-Code =“C” THEN Call A,4 Decision A A,1A,2A,3A,4 Call A,1 Repeat Call A,2 Call A,3 Call A,4 Until EOF = “true” A A A,3 A,1 A,2 Statement X Statement T Statement Z Call A,1 Statement X Statement Y StatementZ Call A,3 Iteration Lexical Inclusion

3. Structured design - 3 © Minder Chen, 1997-2002 Structured Chart Notations (Contd.) Notations used by Page-Jones Decision Iteration Lexical Inclusion (The Hat Symbol)

4. Structured design - 4 © Minder Chen, 1997-2002 Structure Chart Notations Interface Table I/F# Input Output 1 A,B C 2 X Y,Z Interface Table 12 Asynchronous Activation of a Subtask Concurrent Activation Symbol Information Cluster A BC D Modules A, B, and C has exclusive access to Data D Program X Physical Packaging Boundary

5. Structured design - 5 © Minder Chen, 1997-2002 Answer to Problem 2 2.0 Enter Customer payments 2.5 Display Customer payment 2.32 Verify Customer account 2.21 Get Customer record 2.11 Key invoice remittance 2.4 write Customer payment transaction 2.3 Update A/R master 2.2 Add Customer information 2.1 Key remittance 2.33 Rewrite A/R record 2.22 Verify Customer account 2.31 Get receivable record 2.12 Key monthly statement remittance Structure chart for program 2.0. Enter customer payment Exercise - 3 Remittance EOT Customer-ID Invoice- remittance Monthly- Statement- remittance Customer- sold-to- name Remittance Customer-sold- to-name Customer- payment Customer -ID Customer- number Customer- record No-record- on-file Valid- account A/R- record Old- A/R- record New-A/R- record No-record- on-file Valid account Posting-ok

6. Structured design - 6 © Minder Chen, 1997-2002 How would you partition this system?

7. Structured design - 7 © Minder Chen, 1997-2002 Type of Coupling Tightness of Coupling Goodness of Design Normal Coupling Data Coupling Stamp Coupling Control Coupling Common Coupling Content Coupling Loose Tight Good Bad

8. Structured design - 8 © Minder Chen, 1997-2002 Normal Coupling A. Call B. A. Call B using X,Y. BB Module A and module B are normally coupled if - A calls B - B returns to A All information passed between them are through parameter passing X X Y Y

9. Structured design - 9 © Minder Chen, 1997-2002 UPDATE CUSTOMER MASTER FILE GET VALID INPUT VALIDATE CUSTOMER TRANSACTION UPDATE MASTER PUT CUSTOMER MASTER GET INPUT GET CUSTOMER MASTER GET CUSTOMER TRANS Transaction Transaction is valid Transaction Master Record Acct Number Master Record Updated Master Record Master Record Valid Trans- action Updated Master Record Valid Trans- action

10. Structured design - 10 © Minder Chen, 1997-2002 Data Coupling Calculate Monthly payment of a House Calculate Mortgage Payment Mortgage PaymentLoan Amount Term Interest Rate Module A and module B are data coupled if - A calls B - B returns to A - All information passed between them are through parameter passing - Each parameter is a data element

11. Structured design - 11 © Minder Chen, 1997-2002 Stamp Coupling Calculate Monthly Payment of a House Calculate Mortgage Payment Mortgage Payment Customer Loan Record Two module A and B are data coupled if - A calls B - B returns to A - All information passed between them are through parameter passing - A composite piece of data is passed from one module to another

12. Structured design - 12 © Minder Chen, 1997-2002 Control Coupling Produce paycheck Retrieve Employee Record Produce paycheck Retrieve Employee Record Employee ID Employee Record Employee ID Tell the operator that “The Employee Record Is Not Found” Employee Record Not Found Control FlagDescriptive Flag

13. Structured design - 13 © Minder Chen, 1997-2002 Scale of Cohesion Types of CohesionVisibility Strength of Cohesion Maintainability Functional Black box Sequential Not-quite so Communicational black box Procedural Gray Temporal box Logical Transparent Coincidental or white box Strong Weak Good Bad

14. Structured design - 14 © Minder Chen, 1997-2002 Structure Chart and DFD This module is sequentially cohesive. This module is communicationally cohesive.

15. Structured design - 15 © Minder Chen, 1997-2002 Simplify Communicational Cohesion Get Employee Name Calculate YTD Total Deduction Get Employee Name Calculate YTD Total Deduction Get Employee Name Calculate YTD Total Deduction Employee Name Employee YTD Total Deduction Employee ID Employee YTD Total Deduction Employee Name

16. Structured design - 16 © Minder Chen, 1997-2002 Determine Module Cohesion Type of Cohesion Does activities performed by the module related to a single problem-related task What relates the elements within the module ? Neither data nor control Is sequence important ? Data Flow of control Is sequence important ? Are the activities performed by the elements in the same category? YES NO Functional Sequential Communicational Procedural Temporal Logical Coincidental

17. Structured design - 17 © Minder Chen, 1997-2002 DETERMINE CUSTOMER DETAILS FIND CUSTOMER NAME EVALUATE LOAN STATUS DETERMINE CUSTOMER DETAILS Customer Account Number Customer Name Customer Loan Status Customer Account Number Customer Name A Communicationally Cohesive Module at the Bottom of a Structure Chart A Communicationally Cohesive Module Halfway Up a Structure Chart Each of These Functionally Cohesive Module is at the Bottom of a Structure

18. Structured design - 18 © Minder Chen, 1997-2002 GET RANGES GET TIMES GET AZIMUTHS GET SATELLITE TRAJECTORY GET ELEVATION A Functionally Cohesive Module Very High in a Structure Chart Satellite Trajectory Elevation Ranges Azimuths Times

19. Structured design - 19 © Minder Chen, 1997-2002 The Impact of Module Numbers on Cost Intermodule Effects (Coupling) Cost Due to Intramodule Effects (Cohesion) High Low Cost Number of Modules SmallLarge

20. Structured design - 20 © Minder Chen, 1997-2002 Four Basic Types of Modules Coordinate control Transform (Process) Efferent (Output) Afferent (Input)

21. Structured design - 21 © Minder Chen, 1997-2002 Idea System Shape of a Structure Chart Afferent branch Transform branch Efferent branch

22. Structured design - 22 © Minder Chen, 1997-2002 Idea System Shape of a Structure Chart High fan-out High fan-in

23. Structured design - 23 © Minder Chen, 1997-2002 The Procedure of Deriving Structure Charts from Data Flow Diagrams Evaluate a detailed DFD Type of DFD Identify central transform of the DFD Map to transaction structure Map to transform structure Refined the Structure Chart Identify transaction types and transaction center of the DFD Transaction Analysis Transform Analysis

24. Structured design - 24 © Minder Chen, 1997-2002 P OUTPUT FUNCTION C P INPUT FUNCTION B P INPUT FUNCTION D P OUTPUT FUNCTION A P INPUT FUNCTION C P OUTPUT FUNCTION B P TRANSFORM FUNCTION A P TRANSFORM FUNCTION B P INPUT FUNCTION A BOUNDARY B A DDATA STORE D DDATA STORE B DDATA STORE E M L K J I H G F E D C B A Afferent Central Transform Efferent Transform Analysis

25. Structured design - 25 © Minder Chen, 1997-2002 TRANSFORM FUNCTION A TRANSFORM FUNCTION B INPUT FUNCTION A INPUT FUNCTION D INPUT FUNCTION B OUTPUT FUNCTION A INPUT FUNCTION C OUTPUT FUNCTION C BOSS CENTRAL TRANSFORM CONTROLLER OUTPUT FUNCTION B E & F J & I J G & H E, F, & G I J G I F K E C

26. Structured design - 26 © Minder Chen, 1997-2002 Transaction Analysis DFD Get Customer Transactio n Process Customer Transaction Change Customer Record Add New Customer Get Customer Transaction Delete Customer Record Tx-Code Structure Chart Customer Information System Main Menu 1. Add New Customer 2. Change Customer Record 3. Delete Customer Record A Transaction Selection Screen

27. Structured design - 27 © Minder Chen, 1997-2002 Determine Implementation Boundaries Manual Real-time Batch On-line

28. Structured design - 28 © Minder Chen, 1997-2002 Processor Model: Allocation of essential Model Components to Processors Essential Model Processor 1 Processor 2 Processor 3 Processor Level Implementation Model    Netware LAN  UNIX Server T1 TCP/IP Mainframe Allocating processes and data stores to processors