systems analysis and design

Download Systems Analysis And Design

If you can't read please download the document

Upload: hoangtuyen

Post on 08-Dec-2016

291 views

Category:

Documents


31 download

TRANSCRIPT

Systems_Analysis_And_Design__CRC_Press_1998_/Davis & Yen - Systems Analysis And Design [CRC Press 1998]/about.htmltocPreface

Purpose

As the title implies, The Information System Consultants Handbook: Systems Analysis and Design, was written for professional systems analysts, system designers, and information system consultants.

The premise is simple. If you are an information system professional, you often work with existing documentation and are frequently assigned to a new system development project in midstream, after considerable work has already been done. In both cases you are likely to encounter unfamiliar documentation, tools, techniques, and methodologies. The schedule is (always) tight, so you must quickly get up to speed and begin contributing. This book is written to help you quickly get up to speed.

Assumed background

The Information System Consultants Handbook: Systems Analysis and Design assumes that you have a firm grasp of basic information processing technology and that you have had some experience analyzing and designing information systems. Consequently, you understand the underlying principles. The material contained in this book builds on those principles.

Content

The book is organized into eight parts:

Principles

Information gathering and problem definition

Project planning and project management

Systems analysis

Identifying alternatives

Component design

Testing and implementation

Operation and maintenance

Except for Part I, which reviews basic underlying principles, the parts correspond to the primary stages in the system development life cycle.

Each of the 82 chapters covers a single tool, technique, set of principles, or methodology and contains the following major topics:

Contents A list of the chapters key topics.

Purpose A brief, single-paragraph statement of the chapters purpose and content.

Strengths, weaknesses, and limitations.

Inputs and related ideas Things you must know before using the tool; links to other related chapters in this book.

Concepts Explanations, in-context definitions, examples, and so on.

Key terms An alphabetized list of the chapters key words with definitions.

Software A list of programs and other software resources that support the tool or technique.

References Citations, web pages, and suggestions for additional reading.

Clearly, it is impossible to fully cover every detail of 82 different systems analysis and design tools, techniques, principles, and methodologies in a single volume; complete books have been written on virtually every topic in this book. In selecting the material to cover, we relied on Paretos law (Chapter 11), sometimes called the 80 : 20 rule. For most tools, techniques, principles, and methodologies, knowledge of a relatively small subset (perhaps 20 percent) of the underlying concepts and terminology is sufficient to understand the lions share (perhaps 80 percent) of the topics functionality. Our objective was to identify and clearly explain that crucial 20 percent.

Features

The reference value of the book is enhanced by several features, including:

Contents in brief A list of chapter titles.

Detailed contents A complete listing of the chapters contents at the beginning of each chapter.

Glossary A consolidated list of key terms from all the chapters, with chapter references.

Index

Trademarks A list of sources for all the software products referenced in this book.

Chapter cross-references Each chapter contains hyperlink-like references to other related chapters.

References The end-of-chapter references suggest sources for further in-depth study of the topic.

Note that the chapters are written to stand on their own, so, except perhaps for the specific topics mentioned in Inputs and related ideas, you can go directly to the material you actually need.

We enjoyed preparing this book. We hope you find it useful.

toc

Systems_Analysis_And_Design__CRC_Press_1998_/Davis & Yen - Systems Analysis And Design [CRC Press 1998]/about_author.htmltocAuthors/Editors

William S. Davis Professor of Decision Sciences and Management Information Systems, Miami University, Oxford, OH. Professor Davis is the author of thirty textbooks on various computer-related topics.

Dr. David C. Yen Department Chair and Professor of Decision Sciences and Management Information Systems, Miami University, Oxford, OH. Dr. Yen is an experienced researcher and the author of numerous professional journal articles.

Contributors

Dr. John Skip BenamatiDepartment of Decision Sciences and Management Information SystemsMiami UniversityOxford, Ohio

Dr. Bruce L. BowermanDepartment of Decision Sciences and Management Information SystemsMiami UniversityOxford, Ohio

Dr. Michael S. BroidaDepartment of Decision Sciences and Management Information SystemsMiami UniversityOxford, Ohio

Dr. David C. HaddadProfessor and DeanSchool of Applied SciencesMiami UniversityOxford, Ohio

Dr. Timothy C. KrehbielDepartment of Decision Sciences and Management Information SystemsMiami UniversityOxford, Ohio

Dr. Neil B. MarksDepartment of Decision Sciences and Management Information SystemsMiami UniversityOxford, Ohio

Richard T. OConnellDepartment of Decision Sciences and Management Information SystemsMiami UniversityOxford, Ohio

Dr. Eleni PratsiniDepartment of Decision Sciences and Management Information SystemsMiami UniversityOxford, Ohio

Dr. T. M. RajkumarDepartment of Decision Sciences and Management Information SystemsMiami UniversityOxford, Ohio

Maria ScottSoftware ArchitectsColumbus, Ohio

Dan Michael TerrioDirectorP&G Center and SBA TechnologiesRichard T. Farmer School of Business AdministrationMiami UniversityOxford, Ohio

Acknowledgements

Jerry Papke was responsible for signing this project. Enjoy your retirement, Jerry. Suzanne Lassandro and Sue Zeitz managed the production process, and Jane Stark was our marketing manager. Additionally, we would like to acknowledge the contributions of the rest of the editorial, production, and marketing staff at CRC Press.

Portions of this book were derived from or based on three titles previously published by William Davis:

Business Systems Analysis and Design, Wadsworth, Belmont, CA, 1994.

Systems Analysis and Design: A Structured Approach, Addison-Wesley, Reading, MA, 1983.

Tools and Techniques for Structured Systems Analysis and Design, Addison-Wesley, Reading, MA, 1983.

Finally, we would like to thank the contributors, who are listed on a separate page.

William S. DavisDavid C. Yen

toc

Systems_Analysis_And_Design__CRC_Press_1998_/Davis & Yen - Systems Analysis And Design [CRC Press 1998]/appendix-a.htmltocTrademarks

The following trademarks are referenced in this book.

Company or OrganizationProduct or Products

ACCPAC InternationalCA-Clipper

Acius4th Dimension

Adobe Systems, Inc.Adobe Acrobat Read

Allaire, LLCCold Fusion

Alpha Software CorporationAlpha Four

America OnLineAOLPress

Apple CorporationMacintosh, QuickTime Viewer

Applied Business TechnologyProject Management

Workbench

Applied Computer TechnologyITE, SDTF

Andersen ConsultingFoundation

Arity CorporationArity Prolog

Artificial Intelligence Corp.Intellect

Azor Inc..FERRET

Borland InternationalDbase, Turbo Prolo

Bullseye Testing TechnologyC-Cover

Carnegie Mellon UniversityHEARSAY II, HSRL, KBS, IMS,

ISIS-II, OPS83, SRL+

ClarisFilemaker Pro .

Client/Server Solutions Inc.Benchmark Factory

Computer Associates International, IncCA-SuperProject

Compuware CorporationQARun, QAStress

Consumers UnionConsumer Reports

Control Data CorporationSCOPE

Corel CorporationParadox, Quattro Pro

WordPerfect

Decision Engineering, Inc.Crystal Ball

Dell Computer CorporationDimension

Diamond Optimum Systems, Inc.VCS-UX

Digital Equipment CorporationCALLISTO, Cohesion

Dragon SystemsNaturally Speaking

Ganymede SoftwareChariot

Expert Systems InternationalAdvisor-2, ESP Advisor,

Prolog-2

EXSYS, Inc.EXSYS Professional

Frey Associates, Inc.Spock

Goldon Hill ComputersCommon Lis

Helicon, Inc.Expert-II

Hewlett PackardSoftbench

Imperial College, LondonAPES

Inference CorporationART, ART-IM

Information Builders, Inc.FOCUS, Level 5

InsetHiJaak

Integrated Data Management SystemsIDMS

IntellicorpKEE

Intelligence EnvironmentsCrystal

IntelligenceWare, Inc.Auto-intelligence

Intelligent Terminal Ltd.Expert Ease

International Business Machines CorpAD/Cycle, CMVC, DART,

DB2, ISAM, SMF, ViaVoice

Gold, VSAM

International Microcomputer Software, Inc.Formtool 97

IntersolvExcelerator II, PVCS

IPLAdaTEST

Jetform CorporationJetform Design

Joint Photographic Experts Groupjpeg

Knowledge Garden, Inc.KnowledgePro

Learning Company, TheForms Designer

LogicWorksBPWIN, ERWIN, OOWIN

Lotus Development CorporationApproach, Word Pro,

Lotus 1-2-3, Lotus Notes

MacromediaShockwave Player

Massachusetts Institute of TechnologyARS, SYN, WAMPUS

Mathematica, Inc.RAMIS II English

McDonnell Douglas Automation CompanySTRADIS/DRAW

Mercury Interactive CorporationAstra Sitetest, Loadrunner

MicrografxFlowcharter

Microsoft CorporationAccess, Excel, Foxpro, Front

Page, Internet Explorer (IE),

MS-DOS, Office 97

PowerPoint, Project, Visual

Basic (VBA), Visual Modeler,

Visual SourceSafe, Windows,

Windows 95, Word

Minitab, Inc.MiniTab

NETMANSYSFastBench Agent Tester

Netscape Communications CorporationNetscape

Neuma Technology CorporationSTS/CM

Neuron DataNexpert Object

Novell, Inc.Informs

OCLCWebART

Oracle CorporationDesigner, Developer 2000,

ORACLE

Palisade Corporation@RISK

ParasoftCode Wizard

Popkin SoftwareSystem Architect

PowerSoftPowerbuilder, Power-Designer

Primavera Systems, Inc.Project Manager, Suretrack

Pritsker CorporationSLAMSYSTEM

Purdue UniversitySPERIL

Quintus CorporationQuintus Prolog

Quma Software, Inc.QVCS

Radian CorporationRULEMASTER

Radview SoftwareWebexam, Webload

Rand CorporationRITA, ROSIE, ROSS

Rational Software CorporatiRational Roseon

RealNetworksReal Player

Relational SoftwareVisual Test

Rutgers UniversityExpert, SEEK, RULEWRITER

SAS Institute, Inc.SAS

Segue Software Inc.Silkperformer

Silicon Graphics, Inc.Cosmo Player

Silogic, Inc.Knowledge Workbench

Softbridge, Inc.ATF

Software Publishing CompanyHarvard Project Manager

Software ResearchTestWorks/Web

SPSS, Inc.allCLEAR

SRI InternationalPROSPECTOR

SSIGroup, Inc., TheDelphi

Stanford UniversityDART, GUIDON, MYCIN,

PECOS, RLL

Sterling SoftwareComposer

Sun Microsystems, Inc.Java, JavaScript,

SPARCworks/TeamWare

Texas InstrumentsInformation Engineering

Facility (IEF), NaturalLink

Trellix CorporationTrel

University of California, BerkleyFranz Lisp

University of EdinburghCprolog

University of IllinoisADVISE

University of MarylandKMS

University of New South WalesUNSW Prolog

University of UtahPSL

Verac CorporationOPS5

Visio CorporationVisio

Xerox CorporationINTERLISP, SMALLTALK

toc

Systems_Analysis_And_Design__CRC_Press_1998_/Davis & Yen - Systems Analysis And Design [CRC Press 1998]/book-index.htmltocIndex

A

Abrupt cutover, see Direct cutover

Abstraction, or Abstracting, 51, 264, 480, 482

Accepting state, 236

Access control matrix, 572

