没有合适的资源?快使用搜索试试~ 我知道了~
首页体系结构设计 案例 1-Software Architecture Document
体系结构设计 案例 1-Software Architecture Document
需积分: 29 368 浏览量
更新于2023-03-16
评论
收藏 535KB PDF 举报
体系结构设计 案例 1-Software Architecture Document,软件体系结构设计的标准文档 英文版
资源详情
资源评论
资源推荐

COMPREHENSIVE WATERSHED MANAGEMENT
WATER USE TRACKING PROJECT
Software Architecture Document
Southwest Florida Water Management District
2379 Broad Street
Brooksville, FL 34604-6899
Date Revision Description Author

Water Use Tracking Project – February 13, 2007
Software Architecture Document
i
Table of Contents
1 Introduction.............................................................................................................................. 1
1.1 Use Case Driven Software Engineering Process ............................................................ 1
1.2 Software Architecture..................................................................................................... 1
1.3 Purpose............................................................................................................................ 2
1.4 Background..................................................................................................................... 2
1.5 WUT Software Architecture Document Review............................................................ 3
2 WUT Architectural Representation......................................................................................... 4
2.1 Introduction..................................................................................................................... 4
2.2 WUT Architecturally Significant Decisions................................................................... 4
2.3 WUT Architectural Views.............................................................................................. 5
3 WUT Architectural Goals and Constraints.............................................................................. 7
3.1 Support for the WUT Business and Functional Requirements....................................... 7
3.2 Support for the WUT Non-Functional Requirements..................................................... 7
3.3 Mitigation of WUT Technical Risks............................................................................... 7
4 WUT Technical Risks.............................................................................................................. 8
4.1 District Staffing Issues....................................................................................................9
4.1.1 Description.................................................................................................................. 9
4.1.2 Architectural Significance .......................................................................................... 9
4.2 Legacy System Issues ..................................................................................................... 9
4.2.1 Description.................................................................................................................. 9
4.2.2 Architectural Significance .......................................................................................... 9
5 WUT Architecturally Significant Decisions.......................................................................... 10
5.1 Introduction................................................................................................................... 10
5.2 Overview of the WUT Architecturally Significant Decisions...................................... 10
5.3 Object-Oriented Software Development Methodology................................................ 11
5.4 Layering........................................................................................................................ 11
5.4.1 Problem Domain Layers........................................................................................... 12
5.4.2 Solution Space Layers............................................................................................... 13
5.4.3 WUT Software Layers.............................................................................................. 14
5.5 Boundary, Control, and Entity Design Pattern ............................................................. 15
5.5.1 Model, View, and Controller Design Pattern............................................................ 15
5.5.2 Boundary, Controller, and Entity Design Pattern..................................................... 16
5.5.3 WUT Design Model and the BCE Design Pattern.................................................... 19
5.6 Distributed 3-Tier Client/Server Architecture .............................................................. 19
5.7 Thin Web Client Architecture....................................................................................... 21
5.8 Security Architecture .................................................................................................... 23
5.8.1 WUT Application Level Security............................................................................. 23
5.8.2 WUT System Level Security.................................................................................... 23
5.9 Relational Database Management System.................................................................... 24
5.10 Object-Relational Broker Design Pattern ..................................................................... 24
5.11 Trusted User Design Pattern......................................................................................... 25

Water Use Tracking Project – February 13, 2007
Software Architecture Document
ii
5.12 WUT Technical Architecture........................................................................................ 25
5.12.1 Windows 2000 Server............................................................................................... 26
5.12.2 Oracle RDBMS......................................................................................................... 26
5.12.3 GIS Technologies...................................................................................................... 26
5.12.3.1 ArcSDE............................................................................................................. 26
5.12.3.2 ArcIMS ............................................................................................................. 26
5.12.3.3 MapDotNet ....................................................................................................... 27
5.12.4 Microsoft .NET Development Technologies............................................................ 27
5.12.5 Crystal Reports for Visual Studio .NET ................................................................... 28
6 WUT Use Case View............................................................................................................. 29
6.1 Architecturally Significant and High Risk Use Cases.................................................. 29
6.1.1 Architecturally Significant Use Cases ...................................................................... 29
6.1.2 High Risk Use Cases................................................................................................. 30
6.1.2.1 Risk ....................................................................................................................... 30
6.1.2.2 Coverage ............................................................................................................... 30
6.1.2.3 Criticality .............................................................................................................. 31
6.2 WUT UML Use Case Model........................................................................................ 31
6.3 Process Database Replication ....................................................................................... 33
6.3.1 Local WUT UML Use Case Model.......................................................................... 33
6.3.2 Business Context....................................................................................................... 33
6.4 Process WUT System Startup Use Case....................................................................... 34
6.4.1 Local WUT UML Use Case Model.......................................................................... 34
6.4.2 Business Context....................................................................................................... 34
6.5 Maintain WUT News.................................................................................................... 35
6.5.1 Local WUT UML Use Case Model.......................................................................... 35
6.5.2 Business Context....................................................................................................... 35
6.6 View Map...................................................................................................................... 36
6.6.1 Local WUT UML Use Case Model.......................................................................... 36
6.6.2 Business Context....................................................................................................... 36
6.7 View Report.................................................................................................................. 37
6.7.1 Local WUT UML Use Case Model.......................................................................... 37
6.7.2 Business Context....................................................................................................... 37
6.8 View Water Use Permit................................................................................................ 38
6.8.1 Local WUT UML Use Case Model.......................................................................... 38
6.8.2 Business Context....................................................................................................... 38
6.9 View Water Use Permit Search .................................................................................... 39
6.9.1 Local WUT UML Use Case Model.......................................................................... 39
6.9.2 Business Context....................................................................................................... 39
7 WUT Logical View ............................................................................................................... 40
7.1 Introduction................................................................................................................... 40
7.2 Object-Oriented Software Development Methodology................................................ 41
7.2.1 Overview................................................................................................................... 41
7.2.2 UML Model Elements from the WUT Design Model.............................................. 42
7.3 Layering........................................................................................................................ 43
7.3.1 Overview................................................................................................................... 43

