1. IT 21103/41103 System Analysis & Design

2. Chapter 07 System Design Phase

3. System Design “Good Design has no Substitute Bad Design no Escape”

4. System Design Users become very important during this phase….

5. System Design …You must define what the user actually needs in the new system.

6. System Design Key Concern for this Phase: “The USER comes first”

7. System Design Design Phase Termination: When the user is satisfied that the system will perform as intended or when monetary and/or time constraints are exceeded.

8. System Design System Types: Transaction-Processing System Real-Time Data Batch Processing

9. System Design Management Information System (MIS) Enterprise Data

10. System Design Decision Support System (DSS) Decision Support

11. System Design Local Area Networked Information System (LAN-IS) Local Communications

12. System Design Wide Area Networked Information System (WAN-IS) Wider Communication

13. System Design Expert Systems Information Network Analyze & Diagnose Problems

14. System Design Strategic Information System Outside Analysis

15. System Design Alternative Approaches: (See Figure 7-5, Page 179)

16. System Design Structured Design: Breaking the problem into more manageable parts

17. System Design Structured Design: 4GL – 4 th Generation Language Modular Design Object Programming

18. System Design Object-Oriented Design: Analysts skip the DFD & ERD Develop the OM instead (USD, Menu-Tree, System Flowchart)

19. System Design Object-Oriented Design: Makes system design easier when using 4GL programming languages

20. System Design Joint Application Design: Developed in the mid-1980’s Intense Formal Design Workshop Session

21. System Design Joint Application Design: Can also have several small informal sessions over the period of the analysis and design phases

22. System Design Design Specifications: Gives the User the first look at the system, and the Analyst a blueprint to build the system

23. System Design Design Specifications: Develop a New USD Enhances the previous USD to more closely match the users needs

24. System Design Design Prototyping: All Show – gives the user a practical look at the system during the design process

25. System Design Project Deliverable: The Preliminary Presentation A Formal Oral and Written Report

26. System Design Preliminary Presentation: Written Summary of Project Requirements Overview of General Design Concepts Proposed Timetable Proposed Project Budget

27. System Design Preliminary Presentation: Oral Introductions Visuals from Written Report Questions & Answer Period Preview of the Next Step

28. System Design The Presentation: Extremely Important to UsersAnalysts Project Supporters

29. System Design The Design Review Session Requires Careful Documentation

30. System Design Form Design: Create specific form designs to be used in the system

31. System Design Form Design: Today is mostly Graphical in nature Always on – ready for user input May be based on Internet design

32. System Design Form Design: Source Documents Must include some way for users to receive help about the new forms and a way to backup these forms for auditing purposes

33. System Design Graphical User Interface Dialogs (GUIDs) Instructs users how to use the form, and records their selections and inputs

34. System Design Graphical User Interface Dialogs (GUIDs) Should have a consistent look & feel

35. System Design Graphical User Interface Dialogs (GUIDs) Should provide Entrance to the database system

36. System Design Graphical User Interface Dialogs (GUIDs) Correct Errors ASAP, do not wait to look for errors when the system is completed

37. System Design Other Considerations: Design the system for the user not the analyst Make allowances for users who do not have adequate knowledge of computer technology

38. System Design Other Considerations: Make the Design as easy as possible, but still covers all the required system inputs/outputs

39. System Design Other Considerations: Forms need to be designed for the novice computer user Think about programs you have used that were difficult to understand

40. System Design Other Considerations: DOCUMENT EVERYTHING YOU DO DURING THIS PHASE Documentation is required during all phases, but this phase is most critical for keeping current documentation.

41. System Design Other Considerations: This phase is critical to the success of your project…make it count “Put yourself in the shoes of the user and stay there”

42. System Design Questions

43. Assignment # 07 Page 204-205 Parts I & II Due: Nov 15 th