第五版《面向对象的分析与设计：UML方法》详解

2星需积分: 9 2 浏览量更新于2024-07-20 4 收藏 3.3MB PDF 举报

《系统分析与设计：面向对象的方法与UML第五版》是由Dennis、Wixom和Tegarden合著的一本教材，专注于将学生带入实际的系统分析与设计（SAD）实践，同时传授未来所需的核心技能。该书强调动态性，让学生不仅阅读理论，还能理解和应用到实际项目中，解决系统开发过程中的问题。本书分为三个部分：分析建模、设计建模以及建设、安装和运行。在分析建模部分，章节1介绍了项目管理的基础，接着从确定需求（Chapter 3）、业务流程和功能建模（Chapter 4），到结构建模（Chapter 5）和行为建模（Chapter 6）逐步深入，帮助学生掌握分析方法和技巧。设计建模部分（Chapter 7至Chapter 11）则转向系统的设计阶段，包括类和方法设计、数据管理层设计、人机交互层设计，以及物理架构层设计。 UML（统一建模语言）贯穿全书，提供了一套标准化的工具和框架，使得学生们能够在可视化环境中进行模型构建和分析。《可见分析师》（Visible Analyst）作为一个互动式的教学工具，让学生在实践中掌握动态规则、一致性检查、变更管理以及跨IT项目的集成问题。通过这个软件，学生可以快速入门，只需两分钟即可安装，并有机会享受33%的折扣购买。该书提供的资源还包括最新版本的《可见分析师》学生版软件、教程、预加载的示例项目，以及网络研讨会资源，如“如何”和技术指导。注册的学生还可以通过support@visible.com获得电子邮件支持，确保他们在学习过程中得到及时的帮助。《系统分析与设计：面向对象的方法与UML第五版》是一本既理论扎实又注重实践的教材，适合准备成为业务或数据架构师、分析师、设计师和模型师的学生，通过实际操作和理论结合的方式，为他们的IT职业生涯打下坚实基础。

A  C  P

S 322

C  322

Chapter 9

Data Management Layer

Design 326

I 326

O P F 327

Sequential and Random Access Files 327

Relational Databases 330

Object-Relational Databases 332

Object-Oriented Databases 332

NoSQL Data Stores 333

Selecting an Object Persistence Format 335

M P D O  O

P F 337

Mapping Problem Domain Objects to an

OODBMS Format 338

Mapping Problem Domain Objects to an

ORDBMS Format 341

Mapping Problem Domain Objects to a

RDBMS Format 344

O R-B O

S 346

Optimizing Storage E ciency 347

Optimizing Data Access Speed 351

Estimating Data Storage Size 356

D D A  M

C 357

N R  D

M L D 360

V  V  D

M L 361

A  C  P

S 362

C R 362

Chapter 10

Human–Computer Interaction

Layer Design 367

I 367

P  U I D 368

Layout 369

Content Awareness 369

Aesthetics 370

User Experience 371

Consistency 371

Minimizing User E ort 372

U I D P 372

Use Scenario Development 373

Navigation Structure Design 375

Interface Standards Design 376

Interface Design Prototyping 377

Interface Evaluation 380

Common Sense Approach to User

Interface Design 382

N D 383

Basic Principles 383

Types of Navigation Controls 384

Messages 386

Navigation Design Documentation 387

I D 387

Basic Principles 387

Types of Inputs 390

Input Validation 391

O D 392

Basic Principles 392

Types of Outputs 394

Media 394

M C  U I

D 395

S M  U I

D 398

G, M-D I

V,  I

E 400

Games, Gami cation, and User Interface

Design 400

Multidimensional Information Visualization

Design 402

User Interface Design and Immersive

Environments 404

I  C I  U

I D 406

Multilingual Requirements 406

Color 407

Cultural Di erences 407

N R A H-

C I L

D 410

A T C A P

S 411

C  411

xiv Contents

Chapter 11

