0% found this document useful (0 votes)
3 views1 page

S DD New Table of Content

The System Design Document (SDD) outlines the purpose, design goals, and architecture of the proposed software system. It includes details on client/server architecture, subsystem decomposition, persistent data management, and access control and security. Additionally, it provides diagrams for UML package, deployment, and component interfaces, along with descriptions of various subsystem services.

Uploaded by

Mukesh Periasamy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
3 views1 page

S DD New Table of Content

The System Design Document (SDD) outlines the purpose, design goals, and architecture of the proposed software system. It includes details on client/server architecture, subsystem decomposition, persistent data management, and access control and security. Additionally, it provides diagrams for UML package, deployment, and component interfaces, along with descriptions of various subsystem services.

Uploaded by

Mukesh Periasamy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

System Design Document (SDD)

Table of Contents
1 Introduction ......................................................................................................................................... 6
1.1 Purpose of the System ................................................................................................................. 6
1.2 Design Goals ................................................................................................................................ 6
1.3 Definition, Acronyms, Abbreviations ........................................................................................ 7
1.4 References .................................................................................................................................... 8
1.5 Overview ...................................................................................................................................... 8
2 Current Software Architecture.......................................................................................................... 9
2.1 Overview ...................................................................................................................................... 9
3 Client/Server Architecture
Proposed Software Architecture...................................................................................................... 11
3.1 Overview .................................................................................................................................... 11
3.2 Subsystem Decomposition ........................................................................................................ 13
3.2.1 UML Package Diagram .................................................................................................... 13
3.2.2 Deployment Diagram
UML Component Diagram .............................................................................................. 16
3.3 Hardware/ Software Mapping ................................................................................................. 17
3.4 Refer 15.5 pg 261- 275
Persistent Data Management ................................................................................................... 18
3.5 Access Control and Security .................................................................................................... 19
4 Subsystem Architecture.................................................................................................................... 22
4.1 Subsystem Services ................................................................................................................... 22
4.2 Refer 21.2 pg 372-376
Use Case Diagram ..................................................................................................................... 27
4.3 Dynamic Modeling
Component Interface ................................................................................................................ 28
4.3.1 User Service ....................................................................................................................... 28
create communication diagram =Refer 21.2 pg 384-396
4.3.2 Login Service ..................................................................................................................... 29
4.3.3 Customer Service .............................................................................................................. 29
3-5 communication
4.3.4 Product Service ................................................................................................................. 30
4.3.5 Invoice Service ................................................................................................................... 31
4.3.6 Quotation Service .............................................................................................................. 32
4.3.7 Delivery Order Service ..................................................................................................... 33
4.3.8 Sales Report Service.......................................................................................................... 35

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy