Académique Documents
Professionnel Documents
Culture Documents
and Design
Learning Objectives
Chapter 1
Introduction
organizational process.
Used to develop and maintain computerbased information systems.
Used by a team of business and systems
professionals.
Chapter 1
Introduction (Cont.)
Chapter 1
Chapter 1
Application Software
Computer
Systems Analyst
Organizational
Chapter 1
Chapter 1
Chapter 1
10
Summary of Information
Systems Types
Chapter 1
11
Chapter 1
12
Chapter 1
13
Chapter 1
14
Chapter 1
15
Chapter 1
16
Chapter 1
17
Chapter 1
18
Chapter 1
19
20
Chapter 1
21
Chapter 1
22
Software
Engineering (CASE) Tools
Joint Application Design (JAD)
Chapter 1
23
Application Development
(RAD)
Agile Methodologies
eXtreme Programming
Chapter 1
24
Prototyping
Iterative development process:
Requirements quickly converted to a
working system.
System is continually revised.
Close collaboration between users and
analysts.
Chapter 1
25
Prototyping (Cont.)
Chapter 1
26
Computer-Aided Software
Engineering (CASE) Tools
Diagramming tools enable graphical
representation.
Computer displays and report generators
help prototype how systems look and
feel.
Chapter 1
27
Computer-Aided Software
Engineering (CASE) Tools (Cont.)
Analysis tools automatically check for
consistency in diagrams, forms, and
reports.
Central repository for integrated storage of
diagrams, reports, and project
management specifications.
Chapter 1
28
Computer-Aided Software
Engineering (CASE) Tools (Cont.)
Documentation generators standardize
technical and user documentation.
Code generators enable automatic
generation of programs and database
code directly from design documents,
diagrams, forms, and reports.
Chapter 1
29
30
Chapter 1
31
Chapter 1
32
to radically decrease
design and implementation time.
Involves: extensive user
involvement, prototyping, JAD
sessions, integrated CASE tools, and
code generators.
Chapter 1
33
Chapter 1
34
Agile Methodologies
Motivated by recognition of software
development as fluid, unpredictable, and
dynamic.
Three key principles
Adaptive
35
Chapter 1
36
eXtreme Programming
Short, incremental development cycles.
Automated tests.
Two-person programming teams.
Chapter 1
37
Communication
between developers.
High level of productivity.
High-quality code.
Chapter 1
38
Chapter 1
39
40
Chapter 1
41
Phases of OOSAD-based
Development
42
Chapter 1
43
Summary
Chapter 1
44
Summary (Cont.)
Explain
45