database software, 555, 672

method, 345, 346, 347

vector, 333, 339

Access (database software), 358

Acquisition, hardware, 328

Act fork, 456, 457, 458

Action diagram, 511518

diagram conventions, 512514

entry, 462, 463

stub, 462, 463

Action-oriented question-answer dialogue, 388, 392

Activity, 148, 149, 152, 154, 155, 156, 157, 159, 160, 162, 164, 168, 235, 236, 237, 238, 239

Activity, file access, 347

Actor, 222, 223, 224, 225, 231, 521, 531

ADA, 589, 592

Adaptability, 324, 325, 328

Adaptive maintenance, 655, 659660, 662

Adaptive routing, 433, 435

AdaTEST, 604, 612

AD/Cycle, 41, 42

Address, 333, 335, 345, 347

Adobe Acrobat Reader, 406, 413

ADVISE, 54

Advisor-2, 267

Afferent process, 22, 480, 482, 488, 496

Aggregate value, 610

Aggregation, 229230, 231, 521

Algorithm, 49, 179, 180, 185, 271, 274, 332, 333, 339, 440, 450, 455, 456, 461, 462, 465, 466, 474, 481, 486, 487, 488, 500, 504, 609

Alias, 190, 194

allCLEAR, 32, 290, 448

Alpha Four, 358, 672

Alpha test, 599600, 601

Alternative, 19, 29, 30, 34, 93, 95, 162, 186, 279284, 286, 288, 314, 504

America OnLine, 409, 413

Analogical representation, see Direct representation

Analysis, 7, 8, 12, 39, 57, 58, 88, 91, 92, 98, 175276, 280, 286, 302, 314, 317, 324, 352, 360, 362, 370, 376, 381, 388, 391, 396, 426, 432, 440, 450, 456, 462, 466, 474, 480, 486, 488, 500, 504, 512, 552, 568, 574, 578, 582, 596, 652, 658

Analysis-oriented documentation, 562

Analytic model, 134, 142

Ancestor, 335, 339

Andersen Consulting, 42

ANSI standard X3.5-1970, 287

Anti-virus software, 572, 574

AOLPress, 409, 413

APES, 54

Apple, 378, 384, 395, 396, 407, 409, 413, 563

Applet, 409, 411, 556

Application analysis, 326, 328

based documentation, see Execution-oriented documentation

entity diagram, 27, 30

function, 27

generator (code generator, generator, program generator), 39, 243, 245, 247, 248, 250

Applied Business Technology, 158, 164

Applied Computer Technology, 603, 612

Approach, 358, 672

Arc, 338, 339

Archive (History file), 345, 349, 669

Arity Prolog, 54

Array, 332, 333, 339

Arrival rate, 642, 645, 649

ARS, 54

ART, 54

ART-IM, 267

Artificial intelligence, 48, 546

Artificial Intelligence Corporation, 549

A-specs, see System/segment specifications

Assignable cause variation, 72, 74, 75, 76, 77

Assistance dialogue, 388, 392

Association, 226, 227229, 231, 526, 531, 590

Assumption, 26, 223

Assumption building, 51, 265

Astra SiteTest, 604, 612

Asymmetrical relationship, 229, 230

Asynchronous event, 488, 586, 587, 588, 589, 590

ATF, 603, 612

@RISK, 143

Attribute, 12, 27, 45, 191, 193, 196, 203, 205, 206, 210, 212, 214, 221, 222, 226, 227, 230, 339, 344, 349, 353, 362, 530

Audit (Auditing), 380, 573, 601, 626627, 628, 630, 631, 655, 660 test, 600, 601

trail, 626, 627

Authentication, 572, 574

Author, inspection, 169, 170, 171, 172

Auto-intelligence, 267

Automated system, 579

Automation boundary, 177, 279284

Availability requirements analysis, 426, 428

Azor, Inc., 603, 612

B

B-specs, see System/segment design document

Back end, 39, 608

Backtracking, 265, 266, 570, 608, 610

Backup, 326, 328, 345, 349, 572, 617

Backup and recovery, 668, 669, 671

Back-up file, 345, 349

Backward chaining, 262, 266, 267

Backward pointer, 334

Balance, 176, 185, 186

Balanced data flow diagram, 186

Balanced multi-way tree (B-tree), 336

Balk (Balking), 142, 648, 649

Baseline, 653, 654, 655

Batch, 361, 365, 480, 488, 586means approach, 141

processing, 347, 579580, 582

BCNF, see Boyce-Codd normal form

Behavioral requirement, 271, 275

Behavior-oriented paradigm, 112, 114

Benchmark, 328, 600, 636, 639, 654, 655, 661

Benchmark Factory, 604, 612

Benefit, 26, 29, 293, 294, 295, 296, 297, 298

Best route algorithm, 434, 435

Beta site, 619, 620

Beta test, 600, 601

Bias, 66, 67, 68

Bid (Bidding), 313, 314, 317, 328

Bi-directional flow, 399, 400

Bi-directional search, 262

Binary tree, 336, 339

Binding time, 493, 496

Biometric device, 571, 572, 574

Birth, 578, 579, 582

Black box, 274, 275, 288, 316, 487, 500, 504

Black box testing, 597, 599, 602

Blind search, 51, 262, 263, 266

Block, data, 345, 349

Block, logic, 466, 467468, 475, 493496

Bottleneck (Choke point), 427, 428, 432, 435, 420

Bottleneck analysis, 326, 329, 427, 586, 643, 649, 652

Bottom-up, 25, 26, 31, 106, 107, 109, 241, 242, 383 design, 581, 582

testing, 597, 599, 602

Boundary, 5, 7, 27, 176, 177, 180, 581, 582analysis, see Range constraint analysis clash, 492

object (Interface object), 521, 522, 525, 527, 531

Boyce-Codd normal form (BCNF), 213214, 216

BPWIN, 42

Bracket, 512, 515, 516

Brainstorming, 82, 98, 101, 128, 129

Branch, 129, 130, 131, 335, 336, 339, 450, 496

Branch analysis, 610

Breadboarding, 249

Breadth (Span-of-control), 411, 480, 482, 491

Breadth search, 51, 52, 262, 266

Bridge, 420, 428, 554, 556

Broadcast routing, 434, 435

Browser (Browsing), 40, 406, 408, 409, 410, 411

B-tree, 336

Bug, 596, 606607, 610, 659, 661

Bullseye Testing Technology, 604, 612

Burn-in period, 601, 602

Business function-task analysis, 307312

Business systems planning approach, 308

Bus network, 419, 420, 423

Busy hour analysis, 426

Button bar, 396, 400

C

C (C++), 222, 589, 604, 612

Calculated value, 355, 356

Call, 487, 491, 508

Callback, 572, 574

CALLISTO, 537

Candidate key, 213, 214, 216

Capability maturity model, 221, 231

Cardinality, 27, 31, 197199, 203, 228

Carnegie Mellon University, 537

CASE (Computer-aided software engineering), 14, 3342, 100, 176, 182, 187, 190, 194, 204, 233, 239, 245, 247, 248, 249, 250, 251, 258, 276, 284, 357, 374, 383, 384, 392, 400, 401, 481, 502, 510, 533, 565, 666, 667, 672

Case structure, 440, 450, 451, 470, 480, 493, 499, 500, 507508, 512

Cash flow, 295, 296, 297

Casual side, 129

CA-SuperProject, 149

Cause, 87, 88

Cause-and-effect diagram, 72, 82, 127132

C chart, 76

C-Cover, 604, 612

Census, 64, 68, 118, 120, 124

Centralized management, 580

Centralized routing, 432433, 435

Chaining, 348, 349

Change control procedures, 37, 598, 602

Change in state, 586, 588

Chariot, 603, 612

Checkpoint, 669, 671

Check sheet, 72, 82, 128

Child (Son), 274, 275335, 336, 339, 352, 353, 356, 487, 496, 500

Choke point, see Bottleneck

Circular linked list, 334, 339

Class (Object type), 39, 40, 44, 45, 46, 220, 227, 230, 520, 522, 530, 531structure (Class hierarchy), 230, 541

structure diagram, 36, 226, 231

Class, Responsibilities and Collaborations technique (CRC technique), 522525, 531

Client, 404, 410, 428

Client/server, 220, 404, 412, 428, 521, 522

Client/Server Solutions, Inc., 604, 612

Clipper, 557

Close, 345, 347

Closed question (Closed-ended question), 60, 121, 122, 124

CMVC, 42

COCOMO model, 37

Code generator, 14, 15, 36, 39, 40

Code-to-code translator, 548

Code Wizard, 604, 612

Coding error, 607, 610

Coding standard, 630, 658

Coding time, 493

Cohesion, 22, 23, 41, 42, 480, 482, 492493, 496, 500, 502

Coincidental cohesion, 492, 496

Cold Fusion, 555, 557

Collaboration, 522, 531

Collaboration diagram, 526, 527, 529, 530, 531

Collision, 348, 349

Collision detection, 434, 435

Column header, 370, 372, 373, 374

Command bar, see Menu bar

Command-based interface, 377, 383

Command error, 607

Command-oriented documentation, 561, 565

Commercial software package, 551558

Commoncause variation, 72, 73, 75, 77

LISP, 54

sense knowledge, 260, 265

subprocedure, 514

Common-environment coupling, 493, 496

Communicational cohesion, 492, 496

Communication controls, 631

Comparator, 37, 572573, 575

Compatibility, 324

Compatibility analysis, 610, 611

Competitive procurement, 270, 313319, 426, 427

Compilation time, 493

Compiler system, 548

Complex star network, 417, 423

Component design, 323592

Composer, 42

Composite, 22, 176, 177, 180, 181, 182, 185, 186, 190, 191, 193, 194, 203, 210, 216, 257, 315, 344, 332, 354, 356, 500

Composite key, see Concatenated key

Composition, 229, 232

Compression, 411, 412

Computer-aided software engineering, see CASE

Computer Associates, 158, 164

Computer software configuration item (CSCI), 317, 319

Compuware, 603, 604, 612

Concatenated key, 210, 211, 214

Concentration point determination, 427, 428

Concept, 51, 52, 226, 227, 232, 538

Conceptualdatabase, 354355, 356, 667

database design, see Logical database design.

model, 226231, 232, 525, 526, 530

Conceptualization phase, 51

Concurrency, 587, 589, 590control, 589, 590, 670671

relationship, 516

Condition, 257, 442, 451 entry, 462, 463

stub, 462, 463

Conditional data element, 257

Conditional logic, 489, see also Decision, Selection

Confidence interval, 65, 66, 68, 137

Configurationanalysis, 326, 329

approval board, 630, 631, 652, 655

audit, 655

builder, 37

control, 653655

item, 185, 186, 271, 273, 275, 316, 317, 319, 488, 496, 653, 655

item level, 185, 186, 187, 271, 273, 274, 275, 316, 319

management, 35, 37, 626, 651656, 661, 662

management planning, 652653

object, 653, 655

reporting, 655

Configuration Management Version Control (CMVC), 656, 663

Connection diagram, 427, 428

Connectivity, 324, 329

Connector, 287, 441, 444, 446

Consistency, 382

Consistency check, 40

Constantine, L., 18

Constraint, 26, 29, 108, 109, 271, 587, 597

Constraint requirement, see Design requirement

Constraints and goal technique, 51

Construction, 221, 222

Construction phase, 249, 250

Content, 410411

Content coupling, 493, 496

Context diagram (Level 0 data flow diagram), 176, 180, 181, 187, 225

