際際滷

際際滷Share a Scribd company logo

SA Chapter 12

Nuth Otanasap
Nuth Otanasap

SA Chapter 12

Convert to study materialsBETA

Transform any presentation into ready-made study materialselect from outputs like summaries, definitions, and practice questions.

1 of 19
Phase 3 : Systems Design Finalizing Design Specifications 犖犖犖犖朽 12
犢犖犖劇犖犖犖迦犖朽犖犖萎犖犖朽権犖犢犖犖犖犖園犖犖犖朽 : Program Specification Structure Charts Design specification document The Process of Finalizing Design Specifications
犖犖園犖犢犖犖園犖 犖ム験犖犖園犖犖迦犢犖ム鍵犖犖迦牽犖犖犖萎検犖о献犖犖 犖犖萎犖犖犖園犖犖迦牽犖犖園犖犖犖劇犖 (0) 犖犖園犖犖橿犖犢犖犢犖犖犖犖朽 (2.0) 犖犖園犖犖橿牽犖萎犖犖巌 (3.0) 犖犖園犖犖謹犖犢犖犖÷弦犖ム犖迦牽犖犖園犖犖犖劇犖 (1.0) ... (1.1) ... (1.2) ... (1.3) ... (2.1) ... (2.2) ... (3.1) ... (3.2) ... (3.3) ... (3.4)
Section A 犖犢犖犖÷弦犖ム犖犖劇犖犖犖犢犖 ( Preliminary Information) 1.Title and responsibility Application name/ system name Program Identification Design by Date Produced Programmed by Program start date Expected completion date 2. Authorization Approved by 3. Amendment Record Revise date or date of amendments Revised by Program Specification (1)
Section B Aim of the program 1. Purpose of the program 2. Files/Tables Section C Detailed System Description Processing Requirements/ Process Description (Pseudo code/ Structured English / structure chart / Flowchart) Section D Source Document Specifications Screen Layout, Printout specification, example documents Program Specification (2)
犢犖犖犢犖犖犖 : P-STD1 犖犖萎犖 : 犖犖萎犖犖朽権犖犖犖園犖犖謹犖犖 犖о険犖犖犖伍犖犖萎肩犖犖犢 : 犢犖犖犢犖犖犖÷犖園犖犖謹犖犖犖萎硯犖園犖巌犖園犖犖謹犖犖迦犖犖÷ Run Flow : Tables : Input : Faculty Output : Student P STD1 Student Faculty
犖犖迦権犖ム鍵犢犖犖朽権犖犖犖迦牽犖犖橿犖迦 : 犢犖犖犖犖犖犖犖迦 S-STD11 犖犖朽犖犖伍犖÷犖園犖犖謹 犖犖犖о犖犖犖犖犖о顕犖÷犖項犖犢犖犖犖犖犖犖犢犖犖÷弦犖ム犖園犖犖朽 犖犖犖園肩犖犖園犖犖謹犖犖迦犢犖犖犢犖犢犖犖犖園硯犢犖ム犢犖犢犖迦犖園犖 犖犖犖 犖犖迦犖 犖犖ム険犖犖犖項犖 犖犢犖犖犖犖園検犖犖園犖犢犖犖園 犖犖犖о犖犖犖犖犖迦犖犖迦牽犖迦 Faculty 犢犖犖犢犖犢犖 犖犖犖巌 犖犖犖劇賢 犖犖迦権 犢犖犢犖迦犖園犖 犢犖犖∇犖犖犖犖犖巌犢犖犢 犖犖犖園肩 1 犢犖犖犖犖迦権犢犖犢犖犖犖園肩 2 ......... 犖犖犖犖朽犖朽犖犢犖犖÷弦犖ム犖犢犖÷犖犖項犖犢犖犖犢犖犖犖犖犖犖犖迦 S-STD12 犢犖ム鍵犖犖犖犖園犖犢犖犖÷弦犖ム犖犖÷ 犖犖犖犖朽犖朽犖犢犖犖÷弦犖ム犖項犖犢犖犖 犖犖園犖犖謹犖犢犖犖÷弦犖ム犖犖犖迦牽犖迦 student 3. 犖犖伍犖÷犖巌 犖犖犖犖犖迦犢犖犖犢犖犖犖
犖犖犖犖迦 STD11
犖犖迦牽犖迦 student Attributes Type Length Description Value std_ID Number 10 犖犖犖園肩犖犖園犖犖謹犖犖 fac_ID Number 2 犖犖犖園肩犖犖犖 01 -05 .. . 犖犖迦牽犖迦 faculty Attributes Type Length Description Value fac_ID Number 2 犖犖犖園肩犖犖犖 01 -05 Fac_des Text 40 犖犖劇犖犖犖犖
Supporting diagrams and modules Structure Charts Shows how an information system is organized in hierarchical models Shows how parts of a system are related to one another Shows breakdown of a system into programs and internal structures of programs written in third and fourth generation languages
Supporting diagrams and modules Structure Charts Module A self-contained component of a system, defined by a function One single coordinating module at the root of structure chart Single point of entry and exit Communicate with each other by passing parameters Data couple A diagrammatic representation of the data exchanged between two modules in a structure chart Flag A diagrammatic representation of a message passed between two modules
Supporting diagrams and modules Structure Charts Special Symbols Diamond Only one subordinate will be called Curved Line Subordinates are called repeatedly until terminating condition is met Predefined modules means it function is dictated by some preexisting part of the system. Hat Subordinate module is important logically but actual code is contained in superior module
油
油
Run flow from each program Specification can form System Flow-Chart System Flowchart Example : System Flowchart for a Payroll System
The Process of Finalizing Design Specifications Deliverables and Outcome Set of physical design specifications Contains detailed specifications for each part of the system
The Process of Finalizing Design Specifications (1) SYSTEM DESIGN SPECIFICATION Management Summary System Components Details Input Design Output Design File and Database Design Processing Design Environmental Requirements Implementation Requirements Time and Cost Estimates Appendices ( as needed )
Management Summary - Overall System Description (functions, operating environment, type of users, constraints, assumptions and dependencies) System Component details - Interface requirements (user interfaces, hardware interfaces, software interfaces, communication interfaces, DFDs, Hierarchical chart, Dialogue sequence diagram, Source documents, Database design - E-R diagram, data schema, tables, Program specifications screens, reports) System features (feature 1 description . Feature n description) Environment requirements - nonfunctional requirements (performance, safety, security, software quality, business rules) Implementation requirements Time and cost estimates Appendices - supporting diagrams and modules Design specification document contains :
The Process of Finalizing Design Specifications (2) Approvals (Stakeholders IT , User etc.) Technical and Management Presentation IT staff Users Administrators

