Reference no: EM132898626
1. Read the below paragraph and write your opinion. (Chen Zhong)
Business documents are commonly used during the development of software/applications/processes in a modern business setup. I had fair amount of experience with these type of documents when I was working for my old firm to established new channels to accommodate our data needs. To me there are several drawbacks in business documents:
1. If poorly designed, there can be many fields that can be filled with duplicate information, which causes unnecessary waste of time and makes the document harder to read by other people
2. The document doesn't usually provide the full picture. As many requirements are starting off vague and can only be firmed up during later development phases, analyzing purely on business documents can sometimes be miss leading and not efficient.
3. There can often be missing spots and cases where the document can't identify in the beginning.
To solve this issue, I would suggest having a clear outline regarding what are necessary aspects for a successful development program. And extract information that is relevant and useful from the business documents. Also, try to reference multiple sources instead of relying solely on the business document as the golden standard. Also try to consult with departments that will be closely involved in the project and get their view on what's are the necessary steps as well as where might be some area of overlooked places.
2. Read the below paragraph and write your opinion.
We learn about the concept of the Data Flow Diagram (DFD), which demonstrates the flow or process in a very intuitive way. One can include information such as key middle steps or systems; a brief description of the intermediate steps between key steps and systems; adding process controls. There are many aspects and areas a Data Flow Diagram, and one can go into different levels of structure to better facilitate idea demonstration. This is one of the very useful tools that can be applied to some of the projects at my current firm. From time to time, we are working on long-term projects that involve a lot of operation and process automation, which requires a lot of interactions among different systems and very heavy on the exchange of data flow. Hence DFD can be used in various stages throughout the development of such projects. For example, if we are designing a automated trade generate a system that utilizes external data to run signal generation which eventually translates to actual trades to the desk, we can use DFD to clearly demonstrate the input/output of each system and how systems are connected with each other. Also, each process can be broken down into more granular subsections that can capture the flow structure in each detail in a more detailed fashion.