Continuous simulation, 135, 142

Control, 5, 8, 242, 324, 625633analysis, see Volume analysis

break (Control breaks report), 347, 370, 371, 374

center, 22

chart, 64, 7179, 82, 128, 626, 628, 629, 636

couple, 500, 502

coupling, 493, 496

field, 500

flow, 21, 23, 287, 289, 499, 500, 507

integration, 39

limits, 72, 74, 77, 78

module, 481, 597

object, 521, 522, 525, 531

structure, 22, 274, 466, 474, 480, 482, 486, 487492, 496, 502, 503, 504506

structure design, 488490

structure evaluation, 490492

total, 627628, 631

Control Data Corporation, 348

Control, system, 64, 73, 537, 542

Convergence, 589, 591

Conversational transaction, 670, 671

Coordinate module, 22

Core problem, 107, 108

Core page, 407, 410, 411, 412

Corrective maintenance, 659, 660, 662

Correctness proof assistant, 37

Cosmo Player, 406, 413

Cost, 26, 29, 293, 294estimate, 19, 88, 160, 294, 427

reduction, 294

Cost/benefit analysis, 19, 29, 92, 93, 98, 280, 293299, 302, 426, 427, 552, 568, 574, 636

Cost/time tradeoff, 160, 163

Coupling, 22, 23, 480, 482, 493, 496, 499, 500, 502

Coverage, 120

CPM, see Critical Path Method

C Prolog, 54

Cracker, 569, 575, 630

Crashcutover, see Direct cutover

mode, 159, 160, 161, 162, 164

mode analysis, 152, 157, 159165

time, 160, 161, 162

CRC technique, see Class, Responsibilities and Collaborations technique

Critical path, 152, 156, 157, 159, 160, 162, 164, 339

Critical Path Method (CPM), 147, 151, 152, 157, 159, 160, 164

Critical success factors paradigm, 113, 114

Cross referencing, data flow diagram, 183

Crystal, 267

Crystal Ball, 143

Cum-line, 83

Cumulative count, 83, 84

Cumulative percent, 83, 84

Customization, 551558

Cutover, 618619, 620, see also System release

Cutover phase, 249, 250

Cycle, 338, 339

D

DART, 536

Data, 5, 7, 11, 12, 45, 220, 221, 260, 265, 289, 307, 308, 309, 344, 369, 370, 376accuracy, 360, 361, 362

administration, 356, 666, 667, 671

analysis, 12, 310, 609, 610

capture, 359, 360, 361, 365, 366

communication, 325, 416, 423, 428

conservation, principle of, 179, 183

couple, 500, 502

coupling (Input-output coupling), 493, 496

definition, 189, 191

dictionary, 12, 14, 18, 19, 23, 29, 31, 177, 181, 182, 183, 185, 186, 189194, 203, 205, 206, 271, 210, 221, 231, 233, 344, 349, 352, 354, 356, 358, 360, 362, 376, 474, 666, 667, 672

dictionary, contents of, 191

element, 7, 22, 176, 177, 181, 183, 185, 189, 190, 191, 194, 204, 206, 216, 257, 271, 309, 332, 339, 344, 349, 354, 362, 376, 474, 500, 507, see also Attribute

entry, 360, 382, 365, 366, 388, 390, 629

error, 607, 611

flow, 19, 21, 23, 176, 177, 178, 179, 180, 183, 187, 287, 289, 370, 376, 481, 499, 500, 507, 508

flow analysis, 433

flow diagram, 14, 18, 19, 22, 23, 36, 98, 106, 175188, 190, 196, 210, 221, 280, 281, 284, 344, 360, 362, 370, 376, 399, 480, 481, 504, 561

hierarchy, 344

integrity, 242, 629, 631, 667, 668, 671

interface, 355

item, 331, 332, 333

model, 12, 15, 195

name, 190, 206, 257, 474

normalization, 12, 14, 15, 106, 176, 177, 190, 196, 209217, 254, 344, 352, 354, 355, 512, 658, 666

redundancy, 12, 15, 26, 190, 210, 355

relationship, 12, see also Relationship

requirement, 12, 19, 351, 352, 355

store, 177, 178, 179, 181, 183, 185, 186, 187, 284

structure, 7, 22, 26, 29, 31, 181, 183, 187, 189, 191, 194, 196, 204, 205, 206, 209, 216, 253, 254, 255257, 271, 274, 331341, 344, 349, 356, 362, 474, 486, 488489, 507, 536, 538, see also Composite

symbol, 441, 446

transform analysis, 600

use analysis, 14

volume analysis, 609

Database, 8, 12, 14, 49, 176, 186, 190, 194, 195, 196, 260, 261, 332, 344, 347, 349, 351358, 370, 379, 546, 552, 554, 555, 556, 580, 589action, 515516

administration, 354, 356, 358, 665673

administration roles, 666667

design, 209, 210, 324, 351358, 578, 666, 667

design methodology, 354356

integrity, 354, 355, 356, 570

operation and control, 667

planning, 666

software, 243, 245, 251, 374, 658, 659

standards, 667

structure, 352354

Database Management System (DBMS), 194, 274345, 347, 355, 356, 671

Data control language (DCL), 358

Data definition language (DDL), 210, 358

Data-driven, 25, 26, 31, 196, 581, 582

Data Encryption Standard (DES), 573, 575

Data manipulation language (DML), 358

Data-oriented, 106, 107, 109, 261

DBASE, 358, 557, 672

DBMS, see Database Management System

DB2, 358, 672

Deadlock, 338, 588, 591, 671

Death, 579, 582

Debug (Debugging), 8, 486, 499, 606, 608, 611

Debugger, 589

Debugging system, 537, 542

DEC, see Digital Equipment Corporation

Decision, 441, 442, 446, 456, 457, see also Selectionlogic, 467, 468469, 475476

support function, 29, 31

table, 18, 440, 450, 456, 461463, 466, 474, 480, 486, 512, 560

test, 608, 611

tree, 18, 440, 450, 455459, 462, 466, 474, 480, 486, 512, 560

Decision support system (DSS), 112, 379, 580, 582

Decomposition, 19, 29, 105, 106, 109, 179, 184, 185, 221, 257, 480, 482, see also Functional decomposition

Defect, 638, 639

Degree of automation, 579, 581, 582

Delphi, 557

Demand analysis, 590

Demand report, 372, 374

Demand/utilization analysis, 327, 329

DeMarco, T., 18, 178

Deming, W. E., 72

Denormalization, 355, 357

Department of Defense, 270, 314, 315, 653

Dependency relationship, 154, 155, 210, 601, 608

Depth, 411, 412, 491

Depth search, 51, 52, 262, 266

DES, see Data Encryption Standard

Descendent, 335, 339

Design, 7, 8, 12, 39, 52, 88, 221, 222, 243, 247, 270, 280, 286, 314, 323592, 596, 597, 626, 652, 658and construct, 382383

class diagram, 520, 530, 531

pattern, see Pattern

requirement (Constraint requirement), 271, 275

system, 536, 542

Destination (Sink), 177, 178, 180, 181, 185, 187, 376

Detaildiagram, 507508, 510

line, 370, 371, 374

report, 372, 374

Determinant, 213, 214, 216

Deterministic model, 142

Deterministic state transition diagram, 236, 239

Development, 6, 8, 52, 578, 582and maintenance, 658659

costs, 294, 295, 296, 297, 298

real-time system, 589590

Device driver, 345, 346

Diagnosis-oriented documentation, 561, 565

Diagnosis system, 536, 542

Diagrammer, 38

Dialogue, 186, 243, 376, 379, 383, 387393, 396, 400, 555design, 360, 387393, 398, 404, 409

design issues, 390391

design process, 391392, 400

response time, 391

types, 388389, 392

Diamond Optimum Systems, Inc., 656, 663

Digital Equipment Corporation (DEC), 41, 42, 537

Digraph (Directed graph), 338, 339

Directaccess (Random access), 347348, 349, 580

cutover (Abrupt cutover, Crash cutover), 618, 619, 620

representation (Analogical representation), 541, 542

user interface, 376, 383

Directed graph (Digraph), 338, 339

Directory, 345, 349

Disaster plan, 572

Discounting, 294, 295, 296, 297, 298, 299

Discrete simulation, 134, 135, 138142

Dispatcher, 588, 589, 591

Display screen, see Screen

Distributeddatabase, 435

environment, 415, 416

management, 580, 582

routing, 433434, 435

Distribution control, 628, 631

Diverge (Divergence), 154, 157, 589, 591

Division/remainder method, 348

Documentation, 4, 8, 34, 36, 167, 169, 248, 427, 439, 503, 504, 509, 559566, 616, 617, 620, 652contents, 561562

control, 628, 631

tips, 562565

types, 561

Documenter, 38

DoD-STD-490, 315

DoD-STD-499, 315

DoD-STD-2167A, 314, 315317

Domain, 51, 52

DO loop, 469

Domain object, see Entity object

DO statement, 475

Double barreled question, 123

Doubly linked list, 334, 339

DO UNTIL, 442, 444, 451, 496, 512

DO WHILE, 442, 444, 451, 469, 496, 512

Dragon Systems, 384, 549

Drop-down menu, see Pull-down menu

Dummy activity, 155, 157

Dumpster diving, 569, 575

Duplicate symbol, data flow diagram, 179

Duration, 148, 149, 152, 154, 157, 160, 164

Dynamicanalyzer, 37

debugging tool, 659, 663

routing, see Adaptive routing

E

Earliest event time (EET), 152, 155, 157, 159, 160, 164

Echo (Echo printing), 365, 608, 611

Economicevaluation, 636, 639

feasibility, 92, 93, 96, 293, 294

requirement, 271, 275

Edge, 338, 339

Effect of interest, 128, 129, 131

Efferent process, 22, 480, 483, 488, 497

Efficiency, 457458, 636, 660

Electronic meeting system (EMS), 100, 379

Element analysis, 326, 329

Encapsulation, 40, 45, 46, 220

Encrypt (Encryption), 556, 573, 575, 631

End time, 148, 149

End user, 8, 19, 376, 380, 383, see also user

Enterprise analysis approach, 308

Entity, 12, 27, 29, 31, 176, 142, 191, 193, 194, 196, 197, 198, 199, 200, 201, 202, 204, 205, 206, 210, 211, 212, 213, 216, 254, 257, 339, 344, 349, 354, 357, 362diagram, 27, 31, 254, 257

object (Domain object), 520, 521, 522, 525, 527, 531

Entity-relationship diagram, 14, 26, 27, 31, 36, 98, 176, 190, 195204, 205, 206, 210, 221, 254, 257, 349, 352, 355, 504

Entrance-exit test, 608, 611

Entrypage, 407, 410, 411, 412

point, 441, 450, 493, 608

tunnel (Entry chimney), 407, 412

Environment, 35, 36, 40, 41

Environmental control, 572

Environmental issue, 271, 325326, 379380, 381

Ergonomics, 271, 380, 384, 617, 620

Error, 64, 65, 69, 72, 362, 363, 596, 659, 661checking, 40

control, 627, 631

log, 171, 172

rate, 271

report, inspection, 168

time, 391

Errors ofcoverage, 120, 124

non-observation, 118, 120, 124

observation, 118, 120, 125

Erwin, 42

ESP Advisor, 267

Estimate, 63, 64, 65, 66, 69, 303

Evaluation analysis, 661, 662

Evaluation, hardware design, 326328