More Related Content

SA Chapter 12

  • 1. Phase 3 : Systems Design Finalizing Design Specifications 犖犖犖犖朽 12
  • 2. 犢犖犖劇犖犖犖迦犖朽犖犖萎犖犖朽権犖犢犖犖犖犖園犖犖犖朽 : Program Specification Structure Charts Design specification document The Process of Finalizing Design Specifications
  • 3. 犖犖園犖犢犖犖園犖 犖ム験犖犖園犖犖迦犢犖ム鍵犖犖迦牽犖犖犖萎検犖о献犖犖 犖犖萎犖犖犖園犖犖迦牽犖犖園犖犖犖劇犖 (0) 犖犖園犖犖橿犖犢犖犢犖犖犖犖朽 (2.0) 犖犖園犖犖橿牽犖萎犖犖巌 (3.0) 犖犖園犖犖謹犖犢犖犖÷弦犖ム犖迦牽犖犖園犖犖犖劇犖 (1.0) ... (1.1) ... (1.2) ... (1.3) ... (2.1) ... (2.2) ... (3.1) ... (3.2) ... (3.3) ... (3.4)
  • 4. Section A 犖犢犖犖÷弦犖ム犖犖劇犖犖犖犢犖 ( Preliminary Information) 1.Title and responsibility Application name/ system name Program Identification Design by Date Produced Programmed by Program start date Expected completion date 2. Authorization Approved by 3. Amendment Record Revise date or date of amendments Revised by Program Specification (1)
  • 5. Section B Aim of the program 1. Purpose of the program 2. Files/Tables Section C Detailed System Description Processing Requirements/ Process Description (Pseudo code/ Structured English / structure chart / Flowchart) Section D Source Document Specifications Screen Layout, Printout specification, example documents Program Specification (2)
  • 6. 犢犖犖犢犖犖犖 : P-STD1 犖犖萎犖 : 犖犖萎犖犖朽権犖犖犖園犖犖謹犖犖 犖о険犖犖犖伍犖犖萎肩犖犖犢 : 犢犖犖犢犖犖犖÷犖園犖犖謹犖犖犖萎硯犖園犖巌犖園犖犖謹犖犖迦犖犖÷ Run Flow : Tables : Input : Faculty Output : Student P STD1 Student Faculty
  • 7. 犖犖迦権犖ム鍵犢犖犖朽権犖犖犖迦牽犖犖橿犖迦 : 犢犖犖犖犖犖犖犖迦 S-STD11 犖犖朽犖犖伍犖÷犖園犖犖謹 犖犖犖о犖犖犖犖犖о顕犖÷犖項犖犢犖犖犖犖犖犖犢犖犖÷弦犖ム犖園犖犖朽 犖犖犖園肩犖犖園犖犖謹犖犖迦犢犖犖犢犖犢犖犖犖園硯犢犖ム犢犖犢犖迦犖園犖 犖犖犖 犖犖迦犖 犖犖ム険犖犖犖項犖 犖犢犖犖犖犖園検犖犖園犖犢犖犖園 犖犖犖о犖犖犖犖犖迦犖犖迦牽犖迦 Faculty 犢犖犖犢犖犢犖 犖犖犖巌 犖犖犖劇賢 犖犖迦権 犢犖犢犖迦犖園犖 犢犖犖∇犖犖犖犖犖巌犢犖犢 犖犖犖園肩 1 犢犖犖犖犖迦権犢犖犢犖犖犖園肩 2 ......... 犖犖犖犖朽犖朽犖犢犖犖÷弦犖ム犖犢犖÷犖犖項犖犢犖犖犢犖犖犖犖犖犖犖迦 S-STD12 犢犖ム鍵犖犖犖犖園犖犢犖犖÷弦犖ム犖犖÷ 犖犖犖犖朽犖朽犖犢犖犖÷弦犖ム犖項犖犢犖犖 犖犖園犖犖謹犖犢犖犖÷弦犖ム犖犖犖迦牽犖迦 student 3. 犖犖伍犖÷犖巌 犖犖犖犖犖迦犢犖犖犢犖犖犖
  • 9. 犖犖迦牽犖迦 student Attributes Type Length Description Value std_ID Number 10 犖犖犖園肩犖犖園犖犖謹犖犖 fac_ID Number 2 犖犖犖園肩犖犖犖 01 -05 .. . 犖犖迦牽犖迦 faculty Attributes Type Length Description Value fac_ID Number 2 犖犖犖園肩犖犖犖 01 -05 Fac_des Text 40 犖犖劇犖犖犖犖
  • 10. Supporting diagrams and modules Structure Charts Shows how an information system is organized in hierarchical models Shows how parts of a system are related to one another Shows breakdown of a system into programs and internal structures of programs written in third and fourth generation languages
  • 11. Supporting diagrams and modules Structure Charts Module A self-contained component of a system, defined by a function One single coordinating module at the root of structure chart Single point of entry and exit Communicate with each other by passing parameters Data couple A diagrammatic representation of the data exchanged between two modules in a structure chart Flag A diagrammatic representation of a message passed between two modules
  • 12. Supporting diagrams and modules Structure Charts Special Symbols Diamond Only one subordinate will be called Curved Line Subordinates are called repeatedly until terminating condition is met Predefined modules means it function is dictated by some preexisting part of the system. Hat Subordinate module is important logically but actual code is contained in superior module
  • 13. 油
  • 14. 油
  • 15. Run flow from each program Specification can form System Flow-Chart System Flowchart Example : System Flowchart for a Payroll System
  • 16. The Process of Finalizing Design Specifications Deliverables and Outcome Set of physical design specifications Contains detailed specifications for each part of the system
  • 17. The Process of Finalizing Design Specifications (1) SYSTEM DESIGN SPECIFICATION Management Summary System Components Details Input Design Output Design File and Database Design Processing Design Environmental Requirements Implementation Requirements Time and Cost Estimates Appendices ( as needed )
  • 18. Management Summary - Overall System Description (functions, operating environment, type of users, constraints, assumptions and dependencies) System Component details - Interface requirements (user interfaces, hardware interfaces, software interfaces, communication interfaces, DFDs, Hierarchical chart, Dialogue sequence diagram, Source documents, Database design - E-R diagram, data schema, tables, Program specifications screens, reports) System features (feature 1 description . Feature n description) Environment requirements - nonfunctional requirements (performance, safety, security, software quality, business rules) Implementation requirements Time and cost estimates Appendices - supporting diagrams and modules Design specification document contains :
  • 19. The Process of Finalizing Design Specifications (2) Approvals (Stakeholders IT , User etc.) Technical and Management Presentation IT staff Users Administrators