Starting with a context diagram, draw as many nested DFDs as you consider necessary to represent all of the details of the engineering document management system described in the following narrative. You must draw at least a context diagram and a level-0 diagram. In drawing these diagrams, if you discover that the narrative is incomplete, make up rea- sonable explanations to complete the story. Provide these extra explanations along with the diagrams. Projects, Inc. is an engineering firm with approximately 500 engineers that provide mechanical engineering assistance to organi- zations, which requires managing many docu- ments. Projects, Inc. is known for its strong emphasis on change management and quality assurance procedures. The customer provides detailed information when requesting a docu- ment through a web portal. The company liai- son (a position within Projects, Inc.) assigns an engineer to write the first draft of the requested document. Upon completion, two peer engineers review the document to ensure that it is correct and meets the requirements. These reviewers may require changes or may approve the document as is. The original engi- neer updates the document until the reviewers are satisfied with the quality of the document. The document is then sent to the company liaison, who performs a final quality check and ensures that the document meets the require- ments specified by the customer. Finally, the customer liaison sends the document to the customer for approval. The customer can require changes or accept the document. When the customer requires changes, the company liaison assigns an engineer to make the changes to the document. When those changes are made, two other engineers must review them. When those reviewers are satis- fied with the changes, the document is sent back to the company liaison, who sends the document back to the customer. This may hap- pen through several iterations until the cus- tomer is satisfied with the document.
Starting with a context diagram, draw as many
nested DFDs as you consider necessary to
represent all of the details of the engineering
document management system described in
the following narrative. You must draw at
least a context diagram and a level-0 diagram.
In drawing these diagrams, if you discover
that the narrative is incomplete, make up rea-
sonable explanations to complete the story.
Provide these extra explanations along with
the diagrams.
Projects, Inc. is an engineering firm with
approximately 500 engineers that provide
mechanical engineering assistance to organi-
zations, which requires managing many docu-
ments. Projects, Inc. is known for its strong
emphasis on change management and quality
assurance procedures. The customer provides
detailed information when requesting a docu-
ment through a web portal. The company liai-
son (a position within Projects, Inc.) assigns
an engineer to write the first draft of the
requested document. Upon completion, two
peer engineers review the document to ensure
that it is correct and meets the requirements.
These reviewers may require changes or may
approve the document as is. The original engi-
neer updates the document until the reviewers
are satisfied with the quality of the document.
The document is then sent to the company
liaison, who performs a final quality check and
ensures that the document meets the require-
ments specified by the customer. Finally, the
customer liaison sends the document to the
customer for approval. The customer can
require changes or accept the document.
When the customer requires changes, the
company liaison assigns an engineer to make
the changes to the document. When those
changes are made, two other engineers must
review them. When those reviewers are satis-
fied with the changes, the document is sent
back to the company liaison, who sends the
document back to the customer. This may hap-
pen through several iterations until the cus-
tomer is satisfied with the document.
consider the following diagram for representing the context diagram of the requried system:-
The system's operation is depicted in detail in the diagram above. The customer is the one who first notices the issue. An engineer is tasked to create the initial draught of requirements based on the problem. As a result,transmitted to peer engineers, who check for errors and return to the author.Engineer who changes it and returns it There were no more changes to be made after that.
The final document is submitted to the system, which does a final quality check.If the customer still need assistance, the work is completed and the paper is handed over to them.Include some more needs He has the ability to make suggestions for improvements.would be carried out in the same manner. Finally, once the buyer is satisfied,The system receives the approval. Following the deconstruction of the preceding context,The user will next be presented with the Level-0 schematic of the required system.
Trending now
This is a popular solution!
Step by step
Solved in 5 steps with 4 images