Event, 45, 46, 154, 155, 156, 164, 455, 456, 458, 525, 586, 588, 589, 590, 591, 643, 649monitoring, 589

fork, 456, 459

Event-driven, 586, 588, 591

Evolutionaryapproach, 107, 108, 249, 250, 599

design (Stepwise refinement), 582, 583

prototyping, 242, 243, 249

Excelerator II, 42

Exception report, 372, 374

Exception test, 365, 366, 390, 627, 631

Executable specification language, 245, 251, 384, 393

Execution frequency, 27

Execution-oriented documentation (Application based documentation), 561, 565

Execution time, 493

Executive information system (EIS), 112, 580, 583

Existence test, 610

Exitcriteria, 3, 4, 6, 168

page, 407, 412

point, 441, 450, 608

tunnel (Exit chimney), 407, 412

Expandability, 329

Expanded use case, 222, 223, 227, 232

Experimental design, 627, 631

EXPERT, 54

Expert-Ease, 54

EXPERT-II 54

Expert system (Knowledge-based system), 4, 4754, 107, 108, 259267, 379, 535, 536, 537, 538, 542, 546, 547, 548, 578, 580, 583, 610interface, 378, 384

shell, 49, 52

types, 536537

Explanation dialogue, 388, 392

Explanation facility, 49, 52

Explode, 184, 187, 288

Exploded data flow diagram, 179, 185

EXSYS, 267

Extend, 143

Extended description, 508

Externaldocumentation, 561, 565

entity, 27

event, 586

F

Fact, 260, 261, 262

Factoring, 51, 52, 105, 106, 107, 110, 480, 483

Fast Bench Agent Tester, 603, 604, 612

Fault tolerant computer, 581, 587, 591

Feasible solution space, 264

Feasibility study, 35, 51, 57, 9196, 98, 222, 294, 302cost, 93

report, 92, 93, 95, 102, 561

Feasibility, types, 93

Feedback, 5, 7, 8, 236, 239, 243, 249, 360, 364, 383, 390, 397, 580, 586, 626, 627, 631

Feedback and refine, 383

Fence diagram, 238, 239

FERRET, 603, 612

Field, 193, 194, 339, 344, 345, 349, 353, 362, 370, 372, 373, 374

Field/record/file hierarchy, 344

Fifth normal form, (5NF) 215, 216

File, 7, 8, 14, 176, 186, 190, 193, 194, 285, 286, 332, 339, 343350, 370, 374, 580design, 209, 210, 343350, 578

name, 345, 349

organization, 346349

structure, 358, 486

Filemaker Pro, 358, 672

Filter, 357, 372

Finkelstein, Clive, 11

Fire fighting, 659, 661, 662

Firewall, 571572, 575

First normal form (1NF), 210, 216

First-order predicate logic, 537538, 542

Fishbone diagram, 127

5W analysis, 308, 311

Fixed routing, 433, 435

Flash, 410411

Flat-file database, 210, 352, 357

Float 156, see also Slack

Flow test, see Transaction test

Flowchart, see Logic flowchart

Flowcharter (ABC Flowcharter), 32, 158, 164, 186, 204, 206, 239, 258, 290, 448, 459, 463

Flowdown, 274, 275, 276

Flowline, 441, 444, 446

FOCUS, 383

Focus group, 308, 309

Folding algorithm, 348

Follow-up inspection, 171

Follow-up question, 60

Forced-choice survey, 60

Foreign key, 194, 213, 216

Form, 186, 359, 360363, 366, 376, 378, 379, 552, 555, 556design, 359, 361363, 404, 409, 560

generator, 481, 510

Form Designer, 366

Formal logic, 266

Formalization phase, 51

Format constraint analysis, 609, 611

FormTool 97, 366

Forwardchaining, 261, 262, 266, 267

engineering, 38, 41

pointer, 334

Foundation, 42

4th Dimension, 354, 672

Fourth-generation language (4GL), 4, 14, 15, 243, 245, 248, 250, 251, 383, 384, 393, 400, 401, 512, 580, 607, 658, 659

Fourth normal form (4NF), 214, 216

Foxpro, 557

Frame, 119, 125, 409410, 412, 538, 542

Frames and slots technique, 538, 541

Frameset, 409410, 412

Franz LISP, 54

Freeze (Freeze, specifications), 4, 18, 245, 654, 655

Frey Associates, Inc., 549

Front end, 555, 608

Front end routine, 552, 554, 557

Fully connected mesh network, 418, 423

Function, 26, 27, 29, 31, 222, see also Activitycohesion, 492, 497

key, 398

point model, 37

test, 602, 597, 599

Function-related error, 606607, 611

Functionaldecomposition, 106, 184, 187, 483, 486498, 499, 500, 502

dependency, 214, 216

primitive, 185, 187, 225

requirement, 271, 275, 276, 596, 597, 606

segregation, 573, 628, 630

Future projection analysis, 426, 428

Future value, 295, 299

G

Gamma test, 600, 602

Gane and Sarson, 177

Gantt chart, 38, 147150, 152, 166, 596, 601

Ganymede Software, 603, 612

Gateway, 420, 429

GDSS, see Group decision support system

Generalization, 230, 232

General system design, 324, 577584, 596

Generate and test, 105, 108, 109, 110, 480

Generator, 14, 15, 547, 548, see also Application generator, Code generator, Program generator

Generic class, 526

Generic object, 526

Geographical requirements analysis, 426, 429

Gif (Graphic interchange format), 411, 412

Global data, 185, 187, 482, 493

Glossary, 222, 231

Goal, 261, 262, 265, 266, 542driven, 51, 581, 583

programming, 434

state, 261, 262

Goal-oriented, 106, 110, 262

Goals and objectives, 11, 12, 35, 51, 113, 114, 270

Goal-seeking, 536

Good requirement, 271

Go to (GOTO), 496, 514

GPSS, 143

Gradual cutover, 619, 620

Grammar analysis system, 548

Granularity, 670, 671

Graph, 338, 339, 540

Graph base, 49, 53, 379

Graphicinput screen (Touch screen), 365, 366

interchange format, see Gif

user interface (GUI, Object oriented interface), 378, 384

Graphics display dialogue, 389, 392

Gray box testing, 597, 599, 603

Group data item, 191, see also Composite, Data structure

Group decision support system (GDSS), 100, 379, 580

Growth, 578, 583

GUI, see Graphic user interface

GUIDION, 537

H

Hacker, 569, 575, 630

Hard fact, 265

Harvard Project Manager, 158, 164

Hardware, 5, 8, 14, 273, 274, 285, 289, 323330, 376analysis, 426427, 429

design specifications, 317

error, 607, 611

interface, 287, 289

interface design, 323330, 352, 416, 578, 616, 642

monitor, 636, 639

testing, 601

Hardware configuration item (HWCI), 317, 319

Hashing, 348, 349

HEARSAY II, 536

Heuristic rule, 49, 53, 263, 264, 266

Heuristic search, 48, 51, 53, 263264, 266

Heuristics, 48, 49, 53, 260, 263, 264, 267, 541, 543

Hewlett-Packard, 42

Hierarchical database, 352353, 357

Hierarchical topology, see Tree topology

Hierarchy, 18, 108, 335, 338, 407, 487, 581, 597

Hierarchy chart, 382, 399, 428, 440, 450, 499, 500, 502, 503, 504506, 510

High-level system/segment specifications, 271272

High level use case, 222, 223, 232

Highway effect (Turnpike effect), 426, 429, 432, 435

HiJaak, 398

HIPO (Hierarchy plus Input-Process-Output), 106, 440, 450, 456, 462, 466, 474, 486, 503510, 512, 560

Histogram, 72, 82, 128

Historical data, 609, 611

History file (Archive), 345, 349

Home page, 404, 407, 408, 412

Hook, 407, 410

Host, 416, 419, 423, 429, 572

Hot key, 398, 401, 553

HSRL, 54

Html (Hypertext markup language), 406, 409, 410, 412, 413

Html editor, 409, 413

Hub, 417, 420, 427, 429

Hybridcoupling, 493, 497

testing, see Middle out testing

topology, 420

Hyperlink, 360, 378, 404, 406, 407, 408, 412

Hyperlinked screens, 365, 366

Hypertext markup language, see Html

Hypothesis space, 51, 53

Hypothetical data (Simulated data), 599, 609, 611

I

IBM, 41, 42, 97, 286, 307, 308, 348, 384, 536, 549, 636, 639, 656, 663

Icon, 287, 378, 384, 396, 397, 401, 406, 553input screen, 365, 366

window, 397, 401

Icon-based interface, 378

Identification phase, 50, 51

IDMS, 358, 672

IEEE STD-729, 315

IEEE-STD-830, 315

IEF, see Information Engineering Facility

IF-THEN-ELSE, 442, 451, 468, 475, 493, 512

Illegal data flows, 178

Implementation, 8, 14, 39, 249, 328, 560, 578, 597, 615621, 636, 652, 658guidelines, 668

IMS, 537

In-out diagram, 254255, 257

Incrementalbackup copy, 669, 672

design, 582, 583, 599

prototyping, 242, 243

Indegree, 338, 339

Independence, 181, 486, 487, 493

Index, 347, 348, 349, 355, 357

Indexed sequential file, 348349

Indirect user interface, 376, 384

Individuals chart, 76, 77

Industry analysis paradigm, 113, 114

Inference, 260, 261, 266, 267, 540, 543engine, 49, 51, 53

rule, 48

Inference-oriented technique, 260261

Infinite loop, 383, 512

Information, 6analysis, 12, 13

engineering, 4, 1116, 106, 511, 512

gathering stage, 57146, 190, 196, 254, 260, 270, 280, 285, 317, 360, 370, 376, 381, 578, 661

hiding, 482, 483

processing control, 627, 631

system, 3, 5, 6, 8, 583

system types, 580

systems strategy, 15, 308

Information Engineering Facility (IEF), 357, 672

Information-oriented paradigm, 112, 114

Information-oriented question-answer dialogue, 388, 392, 555

Informs, 366

Inheritance, 39, 40, 45, 46, 220, 230, 541

Initial state, 236, 262

Input, 5, 270, 274control, 359, 360, 365366, 627, 631

design, 324

error, 607, 611

Input-output coupling, see Data coupling

IPO chart (Input-Process-Output chart), 440, 450, 456, 462, 466, 474, 486, 503, 504, 506509, 510, 512

IPO chart, simplified, 508509

Inspection, 64, 167172, 482, 560, 564, 596, 607, 626, 630, 658process, 169171

session, 170, 171

team, 169, 171

Inspector, 169, 170, 172

Instance, 44, 191

Instruction dialogue (Systems information interface), 388, 392

Instruction system, 537, 543

Intangible, 299, 301, 303, 304, 552

Integration, 39

Integration test, 599, 603

Integrity, 354, 355

Intellect, 549

Interaction diagram, 527529

Interactive (Interactive system), 241, 242, 347, 361, 366, 410, 586

Interarrival time, 643, 645, 649

Interconnectivity, 41

Interface, 5, 8, 49, 222, 242, 249, 480, 581error, 607, 611

object, see Boundary object

requirement, 271, 275

INTERLISP, 54

Internal documentation, 561, 565

Internal rate of return, 297298, 299

International Microcomputer Software, Incorporated, 366

Internet, 325, 378, 404, 406, 412, 555, 568, 569, 571, 572

Interpretation system, 536, 543

Interpreter system, 548

Interrupt, 488, 580, 588, 589, 590, 591

