Milestone 9&10 – Database Design Solution

MILESTONE 9 – APPLICATION ARCHITECTURE

? Synopsis

J

ust as we modeled business requirements during systems analysis, we 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 12

2. Application architecture and physical DFDs – Chapter 13

? Assignment

In this milestone we will construct a physical Data Flow Diagram for a process.

? Activities

1. Prepare the physical DFD based on the narrative provided in Exhibit 9.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 9" and accompanied with a Milestone Evaluation Sheet.

References:

Export Production Information Narrative

Exhibit 9.1

Templates

See on-line learning center website for the textbook.

Deliverables:

Physical Data Flow Diagram: Due: __/__/__

Time: _______

Milestone's Point Value: _______

Exhibit 9.1

The selected architecture for the CTTS will employ a back-end database running in SQL Server. An ASP.NET web application will be written for the service request system. A VB .NET desktop client-server application will be written for the component & configuration system.

Use the following narrative to construct a Physical Data Flow Diagram for the Enter Component Information process, which is part of the component & configuration system.

The technician will click the Enter Component Information button from the application toolbar on the main screen. This will open the Enter Component Information screen. The screen will display a ComboBox listing all clients. After the technician selects a client, the screen will display a ComboBox listing all equipment for the selected client.

The screen will then display a list of all components installed for that piece of equipment that have a blank DateRemoved field. A Remove button will be displayed for each component along with an Add New Component button at the bottom of the list.

If the technician clicks the Remove button for any component, a pop-up message will first ask the user to confirm the removal. If it is confirmed, the system will issue an SQL Update statement to the database to update the DateRemoved field for that record with the current system date on the technician's PC. The list of installed components will then be re-queried and re-displayed.

If the technician clicks the Add New Component button, the screen will display a TextBox where the technician can either type or scan the barcode of the item being installed. Textboxes will also be displayed for Date Installed and Quantity, with Date Installed defaulting to the current system date on the technician's PC and Quantity defaulting to 1. The technician can change either or just click OK. The program will validate the barcode to make sure it is not blank, validate the Date Installed to make sure that a valid date has been entered, and validate the Quantity to make sure a number larger than zero has been entered. If any of these validations fail, an error message will be displayed. Otherwise the data