Water Use Tracking Project – February 13, 2007
Software Architecture Document
iii
7.3.2 UML Model Elements from the WUT Design Model.............................................. 43
7.4 Boundary, Control, and Entity Design Pattern ............................................................. 45
7.4.1 Overview................................................................................................................... 45
7.4.2 UML Model Elements from the WUT Design Model.............................................. 46
7.4.2.1 Process Database Replication Use Case – Stereotyped VOPC ............................ 46
7.4.2.2 Process WUT System Startup Use Case – Stereotyped VOPC............................ 47
7.4.2.3 Maintain WUT News Use Case – Stereotyped VOPC......................................... 48
7.4.2.4 View Map Use Case – Stereotyped VOPC........................................................... 49
7.4.2.5 View Report Use Case – Stereotyped VOPC ....................................................... 50
7.4.2.6 View Water Use Permit Use Case – Stereotyped VOPC ..................................... 51
7.4.2.7 View Water Use Permit Search Use Case – Stereotyped VOPC.......................... 52
7.5 Security Architecture .................................................................................................... 53
7.5.1 Overview................................................................................................................... 53
7.5.2 UML Model Elements from the WUT Design Model.............................................. 54
7.6 Object-Relational Broker Design Pattern ..................................................................... 55
7.6.1 Overview................................................................................................................... 55
7.6.2 UML Model Elements from the WUT Design Model.............................................. 56
7.7 Trusted User Design Pattern......................................................................................... 57
8 WUT Deployment View........................................................................................................ 58
8.1 Introduction................................................................................................................... 58
8.1.1 Relational Database Management System................................................................ 58
8.1.2 Distributed 3-Tier Client/Server Architecture.......................................................... 58
8.1.3 Thin Web Client Architecture................................................................................... 59
8.1.4 WUT Technical Architecture.................................................................................... 60
8.2 WUT UML Deployment Model ................................................................................... 60
9 WUT Technical Risk Mitigation ........................................................................................... 62
9.1 Introduction................................................................................................................... 62
9.2 District Staffing Issues.................................................................................................. 62
9.2.1 Architectural Significance ........................................................................................ 62
9.2.2 Technical Risk Mitigation......................................................................................... 63
9.2.2.1 Object-Oriented Software Development Methodology........................................ 63
9.2.2.2 Layering................................................................................................................ 63
9.2.2.3 Relational Database Management System............................................................ 64
9.3 Legacy System Issues ................................................................................................... 64
9.3.1 Architectural Significance ........................................................................................ 64
9.3.2 Technical Risk Mitigation......................................................................................... 64

Water Use Tracking Project – February 13, 2007
Software Architecture Document
1
Software Architecture Document
1 Introduction
1.1 Use Case Driven Software Engineering Process
The software engineering process utilized by the Water Use Tracking (WUT) Project
Development Team is frequently characterized as a use case driven process. This
characterization is based on the understanding that the behaviors, as well as the business and
functional requirements that the application must support, are captured in the WUT Software
Requirement Specification (SRS) and the WUT Use Case Model. Upon the approval of the SRS
and throughout the balance of the software life cycle, the use cases that comprise the WUT Use
Case Model provide the unifying thread for the software engineering process, a role that is
particularly evident during the Elaboration Phase.
One of the primary deliverables produced during the Elaboration Phase is the WUT Design
Model, an object model that describes the realization of the use cases documented in the WUT
Use Case Model. The design model, which serves as an abstraction of the Implementation
Model and its source code, is created through a use case realization process. That is, using the
behavior described in each use case as input, the WUT Design Model is methodically
constructed, use case by use case, through the creation of a number of interaction and class
diagrams, each of which identifies the collection of classes that collaborate together to support
the behavior documented in each use case. As the design model is iteratively refined and
polished through the use case realization process, the design of the software system is conceived
and, most importantly, the software architecture begins to emerge.
1.2 Software Architecture
Software architecture is intimately related to system design and it encompasses the major
decisions being made regarding the behavior, structure, organization, implementation, and
deployment of the software system. The Rational Unified Process defines software architecture
as the set of significant decisions about:
• The organization of the software system
• The selection of structural elements and their interfaces by which the system is composed
• Their behavior, as specified in the collaboration among those elements
• The composition of these elements into progressively larger subsystems
• The architectural style embraced by the software architect that guides the project
In addition, software architecture is also concerned with usage, functionality, performance,
resilience, reuse, comprehensibility, economic and technological constraints and trade-offs, and
aesthetics.
One of the major challenges related to discussions concerning software architecture is that, due
to its breadth and complexity, there is no direct way to model the architecture as such in order to
前言
剩余67页未读,继续阅读

















安全验证
文档复制为VIP权益,开通VIP直接复制

评论0