SA Chapter 12

1,460 views

Published on

SA Chapter 12

Published in: Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,460
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

SA Chapter 12

  1. 1. Phase 3 : Systems Design – Finalizing Design Specifications บทที่ 12
  2. 2. เนื้อหาที่จะเรียนในครั้งนี้ : <ul><li>Program Specification </li></ul><ul><li>Structure Charts </li></ul><ul><li>Design specification document </li></ul><ul><li>The Process of Finalizing Design Specifications </li></ul>
  3. 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. 4. <ul><li>Section A – ข้อมูลเบื้องต้น ( Preliminary Information) </li></ul><ul><li>1.Title and responsibility </li></ul><ul><ul><ul><li>Application name/ system name </li></ul></ul></ul><ul><ul><ul><li>Program Identification </li></ul></ul></ul><ul><ul><ul><li>Design by </li></ul></ul></ul><ul><ul><ul><li>Date Produced </li></ul></ul></ul><ul><ul><ul><li>Programmed by </li></ul></ul></ul><ul><ul><ul><li>Program start date </li></ul></ul></ul><ul><ul><ul><li>Expected completion date </li></ul></ul></ul><ul><li>2. Authorization </li></ul><ul><ul><ul><li>Approved by </li></ul></ul></ul><ul><li>3. Amendment Record </li></ul><ul><ul><ul><li>Revise date or date of amendments </li></ul></ul></ul><ul><ul><ul><li>Revised by </li></ul></ul></ul>Program Specification (1)
  5. 5. <ul><li>Section B – Aim of the program </li></ul><ul><ul><li>1. Purpose of the program </li></ul></ul><ul><ul><li>2. Files/Tables </li></ul></ul><ul><li>Section C – Detailed System Description </li></ul><ul><ul><li>Processing Requirements/ Process Description (Pseudo code/ Structured English / structure chart / Flowchart) </li></ul></ul><ul><li>Section D – Source Document Specifications </li></ul><ul><li>Screen Layout, Printout specification, example documents </li></ul>Program Specification (2)
  6. 6. <ul><ul><ul><li>โปรแกรม : P-STD1 </li></ul></ul></ul><ul><ul><ul><li>ระบบ : ทะเบียนนักศึกษา </li></ul></ul></ul><ul><ul><ul><li>วัตถุประสงค์ : โปรแกรมบันทึกประวัตินักศึกษาใหม่ </li></ul></ul></ul><ul><ul><ul><li>Run Flow : </li></ul></ul></ul>Tables : Input : Faculty Output : Student … P –STD1 Student Faculty
  7. 7. <ul><ul><ul><li>รายละเอียดการทำงาน : </li></ul></ul></ul><ul><ul><ul><li>แสดงจอภาพ S-STD11 </li></ul></ul></ul><ul><ul><ul><li>ที่ปุ่มบันทึก </li></ul></ul></ul><ul><ul><ul><li>ตรวจสอบความถูกต้องของข้อมูลดังนี้ </li></ul></ul></ul><ul><ul><ul><ul><li>รหัสนักศึกษาต้องเป็นตัวเลขเท่านั้น </li></ul></ul></ul></ul><ul><ul><ul><ul><li>คณะ สาขา หลักสูตร ต้องสัมพันธ์กัน ตรวจสอบจากตาราง Faculty </li></ul></ul></ul></ul><ul><ul><ul><ul><li>เพศเป็น หญิง หรือ ชาย เท่านั้น โดยเพศหญิงใช้ รหัส 1 เพศชายใช้รหัส 2 </li></ul></ul></ul></ul><ul><ul><ul><ul><li>......... </li></ul></ul></ul></ul><ul><ul><ul><li>กรณีที่ข้อมูลใดไม่ถูกต้องแสดงจอภาพ S-STD12 และรอรับข้อมูลใหม่ </li></ul></ul></ul><ul><ul><ul><li>กรณีที่ข้อมูลถูกต้อง บันทึกข้อมูลในตาราง student </li></ul></ul></ul><ul><ul><ul><li>3. ปุ่มปิด ออกจากโปรแกรม </li></ul></ul></ul>
  8. 8. จอภาพ STD11
  9. 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. 10. Supporting diagrams and modules <ul><li>Structure Charts </li></ul><ul><ul><li>Shows how an information system is organized in hierarchical models </li></ul></ul><ul><ul><li>Shows how parts of a system are related to one another </li></ul></ul><ul><ul><li>Shows breakdown of a system into programs and internal structures of programs written in third and fourth generation languages </li></ul></ul>
  11. 11. Supporting diagrams and modules <ul><li>Structure Charts </li></ul><ul><ul><li>Module </li></ul></ul><ul><ul><ul><li>A self-contained component of a system, defined by a function </li></ul></ul></ul><ul><ul><ul><li>One single coordinating module at the root of structure chart </li></ul></ul></ul><ul><ul><ul><li>Single point of entry and exit </li></ul></ul></ul><ul><ul><ul><li>Communicate with each other by passing parameters </li></ul></ul></ul><ul><ul><ul><ul><li>Data couple </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>A diagrammatic representation of the data exchanged between two modules in a structure chart </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><li>Flag </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>A diagrammatic representation of a message passed between two modules </li></ul></ul></ul></ul></ul>
  12. 12. Supporting diagrams and modules <ul><li>Structure Charts </li></ul><ul><ul><ul><li>Special Symbols </li></ul></ul></ul><ul><ul><ul><ul><li>Diamond </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Only one subordinate will be called </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><li>Curved Line </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Subordinates are called repeatedly until terminating condition is met </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><li>Predefined modules means it function is dictated by some preexisting part of the system. </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Hat </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Subordinate module is important logically but actual code is contained in superior module </li></ul></ul></ul></ul></ul>
  13. 15. Run flow from each program Specification can form System Flow-Chart System Flowchart Example : System Flowchart for a Payroll System
  14. 16. The Process of Finalizing Design Specifications <ul><li>Deliverables and Outcome </li></ul><ul><ul><li>Set of physical design specifications </li></ul></ul><ul><ul><ul><li>Contains detailed specifications for each part of the system </li></ul></ul></ul>
  15. 17. The Process of Finalizing Design Specifications (1) <ul><li>SYSTEM DESIGN SPECIFICATION </li></ul><ul><li>Management Summary </li></ul><ul><li>System Components Details </li></ul><ul><li>Input Design </li></ul><ul><li>Output Design </li></ul><ul><li>File and Database Design </li></ul><ul><li>Processing Design </li></ul><ul><li>Environmental Requirements </li></ul><ul><li>Implementation Requirements </li></ul><ul><li>Time and Cost Estimates </li></ul><ul><li>Appendices ( as needed ) </li></ul>
  16. 18. <ul><ul><li>Management Summary - Overall System Description (functions, operating environment, type of users, constraints, assumptions and dependencies) </li></ul></ul><ul><ul><li>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) </li></ul></ul><ul><ul><li>System features (feature 1 description …. Feature n description) </li></ul></ul><ul><ul><li>Environment requirements - nonfunctional requirements (performance, safety, security, software quality, business rules) </li></ul></ul><ul><ul><li>Implementation requirements </li></ul></ul><ul><ul><li>Time and cost estimates </li></ul></ul><ul><ul><li>Appendices - supporting diagrams and modules </li></ul></ul>Design specification document contains :
  17. 19. The Process of Finalizing Design Specifications (2) <ul><ul><li>Approvals (Stakeholders – IT , User etc.) </li></ul></ul><ul><ul><li>Technical and Management Presentation </li></ul></ul><ul><ul><ul><li>IT staff </li></ul></ul></ul><ul><ul><ul><li>Users </li></ul></ul></ul><ul><ul><ul><li>Administrators </li></ul></ul></ul>

×