Interrupt control, 627, 631

InterSolv, 42, 656, 663

Interview, 5762

Inventory control, 628, 632

Inverse operator, 262, 267

Inverted-L chart, 190, 191, 203, 205208, 210

Investment, 293, 294, 297

Invoke, 487

IPL, 604, 612

IRR function, 297, 299

ISAM (Indexed sequential access method), 348

Ishikawa diagram, 127

ISIS-II, 537

ISO R1028, 287

ITE, 603, 612

Iteration, see Repetition

Iteration, principle of, 180, 184

Iterative design approach, 249

J

JAD (Joint Application Design), 35, 64, 97103, 113, 247, 248, 249, 250, 596, 597report, 102

session, 100, 101

team, 98, 99

workbook, 100

Java, 222, 409, 410, 412, 556, 557

JavaScript, 410, 412

Jetform Design, 366

Job control language, 286

Join, 215, 216

Join dependency, 215, 216

Joint Application Design, see JAD

Joint Application Development, see JAD

Jpeg (Joint Photographic Experts Group), 411, 412

Junction test, 608, 611

Justification, 265, 267

Justification building, 51, 265, 480

K

KBS, 54

KEE, 54

Kernel, 572, 575

Key, 12, 193, 194, 206, 210, 211, 212, 213, 216, 333, 336, 339, 344, 347, 348, 349, 370, 371

Key indicator report, 372, 374

KMS, 54

Knowledge, 49, 260, 265, 267, 543acquisition facility, 49, 53

base, 49, 51, 53, 259, 267, 546, 547, 548

engineer, 48, 49, 51, 53

representation, 48, 51, 260, 535544, 616

representation techniques, 537542

Knowledge-based system, see Expert system

KnowledgePro, 267

L

LAN (Local area network), 416, 423, 429

Language parser, 543

Language-to-language system, 548

Language translation, 548

Latest event time (LET), 152, 155, 156, 157, 159, 160, 164

Layer, security, 572

Leaf (Leaf node), 335, 336, 340, 487, 497

Learning Company, The, 366

Legal data flows, 178

Legend, 506

Length constraint analysis, 609, 611

Level 0 data flow diagram, see Context diagram

Level 1 data flow diagram, 181, 183, 187, 281, 284

Level 2 data flow diagram, 184, 185, 187, 284

Level 5 Object, 267

Level identifier, 487488

Lexical analyzer, 543, 546, 548

Librarian, 37

Library control procedures, 598, 603

Library module, 487

Life, 294, 296, 299

Line monitoring, 631, 632

Link, 353, 526

Linked list, 333334, 340, 348

LISP, 54, 540, 544, 580

List, 333335, 340, 540

Littles rule, 649

Load module, 18, 22, 23

Loaded question, 123, 125

Loadrunner, 604, 612

Load time, 493

Local area network, see LAN

Local data, 185, 187

Location connectivity analysis, 14, 427, 431, 432, 435

Location implementation, see Pilot implementation

Lock and key security, 568

Locking, 589, 591, 670, 672

Log, 589, 629, 668, 672

Logicbomb, 570, 575

flowchart (Flowchart, Process flowchart), 439448, 449, 450, 456, 461, 466, 474, 480, 486, 493, 512, 560

flowchart symbols, 440441

structure, 253, 254, 257

test, 607608, 611

Logical, 7access map, 489490, 497

cohesion, 492, 497

constructs, 493496

data flow diagram, 186, 187

data structure, 29, 31, 183, 205, 206, 210, 243, 253, 254, 344, 354, 360, 370, 486, 500

database design, 354355, 356, 357

design phase, 2729, 31, 52, 521

documentation and preparation, 428

I/O, 345, 346, 347

model, 15, 19, 23, 93, 186, 242, 270, 271, 276, 279, 280, 504

record, 345, 346, 349

requirement, 315, 316

security, 572573, 575, 629630, 632

sequential processing, 347

system, 27, 176, 180

LogicWorks, 42

Loop, 257, 512back analysis, 631, 632

network, 422

test, 608, 611

Lotus Notes, 102, 251

Lotus 1-2-3, 149, 299

Lower CASE, 39, 41

Lower control limit, 74

Lower-level system/segment specifications, 273

M

Machine learning, 48, 53

Machine repair problem, 648

Macintosh, 378, 384, 395, 396, 409, 555, 563

Macro, 553, 557

Macromedia, 407, 413

Main control module, see Root

Mainline functional flow diagram, 27, 29, 31

Main problem, 108

Maintainability, 271

Maintenance, 6, 8, 34, 35, 39, 44, 64, 210, 211, 328, 486, 499, 521, 560, 574, 578, 616, 642, 652, 657663management of, 661662

standard, 662

types, 659661

Make-or-buy decision, 14, 15, 552

Management information system (MIS), 379, 580, 583

Mandatory relationship, 197

Manual procedure, 444, 466, 473, 601

Manual system, 579

Many-to-many relationship, 198, 199, 200, 201, 202, 204

Mapping function, 333, 335

Marketing requirement, 271

Martin, James, 4, 11, 248, 489, 511, 512

Master file, 344, 347, 350, 580

Material flow, 178

Mathematica, Inc., 549

Matrix, 332, 340

Maturity, 579, 583

McCabe statistics, 38, 41

McDonnell Douglas Automation Company, 502

Mean, 65, 67, 69, 644, 645

Mean time between failures (MTBF), 271, 327, 587, 590, 637, 639

Mean time to repair, 271

Mental model, 379

Menu, 377, 378, 382, 395, 396, 406, 553bar (Command bar), 396, 399, 401

builder, 243, 245, 251, 384, 393

interface, 377378, 384

Mercury Interactive Corporation, 604, 612

Merge, 154, 157, 589, 591

Merged entity diagram, 27, 31

Mesh network, 418, 432, 433

Message, 220, 221, 434, 525, 526, 527duration analysis, 426

switching, 428, 429

volume, 426

Meta-data, 191, 194

Metaphor, 408, 409, 410, 413, 563

Meta-problem, 51, 53, 106, 107, 110, 541

Meta-unit, 308

Method, 45, 46, 220, 221, 222, 226, 230, 526, 530, 531

Methodology, 3, 4, 68, 9, 11, 12, 5052, 583

Metrics, 36, 38

Micrografx, 32, 158, 164, 187, 204, 206, 239, 258, 290, 448, 454, 459, 463

Microsoft, 39, 42, 131, 378, 379, 384, 388, 389, 395, 396, 397, 400, 406, 409, 413, 554, 563, 656, 663, 660Access, 555

Excel, 136, 149, 295, 296, 297, 299, 311, 400, 660

Front Page, 409, 413

Internet Explorer, 384, 406, 413

PowerPoint, 131

Project, 149, 158, 164

Word, 388, 409, 413, 548, 553, 554

Middle out, 249, 581, 583

Middle-out prototyping, 242, 243

Middle out testing (Hybrid testing), 597, 599, 603

Midpoint, 303, 304

MIL-STD-483, 653

MIL-STD-1521A, 653

Minimum spanning tree, 339, 340

Mini-spec, 185, 187

Minitab, 69, 78, 85, 131, 650

Mission requirements, 315

Mission statement, 88

MIT, 536, 537

Model, 134, 135, 649

Model base, 49, 53, 379

Moderator, 99, 101, 169, 170, 171, 172

Modula-2, 589, 592

Modularization, 481482

Module, 22, 23, 26, 44, 439, 444, 448, 449, 450, 454, 465, 470, 473, 476, 481482, 486, 487, 500, 503, 504, 506, 512design, 492496

name, 506

test, see Unit test

Monitor, 590, 591

Monitoring system, 536, 543

Monte-Carlo simulation, 135138, 142

Morphology, 490491, 497

Multi-determine, 214, 216

Multilinked list, 334, 340

Multi-part question, 60

Multiplicity, 228, 232

Multiprocessing (Parallel processing), 587588, 591

Multiprogramming, 587, 588, 591

Multitasking, 587, 591

Multi-value dependency, 214, 216

Multi-way tree, 336, 340

Mutually exclusive relationship, 199

Mutually inclusive relationship, 199

MYCIN, 536

N

Naming conventions, data flow diagram, 179

Nassi-Shneiderman chart, 440, 449454, 456, 461, 466, 474, 480, 486, 512

Natural languageimplementation, 547

processing, 48, 49, 53, 376, 378, 379, 384, 545549

-sub2:phases, 546547

shell, 547, 548

NaturalLink, 549

Naturally Speaking, 384, 549

Navigation, 408, 409, 410, 413

Need, 19, 29, 270

Nested decision, 455, 457, 461, 466, 468469, 470, 475476,

Nesting, 450, 451, 512

Net benefit, 294, 299

NETMANSYS, 604, 612

Net present value, 296297, 299

Netscape, 384, 406, 413

Network, 338, 339, 340, 352, 379, 404415, 416, 425430, 435, 568, 569, 570, 642, 643, 648analysis, 14, 135, 425430, 432

database, 353, 357

data flow, 431, 432

design, 324, 325, 416, 427, 578

model, 14, 415429, 426, 429, 432

routing, 135, 431437

topology, see Network model

Network (Weighted graph), 339, 340

Neuma Technology Corporation, 656, 663

Nexpert Object, 267

Next-event simulation, 138

Node, 236, 239, 262, 333, 334, 335, 336, 338, 340, 416, 417, 419, 420, 422, 423, 428, 429, 431, 432, 433, 434, 435, 540, 643

Non-behavioral requirement, 271, 275

Non-deterministic state transition diagram, 236, 239

Non-key attribute, 211, 212

Non-response, 120, 125

Non-response bias, 66, 69

No opinion response, 122

Normalized data structure, 209, 210

Novel, 366

NPV function, 296, 297, 299

O

Object, 43, 44, 45, 46, 196, 220, 221, 222, 226, 227, 229, 344, 409, 410, 413, 519534interaction diagram, 520, 525, 526529, 532

type, see Class

visibility, 527

Object-oriented, 35, 36, 39, 40, 4346, 536, 538, 540, 541, 658, 659analysis, 44, 219233, 520, 532

database, 354

design, 44, 221, 519534

interface, 378, 384

language, 4, 556

life, cycle 221

system, 235, 236, 241, 242

tools, 248, 383

Objectives, 88, 89, 90, 168, 183, 270, 271, 272, 273interview, 58

organizational, 11, 12, 27, 93, 100

survey, 119

Objectory, 40

Occurrence, 44, 191, 193, 194, 197, 198, 204, 210, 217, 340, 344, 350, 354

OCLC, 604, 612

Office 97, 548, 553

Off-page connector, 287, 441, 444, 448, 508

OMT, 40

One-to-many relationship, 198, 200, 201, 202, 204

One-to-one relationship, 198, 200, 204

On-line debugger, 659, 663

On-line processing, 480, 580, 583

On-page connector, 287, 444, 508

OOWIN, 42

Open, 345, 347

Open question (Open-ended question), 59, 60, 121, 122, 125

Open systems interconnection (OSI), 325, 329

Operating cost, 294, 299

Operating system, 345, 346, 347, 587, 588

Operation, 45, 522529, 530, 533, 560, 574, 578, 616

Operationalcontrol, 627628, 632

evaluation, 636, 639

feasibility, 93, 96

Operation-oriented documentation, 561, 565

Operations concept document, 88

Operator sequence analysis, 600

OP55, 54

OPS83, 267

Optimal allocation, 67, 68

Optimal path, 432, 433

Optimistic concurrency, 670671, 672