Physical Architecture Layer

Design 418

I 418

E   P A

L 419

Architectural Components 419

Server-Based Architectures 420

Client-Based Architectures 420

Client–Server Architectures 421

Client–Server Tiers 422

Selecting a Physical Architecture 424

C C 426

U C   I

 T 428

G IT 431

I D 432

Deployment Diagram 432

Network Model 434

H  S S

S 438

N R  P

A L D 440

Operational Requirements 441

Performance Requirements 442

Security Requirements 444

Cultural and Political Requirements 447

Synopsis 448

V  V  P

A L 449

A  C  P

S 450

C R 450

■ PART THREE

CONSTRUCTION, INSTALLATION,

AND OPERATIONS 455

Chapter 12

Construction 456

I 456

M P 457

Assigning Programmers 457

Coordinating Activities 458

Managing the Schedule 458

Cultural Issues 460

D D 462

Types of Documentation 463

Designing Documentation Structure 463

Writing Documentation Topics 465

Identifying Navigation Terms 465

D T 467

Testing and Object Orientation 468

Test Planning 469

Unit Tests 471

Integration Tests 475

System Tests 476

Acceptance Tests 477

A  C  P

S 478

C R 478

Chapter 13

Installation and

Operations 481

I 481

C I  I

T A 483

C 485

Conversion Style 486

Conversion Location 486

Conversion Modules 487

Selecting the Appropriate Conversion

Strategy 488

C M 489

Understanding Resistance to Change 490

Revising Management Policies 491

Assessing Costs and Bene ts 492

Motivating Adoption 493

Enabling Adoption: Training 495

P-I A 497

System Support 497

System Maintenance 498

Project Assessment 500

A  C  P

S 502

C R 502

I 507

Contents xv

Chapter 1 introduces the systems development life cycle (SDLC), the fundamental four-

phase model (planning, analysis, design, and implementation) common to all information

systems development projects. It describes the evolution of system development method-

ologies and discusses the roles and skills required of a systems analyst.  e chapter then

overviews the basic characteristics of object-oriented systems and the fundamentals of

object-oriented systems analysis and design and closes with a description of the Uni ed

Process and its extensions and the Uni ed Modeling Language.

OBJECTIVES

■

Understand the fundamental systems development life cycle and its four phases

■

Understand the evolution of systems development methodologies

■

Be familiar with the di erent roles played by and the skills of a systems analyst

■

Be familiar with the basic characteristics of object-oriented systems

■

Be familiar with the fundamental principles of object-oriented systems analysis

and design

■

Be familiar with the Uni ed Process, its extensions, and the Uni ed Modeling

Language

INTRODUCTION

The systems development life cycle (SDLC) is the process of understanding how an infor-

mation system (IS) can support business needs by designing a system, building it, and

delivering it to users. If you have taken a programming class or have programmed on

your own, this probably sounds pretty simple. Unfortunately, it is not. A 1996 survey by

the Standish Group found that 42 percent of all corporate IS projects were abandoned

before completion. A similar study conducted in 1996 by the General Accounting Office

found 53 percent of all U.S. government IS projects were abandoned. Unfortunately,

many of the systems that are not abandoned are delivered to the users significantly late,

cost far more than planned, and have fewer features than originally planned. For exam-

ple, IAG Consulting reports that 80 percent of the projects were over time, 72 percent

were over budget, and 55 percent contained less than the full functionality; Panorama

Consulting Solutions reports that 54 percent of the ERP projects were over time, 56 percent

were over budget, and 48 percent delivered less than 50 percent of the initial bene ts;

andan IBM study reports that 59 percent of the projects missed one or more of on time,

within budget, and quality constraints.

Although we would like to promote this book as

a silver bullet that will keep you from IS failures, we readily admit that a silver bullet that

guarantees IS development success simply does not exist. Instead, this book provides you

CHAPTER 1

Introduction to Systems

Analysis and Design

