Question

Case Study: Auto-Parts Warehouse Management System

Jack Greig and Daniel Cox have several years of experience of running an auto-parts business as a supplier in a major city of Australia. The current warehouse management system is not able to handle highly dynamic procedures that can help them move and store inventory at peak efficiency and lowest cost. Jack and Daniel have decided to develop a new Auto-Parts Warehouse Management System where its functionality can be applied throughout all core warehouse processes, transforming the warehouse into a competitive advantage.

You are the business system analyst assigned to develop this system. In your meeting with Jack and Daniel, they provided significant details regarding the basic operations of the system. They expect the system will perform the various functions such as receiving all types of orders, inventory control, order processing, pick up and process orders, order load management, outbound documentation, system alerts, packing orders, and crystal reports. Please note, you must consider the number of wireless communication devices that configure with the proposed system and enables the warehouse management to run the distribution using real-time operations. These extensive system functions will improve warehouse operations by minimising costs and increasing productivity.

Task

Further background

Refer to the Project Vision Document submitted in Assessment Item 1 regarding Auto-Parts Warehouse Management System. In this assignment, you are required to prepare a report that describes the detailed architecture and design of the proposed system.

Complete the Following

Please refer to the marking guide when preparing your response to see what criteria and standards will be used to assess your work and your progress.

Amongst the information sought are answers to the following questions:

Identify use cases and draw use case diagrams for the proposed system that show major use cases and actors.

system vision document assignment 1 -

Answer 1

Related data

List of chapters

1. Presentation

1.1 Purpose

1.2 Scope

1.3 Definitions, Acronyms and Abbreviations

1.4 References

2. Engineering Representation

3. Engineering Goals and Constraints

4. Use-Case View

4.1 Architecturally-Significant Use Cases

5. Legitimate View

5.1 Architecture Overview – Package and Subsystem Layering

6. Procedure View

6.1 Processes

6.2 Process to Design Elements

6.3 Process Model to Design Model Dependencies

6.4 Processes to the Implementation

7. Sending View

7.1 External Desktop PC

7.2 Desktop PC

7.3 Registration Server

7.4 Course Catalog

7.5 Billing System

8. Size and Performance

9. Quality

Programming Architecture Document

1. Presentation

1.1 Purpose

This archive gives an exhaustive compositional review of the framework, utilizing various distinctive building perspectives to portray various parts of the framework. It is planned to catch and pass on the huge structural choices which have been made on the framework.

1.2 Scope

This Software Architecture Document gives an engineering review of the C-Registration System. The C-Registration System is being created by Wylie College to help online course enlistment.

This Document has been created straightforwardly from the C-Registration Analysis and Design Model executed in Rose. Most of the areas have been extricated from the Rose Model utilizing SoDA and the Software Architecture Document layout.

1.3 Definitions, Acronyms and Abbreviations

See the Glossary [4].

1.4 References

Pertinent references are:

Course Billing Interface Specification, WC93332, 1985, Wylie College Press.

Course Catalog Database Specification, WC93422, 1985, Wylie College Press.

Vision Document of the C-Registration System, WyIT387, V1.0, 1998, Wylie College IT.

Glossary for the C-Registration System, WyIT406, V2.0, 1999, Wylie College IT.

Use Case Spec - Close Registration, WyIT403, V2.0, 1999, Wylie College IT.

Use Case Spec – Login, WyIT401, V2.0, 1999, Wylie College IT.

Use Case Spec - Maintain Professor Info, WyIT407, Version 2.0, 1999, Wylie College IT.

Use Case Spec - Register for Courses, WyIT402, Version 2.0, 1999, Wylie College IT.

Use Case Spec - Select Courses to Teach, WyIT405, Version 2.0, 1999, Wylie College IT.

Use Case Spec - Maintain Student Info, WyIT408, Version 2.0, 1999, Wylie College IT.

Use Case Spec - Submit Grades, WyIT409, Version 2.0, 1999, Wylie College IT.

Use Case Spec - View Report Card, WyIT410, Version 2.0, 1999, Wylie College IT.

Programming Development Plan for the C-Registration System, WyIT418, V1.0, 1999, Wylie College IT.

E1 Iteration Plan, WyIT420, V1.0, 1999, Wylie College IT.

Strengthening Specification, WyIT400, V1.0, 1999, Wylie College, IT.

2. Structural Representation

This record shows the design as a progression of perspectives; use case see, consistent view, process view and arrangement see. There is no different usage view depicted in this record. These are sees on a basic Unified Modeling Language (UML) model created utilizing Rational Rose.

3. Compositional Goals and Constraints

There are some key prerequisites and framework requirements that have a noteworthy bearing on the design. They are:

The current heritage Course Catalog System at Wylie College must be gotten to recover all course data for the present semester. The C-Registration System must help the information arrangements and DBMS of the inheritance Course Catalog System [2].

