close

Вход

Забыли?

вход по аккаунту

?

INTRODUCTION - DESIGN

код для вставкиСкачать
INFORMATION SYSTEMS
DESIGN
The Systems Development Life Cycle
(SDLC)
пЃµ Systems
Planning
пЃµ Systems
Analysis
пЃµ Systems
Design
пЃµ Systems
Implementation
Planning
Evolution
Implementation
пЃµ Systems
Evolution
Analysis
Design
System Model with its Six Compone
SYSTEM
boundary
processing
controls
inputs
feedback
outputs
Examples:
• Automobile
• Student Registration Syst
• Others...
3
SYSTEMS DESIGN
пЃ®
data
software
An AUTOMATED INFORMATION SYSTEM IS
пЃ¶ a type of fabricated system
пЃ¶ used by one or more persons
пЃ¶ to help people accomplish some task
or assignment that they have
пЃ¶ utilizes hardware and software
people
procedures
hardware
SYSTEMS DESIGN
DATA
FUNCTIONS
An AUTOMATED INFORMATION
SYSTEM has three basic
relationships to consider
BEHAVIOR
пЃ®
DATA - input, output or already stored
electronically
пЃ®
FUNCTIONS - transformations or actions taken
пЃ®
BEHAVIOR - the observable effects from
General Model of Information Systems Development (“Partnership”)
Stakeholder
Requirements
(1)
Analysis
Continued
Involvement
(5)
Information
System (6)
Requirements Specification
(3)
Problem
Definition
Skills (2)
Design and
Implementation
Problem
Solution
Skills (4)
Information
Technology
Staff
Systems Analysis and Design Activities and Deliverables
DESIGN
ANALYSIS
Activities:
• Systems Planning
• Feasibility Study (optional)
• Requirements Determination
• User Acceptance
• Prototyping (optional)
Deliverables:
• Requirements Specification
• Prototype (optional)
Activities:
• Physical Design
• Prototyping (optional)
• Software Construction/Purchase
• User Documentation - “Deliverable”
• Testing
• Training
• User Acceptance
• Conversion
• Implementing the system
Deliverable:
• Information System
Two on-going activities
• Project Management
• Project Documentation - “Scaffolding”
SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC
Design
Analysis
пЃµ Planning
пЃµ Feasibility
Study (optional)
пЃµ Requirements Determination
пЃµ Conceptual Design
пЃµ Physical Design
пЃµ Construction and/or Purchase
(prototype)
пЃµ Training
пЃµ Conversion - old to new
пЃµ Implementation
пЃµ Evolution - maintenance &
8
In addition: User acceptance, documentation, project manageme
SYSTEMS DESIGN ACTIVITIES
пЃµ Economic,
Operational & Technical
Feasibility
пЃµ Security
пЃµ Make
Issues
(in-house versus outsource) versus
Buy
пЃµ Documentation
1 of 3
INFORMATION SYSTEMS TESTING LAYERS
User Acceptance
System and Integration
Sub-system
Function
•
Alpha &
Beta tests
•
Creeping
Commitment
Module
2 of 3
SYSTEMS DESIGN ACTIVITIES
пЃµ User-Interface
Design (GUI design)
пЃµ Prototyping
пЃµ Training
пЃµ Conversion
- cutover and parallel
пЃµ Implementation
institutionalize
- install, activate,
3 of 3
Verification and Validation*
пЃµ
пЃµ
Verification: The process of evaluating a system
or component to determine whether the products
of a given phase satisfy the conditions imposed
at the start of that phase. (Mainly a paper-based
activity that requires you to confirm that each
stage of the development conforms to the
requirements defined in the previous stage.)
Validation: The process of evaluating a system or
component during or at the end of the
development process to determine whether it
satisfies specified requirements. (Mainly a
confirmation that the implemented
system/component actually works to
specification.)
OBJECT-ORIENTED SYSTEMS DESIGN
Information System Model
Human Interaction (HI)
Problem Domain (PD)
(created during analysis;
refined during design)
Data Management (DM)
System Interaction (SI)
• Good strategy (technique) for developing Client-Server (n-Tier) Sy
Types of Information System Features
Log Information
(“needed information”)
•Business Problem
Master/Reference Data
Analyze results
Conduct Business
• Business Problem
Transaction Data
Interact with
other systems
• Business Problem Results
• Business Problem Integration
The HI to PD Relationship
Human Interaction
ProblemDomain
LogonWindow
attributes
Student
services
RegForCourseWin
DropCourseWin
Student
Student
services
services
RequestTranscriptWin
Student
PayStudentFeesWin
services
services
Student
studentIDNumber
studentName
etc...
registerForCourse
dropCourse
requestTranscript
payStudentFees
etc...
Information System
HumanInteraction
• Screens
• Reports
DataManagement
• Databases
ProblemDomain
• Business Problem
SystemInteraction
• Devices
• Other Systems
OBJECT-ORIENTED SYSTEMS DESIGN
Human Interaction (HI)
пЃµ Security/Logon
пЃµ Setup
Window(s)
Windows - persistent objects
пЃµ Business
Function Windows supports the human interface for the
Problem Domain functionality
OBJECT-ORIENTED SYSTEMS DESIGN
Human Interaction
Human Interaction (HI)
Video Store Example
Check-InWindow
CustomerWindow
EmployeeWindow
InventoryWindow
LogonWindow
PurchaseOrderWindow
Sale-RentWindow
VendorWindow
CustomerStatusReport
DailySalesRentReport
InventoryStatusReport
OverdueRentalItemReport
OpenPurchaseOrderReport
SaleRentReceiptReport
Compare this list with the
Video Store’s PD Component
OBJECT-ORIENTED SYSTEMS DESIGN
Human Interaction
Check-InWindow
CustomerWindow
EmployeeWindow
InventoryWindow
LogonWindow
PurchaseOrderWindow
Sale-RentWindow
VendorWindow
CustomerStatusReport
DailySalesRentReport
InventoryStatusReport
OverdueRentalItemReport
OpenPurchaseOrderReport
SaleRentReceiptReport
Check-InWindow
CustomerWindow
attributes
attributes
services
services
EmployeeWindow
attributes
InventoryWindow
services
services
LogonWindow
PurchaseOrderWindow
attributes
attributes
attributes
services
services
.....plus 8 more
OBJECT-ORIENTED SYSTEMS DESIGN
Human Interaction (HI)
пЃµ Who
“I” Know - connections &
constraints
пЃµ What
“I” Know - attributes
пЃµ What
“I” Do - services
OBJECT-ORIENTED SYSTEMS DESIGN
Data Management (DM)
пЃµ Stores
the problem domain classes
with objects that are persistent
пЃµ Encapsulates
search & storage
mechanisms for all persistent
classes with objects
OBJECT-ORIENTED SYSTEMS DESIGN
Problem Domain
ConcessionItem
Employee
Game
Inventory
Member
POLineItem
PurchaseOrder
RentalItem
RentalTransaction
SaleItem
SaleRentalLineItem
SalesTransaction
StoreLocation
Transaction
VCR
Vendor
Video
Data Management
ConcessionItemDM
EmployeeDM
GameDM
MemberDM
POLineItemDM
PurchaseOrderDM
RentalTransactionDM
SaleRentalLineItemDM
SalesTransactionDM
StoreLocationDM
VCRDM
VendorDM
VideoDM
Problem Domain
class with objects
that need persistence
will most often
correspond directly
with the DM class
with objects.
Reason: “Plug-and-Play” concept or the
“Separation of Concerns” conce
INFORMATION SYSTEMS DESIGN
ANALYSIS
DESIGN
PROGRAMMING DATABAS
Object
RDBMS
OODBMS
RDBMS
Object
Object
OODBMS
RDBMS
Structured Conventional, 3rd/4th GL
Object
Object
RDBMS
Conventional, 3rd/4th GL
Object
Object
Object
Object
RDBMS
Mix of Conventional/Object
OODBMS
OODBMS
Object
Structured
Structured
Structured Object
Документ
Категория
Презентации
Просмотров
4
Размер файла
176 Кб
Теги
1/--страниц
Пожаловаться на содержимое документа