TruQuote SoftwareArchitectureDocument(SAD) tủ tài liệu bách khoa

Smart World Technology Co... The document audience is the Software Architect and the Project Team and will be used as input to the detailed design process.. All document used Enterprise

Trang 1

Smart World Technology Co ltd.

Address: 02 No Trang Long Street, ward 13, Binh Thanh District, HCMC Vietnam

Phone: 84-8-66 749 024

Fax: 84-8-62 584 459

Software Architecture

Document

Date [May 18, 2010]

Trang 2

Revision History

Trang 3

Address: 02 No Trang Long Street, ward 13, Binh Thanh District, HCMC Vietnam Phone: 84-8-66 749 024

Fax: 84-8-62 584 459

Table of Contents

1 INTRODUCTION 4

1.1 PURPOSE

4 1.2 SCOPE

4 1.3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS

4 1.3.1 Terminology and Definitions 6

1.3.2 Abbreviations and Notations 7

1.4 REFERENCES

8 1.5 OVERVIEW

8 2 ARCHITECTURAL REPRESENTATION 8

3 ARCHITECTURAL GOALS AND CONSTRAINTS 9

3.1 SPECIFIC REQUIREMENTS

9 3.1.1 Functions 9

3.1.2 Non Functions 9

3.2 EXTERNAL INTERFACES

9 3.2.1 User interfaces 9

3.2.2 Hardware interfaces 9

3.2.3 Software interfaces 9

3.2.4 Communications interfaces 9

4 USE-CASE VIEW 9

5 LOGICAL VIEW 9

6 PROCESS VIEW 10

7 DEPLOYMENT VIEW 12

8 DATA VIEW (OPTIONAL) 12

Trang 4

1 Introduction

1.1 Purpose

This Software Architecture Document (SAD) provides a comprehensive architectural overview of the Card Management System, using a different number of architectural views to depict different aspects of the system It is intended to capture and convey the significant architectural decisions which have been made on the system The SAD will show the identified

subsystems and their interfaces, layers, packages and essential classes The document audience is the Software Architect and the Project Team and will be used as input to the detailed design process

All document used Enterprise Architect software to analysis and design Click here to view all

1.2 Scope

Software Architecture Document applies:

- Usecase view

- Logical view

- Process view

- Deployment view

- Implement view

- Data view

1.3 Definitions, Acronyms and Abbreviations

1 Dealer Nhân viên công ty đi bán những mẫu thiết kế

Trang 5

Phone: 84-8-66 749 024

Fax: 84-8-62 584 459

Structure Type Tên gọi của các mẫu nhà

Wind Region Vùng gió

Terrain

Category Kiểu địa hình

Base Type Kiểu trụ của nhà xưỡng

Roof Pitch Độ nghiêng mái

Bay Số gian của ngôi nhà

Height Chiều cao của ngôi nhà

Lookup code Một kiến trúc có một con số quy định

Structure_Close

? Cấu trúc của nhà xưỡng đóng hay mở

Column Cột trụ

Purlin Xà gồ, vuông góc với rafter

Girt Xà gồ đóng ngang

Roof sheeting Tôn mái

Wall sheeting Tôn tường

Gutter Máng xối (có bao thành phần gutter chính hai

hai phần chắc hai bên)

Haunch Plate

Tấm nối giữa column với rafer (dùng trợ lực, trong trường hợp kiến trúc lớn thì có thể thay bằng một column)

Apex Plate Tấm nối hai rafter

PADoor Cửa chính

SLDDoor Cửa trượt

Trang 6

No Term Description

Bolt Buloong

Plate & Bracket

Wind Bracing Một loại dây

Awning Mái hiên (là một kiến trúc phụ cũng bao gồm

colum, rafter, purlin, purlin, girt…) Downpipe Ống nước

Knee Brace Giống như haunch plate

Briding Dùng để nối Purlin

Flashing Bao che nơi các chi tiết gắn với nhau

Carry Beams Kết hợp với những chi tiết khác cho khoảng

rộng gấp đôi một bay (là một Options) Trac Đường nối (cho SLDDoor)

Vent Vòng xoay tản nhiệt

1.3.1 Terminology and Definitions

Trang 7

Fax: 84-8-62 584 459

1.3.2 Abbreviations and Notations

Trang 8

1.4 References

<List any other documents or Web addresses to which this SAD refers.>

1.5 Overview

Sections 2-10 of this document provide the details of the software

architecture

2 Architectural Representation

The architecture of the application is represented following the

recommendations of the Rational Unified Process and the Rational Architecture Practice guidelines The UML specification of the systems has been divided into six models:

• Use Case Model [Use Case View::Use-Case Model]

• Analysis Model [Logical View::Analysis Model]

• User Experience Model [Logical View::User Experience Model]

• Design Model [Logical View::Design Model]

• Implementation Model [Component View::com], and

• Deployment Model [Deployment View]

The Logical View and the Component View also include packages that represent the Java language and the struts framework elements Collectively the above models and packages form a complete UML specification of the system

Trang 9

Phone: 84-8-66 749 024

Fax: 84-8-62 584 459

3 Architectural Goals and Constraints

3.1 Specific requirements

\1.Requirement\SoftwareRequirementSpecification(SRS)\TruQuote_1.Softwa reRequirementSpecification(SRS).doc

3.1.1 Functions

\1.Requirement\REQs\TruQuote_3.FunctionREQs.doc

3.1.2 Non Functions

\1.Requirement\NonFuntionalREQs\TruQuote_4.NonFunctionREQs.doc

3.2 External interfaces

3.2.1 User interfaces

\1.Requirement\UserInterfacePrototype\TruQuote_6.UserInterfaceProtot ype.doc

3.2.2 Hardware interfaces

3.2.3 Software interfaces

3.2.4 Communications interfaces

4 Use-Case View

\1.Requirement\UseCase\TruQuote_UseCaseModel.doc

5 Logical View

1.HighLevelDesign\TruQuote_1.HighLevelDesign.doc

1.HighLevelDesign\TruQuote_2.DomainModel.doc

2.LowLevelDesign\3.ClassModel.doc

Trang 10

6 Process View

2.LowLevelDesign\4.ProcessView.doc

Trang 11

Fax: 84-8-62 584 459

Trang 12

7 Deployment View

2.LowLevelDesign\5.DeploymentView.doc

8 Data View (optional)

3.DatabaseDesign\6.DataView.doc

Trang 13

Fax: 84-8-62 584 459

Định dạng
Số trang	13
Dung lượng	151 KB