Your SlideShare is downloading. ×
Sen2 Architectural Design
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Sen2 Architectural Design

736
views

Published on


0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
736
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
33
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Architectural Design Fontys University of Applied Sciences Group 4
  • 2. Overview
    • Introduction
    • 3. Architectual desicions
    • 4. System Organisation
    • 5. Decomposition
    • 6. Control types
    • 7. Conclusuion
  • 8. Introduction
    • First Design
      • Communication with Project team
      • 9. System analysis
  • 14. Architectural desicion
    • Fundamental questions
      • Is there already a pattern for that problem?
      • 15. What architectual styles are suiteable ?
      • 16. How could we divide in Subsystems and modules ?
      • 17. Wich strategy is suitable to control the system ?
      • 18. How could we evaluate our System ?
  • 19. Architectural decission : Subsystem
    • Subsytem models
      • Static model
      • 20. Dynamic process model
      • 21. Interface model
      • 22. Relation model
      • 23. Distribution model
  • 24. System Organisations Overview
    • Reflects the basic strategy that is used to structure a system
    • 25. patterns of system organization
    • 26. Three popular structures
      • repository model
      • 27. client/server model
      • 28. layered style model
    • Maybe more than one structure is used in a software system
    • 29. described in ADL, UML or Box-diagrams
  • 30. System Organisation: repository model
    • Usage of central database
    • 31. Single database per subsystem ( de-central )
      • Sharing data by sending messages
      Pros:
    • Large amount of data
    • 32. Centralised backup, protection, access control, data recovery
    • 33. Efficient way of sharing data
      Cons:
    • Subsystems needs to fit into data save model
    • 34. Subsystems maybe have other requirements (e.g. other kind of access control)
  • 35. System Organisation: client/server
    • System of multiple services and server
    • 36. Multiple clients are using services
    • 37. Remote procedure calls (RPC, network communication)
      Pros:
    • Shared architecture
    • 38. Large amount of different services
    • 39. Increase reliability
    • 40. Easy to add servers and services
      Cons:
    • No combined data model
    • 41. Subsystems are organising data in different ways
    • 42. contingency risk
    • 43. Redundant server management costs
  • 44. System Organisation: layered style
    • Divide system into multiple layers
    • 45. 3 tier architecture (client, application-server, data-server)
    • 46. OSI reference model
      Pros:
    • Incremental developing of systems
    • 47. Easy to extend and to modify
    • 48. Security
    • 49. Testability
      Cons:
    • Performance, redundancy calls
    • 50. add overhead and latency to the processing of data
  • 51.  
  • 52.  
  • 53. Decomposition Subsystem vs. Modul
    • Subsystem :
      • Independent System wich operations are not based on other subsystems
      • 54. Include modules
      • 55. Interfaces for communication with other subsystems
    • Modul :
      • Part of a Subsystem ( System component )
      • 56. Provides services to other components
      • 57. Normaly not considered as a seperate system
  • 58. Decomsposition
    • Partitioning
      • Objectoriented
        • Differ a System in communicating Objects
      • Function oriented Pipeline
        • Differ a system in functional modules that receive data and convert it to outputable data ( receive – edit – output )
  • 59. Object
  • 60. Pipeline
  • 61. Control styles
    • Are concerned with the control flow between sub-systems. Distinct from the system decomposition model.
    • 62. Centralised control
      • One sub-system has overall responsibility for control and starts and stops other sub-systems.
  • 63. Control styles
    • Event-based control
      • Each sub-system can respond to externally generated events from other sub-systems or the system’s environment.
      • 64. Broadcast model :
        • Event is sent to every subsystem and this is programmed to handle these event
      • Interrupt-driven model :
        • Extern interrupts are handled by an interrupt handler and this handler send events to other components
        • 65. Only used in Real-time-environments ( airbag in cars )
  • 66. Conclusion
    • Architectural design is important (Root of complex software systems)
      • Structure of your system
      • 67. Dividing system into multiple subsystems
      • 68. System analysis and stakeholder communication
      • 69. Supports models for better re-usability
      • 70. Supports models for different non-functional requirements
  • 71. Questions?