preview

Nt1310 Unit 1 Assignment

Decent Essays
Open Document

4.3.3 Delivery Entity This entity stores all information about active delivery runs, to include pickup and drop off dates, client’s making a request for service, and the receiving client (destination). This entity is the general correlationd point for other domain objects within the software. 4.3.4 Payment Entity This entity stores information about a payment that correlates directly from a client to a package being delivered. 4.3.5 Finances Entity This entity stores informationabout all payment made to the company through GT. 5. Dependency Description Figure 6. Level 1 Data Flow Diagram The services modules save, delete and update the domain object via the database module entities. The user interface module interacts with the service module. …show more content…

These include the user interface, services, domain objects and database. For the scope of this document, the database module is called directly by the service modules as appropriate, and will not be extracted as a core module for description. In figure 7, these are highlighted as dependenceies, with the added interaction of the user in the user terminal. Figure 7. Inter – module dependencies diagram • The user interface component has dependencies on the service module. Since the user interface is tasked with displaying information from the GT, this dependenccy allows the business logic from the services module to be represented in the main screen directly at user terminal. The user has a dependency on the user interaction. • The services component has dependencies on both the user interface element to represent the view, as well as the domain objects element to store information. • The domain objects element has a dependency on the services element to process information with business logic, as explained above. 5.2 Inter – Process …show more content…

PackagePickup has a dependency on the other services that include: • CreateTicket – this defines the package information for a client’s order. • CalendarLookup – this relationship is defined by the link between a set of dates, and the subsequent client order at the company. • TakeClientInformation – this dependency is used to drive information for a clients object, which directly corresponds to a order. • MakePayment – the relationship is defined as the payment by a client which is linked to a ticket creation. 2. LookForDelivery process is loosley related to the CreateTicket service bceause this process is defined as a concurrent service that scans the inventory to remove packages from storage in the event that the guarantee delivery date is near. 5.3 Data Dependencies Data dependencies in the GT are loosely linked through process depencdencies to the services. This is done to abstract business logic away from both the user interface element and the domain object model. Due to this fact, there is no direct correlation between any of the domain objects. Instead, the processes and services share the dependencies to assist in business logic needs and abstraction between modules. Figure 10. Data dependencies diagram 6. Interface

Get Access
Related
Get Access