Optional relationship, 197

Oracle, 42, 358, 672

Oracle Developer 2000, 557

Ordered list, 340

Organizationalcycle analysis, 29

feasibility, 93, 96

unit, 307, 308, 309

unit-process matrix, 309, 311

Orr, Ken, 4, 25, 26, 254

OSI, see Open systems interconnection

Outcome, 456, 457, 459, 643, 649

Outdegree, 338, 340

Output, 5, 270, 274analysis, 136138, 141, 142

design, 324

error, 607, 611

oriented, 25, 26, 31, 106

Outsourcing, 14, 15, 270

Overviewaction diagram, 514

and define, 380381, 383

diagram, 506507, 510

inspection, 169

P

Page, 406, 407, 409411, 413design, 410411

load time, 411, 413

Paradox, 358, 557, 672

Paralleloperation, 618619, 620

processing, see Multiprocessing

simulation, 626, 632

Parameter, 493, 525, 533

Parameter analysis, 328, 329

Parasoft, 604, 612

Parent, 22, 274, 275, 335, 336, 340, 352, 353, 357, 487, 506

Parent-child relationship, 22

Parent class, 230

Pareto diagram, 72, 8185, 128

Pareto principle, 81, 82, 84

Parse tree, 547, 549

Parser, 547, 549

Partial conversion, see Phased implementation

Partially connected mesh network, 418, 423

Partition, 12, 50, 53

Partition analysis, 610, 611

Password, 569, 572, 573, 575, 629, 630

Path, 338, 340, 405, 432, 433, 436, 451, 488, 489

Path test, 608, 609, 611

Pattern, 520, 529, 533

Payback period, 295, 299

Payoff, 302, 303, 304

P chart, 77

PDF file, 406, 413

Peakload (Peak load analysis), 426, 609

load test, 600, 603

time workload, 590

PECOS, 537

Perfective maintenance, 656, 660, 662

PERFORM, 467468

Performance, 356, 627, 667analysis, 635640, 652, 642

monitoring, 660

requirement, 29, 271, 275, 276, 596, 597, 606

Personnel control, 628

Personnel security, 573

PERT (Program Evaluation and Review Technique), 38, 147, 151, 152, 157

PGP (Pretty Good Privacy), 573, 575

Phased approach, 4, 599

Phased implementation (Partial conversion), 619, 620

Physical, 7, 15, 18, 19, 22, 23, 596database, 500, 667

database design, 14, 354, 355, 356, 357

data flow diagram, 186, 187, 286

data structure, 29, 31, 486, 492

design phase, 2930, 31, 52, 176, 279, 317, 323592

documentation and preparation, 428

I/O, 345, 346

-sub2:model, 93, 241, 243, 285, 286

record, 345, 346, 350

security, 570572, 575, 629, 632

specification, 29

Picture clause, 206

PIDS, see Prime item development specification,

Pilot implementation (Location implementation), 619, 620

Pixel, 365, 366

Planningconfiguration management, 652653

hardware design, 326

inspection, 169

system, 537

Platform, 222, 325, 352, 579

Plug-in, 406407

Pointer, 333, 334, 335, 336, 340, 353, 354, 378

Political feasibility, 93

Political requirement, 271

Polymorphism, 46

Pop, 334, 340

Pop-up window, 396

Popkin Software, 42

Population, 63, 64, 65, 69, 118, 119, 120, 125

Portability, 271

Portfolio, 433, 436

Post conditions, 525, 527, 533

Post-implementation review (Post-release review), 620

Power Builder, 557

Power dialing, 569, 575

Power-Designer, 42

PowerSoft, 42

Precedence (Precedence relationship), 147, 154, 236

Preconditions, 525, 533

Predefined process, 287288, 289, 440, 441, 444, 448

Prediction system, 536, 543

Preparation, inspection, 169, 170

Preparation, JAD, 100

Presentation integration, 39

Present value, 295, 299

Preventive maintenance, 659, 660661, 662

Primary use case, 225

Primavera, 149, 158, 164

Prime item development specifi-cation (PIDS), 274, 275, 317, 319

Primitive, 19, 22, 23, 346, 350

Prioritize (Prioritization), 302, 308, 589, 661

Privilege, 572

Probabilistic model (Stochastic model), 142

Probability mass function (pmf), 644, 645, 649

Problem, 81, 82, 105, 111analysis, 12, 105110, 480

definition, 7, 9, 35, 39, 50, 57, 58, 88, 91, 98, 118, 128, 152, 160, 196, 242, 243, 249, 254, 260, 270, 280, 302, 314, 317, 352, 360, 370, 376, 381, 388, 391, 396, 440, 450, 456, 462, 466, 474, 480, 552, 568, 574, 578, 661

definition tools and techniques, 57146

description, 92, 93

domain, 267, 541

search space, see Search space

solving analysis, 536

space, see Solution space

statement, 8790

Procedural analysis, 23

Procedural cohesion, 492, 497

Procedural/production system, 542, 543

Procedure, 6, 7, 8, 14, 15, 176, 186, 281, 282, 284, 285, 376, 383, 440, 444, 448, 466, 468, 470, 476, 538, 541, 542, 617, 626

Procedure/subroutine approach, 541542, 543

Process (Transform) 5, 7, 9, 22, 23, 27, 31, 45, 71, 72, 73, 74, 176, 177, 178, 179, 181, 182, 183, 184, 185, 186, 187, 193, 196, 221, 223, 224, 225, 243, 271, 280, 281, 282, 283, 284, 307, 308, 309, 376, 439, 440, 441, 448, 449, 454, 479483, 486, 497, 507content, 481

description, 182, 183, 184, 186, 488

design, 479483

design factors, 480482

design guidelines, 481482

driven, 176, 486

error, 607, 611

flowchart (Flowchart, Logic flowchart), 72, 82, 128, 176, 444

name and number, 179, 183, 184, 481

timing, 480

Process-data element matrix, 309310, 311

Processing control, 627, 632

Procurement process, 317318

Production version, 654, 655

Productivity, 34, 560, 637638, 639

Profiler, 37

Program, 7, 8, 176, 186, 281, 282, 284, 285, 286, 344, 345, 439, 440, 449, 450design, 391, 485498, 503, 504, 578

design specifications, 317

documentation, 561, 562

generator, 14, 15, 658, 659, see also Application generator, Code generator, Generator

logic, 511, 512

profiler, 590, 591

specification synthesis, 15

structure, 253, 254, 257, 440, 450, 456, 462, 466, 474, 512, 606

Program Evaluation and Review Technique, see PERT

Projectdependency, 102

interrelationship, 102

life, 294

management, 4, 5, 36, 37, 38, 92, 147172, 248, 286, 294, 504

management workbench, 158, 164

network, 148, 151, 152, 154, 155, 158, 159, 160, 164, 339, 596, 601

planning, 92, 147172, 286, 294, 636

Projection, 215, 217

Projection-join normal form (PJNF), 215

Project-oriented paradigm, 113, 114

PROLOG, 54, 580

Prolog-2, 54

Property lists approach, 540, 543

Proportional allocation, 67

PROSPECTOR, 536

Protocol, 429, 436

Prototype, 48, 51, 52, 53, 92, 93, 241, 243, 245, 249, 250, 270, 360, 370, 381, 382, 383, 384, 392, 552, 627

Prototyping, 40, 108, 220, 236, 241, 243, 245, 247, 248, 249, 250, 326, 364, 365, 366, 374, 376, 380, 381, 384, 400, 401, 404, 481, 578, 582, 616, 619

Pseudocode, 440, 450, 456, 461, 465471, 474, 480, 486, 504, 507, 512

Pseudocode conventions, 466

PSL, 54

Public/private key system, 573, 575

Pull-down menu (Drop-down menu), 396, 399, 401

Purdue University, 536

Push, 334, 340

PVCS, 42, 656, 663

Q

QARun, 603, 612

QAStress, 604, 612

Quality, 34, 314, 638639assurance, 638, 639

control, 64, 168

requirement, 271, 275

tools, 72, 81, 82, 128

Quantifying risk, 303

Quantity control, 627

Quattro Pro, 149

Query, 357, 358, 547, 580

Query language, 358, 370, 373, 667

Question-answer dialogue, 388389, 392

Questionnaire, 117, 118, 119, 120124

Question ordering, 120, 121

Question wording, 123, 124

Queue, 335, 340, 586, 589, 641650

Queuing system cost, 648649

Queuing theory, 64, 135, 328, 426, 427, 586, 641650, 652

Quick-hit approach, 250

Quickest route algorithm, 433434, 436

QuickTime Viewer, 407, 413

Quintus Prolog, 54

QVCS (Quma Version Control System), 656, 663

R

Rabbit, 570, 575

RAD (Rapid Application Development), 113, 236, 247252, 360, 376, 380, 404, 616, 619

Radview Software, 604, 612

RAMIS II English, 549

Randomaccess, see Direct access

number, 66, 67, 69, 135

sample, 66, 69, 119, 120

variable, 643, 644, 649

Random-like sample, 66, 67

Range, 65, 69

Range constraint analysis (Boundary analysis), 609, 611

Rapid Application Development, see RAD

Rational Corporation, 39, 42

Rational Rose, 42

Rational subgroup, 77, 78

Real data, 609, 612

RealNetworks, 407, 413

Real Player, 407, 413

Real-time, 347, 480database, 589

language, 589

system, 4, 12, 235, 236, 239, 578, 580, 583, 585592, 606, 608, 610

system design considerations, 586589

system development, 589590

Reasonableness test, 365, 366, 390, 627, 632

Reasoning, 49, 51, 53, 107, 265, 266, 267, 543

Reasoning capability, 49, 51, 53

Reconciliation control, 627, 632

Record, 193, 194, 332, 340, 344, 345, 346, 349, 350, 354, 356, 370, 371, 372

Record control, 627, 632

Recovery, 572, see also Backup and recovery

Recovery test, 600, 603

Recursion, 236, 239, 332, 335, 340, 450, 608

Recursive relationship, 199

Redundancy, 326, 329, 587, 591

Reengineering, 14, 15, 36, 38, 41, 660, 662

Referential group, 669, 672

Refine-and-test, 243

Regression test (Regression testing), 600, 603, 626, 632, 654, 656

Reinspection, 171

Relation, 53, 213, 214, 215, 217, 357

Relational database, 210, 248, 353354, 357

Relational Software, 603, 612

Relationship, 12, 27, 193, 194, 196, 197, 198, 199, 200, 201, 202, 204, 206, 217, 220, 228, 331, 353, 354, 356, 357, 358

Relationship, analyzing, 200201

Relative addressing, 347348, 350

Release, see System release

Release cycle, 654

Reliability, 271, 326, 587, 591, 601, 636637, 639, 660

Reliability requirements analysis, 426, 429

Remembered information, 572

Repair system, 537, 543

REPEAT UNTIL, 469, 476

Repetition (Iteration), 22, 29, 257, 441, 442, 450, 451, 467, 469, 476, 496, 497, 500, 512

Repetitive data (Repetitive data structure), 210, 257, 370

Report, 7, 186, 243, 249, 285, 286, 363, 369374, 376, 379, 388, 552body, 370, 372

design, 360, 369374, 404, 409, 560, 578

design guidelines, 373

format, 370371

generator, 243, 248, 245, 251, 358, 370, 373, 374, 384, 393, 580

header (Report title), 370, 372, 374

summary, 371, 374

types, 372

Reporting control procedures, 598, 603

