1. Intro To Design 2 Architecture Diagrams
Software Engineering
CSCI-3321
Dr. Tom Hicks
Computer Science Department

2. "Good Design Is Good Design"
Language Independent!
Data Independent  Database Table Direct Access File  Text File
Should Not Have Multiple Copies Of Redundant Data
 Never Makes Sense To Lock & Change Multiple Records When We Could Lock & Change One Record!

3. Select A Team Recorder  Take Really Good Notes During Lectures

4. Part Of Your Next Homework: Decide Upon A Team Name!

5. Final Project System's Analysis Will Include: Readable (Our Classroom) Power Power-Point Presentation: All Of Your Class Diagrams.

6. Your Presentation Will Have A Cover Slide: Part Of Your Next Homework: Create Cover Slide For Class Diagrams

7. NorthPark Class Diagrams Red Team

8. Team 4: Top Snek
North Park
Class Diagrams

12. Final Project System's Analysis Will Include: Readable (Our Classroom) Power Power-Point Presentation: All Of Your Architecture Diagrams.

13. Your Presentation Will Have A Cover Slide: Part Of Your Next Homework: Create Cover Slide For Architecture Diagrams

14. Final Project System's Analysis Will Include: Readable (Our Classroom) Power Power-Point Presentation: All Of Your Class Diagrams.

15. NorthPark Architecture Diagrams Red Team

16. NorthPark Class Diagrams
Team TRINICLASSY
NorthPark Class Diagrams

17. Architecture Diagrams
Team 4: Top Snek
North Park
Architecture Diagrams

20. About ARCHITECTURE DIAGRAMS (Lots Of Interaction/Meetings Between Developers & Stakeholders)

21. Architecture Diagrams Are For The Stakeholder
AD Should Confirm, To The Stakeholder, What Functionality Can They Expect In Each Sub-System
AD Should Establish, For The Developer, That Functionality They Should Make Available In Each Sub-System
Architecture Diagrams Are For The Developer Team

22. Good Architecture Diagrams Increase The Probability That The Designer Will Construct An Acceptable Prototype! 22

23. There Are A Number Of Ways To Represent Architecture Diagrams.
All Approaches: Detail :High Level  Low Level
Generally Involve Some Degree Of
Graphical Components

24. A High Level Architecture Diagram(s) User Sub-System
Basic Sub-Systems:
User Sub-System
Inventory Sub-System
Vendor Sub-System
Transactional Sub-Systems:
CheckOut Sub-System
Fines Sub-System
Purchase Order Sub-System

25. B High Level Architecture Diagram(s) User Sub-System
Inventory Sub-System
Vendor Sub-System
CheckOut Sub-System
Fines Sub-System
Purchase Order Sub-System

26. C High Level Architecture Diagram(s) Vendor Sub-System
Fines Sub-System
Inventory Sub-System
Purchase Order Sub-System
User Sub-System
CheckOut Sub-System
Basic Sub-Systems:
Transactional Sub-Systems:

27. D High Level Architecture Diagram(s) Fines Sub-System
Purchase Order Sub-System
CheckOut Sub-System
Vendor Sub-System
Inventory Sub-System
User Sub-System

28. At Least One Level Of Refined Diagrams (sometimes more)
2 Rights!
Are We Building The Right System? Are We Building The System Right?

29. 10+ Years Ago Bad Examples Of Student Architecture Diagrams
2 Hats - Stakeholder & Developer These Are Not Great AD's 29

30. A Put On The Programmer Hat
Carefully Examine only the User Sub-System functionality described in each of the following (later) to determine which would be Most Helpful if you were expected to produce something similar to the Prototype Above.

31. Architectural DiagramB

32. Customer Architecture Diagram

33. Customer & Employee Architecture Diagram

34. Architectural Diagram

36. F

37. F
Best, But Not Great! F
Next
btnA,…, btnZ
Last
First
Next
Previous

38. ARCHITECTURE DIAGRAMS (What Has Worked Best For Me!)

39. User Sub-System General - Basic Functionality

40. User Sub-System General - Basic Functionality
Delete
Save
Cancel
Add
User Sub-System General - Basic Functionality

41. User Sub-System Navigation

42. User Sub-System Navigation
BtnA … BtnZ
Next
User Sub-System Navigation

43. User Sub-System OrderBy

44. User Sub-System OrderBy
Full Name ID
Order By
User Sub-System OrderBy

45. User Sub-System Select Filters

46. User Sub-System Select Filters
All Users
Administrators
Select
Customers
Employees
User Sub-System Select Filters

47. User Sub-System Technology - Text - Email - Etc.

48. User Sub-System Supporting Class Support

49. User Sub-System Technology - Text - Email - Etc.? ? ? ?
Text
User Sub-System Technology - Text - - Etc.

50. User Sub-System Short Cut Jumps

51. User Sub-System Short Cut Jumps
Open Maintenance Order
Auto Purchase
User Sub-System Short Cut Jumps

52. User Sub-System Search

53. User Sub-System Search
By Name
By ID
Advanced Search
User Sub-System Search

54. User Sub-System Views

55. User Sub-System Transaction Views
My Maintenance Orders -- Grid
User Sub-System Transaction Views

56. User Sub-System Forms Needed

57. User Sub-System Forms Needed
Simple Search
Undelete
Add
Edit
UserType
Delete
User
User Sub-System Forms Needed

58. User Sub-System Reports

59. User Sub-System Reports
Print This Record
User Sub-System Reports

60. Can Combine! (If Not Enough Data To Fill Slide)

61. User SubSystem OrderBy & Select Filters
All Users
Administrators
Select
Customers
Employees
Full Name ID
Order By
User SubSystem OrderBy & Select Filters