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.
After completing this milestone, you should be able to:
⇒ Draw physical data flow diagrams for an information system’s architecture and processes.
Before starting this milestone the following topics should be covered:
1. Systems design - Chapter 12
2. Application architecture and physical DFDs – Chapter 13
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.
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.
Exhibit 9.1
See on-line learning center website for the textbook.
Enter Component Information Narrative
To add a component to a piece of equipment a technician will use a web browser and go to the URL of the ASP.NET page for the Customer Response System. If the technician has not already logged on for this session, the system will require that the technician logon. Once the logon is verified, the system will present an ASP.NET page with a choice of clients using an HTML select object. Once the client is selected, the system will present a list of equipment for that client with hyperlinks. The technician will click on the hyperlink for the appropriate piece of equipment. The system will present an ASP.NET page with the component input form with inputs for Component (using an HTML select object that is filled in with choices from the ComponentType table), Quantity (using an HTML textbox object), and SerialNum (using an HTML select object). DateInstalled will be filled in from the system date but with an option for the technician to override (using an HTML select object). EquipNum will be filled in from the previous selection of equipment. ComponentNum is sequential number auto-generated by Oracle.
Clicking the submit button will launch an ASP.NET page that adds the new component to the EquipmentComponent table using an SQL INSERT command. The system will then display an ASP.NET page with a list of all components installed for that piece of equipment that do not have a DateRemoved along with links that allow the technician to delete any components that were removed at the same time. If a “remove” link is clicked for a component, an ASP.NET page will launch that sets the DateRemoved for that component using an SQL UPDATE command and the system date. The system will then return to the revised list of installed components for that piece of equipment.
本文来源：https://www.2haoxitong.net/k/doc/8791ce1152d380eb62946dfb.html
文档为doc格式