MIS102 Data and Networking Research Report Sample

Introduction

Woolworths Group is a renowned retail conglomerate based in Australia that operates specifically in supermarkets and general merchandise. The company was founded in 1924 and is headquartered in Bella Vista, New South Wales. The firm’s largest division is Woolworths Supermarkets, which is the largest supermarket chain in Australia, with over 1,000 stores nationwide. Woolworths Supermarkets sells a range of products, including groceries, fresh produce, and household items.

Historical financial context: the 2021 annual report (p. 19) lists AUD 55,694 million in sales from continuing operations and AUD 67,278 million in total Group sales, including discontinued operations. Total Group sales increased 5.7%. These are dated sales figures, not current revenue statistics. The report separately identifies the Endeavour businesses as discontinued operations.

How to use this sample: the network analysis below is an original illustrative retail model. It is not a verified description of Woolworths’ internal systems or an official MIS102 assessment answer. No company servers, packet traces or configurations were inspected. Use your own course brief to decide what evidence, diagrams and analysis your report needs.

Discussion of Data Flows and Communication Protocol Stacks of the Company

Network Topology Diagram

Figure 1: retained topology illustration. Its company and provider labels have not been independently verified. The two existing illustrations are retained as teaching material, not evidence of a deployed company network. For the model below, follow each data item from its origin to its destination:

  1. Updating product information: a staff client sends a product ID, new price and record version to a catalogue service over HTTPS. The service checks permission and validates the change before updating the product record. A receiving store system checks the version so that an older update does not overwrite a newer one. Test the example with a duplicate request and an out-of-date version.
  2. Generating sales reports: a simulated point-of-sale system exports a batch of synthetic sales records. In this model, SFTP transfers the batch to a reporting host, which checks the expected record count and reporting period before aggregation. An authorized user retrieves the finished report over HTTPS. A file arriving successfully does not establish that its contents are complete.
  3. Conducting product research: an analyst requests aggregated product-level sales from a reporting service over HTTPS. Record the source, period and any missing records with the output. Use synthetic data for a class demonstration and exclude customer identifiers that the question does not require.
flow of data and the protocols

Figure 2: retained illustrative data flow. Read its collection, aggregation, analysis, sharing and storage steps within the model’s stated scope.

Description and Analysis of the Architecture and the Distribution of Data Used by the Company

The model separates the catalogue’s transactional records from the reporting copy. This is a design choice for the exercise, not a claim that Woolworths uses particular databases, cloud providers or network routes. Explain the choice through requirements and trade-offs:

  • Catalogue records: define a product key, validation rules and a version check for updates. Explain how a failed or repeated request is handled.
  • Reporting copy: keep a record of which batches were imported and the time of the last successful refresh. Explain when a report may lag behind the source.
  • Distribution: identify which components communicate and which data must cross a boundary. Additional nodes may help with a requirement, but they also create synchronization and recovery work.
  • Evaluation: compare response time, missing/duplicate records and recovery behavior using a documented test in a permitted lab. Do not claim a performance improvement before measuring it.

Comparison of the Communication Protocol Stacks in the Company.

HTTPS, SFTP and TCP are not three interchangeable services at one layer. HTTPS and SFTP support application tasks; TCP is a transport protocol that other protocols can use. The following comparison describes mechanisms, not a list of protocols observed inside Woolworths:

HTTPS: interactive web/API requests
Use it for the model’s catalogue requests and report retrieval. HTTP Semantics (RFC 9110) defines the HTTPS scheme and its default port, 443. TLS provides protected communication; RFC 9846 specifies TLS 1.3. HTTPS does not by itself decide which business records a signed-in user may change.
SFTP: batch-file transfer
Use it for the model’s sales-export file. The OpenSSH sftp manual describes file transfer over an encrypted SSH transport. Connect to the configured SSH service port; it need not be a hard-coded value in your design. Check file identity, import status and content completeness separately.
TCP: transport beneath applications
RFC 9293 specifies a reliable, ordered byte stream. TCP alone does not encrypt the application payload or establish whether a business transaction succeeded. It has no single application-service port. Avoid saying all HTTPS uses TCP: HTTP/3 (RFC 9114) maps HTTP onto QUIC.

Conclusion

A useful networking report connects a business task to a data item, a route, a protocol choice and a check that the task completed correctly. In this example, interactive requests and batch exports have different needs, while transport security and application permissions address different questions. Keep the documented company context separate from the model’s assumptions, and support each technical claim with the source that actually describes it.

Recommendations

For this illustrative design, evaluate the following actions against the course requirements. They are proposed checks, not findings of weaknesses in Woolworths’ systems:

  1. Access and validation: define who may update catalogue records or retrieve reports. Reject invalid input, check the remote endpoint and use protected transport. Record a lab test showing an unauthorized update is rejected.
  2. Performance and data quality: measure response time and batch delay with synthetic workloads. Check missing and duplicate records before proposing caching or extra servers; record the baseline and the changed result.
  3. Recovery: state the acceptable recovery time and data-loss limit for the exercise. Test restoration from a permitted backup and verify the restored records. Do not infer that a real company lacks a recovery plan from the absence of public detail.

References

Leave a Reply

Your email address will not be published. Required fields are marked *