Essays on Infrmtin System Design Assignment

Download full paperFile format: .doc, available for editing

The paper "Infоrmаtiоn System Design " is a good example of a business assignment. In this report, I will discuss the process of this portfolio development. We worked in a team to complete this assignment. Every team member has taken an equal part and completed the tasks which were assigned to them. I also completed my tasks. In this report I will write my viewpoints and what I learned from this assignment. We had to design various UML diagrams for The Tourist Information Centre. We started this system development process by analyzing the system.

We then decided on the entities and classified the information required to complete certain tasks of UML diagrams. In this report, I will discuss different aspects of UML development. I will present reflection in the context of different diagrams. Value of Data Flow Diagram A data flow diagram is a very good way to offer a deep and detailed analysis of system functions processes and functions. This diagram offers a comprehensive analysis of some of the major areas and aspects of the system interactions and communications among system entities and database.

Basically, a data flow diagram is an excellent way of showing a system at any level of detail with a graphic network of symbols demonstrating data flows, data stores, data processes, and data sources/destinations. This assignment has helped me to understand some of the basic techniques of system design and development. I have learned about one of the essential tools for system development is known as a data flow diagram. As discussed above, it is used to identify the flows of data from one entity to another. This flow is demonstrated using arrows.

These arrows help us understand where data is coming, where it will be processed and where it will be stored. This is an excellent way to understand the system’ s working. In addition, the data flow diagrams are used to build a semantic bridge between system developers and system users. The diagrams are: Graphical demonstration of a system allows us to eliminate thousands of words; It presents a logical model which helps us understand what a system will do, instead of physical demonstration demonstrating how it will be done; A hierarchy of activities and functions demonstrating systems at any level of detail; and Easy way of understanding allowing user understanding and reviewing.


Ambler, S.W., 2012. UML 2 Use Case Diagrams. [Online] Available at: [Accessed 18 December 2012].

JKiNFOLINE, 2010. Software Engineering: Object Oriented Analysis and Design. [Online] Available at: [Accessed 16 December 2012].

Kozar, K.A., 1997. The Technique of Data Flow Diagramming. [Online] Available at: [Accessed 10 December 2012].

Mishra, R.K. & Lohani, B., 2010. OBJECT ORIENTED SOFTWARE ENGINEERING FOR DESIGNING AN AERIAL SURVEY LIDAR SIMULATOR. [Online] Available at: [Accessed 13 December 2012].

Pressman, R.S., 2001. Software Engineering: A Practicioner's Approach, 5th Edition. London: McGraw Hill.

Sommerville, I., 2004. Software Engineering, 7th Edition. New York: Pearson Education (Addison Wesley).

TechnologyUK, 2012. An Introduction to OOAD. [Online] Available at: [Accessed 16 December 2012].

TutorialsPoint, 2012. UML Class Diagram. [Online] Available at: [Accessed 16 December 2012].

Download full paperFile format: .doc, available for editing
Contact Us