Documentation through Diagrams" Please respond to the following:

Imagine that you have been working on a project to design and build a given system. You have completed the elicitation and evaluation phases and now you need to specify and document the system-to-be.

Suppose you have decided to use diagrammatic notations for the specification and documentation. Your options are to use context diagrams or frame diagrams. Evaluate each type of diagram and select the one you feel is the best fit. Provide a rationale.

Compare Entity-Relationship (ER) diagrams, Structured Analysis and Design Technique (SADT) diagrams, data flow diagrams (DFD), and Unified Modeling Language (UML) use cases.

Determine which diagram you are most likely to use for your system documentation. Provide a rationale.

Classmates:

Imagine that you have been working on a project to design and build a given system. You have completed the elicitation and evaluation phases and now you need to specify and document the system-to-be. Suppose you have decided to use diagrammatic notations for the specification and documentation. Your options are to use context diagrams or frame diagrams. Evaluate each type of diagram and select the one you feel is the best fit. Provide a rationale.

Context Diagrams

System Context Diagrams... represent all external entities that may interact with a system... Such a diagram pictures the system at the center, with no details of its interior structure, surrounded by all its interacting systems, environments and activities. The objective of the system context diagram is to focus attention on external factors and events that should be considered in developing a complete set of systems requirements and constraints.

Frame Diagrams

The advantage and disadvantage of frame diagrams

The major disadvantages of using frame diagrams are:

Bookmarks only bookmark the top level pages (the framesets themselves). A user is unable to bookmark any of the Web pages viewed within a frame.

Frames can make the production of a website complicated, although current software addresses this problem.
It is easy to create badly constructed websites using frames. The most common mistake is to include a link that creates duplicate Web pages displayed within a frame.

Search engines that reference a Web page only give the address of that specific document. This means that search engines might link directly to a page that was intended to be displayed within a frameset.

Users have become so familiar with normal navigation using tables, the back button, and so on, that navigating through a site that uses frames can be a problem.

The use of too many frames can put a high workload on the server. A request for, say, ten files, each 1 Kilobyte in size, requires a greater workload than a request for a single 10 Kilobyte file.
Older browsers do not support frames.

The advantages of Frame Diagram include:

The main advantage of frames is that it allows the user to view multiple documents within a single Web page.
It is possible to load pages from different servers in a single frameset.

The concern that older browsers do not support frames can be addressed using the tag. This tag provides a section in an HTML document to include alternative content for browsers without support for frames. However, it requires that the Web designer provide two formats for one page ( University of Cape Town, 2010).

Compare Entity-Relationship (ER) diagrams, Structured Analysis and Design Technique (SADT) diagrams, data flow diagrams (DFD), and Unified Modeling Language (UML) use cases. Determine which diagram you are most likely to use for your system documentation. Provide a rationale.

Entity-Relationship (ER) diagrams: Entity Relationship Diagrams is a network model that describes the stored data layout of a system at a high level of abstraction.

SADT Diagram : is a system engineering and software engineering methodology for describing systems as a hierarchy of functions. SADT is a modelling language, which uses two types of diagrams: activity models and data modles. It was developed in the late 1960s by Douglas Ross, and was formalized and published as lDEF0 in 1981.

Unified Modeling Language : Unified Modeling Language (UML) diagramming was created: to forge a common visual language in the complex world of software development that would also be understandable for business users and anyone who wants to understand a system.

However, the diagram that will make the best fit for the system will be Entity-Relationship (ER) diagrams because you can just about structure the foundation of any projects base off of relationships of those structures foundations.