SADM 5/ed – CASE STUDY 4 – Milestone 7: Application Architecture
Page: 7-1
MILESTONE 7 – APPLICATION ARCHITECTURE
 Synopsis
J
ust as you modeled business requirements during systems analysis, you should
model technology architecture and requirements during systems design. The
models serve as blueprints for system design, prototyping and construction.
In this milestone, you will prepare a Physical Data Flow Diagram. Physical data
flow diagrams model the technical and human design decisions to be implemented as
part of an information system. They communicate technical and other design
constraints to those who will actually implement the system. In other words, they
serve as a technical blueprint for the implementation.
 Objectives
After completing this milestone, you should be able to:
 Draw physical data flow diagrams for an information system’s architecture and
processes.
 Prerequisites
Before starting this milestone the following topics should be covered:
1. Systems design – Chapter 10
2. Application architecture and physical DFDs – Chapter 11
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 5ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman
Copyright Irwin/McGraw-Hill 2001
SADM 5/ed – CASE STUDY 4 – Milestone 7: Application Architecture
Page: 7-2
 Assignment
The goal of this project is to produce a high-level general design that can serve as an
application architecture for the system and a general design for the processes that
make up the system.
 Activities
1. Prepare the physical DFD based on the narrative provided in Exhibit 7.1. Make
assumptions where necessary.
Deliverable format and software to be used are according to your instructor’s
specifications. Deliverables should be neatly packaged in a binder, separated with a
tab divider labeled “Milestone 7,” and accompanied with a Milestone Evaluation
Sheet.
References:
Export Production Information Narrative
Exhibit 7.1
Templates
See online learning center web site for the textbook.
Deliverables:
Physical Data Flow Diagram:
Milestone’s Point Value:
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 5ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman
Due: __/__/__
Time:_______
_______
Copyright Irwin/McGraw-Hill 2001
SADM 5/ed – CASE STUDY 4 – Milestone 7: Application Architecture
Page: 7-3
Exhibit 7.1
Add New Request Narrative
To add a service request, a technology user will launch a web browser and go to
the URL of the Active Server Page containing the service request form. The
Active Server Page will use info from the Equipment data store to load a combo
box on the form so that the user must select a valid Equipment ID. The user will
enter the rest of the service request information including the user’s name and a
description of the problem.
Clicking the Submit button will launch the Active Server Page that adds the new
service request. It will issue an SQL INSERT command to the Service Request
data store. The Report Date will be automatically filled in with the current system
date from the operating system. The system will trigger an e-mail message to be
sent to the IT Director with notification of the new service request. The system
will also send a confirmation page to the technology user’s browser.
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 5ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman
Copyright Irwin/McGraw-Hill 2001