2 Chapter 1Introduction to Systems Analysis and Design

with several fundamental concepts and many practical techniques that you can use to

improve the probability of success.

 e key person in the SDLC is the systems analyst, who analyzes the business situation,

identi es opportunities for improvements, and designs an information system to implement

them. Being a systems analyst is one of the most interesting, exciting, and challenging jobs

around. Systems analysts work with a variety of people and learn how they conduct business.

Speci cally, they work with a team of systems analysts, programmers, and others on a com-

mon mission. Systems analysts feel the satisfaction of seeing systems that they designed and

developed make a signi cant business impact, knowing that they contributed unique skills to

make that happen.

However, the primary objective of a systems analyst is not to create a wonderful sys-

tem; instead, it is to create value for the organization, which for most companies means

increasing pro ts (government agencies and not-for-pro t organizations measure value

di erently). Many failed systems have been abandoned because the analysts tried to build a

wonderful system without clearly understanding how the system would  t with an organi-

zation’s goals, current business processes, and other information systems to provide value.

An investment in an information system is like any other investment.  e goal is not to

acquire the tool, because the tool is simply a means to an end; the goal is to enable the

organization to perform work better so that it can earn greater pro ts or serve its constit-

uents more e ectively.

 is book introduces the fundamental skills a systems analyst needs.  is pragmatic book

discusses best practices in systems development; it does not present a general survey of systems

development that covers everything about the topic. By de nition, systems analysts do things

and challenge the current way that organizations work. To get the most out of this book, you

will need to actively apply to your own systems development project the ideas and concepts in

the examples.  is book guides you through all the steps for delivering a successful informa-

tion system. By the time you  nish the book, you won’t be an expert analyst, but you will be

ready to start building systems for real.

THE SYSTEMS DEVELOPMENT LIFE CYCLE

In many ways, building an information system is similar to building a house. First, the house

(or the information system) starts with a basic idea. Second, this idea is transformed into a

simple drawing that is shown to the customer and re ned (o en through several drawings,

each improving on the last) until the customer agrees that the picture depicts what he or she

wants.  ird, a set of blueprints is designed that presents much more detailed information about

thehouse (e.g., the type of water faucets or where the telephone jacks will be placed). Finally,

the house is built following the blueprints, o en with some changes directed by the customer

as the house is erected.

 e SDLC has a similar set of four fundamental phases: planning, analysis, design, and

implementation. Di erent projects might emphasize di erent parts of the SDLC or approach the

SDLC phases in di erent ways, but all projects have elements of these four phases. Each phase is

itself composed of a series of steps, which rely upon techniques that produce deliverables (speci c

documents and  les that provide understanding about the project).

For more information on the problem, see Capers Jones, Patterns of So ware System Failure and Success (London:

International  ompson Computer Press, 1996); KeithEllis, Business Analysis Benchmark:  e Impact of Business

Requirements on the Success of Technology Projects (2008). Retrieved May 2014 from IAG Consulting, www.iag.biz;

H. H. Jorgensen, L. Owen, and A. Neus, Making Change Work (2008). Retrieved May 2014 from IBM, www.ibm.

com; Panorama Consulting Solutions, 2012 ERP Report (2012). Retrieved May 2014 from Panorama- Consulting.com.

剩余543页未读，继续阅读

ramissue

粉丝: 354
资源: 1487

第五版《面向对象的分析与设计：UML方法》详解

systems analysis and design

Systems Analysis and Design with UML Version 2.0

Systems Analysis and Design

computer-architecture-a-quantitative-approach-solution-for-5th-edition

analysis with an introduction to proof, 5th

校园交互式导识系统用户体验设计研究英文参考文献

列举五篇基于STM32的智能室内安全监控系统的外文参考文献

COMPUTER ORGANIZATION AND DESIGN.pdf

2020后计算机网络自顶向下方法文献

学生社团管理系统外文参考文献

最新资源