Repository, 36, 38, 39, 41, 182, 276, 480, 654

Request for proposal (RFP), 328, 329, 561

Request for quotation (RFQ), 561

Requirements, 4, 19, 23, 29, 30, 35, 52, 88, 222, 223, 241, 242, 243, 245, 249, 254, 270, 271274, 275, 314, 316, 380, 520, 606analysis, 111115

characteristics of, 271

identification, 426427

planning, 249, 251

specification, 30, 177, 190, 269276, 280, 314, 324, 360, 362, 376, 426, 432, 486, 488, 500, 561, 568, 574, 596, 597, 606, 612, 626, 636, 638

types, 271

Resolution, 365, 366

Resourceallocation, 4, 19, 91, 588

analysis, 327, 329

implications, 87, 88

Response time, 29, 222, 271, 280, 281, 282, 283, 284, 326, 328, 347, 391, 392, 426, 580, 581, 583, 586, 587, 589, 590, 591, 609, 636

Response time analysis, 426, 429

Responsibility, 533

Restructuring, 36, 38, 660, 662

Reusable object, 396, 400, 401

Reuse, 40, 44, 220, 520, 396, 560

Reuse maturity model, 221, 232

Revenue enhancement, 294

Reverse engineering, 38, 41, 660, 662

Rework, inspection, 171

RFP, see Request for proposal

Ring network, 422

Ripple effects, 34, 44, 190, 242, 486, 493, 520, 653, 654, 655, 661, 662

Risk (Risk analysis), 26, 29, 92, 98, 135, 138, 142, 293, 294, 299, 301, 302, 303, 456, 568, 569

Risk-payoff analysis, 301305

Risk-payoff matrix, 303304

RITA, 54

RLL, 54

Root (Root node), 335, 336, 340, 420, 487, 488, 497, 505

Root cause analysis, 127, 130, 131

Rooted tree network, 420, 423

ROSIE, 54

ROSS, 54

Route, 431, 432, 436

Router, 420, 428, 429, 431, 432, 436

Routine, 439, 440, 441, 444, 448, 449, 450, 454, 456, 462, 465, 471, 473, 474, 476

Routing, 416, 431437

Routing table, 432, 433

Rule, 49, 53, 260, 261, 262, 267, 543

Rule base, 49, 53, 259, 261, 262, 267, 379

Rule-based system, see Expert system

RULEMASTER, 54

RULE WRITER, 54

Run chart 73

S

Sample (Sampling), 63, 64, 65, 66, 67, 68, 69, 77, 118, 120, 125error, 65, 118, 120, 125

size, 65, 68

space, 643, 649

SAS, 69, 78, 85, 131, 650

Scaffolding, 598599, 603

Scatter diagram, 72, 82, 128

Scatter storage, 348

Schedule, 4, 19, 88, 92, 93, 147, 149, 151, 152, 155, 159

Scheduled report, 372, 374

Scheduling control, 628, 632

Schema, 356, 357, 358

Scope, 27, 31, 87, 88, 89, 90, 92, 93, 100, 284, 581, 584

SCOPE, 348

Screen, 186, 243, 249, 285, 286, 289, 359, 360, 362, 366, 376, 377, 382, 383, 388, 391, 395, 396, 398design, 359, 363365, 374, 404, 409, 560

painter, 243, 245, 251, 384, 393

Screen/form generator, 248, 392, 480

Screening questions, 122, 125

Scroll bar, 408

SDLC, see System development life cycle

SDTF, 603

Search (Searching), 332, 333, 336, 480, 541engine, 556

space (Problem search space), 262, 267

Search-oriented technique, 262264

Secondary control break, 371

Secondary use case, 225

Second normal form (2NF), 211212, 214, 217

Sector, 345, 346

Secure area, 570

Security, 271, 324, 555, 556, 567576, 601, 616, 626, 629630, 632, 667, 668, 672counter measures, 570573

design, 573574

plan, 574

standard, 573, 574

threat, 568570

SEEK, 54

Segue, 604, 612

Selection, 22, 29, 450, 451, 493, 497, 500, 512, see also Decision

Semantic analysis, 546, 549

Semantic net technique, 540541, 543

Sensitivity (Sensitivity analysis), 136, 427

Sequence, 22, 29, 441, 450, 466, 474475, 488, 493, 497, 500, 512diagram, 527, 533

test, see Transaction test

Sequentialaccess, 346347, 348, 350, 580

cohesion, 492, 497

increment approach, 582

Server, 324, 404, 405, 409, 428, 572

Servicecontrols, 628, 632

rate, 642, 645, 649

time, 645, 649

Shared aggregation, 229

Shell, 547

Shockwave Player, 407, 413

Siblings, 335, 340

Signal, 43, 45, 46, 533

Sign-off procedures, 248

Silicon Graphics, 406, 413

Silkperformer, 604, 612

Simple list, 333

Simple star network, 416417, 423

Simplified IPO chart, 508509

SIMSCRIPT, 143

Simulated data, see Hypothetical data

Simulated tracing, 608, 612

Simulation, 64, 92, 93, 133143, 242, 328, 329, 426, 427, 642, 648

Singly linked list, 334, 340

Sink, 338, 340, see also Destination

Site preparation, 616617, 621

SLAM II, 138, 143

Slack, 152, 156, 158, 159

Slot, 538, 543

SMALLTALK, 54

SMF, 636, 639

Social engineering, 569, 575

Softbench, 42

Softbridge, 603, 612

Soft fact, 265

Software, 5, 14, 273, 274, 289, 376customization, 551558

design, 324, 352

development, 35, 43, 663

development controls, 630, 632

engineering, 34, 35

error, 607, 612

monitor, 636, 639

productivity, 637

Software Publishing Company, 158, 164

Software requirements specification (SRS), 274, 276, 317, 319

Software Research, 604, 612

Solution space (Problem space), 51, 53, 261, 262, 264, 267

Son, see Child

Source, 177, 178, 180, 181, 185, 187, 338, 340, 376

Source data, 361, 366

Sources of variability, 131

Span-of-control (Breadth), 480, 482, 483, 491, 496, 497

Spanned record, 346, 350

Spanning tree (Subtree), 339, 340

SPARCworks/TeamWare, 656, 663

Specialization, 230, 232

Speech recognition, 547, 549

SPERIL, 536

Split screen, 397, 401

Spock, 549

SPSS, 32, 290, 448

SQL (Structured query language), 358, 547, 548

SRL (SRL+), 54

SRS, see Software requirements specification

Stable process, 72, 74, 75, 76, 77, 78

Stack, 334, 340, 586, 589

Standard deviation, 65, 69

Stanford University, 536, 537

Star network, 416417, 420, 423

Start time, 148, 149

Start-up failure, 601

State, 45, 46, 235, 236, 237, 238, 239, 586, 588, 591

Statement of scope and objectives, 88

State test, 606, 608, 612

State transition diagram, 235239, 521, 546, 586, 589, 590

Staticcode analyzer, 37, 630, 632, 659, 662, 663

diagram, 226, 232

information, 481, 483

model, 520

routing, 433, 436

Steady state, 141, 142, 645, 650

Steering committee, 91, 96, 302

Stepwise checking, 608, 612

Stepwise refinement, 481, 483, 582

Stereotype, 538, 543

Sterling Software, 42

Stochastic model (Probabilistic model), 142

Stochastic process, 650

Storage efficiency, 345, 346, 348

STRADIS/DRAW, 502

Strata (Stratum), 67, 68, 69

Strategic requirements analysis, 12

Stratified random sampling, 67, 68, 69

Stress test, 601, 603

Structure analysis testing, 609, 612

Structure chart, 18, 21, 22, 23, 221, 440, 450, 456, 462, 466, 474, 480, 486, 499502, 512

Structure clash, 492

Structuredanalysis and design, 1724, 106, 176, 220, 221, 481

English, 18, 392, 440, 450, 456, 461, 466, 473477, 480, 486, 504, 512

English conventions, 474

methodology, 35

program, 440, 486, 499, 504

program design, 18, 19, 485498

programming, 220, 254

requirements specification, 4, 2532, 107, 196, 254

software development, 658, 659

specification, 19

walkthrough, 482, 607

Structured query language, see SQL

STS/CM, 656, 663

Style, 553, 557

Subclass, 45

Subcontract, 270, 313, 314

Sub-problem, 106, 107, 108, 109, 110

Subprocess, 184, 186, 514

Subroutine, 288, 332, 440, 441, 444, 450, 468, 487, 508, 514

Subschema, 356, 357, 358

Sub-specification, 272

Substructure, 191

Subtree (Spanning tree), 335, 339, 340

Summary line, 371, 374

Summary report, 372, 374

Sun Microsystems, 410, 656, 663

Super Project, 158, 164

Suprasystem, 5, 9

SureTrack Project Manager, 149, 158, 164

Surge protector, 325, 329, 616

Survey, 58, 60, 66, 117125, 360

Symbolicmanipulation analysis, 600

reasoning, 48, 53

representation, 48, 53

Symbols, data structure, 192

Symptom, 87, 88, 89

SYN, 536

Synch point, 669, 672

Synchronization, 40, 236, 668, 669, 672

Synonym, 227

Syntactic analysis, 547, 549

Syntaxchecking, 183

error, 607

test, 607, 612

Synthesis, 105, 107, 108, 110

System, 5, 7, 9, 133, 134, 142, 584access monitoring, 636, 639

control, 168, 324, 360, 568, 590, 606, 652, 666

dependent test data, 610

design, 52, see also Design

design strategies, 581582

development, 52

development cost, 294, 296, 552

development life cycle (SDLC), 3, 78, 9, 12, 18, 26, 35, 39, 40, 48, 50, 52, 58, 64, 91, 92, 98, 118, 128, 152, 160, 168, 190, 245, 248, 270, 314, 317, 352, 360, 376, 380, 388, 391, 396, 426, 432, 440, 450, 456, 462, 466, 474, 480, 486, 504, 512, 552, 560, 568, 574, 578, 584, 596, 597, 601, 638, 652

documentation, 561

entity diagram, 254

error, 607, 612

flowchart (System flow diagram), 98, 280, 285291, 360, 376, 381, 440, 480, 504, 507

flowchart symbols, 286287

life cycle, 6, 9, 578, 584

manual, 561

maintenance life cycle, 658, 661

objective, 27, 29, 31, 552, see also Objectives

outputs, 26, 27, 31

performance analysis, 590, 592

performance test, 600, 603

release, 618, 619620, 621, 636, see also Release

response time, 391

test, 599, 603, 654

System Architect, 42

System/segment design document (SSDD, B-specs), 273274, 276, 316, 319

System/segment specifications (SSS, A-specs), 271273, 276, 315316, 317, 319

Systemsanalysis, 12, 175276

information interface, see Instruction dialogue

simulation, 135

T

Table, 352, 353, 668, 669

Tag, html, 406, 409

Tangible, 294, 299, 303, 304

Task, 148, 152, 587, 588, 589, 592sequence, 589

synchronization, 589, 590

Technical evaluation, 636, 639

Technical feasibility, 92, 93, 96

Technological change, 302, 324

Template, 529, 553554, 557

Temporal cohesion, 492, 487

Temporary file, 345, 350

Testand evaluate, 383

criteria, 270, 383, 598

data, 270, 383, 596, 597, 598, 599, 605613

data generation, 608610

plan, 222, 595604, 606

procedures, 597598

schedule, 596, 601

version, 654, 655

Testable, 271