The current heritage Billing System at Wylie College must be interfaced with to help charging of understudies. This interface is characterized in the Course Billing Interface Specification [1].

All understudy, educator, and Registrar usefulness must be accessible from both nearby grounds PCs and remote PCs with web dial up associations.

The C-Registration System must guarantee total assurance of information from unapproved get to. Every remote access are liable to client recognizable proof and secret phrase control.

The C-Registration System will be actualized as a customer server framework. The customer segment lives on PCs and the server part should work on the Wylie College UNIX Server. [3]

All presentation and stacking prerequisites, as stipulated in the Vision Document [3] and the Supplementary Specification [15], must be mulled over as the design is being created.

4. Use-Case View

A portrayal of the utilization case perspective on the product engineering. The Use Case View is significant contribution to the determination of the arrangement of situations or potentially use cases that are the focal point of an emphasis. It portrays the arrangement of situations and additionally use cases that speak to some critical, focal usefulness. It likewise portrays the arrangement of situations as well as use cases that have a considerable engineering inclusion (that activity numerous building components) or that pressure or represent a particular, sensitive purpose of the design.

The C-Registration use cases are:

- Login

- Register for Courses

- Maintain Student Information

- Maintain Professor Information

- Select Courses to Teach

- Submit Grades

- View Report Card

- Close Registration.

These utilization cases are started by the understudy, teacher, or the recorder entertainers. What's more, collaboration with outside on-screen characters; Course Catalog and Billing System happen.

4.1 Architecturally-Significant Use Cases

Chart Name: Architecturally Significant Use-Cases

4.1.1 Close Registration

Brief Description:This use case enables a Registrar to close the enlistment procedure. Course contributions that need more understudies are dropped. Course contributions must have at least three understudies in them. The charging framework is informed for every understudy in each course offering that isn't dropped, so the understudy can be charged for the course advertising. The fundamental on-screen character of this utilization case is the Registrar. The Billing System is an on-screen character required inside this utilization case.

4.1.2 Login

Brief Description:This use case portrays how a client signs into the Course Registration System. The on-screen characters beginning this utilization case are Student, Professor, and Registrar.

4.1.3 Maintain Professor Information

Brief Description:This use case enables the enlistment center to keep up teacher data in the enrollment framework. This incorporates including, adjusting, and erasing educators from the framework. The on-screen character of this utilization case is the Registrar.

4.1.4 Select Courses to Teach

Brief Description:This use case enables a teacher to choose the course contributions (date-and time-explicit courses will be given) from the course index for the courses that he/she is qualified for and wishes to educate in the forthcoming semester. The on-screen character beginning this utilization case is the Professor. The Course Catalog System is an on-screen character inside the utilization case.

4.1.5 Register for Courses

Brief Description:This use case enables an understudy to enroll for courses in the present semester. The understudy can likewise adjust or erase course determinations if changes are made inside the include/drop period toward the start of the semester. The Billing System is advised of all enlistment refreshes. The Course Catalog gives a rundown of all the course contributions for the present semester. The fundamental on-screen character of this utilization case is the understudy. The Course Catalog System is an entertainer inside the utilization case.

4.1.6 View Report Card

Brief Description:This use case enables an understudy to see his/her report card for the recently finished semester. The understudy is the on-screen character of this utilization case.

4.1.7 Submit Grades

Brief Description:This use case enables a teacher to submit understudy reviews for at least one classes finished in the past semester. The entertainer in this utilization case is the Professor.

4.1.8 Maintain Student Information

Brief Description:This use case enables the enlistment center to keep up understudy data in the enrollment framework. This incorporates including, adjusting, and erasing understudies from the framework. The entertainer for this utilization case is the Registrar.

5. Legitimate View

A depiction of the legitimate perspective on the engineering. Portrays the most significant classes, their association in administration bundles and subsystems, and the association of these subsystems into layers. Likewise portrays the most significant use-case acknowledge, for instance, the dynamic parts of the engineering. Class charts might be incorporated to show the connections between structurally noteworthy classes, subsystems, bundles and layers.

The sensible perspective on the course enlistment framework is involved the 3 principle bundles: User Interface, Business Services, and Business Objects.

The User Interface Package contains classes for every one of the structures that the on-screen characters use to speak with the System. Limit classes exist to help login, keeping up of calendars, keeping up of teacher information, choosing courses, submitting grades, keeping up understudy data, shutting enrollment, and survey report cards.

The Business Services Package contains control classes for interfacing with the charging framework, controlling understudy enrollment, and dealing with the understudy assessment.

The Business Objects Package incorporates substance classes for the college ancient rarities (for example course offering, calendar) and limit classes for the interface with the Course Catalog System.

5.1 Architecture Overview – Package and Subsystem Layering

5.1.1 Application

layer

This application layer has all the limit classes that speak to the ap