Valacich J., George J., Hoffer J.A. Essentials of Systems Analysis and Design
Подождите немного. Документ загружается.
Normalization, 274, 281–284
Normalized relations, 276
NPV (net present value), 95, 96–97, 98t
Null values, 297
NUnit, 329
O
Object class, defined, 365
Object class libraries, reuse of, 37
Object diagrams, 365–366
Object modeling, 362, 365–368
Object-oriented modeling, 361–376
aggregation, 370
benefits of, 361
class diagrams, 365–368
development life cycle, 361–362
generalization, 368–370
reusing existing software, 36
sequence diagrams, 372–375
state diagrams, 371–372
systems analysis in, 361–362
systems design in, 361, 362, 375–376
Unified Modeling Language, 362
use-case modeling, 362–365
Objects, 361
Off-the-shelf software, 30–31, 33–36
One-time costs, 93, 94f
Open-ended questions, 128–129
Open-source software, 32–33
Operation. See systems implementation and operation
Operational feasibility, 98
Operations, 17, 365, 366
Oracle Corp., 31–32
Outsourcing, 28–29
Overlapping (subclass constraint), 370
P
Packaged software, 30–31, 33–36
Packaged software producers, 30–31, 33t
Packages, Unified Modeling Language, 375
Pages, 297
Parallel installation, 330, 331f, 332t
Participatory design (PD), 21
People, management of, 56–57
PeopleSoft, Inc., 31
Perfective maintenance, 344
Performance testing, 330, 352, 353t
PERT (Program Evaluation Review Technique), 67
Phased installation, 330, 331f, 332t
Physical design, 15, 16f, 274
Physical file design, 293–294
Physical files, 299
Index 413
K
Key business processes, 141–142
L
Latent defects, 344
Layout design, 247–251
See also interface design
Legal and contractual feasibility, 98
Level-0 data-flow diagrams, 159, 175–177
Level-n diagrams, 162, 163–164
Lifelines, 373
Lightweight graphics, 264
Logical design, 15, 16f, 274
Logic modeling, 171–175
M
Maintenance, 343
See also systems maintenance
Managed reuse, 38
Management. See project management
Mandatory features, 214–215
Maximum cardinality, 203–204
Mean time between failures (MTBF), 345
Methodologies, 5
Microsoft Access, 295t
Microsoft PowerPoint, 108
Microsoft Project for Windows, 66, 72–74
Microsoft Visio
in database design, 276, 277f
entity type representation, 200
E-R diagram creation, 192–193, 194f
Microsoft Visual Basic.Net, 236, 237f
Minimum cardinality, 203
Modularity, 9
Module testing, 327
MTBF (mean time between failures), 345
Multiplicities, 366–367
Multivalued attributes, 200
N
Narrative overview, 237, 238f, 247
Navigation design, 248–249, 250f, 264–265
Net present value (NPV), 95, 96–97, 98t
Network diagrams
defined, 57
estimated times/completion times in, 67, 70
examples, 68–70
scheduling project plans, 64–65, 66
task relationships and sequences in, 57, 66–67
vs. Gantt charts, 64–65, 66–67
Nonkeys, 290–291
414 Index
Physical tables, 297–304
Pine Valley Furniture Company, 44–45
See also PVF Company, examples from; PVF Company
WebStore, examples from
Planning Game, 388–389
Pointer, 299
Political feasibility, 98
Postproject reviews, 64, 66, 342
Presentation guidelines, 108, 109t
Present value, 95
Preventive maintenance, 344
Primary keys, 276, 280, 282
Primitive data-flow diagrams, 168
Procedure documents, document analysis of, 133–134
Process, 156, 157–158
Process modeling, 154–177
decision tables, 172–175
defined, 154
deliverables and outcomes, 154–155 (See also data-flow
diagrams)
example, 175–177
logic modeling, 171–172
Productionizing, 390
Project, defined, 45
Project charter, 51, 52f
Project closedown, 63–64, 342–343
Project execution, 60–63
Project feasibility
assessing, 90–91, 114
examples, 90–91, 112t, 113t
factors influencing, 90, 98–99, 113t
See also economic feasibility
Project identification and selection, 84–88
Project initiation
activities, 49–53, 88–89
defined, 49
deliverables, 89–90
examples, 45–47, 111
project workbook, 50–51
See also project planning
Project management, 44–74
defined, 48
examples, 44–45, 68–71
process of, 48
project closedown, 43f, 63–64
project execution, 43f, 60–63
project initiation, 43f, 45–47, 49–53
project planning, 43f
software tools for, 71–74
See also project planning
Project managers, 45, 48f, 49t, 342
Project planning
activities, 53, 54t, 88–89, 90t
baseline project plan, 59–60
budget, preliminary, 59
communication plan, 57–59
critical path scheduling, 66
defined, 53
deliverables, 89–90 (See also baseline project plan (BPP);
project scope statement)
expected time duration calculation, 67, 68–69
feasibility assessment (See economic feasibility; project
feasibility)
level of detail, 53f
Microsoft Project for Windows, 66
nearer-term vs. long-term projects, 53
in project management process, 53–60
project scope statement, 59
resource estimates, 55–57
risk assessment, 59
schedule, preliminary, 57
scope, alternatives, and feasibility, 53–54
standards and procedures, 59
systems analyst’s role in, 89
task division, 54–55
tools (See Gantt charts; Network diagrams)
See also project initiation
Project reports, reviewing, 73–74
Project repositories, 19, 191, 194–195
Project scope statement
example, 100–101, 102
overview, 14, 59, 89, 100
Project workbooks, 50–51, 62
Prototyping
as alternative to SDLC, 18
defined, 18
in determining system requirements, 139–140
in dialogue design, 260–261
in forms/reports design, 235
in rapid application development, 19
Purpose, 6f, 7
PVF Company, background of, 44–45
PVF Company, examples from
baseline project plan, 99–108
conceptual data modeling, 195–197, 205–206
dialogue design, 259, 260, 261f
feasibility assessment, 90–91, 92–97
forms/reports formatting, 239–240, 243, 244f,
245, 246f
forms/reports specifications,
237–238, 247
Gantt charts/Network diagrams, 68–71
logical database design, 276–284, 285–288, 289–291
maintenance, 349–350
physical database design, 278–279
PVF Company WebStore, examples from
conceptual data modeling, 209–213
database design, 306–309
interface design, 259, 263–266
process modeling, 175–177
system requirement determination, 143–146
systems implementation and operation, 350–353
systems planning and selection, 110–113
Q
Quick reference guides, 334
R
RAD (rapid application development), 19–20, 155
Range control, 296
Recovery testing, 330, 352, 353t
Recurring costs, 94, 95f
Recursive foreign keys, 288
Recursive relationships, 202, 286, 288, 367f
Reengineering processes, 141–142, 348
Refactoring, 390
Reference guides, 334
Referential integrity, 284, 296–297
Relational database model, 279–281
Relations
defined, 280
merging, 285, 289–291
normalizing, 285
transforming E-R diagrams into, 284–289
Relationships
aggregation, 370
association, 366–368
cardinalities in, 203–204
defined, 201
degrees of, 202–203
in E-R diagram transformation, 284, 286–288
generalization, 368–370
Release descriptions, 334–335
Repeating groups, 201
Reports, 234, 245–246
See also forms and reports design
Repositories, 19, 191, 194–195
Request for proposal (RFP), 35–36
Request for quote (RFQ), 35
Requirements, system, 126
use-case modeling, 362–365
See also conceptual data modeling; process modeling;
system requirements, determining
Resources, 55–57, 66
Response time, 35
Return on investment (ROI), 96, 98t
Reusing existing software, 36–39
Reverse engineering, 348
Reviews, postproject, 64
RFP (request for proposal), 35–36
RFQ (request for quote), 35
Risk assessment, 59
ROI (return on investment), 96, 98t
Rules, decision table, 172–173
S
Sample design, 247
Sample designs, 237, 238f
SAP AG, 31
Schedule feasibility, 98
Scope determination, 14, 59, 99–100
See also project scope statement
Scribes, 138, 139
SDLC (systems development life cycle)
Agile Methodologies’ approach to, 385
defined, 12, 13f
maintenance activities within, 323–324
overview, 13–17
phase 1 (See systems planning and selection)
phase 2 (See systems analysis)
phase 3 (See database design; interface design;
systems design)
phase 4 (See systems implementation and operation)
vs. rapid application development, 20f
Search engines, reregistering with, 349
Second normal form (2NF), 281, 282–283
Security testing, 330, 352, 353t
Sequence diagrams, 362, 372–375
Sequential file organizations, 301, 304t
Servers, 10
Simple design, 390
Simple messages, 374
Single location installation, 330, 331f, 332t
Slack time, 70, 71
Software application testing, 325
See also testing
Software companies, 30t
Software engineering process, 5
Software help components, 337–338
Software sources, 27–39
cloud computing, 32
comparison of, 33t
enterprise solutions software, 10, 31–32, 345
in-house development, 27, 32–33
IT services firms, 29–30
open-source software, 32–33
outsourcing, 28–29
packaged software, 30–31, 33–36
reuse, 36–39
SourceForge.net, 33
Source/sink, 156–158, 159
SSR (system service request), 46
State, of objects, 365
State diagrams, 362, 371–372
Index 415
416 Index
State transition, 371–372
Story Cards, 388–389
Stress testing, 330, 352, 353t
Stub testing, 325t, 327
Subclasses, 368–370
Subsystems, 6f, 7, 9
Superclasses, 368–370
Support, defined, 336
Supporting users, 322–323, 336, 338–341
Synchronous messages, 373–374
Synonyms, defined, 290
Syntax checking, 325t, 326
System administrator’s guides, 335
System audits, 343
System documentation, 333–336
audience of, 322, 334
automatic updating of, 348
as criterion for packaged software, 35
defined, 333
deliverables and outcomes, 323
effect on maintenance, 345
overview, 16
process of, 322
types of, 333–334
user documentation, 333, 334–336
System features, 214–216
System feedback, 254–255
System librarians, 347–348
System requirements, determining, 124–146
in Agile Methodologies, 386–389
business process reengineering, 141–142
data modeling questions, 195, 196f
deliverables and outcomes, 125–126
direct observation of users, 131–132, 137t
disruptive technologies, 142–143
document analysis, 132–137
example, 143–146
interviewing, 126–131
joint application design, 136–139
in object-oriented modeling, 363
process of, 124–125
prototyping, 139–140
System requirements, structuring, 126
See also conceptual data modeling; process modeling
Systems, 6–10, 12–17
See also SDLC
Systems acquisition. See software sources
Systems analysis
in object-oriented modeling, 361–362
overview, 14–15, 17t, 123f
system requirement determination (See system
requirements, determining)
system requirement structuring, 126 (See also conceptual
data modeling; process modeling)
Systems analysis and design
approaches to, 10–12, 18–21 (See also Agile Methodologies)
basic concepts, 4–6
history of, 27–28
role of systems analyst in, 11–12
systems development life cycle, 12–17 (See also SDLC)
Systems analysts
defined, 11
design strategy influences, 214
job market, 11
role in coding, testing, and installation, 322
role in project initiation and planning, 88, 89f
role in support, 340
role in systems development, 11–12
skills needed, 11, 12f, 124
Systems design
designing databases (See database design)
designing human interface (See interface design)
in object-oriented modeling, 361, 362, 375–376
overview, 15, 17t, 233f
Systems development methodology, 12
System service request (SSR), 46
System shut down, 332–333
Systems implementation and operation, 320–353, 329–330
in Agile Methodologies, 391
coding (See coding)
configuration management, 347–348
documentation (See system documentation)
example, 350–353
implementation failure, 341–342
installation (See installation)
maintenance (See systems maintenance)
in object-oriented modeling, 376
overview, 15–17, 319f
project closedown, 63–64, 342–343
support, 322–323, 336, 338–341
testing, 329–330 (See also testing)
training, 322–323, 336–338
Systems integration, 10
Systems maintenance
automated development tools in, 348
configuration management, 347–348
controlling requests for, 346–347
cost of, 344–345
deliverables and outcomes, 324–325
example, 349–350
factors affecting, 344–345
measuring effectiveness of, 345–346
process of, 323–324
types of, 343–344
for web sites, 348–349
Systems planning and selection, 84–113
overview, 14, 17t, 83f
project identification and selection, 84–88
Index 417
project initiation and planning (See project initiation;
project planning)
reviewing the baseline project plan, 105–108
Systems thinking, 11
System testing, 325t, 327
T
Tables, formatting, 242–245
Tangible benefits, 92
Tangible costs, 93
Task Cards, 389
Task responsibility, 103
Technical feasibility, 98
Techniques, software engineering, 5
Template-based HTML, 265–266
Ternary relationships
in conceptual data modeling, 202f, 203
in database design, 286–288
in object-oriented analysis/design, 367
Test cases, 328–329, 351–352
Testing
defined, 327
deliverables and outcomes, 321–322
in eXtreme Programming, 385
overview, 15–16
process of, 321, 325, 327–329
software application, 325
system, 325t, 327
types of tests, 325–327
Testing, acceptance, 329–330
Testing harness, 329
Testing software before purchase, 36
Text formatting, in forms and reports, 242, 243f
Third normal form (3NF), 281, 283–284
Time value of money (TVM), 94–97
Tools, software engineering, 5
Top-down data modeling, 195
Top-down project initiation, 87
Total slack time, 71
Training programs, 16
Training users, 322–323, 336–338
Turnkey systems, 30–31, 33–36
TVM (time value of money), 94–97
U
Unary relationships, 202, 286, 288, 367f
Unified Modeling Language (UML), 362, 375
Unit testing, 325t, 327
Usability assessment
in forms/reports design, 237–238
in interface/dialogue design, 247, 250t, 260–261
Use-case modeling, 362–365
Use cases, 362–365
User documentation, 333, 334–336
Users
acceptance testing by, 329–330
direct observation of, 131–132, 137t
involvement in Agile Methodologies development, 21,
386–387
involvement in participatory design, 21
role in rapid application development, 20
support of, 322–323, 336, 338–341
training of, 322–323, 336–338
understanding skills of, 235, 238
V
Vendors, software, 34–35
View integration, 274
W
Walkthroughs, 105–108, 111, 325t, 326
WBS (work breakdown structure), 54, 103
Weak entities, 200
Web sites
interface design, 262–263, 264t
maintenance of, 348–349
See also PVF Company WebStore, examples from
Well-structured relations, 280–281
Workbooks, project, 50–51, 62
Work breakdown structure (WBS),
54, 103