Testing, 8, 9, 14, 35, 37, 39, 52, 64, 108, 168, 270, 383, 486, 560, 564, 578, 589, 595604, 605613, 636, 652, 658levels, 598601

techniques, 607608

Testing and evaluation phase, 52

Test-oriented, 108

Test Works, Web, 604, 612

Texas Instruments, 357, 549, 672

Theme, 408409, 413

Third generation web site, 407

Third normal form (3NF), 212213, 214, 217

Throughput, 14, 15, 25, 325, 328, 392, 581, 584, 590, 636

Timebomb, 570, 575

frame, 27, 31, 552

in queue, 647, 648

in system, 647, 648

period, 295

stamp, 589, 671

Timed box approach, 225, 226, 232

Time-sharing, 588, 592

Time value of money, 295

Token passing, 422, 423, 429, 436

Tool, 3541

Top down, 11, 18, 106, 110, 383, 481, 580design, 581, 584

testing, 486, 597, 599, 603

Topology, 416, 423, 426, 429, 432, 436Design, see Network design

determination, 427, 429

Touch screen (Graphic input screen), 365, 366

TQM (Total quality management), 72, 271

Traceable, 271, 520

Tracing, 183, 274, 276

Traffic flow pattern analysis, 426, 429

Traffic load analysis, 426, 429

Training, 617618, 621

Transaction, 22, 23, 344, 345, 355, 357, 364, 372, 579, 580, 668, 669, 670, 672analysis, 22, 23, 355, 357

center, 500

file, 344, 350, 580

frequency, 590

log, 572, 576, 668, 669

response time, 391

test (Flow test, Sequence test), 608, 612

Transaction-oriented process, 480, 483

Transaction processing system (TPS), 580, 584

Transform (Transform process), 480, 483, 488, 497, see also Process

Transform analysis, 22, 23

Transform-oriented process, 480, 483

Transient state, 141, 142

Transitive dependency, 212, 217

Transmission control, 627, 633

Transmission delay, 431, 432

Traversing a graph/network, 339

Tree, 335337, 340

Tree topology (Hierarchical topology), 420421, 432

Trellix, 409, 413

Trigger event, 280, 281, 282, 283, 284, 488, 497

Trojan horse, 570, 576, 630

Truncation algorithm, 348

Trunk, 129, 131

Tuple, 217

Turbo Prolog, 54

Turnaround time, 14, 15, 29, 73, 243, 590, 636

Turnpike effect, see Highway effect

Two-phase commit, 668, 672

U

UML (Unified Modeling Language), 39, 40, 225, 226, 228, 232, 533

Unbalanced network, 419

Unbiased estimate, 66, 69

Uncertainty, 301, 302, 303

Undirected graph, 338, 340

Unidirectional flow, 399, 401

Unified Modeling Language, see UML

Uniform resource locator, see URL

Uninterruptible power supply (UPS), 325, 329, 587, 616

Unit test (Module test), 599, 603, 654

Unrooted tree network, 420, 423

Unstable process, 72, 74, 75, 76, 77, 78

UNSW Prolog, 54

Unusual occurrence report, 372

Upper CASE, 39, 41

URL (Uniform resource locator), 404406, 413

Use case, 222226, 227, 232, 520, 521, 522, 525, 533

Use case diagram, 225, 226, 232, 520, 533

User, 4, 8, 26, 97, 113, 243, 354, 362, 364, 370, 376, 383, 387, 388, 392, 399, 404, 521, 555, 562, 563, 596, 615, 619, 620acceptance test, 599600

design phase, 249, 251

friendliness, 325, 580, 581

manual, 222, 561, 562, 617

response time, 391

scan/read time, 391

sign-off, 620

think time, 391

training, 377, 379, 560, see also Training

User-driven, 11

User interface, 360, 369, 370, 375385, 388, 392, 396, 398, 399, 401, 546, 548, 560, see also Interfacedesign, 360, 375385, 388, 391, 398, 400, 409, 560

design criteria, 378379

design process, 380383

standard, 396

types, 377378

V

Validation, 35, 36, 560

Validity test, 365, 366, 390, 627, 633

Value analysis, 609, 612

Variance, 69, 644, 645

VBA (Visual Basic for Applications), 554

VCS/UX, 656, 663

Vertex, 338

Vector, 332, 340

Verification, 35, 36, 87, 89, 183, 274, 390

Version, 37, 39, 653

Version control, 37, 561, 596, 598, 626, 630, 633, 653654, 656

ViaVoice Gold, 384, 549

View, 45, 352, 354, 356, 357

Virus, 570, 572, 576

Visibility, 533

Visio, 32, 149, 158, 164, 187, 204, 206, 239, 258, 290, 448, 454, 459, 463, 510, 517

Visualmodeler, 42

test, 603, 612

Visual Basic, 222, 554, 555, 557

Visual Source Safe, 42, 656, 663

Visual Table of Contents (VTOC), 510

Voice recognition, 378, 384, 549

Volume analysis (Control analysis), 610, 612

VRML (Virtual reality markup language), 406, 413

W

Waiting time, 647, 648, 650

Walkthrough, 168, 172, 482, 607, 658

WAN, see Wide area network

Warnier, J. D., 26, 254

Warnier-Orr diagram, 26, 29, 32, 107, 190, 191, 206, 210, 253258, 344, 360, 370, 480, 512

Waterfall method, 7, 8

Webcustomization, 555556

page, 376, 409311

page design, 360, 403414, 552, 555, 560

site, 407409, 413

-sub2:navigation, 408, 409

structure, 407

WebArt, 604, 612

Webexam, 604, 612

Web-form interface, 378, 384

Webload, 604, 612

Weighted graph (Network), 339

Weighted routing, 433, 436

White box testing, 597, 599, 600, 603

White space, 366, 372, 373

Wide area network (WAN), 416, 423, 429

Window (Windows), 376, 377, 378, 379, 382, 383, 388, 391, 395401, 409, 410design, 360, 395401, 404, 409

flow analysis, 399, 401

sequence analysis, 399, 401

template, 401

Windows, Microsoft, 378, 379, 384, 395, 396, 409, 555, 563

Windows 95, 388, 389, 397

WordPerfect, 409, 413, 548

Word Pro, 409, 413

Word recognition, 546, 549

Wording of questions, 123, 124

Workbench, 39, 41

Workload performance analysis, 590, 592

World Wide Web, 378, 404, 413, 552, 555, 563, 576

Worm, 570, 576

WUMPUS, 537

WYSIWYG, 409

X

X-bar and R chart, 77

Y

Yourdon, E., 18, 178

Z

Zero cardinality, 199

toc

Systems_Analysis_And_Design__CRC_Press_1998_/Davis & Yen - Systems Analysis And Design [CRC Press 1998]/ch01.htmltoc ch2>Part IPrinciples

Chapter 1The systems development life cycle

William S. Davis

1.1 Purpose

The purpose of a methodology is to specify a set of well-defined steps or phases, coupled with a set of clear, measurable exit criteria, for solving a complex problem (such as developing an information system). The system development life cycle (SDLC) is a set of steps that serves as the basis for most systems analysis and design methodologies.

1.2 Strengths, weaknesses, and limitations

A methodology (such as the system development life cycle) acts as a memory aid by imposing discipline, thus reducing the risk that key details will be overlooked. Communication is enhanced because the methodology imposes a consistent set of documentation standards. The steps in the methodology enhance management control, providing a framework for scheduling, budgeting, and project management. The tools associated with a good methodology make it easier to solve the problem. Finally, a good methodology increases the likelihood that significant errors are detected early.

There are dangers associated with using a methodology, however. Some people become so bogged down in the mechanics of following the steps and completing the exit criteria that they fail to solve the real problem. (There is a fine line between discipline and rigidity.) Additionally, no matter what methodology is chosen, there will be problems for which that methodology is (at best) inappropriate, and it is a mistake to try to force the application to fit the tool.

There is always a concern that the system developed may not accurately reflect the current business environment. The elapsed time between the initial proposal and system completion can be quite lengthy (often one or more years). Many methodologies require that specifications be frozen as work progresses from one step to the next, and user requirements do change over time. Given the fast pace of technology, this problem is particularly acute with hardware and/or software selected early in the process.

The traditional methodologies are not optimal for developing some types of information systems, such as expert systems and real-time processing systems. Additionally, fourth-generation, fifth-generation, and objected-oriented languages require modifications to the traditional approach.

Sometimes management is tempted to believe (or hope) that technology can replace technical experts. A good methodology makes a competent analyst more productive, but no methodology can convert an unskilled, untrained person into a competent analyst.

1.3 Inputs and related ideas

The system development life cycle provides a framework or structure for virtually all the tools and techniques discussed in this book.

The system development life cycle implies a phased approach, with complex tasks decomposed into smaller phases (stages, steps) that are easier to achieve, control, and manage. Many traditional methodologies, such as Martins information engineering (Chapter 2) and Orrs structured requirements definition (Chapter 4), emphasize the phased approach, with clearly defined entrance and exit criteria for each individual phase. Practicing analysts often deviate from the rigidly phased approach defined by the methodology, however.

The project management life cycle is similar to the system development life cycle, with stages or phases defining a schedule and triggering resource allocations. Note, however, that a given project might encompass several related systems, and a given system might be divided into several sequential or concurrent projects.

1.4 Concepts

A system (Figure 1.1) is a set of interrelated components that function together in a meaningful way. A system is delimited from its environment (its suprasystem) by a boundary. A system accepts inputs at its boundaries. Outputs flow back across the boundaries. A process is an activity that changes the system in some way. Of particular interest are the interfaces, the points at which the various systemcomponents communicate or interact. As a general rule, the more interfaces a system contains, the more complex the system.

In addition to inputs, processes, interfaces, and outputs, the system also includes control and feedback mechanisms that together allow the system to determine if it is achieving its purpose. Feedback is the return of a portion of the systems output to its input. If the feedback suggests a deviation from the expected value (the control), the system reacts by attempting to adjust itself.

1.4.1 Information systems

This book is concerned with the analysis and design of information systems. An information system is a set of hardware, software, data, human, and procedural components intended to provide the right data and information to the right person at the right time.

Figure 1.1A system.

1.4.2 The system life cycle

Every system has a life cycle (Figure 1.2). An information system is born when a problem is recognized. After the system is developed, it grows until it reaches maturity. Eventually, a change in the nature of the problem or increasing maintenance costs degrade the value of the system, so it dies and a new or replacement system is born to take its place.

Figure 1.2The system life cycle.

1.4.3 Methodologies

A methodology is a body of practices, procedures, and rules used by those who work in a discipline or engage in an inquiry. Often, a methodology is implemented as a set of well-defined steps or phases, each of which ends with a clear, measurable set of exit criteria. A key purpose of a methodology is ensuring that nothing is overlooked in the process of solving a complex problem (such as developing a complex information system).

Figure 1.3The system development life cycle is sometimes called the waterfall method.

1.4.4 The waterfall method

The basis for most systems analysis and design methodologies is the system development life cycle or SDLC (Figure 1.3). It is sometimes called the waterfall method because the model visually suggests work cascading from step to step like a series of waterfalls. (Note: In reality, there is considerable feedback between the various steps or phases.)

The first step is problem definition. The intent is to identify the problem, determine its cause, and outline a strategy for solving it.

Given a clear problem definition, analysis begins. The objective of analysis is to determine exactly what must be done to solve the problem. Typically, the systems logical elements (its boundaries, processes, and data) are defined during analysis.

The objective of design i