UML Diagram Explanation: SPB's Engineering Document Management

This report provides a detailed explanation of UML diagrams and Data Flow Diagrams (DFDs) for SPB, an engineering firm specializing in mechanical engineering assistance. The report includes a context-level DFD and a Level 0 DFD, illustrating the flow of documents and information within the firm. The context diagram outlines interactions between customers, peer engineers, and the engineering department, while the Level 0 DFD elaborates on processes such as document requesting, reviewing, editing, and storage. The system emphasizes quality assurance and change management, ensuring documents are thoroughly reviewed and updated based on customer and peer engineer feedback. The continuous feedback loop allows for modifications and updates until the customer's requirements are fully met, highlighting the iterative nature of the document management process.

Running head: UML EXPLAINATION
UML Explanations
Name of the Student:
Name of the University:
Author Note

1
UML EXPLAINATION
Context Level DFD

2
UML EXPLAINATION
Level 0 DFD
Explanation
The report has described DFD for the engineering firm SPB. This firm is associated with
providing mechanic engineering assistance towards organizations. This includes managing the
documents properly so that they can be accessed at time. There are around 500 engineers
associated with the organization. The main strength of SPB is that it entirely focuses on quality
assurance procedures and change management. The developed context diagram describes three
components customers, peer engineer and engineering. Engineering department is responsible for
writing the draft and submitting it to peer engineers. Once the draft gets assured than SPB
provides feedback towards the peer engineer. After this the documents are being fetched by SPB

3
UML EXPLAINATION
from peer engineer. After this the customers can request for the document from the SPB. The
process is continuous and there is no end at this level. The customer needs to provide details
while they requesting for the documents through the web portal. The engineer will further
circulate the processing. Once the need of the customer is being processed the step goes to next
level. The document gets updated until the customer is satisfied. Thus this will be an on going
process.
Level 0 DFD describes the process that includes two stores that includes reviewing data
and document store. Customer can request document from document requesting process. Once
the document request is provided by the customer it gets approved by the enginners.this
documents undergoes reviewing process once the process is found perfect the reviewed record
gets passed on to the store of review record. After this the review is being fetched and transferred
to engineers. Then it is the responsibility of engineers to submit a draft to document editing
process. After the document is being updated it gets saved within the document store. Then after
proper checking the data gets dispatched to the customer and the customer gets requested
documents. At each step the documents are verified and checked. Level 0 DFD includes several
stages and process that are needs to be completed before sending the requested documents.
Fetching the data and proper updation is needed so that it ensures that proper and correct data are
submitted to their customer. Peer engineers are responsible for providing proper review towards
the document process. This will ensure that the record stored into storage is prominent. However
the process is continuous and gets executed in loop. However customers are allowed to change or
modify their requirements. Once the customer updates their document it becomes responsibility
of the peer engineer to review the documents properly and then storing for further purposes.
After this document is sent directly to the updating process where the new data gets updated and

4
UML EXPLAINATION
the customer can get newly developed documents. The process goes on until the customer gets
their required document.

5
UML EXPLAINATION
Bibliography
Soares, J. A. C. (2017). Automatic Model Transformation from UML Sequence Diagrams to
Coloured Petri Nets.
Torre, D., Labiche, Y., Genero, M., &Elaasar, M. (2018). A systematic identification of
consistency rules for UML diagrams. Journal of Systems and Software.