{"id":36911,"date":"2024-03-04T00:28:01","date_gmt":"2024-03-04T00:28:01","guid":{"rendered":"https:\/\/essays.homeworkacetutors.com\/2024\/03\/a-data-flow-diagram-information-technology-essay\/"},"modified":"2024-03-04T00:28:01","modified_gmt":"2024-03-04T00:28:01","slug":"a-data-flow-diagram-information-technology-essay","status":"publish","type":"post","link":"https:\/\/www.colapapers.com\/us\/a-data-flow-diagram-information-technology-essay\/","title":{"rendered":"A Data Flow Diagram Information Technology Essay"},"content":{"rendered":"
\n

Other than data flow, system requirement specification also need to be focuses. A requirements specification is a document which is used as a communication medium between the customers and the supplier. When the software requirement specification is completed and is accepted by all parties, the end of the requirements engineering phase has been reached.<\/p>\n

In the end of the assignment, we will learn about the flow of system shown uses Data Flow Diagram and how Requirement Specification work.<\/p>\n

2.0 Data Flow Diagram<\/h2>\n

Data Flow Diagram (DFD) is a graphical uses to represent the flow of data in a system. It shows the flow of data as they moving between input and output. The purpose of using Data Flow Diagram as a representative of a system is to provide a simple method of describing how the system work without needed to focus on the detail of the computer systems.<\/p>\n

Symbol of Data Flow Diagram<\/h2>\n

A Data Flow Diagram uses 4 basic symbols as representative of process, data stores, data flow and entities. There are few different versions of DFD uses but still it is also serving as the same purpose.<\/p>\n

Description<\/p>\n

Symbol<\/p>\n

Entities<\/h2>\n

It uses can represent a human, subsystem or system. This where certain data comes from \/ goes to. People often draw external entities on the edge of a diagram.<\/p>\n

Process<\/h2>\n

A process is a function or activity where the manipulation and change of data takes place. A process can be decomposed to better level of details purpose of representing how data is being processed within the process.<\/p>\n

Data Store<\/h2>\n

A data store represents the storage of data required and which it produced by the process. Examples of data stores: database, membership forms, and more.<\/p>\n

Data Flow<\/h2>\n

A data flow represents the flow of the system, whereby its direction represented by an arrow head that shows at the end of flow.<\/p>\n

2.1 Level of Data Flow Diagram<\/p>\n

A Data Flow Diagram is hierarchical, divide into 3 types:<\/p>\n

Level 0<\/p>\n

Level 1<\/p>\n

Level 2<\/p>\n

2.1.1 Level 0 DFD<\/h2>\n

In level 0 DFD, it only focuses on the context view of the flow in 1 process which is the most simplify version of DFD.<\/p>\n

2.1.2 Level 1 DFD<\/h2>\n

In level 1 DFD, it goes deeper then level 0, which it expand the graphical model into more complex that represent the flow of data.<\/p>\n

2.1.3 Level 2 DFD<\/h2>\n

In level 2 DFD, it focuses more closely in one particular process in level 1.<\/p>\n

2.2 Rules of Data Flow Diagram<\/h2>\n

There are few rules that must be follow when creating a Data Flow Diagram (DFD):<\/p>\n

Data flow that connects<\/p>\n

YES<\/h2>\n

NO<\/h2>\n

A process to another process<\/p>\n

Check mark symbol<\/p>\n

A process to an external entity<\/p>\n

Check mark symbol<\/p>\n

A process to a data store<\/p>\n

Check mark symbol<\/p>\n

An external entity to another external entity<\/p>\n

Check mark symbol<\/p>\n

An external entity to a data store<\/p>\n

Check mark symbol<\/p>\n

A data store to another data store<\/p>\n

Check mark symbol<\/p>\n

2.3 Student Registration System<\/h2>\n

Below is an example of 3 different types of Data Flow Diagram uses in a simple student registration system for a college:<\/p>\n

2.3.1 Level 0:<\/h2>\n

Registration Form<\/p>\n

Student registration system<\/p>\n

Student<\/p>\n

Confirmation Letter<\/p>\n

2.3.2 Level 1:<\/h2>\n

1.0<\/p>\n

Verify<\/p>\n

Availability<\/p>\n

Open course<\/p>\n

D1<\/p>\n

Accept \/ Reject<\/p>\n

result<\/p>\n

Registration form<\/p>\n

Course<\/p>\n

Course info<\/p>\n

Course enrollment<\/p>\n

2.0<\/p>\n

Enroll<\/p>\n

Student<\/p>\n

Student<\/p>\n

Student info<\/p>\n

Registration<\/p>\n

Confirmation letter<\/p>\n

D2<\/p>\n

3.0<\/p>\n

Confirm<\/p>\n

Registration<\/p>\n

Student<\/p>\n

Update info<\/p>\n

2.3.3 Level 2:<\/h2>\n

Course<\/p>\n

Open course<\/p>\n

D1<\/p>\n

1.0<\/p>\n

Verify<\/p>\n

Availability<\/p>\n

Advisor<\/p>\n

Registration form<\/p>\n

Student<\/p>\n

Course info<\/p>\n

Reject<\/p>\n

1.1<\/p>\n

Permission<\/p>\n

Course enrollment<\/p>\n

Accept<\/p>\n

Confirmation Letter<\/p>\n

2.0<\/p>\n

Enroll<\/p>\n

student<\/p>\n

Student<\/p>\n

Registration<\/p>\n

Student info<\/p>\n

D2<\/p>\n

Update info<\/p>\n

Payment<\/p>\n

Registration<\/p>\n

fee<\/p>\n

2.1<\/p>\n

Account<\/p>\n

D3<\/p>\n

2.2<\/p>\n

Course payment method<\/p>\n

Receipt issued<\/p>\n

2.2.2<\/p>\n

2.2.1<\/p>\n

Installment<\/p>\n

Financial<\/p>\n

aid<\/p>\n

Update info<\/p>\n

3.0 Requirement Specification<\/h2>\n

In a large project the analyst could also have a number of people work under them. Theses extra staff would carry out the questionnaires, observations and interviews, required to develop the overall specification.<\/p>\n

When developing a project, an agreement between the client and project team are formed. Document of requirement specification gave the information to client or customer regarding the project.<\/p>\n

3.1 Layout of Requirement Specification<\/h2>\n

The requirement specification is carefully listed and highlighted according the following:<\/p>\n

Scope of the system<\/p>\n

Objectives<\/p>\n

Timing<\/p>\n

Constraints<\/p>\n

Inputs<\/p>\n

Outputs<\/p>\n

Processing requirement<\/p>\n

Contract<\/p>\n

3.1.1 Scope of the system<\/h2>\n

This offers a context for the system within the organization. For instance, the scope will regularly define what it will not do and general explanation of what it will do.<\/p>\n

3.1.2 Objective<\/h2>\n

It laid out point by point so it is clear define that what the system needs to do. Table or bullet points could be used in this process.<\/p>\n

3.1.3 Timing<\/h2>\n

In this section, it provides a timeline of how the project will proceed and the time require for it to be done.<\/p>\n

3.1.4 Constraints<\/h2>\n

It is referring to the budget and manpower that which is available for the project.<\/p>\n

3.1.5 Inputs<\/h2>\n

In this section, it defines what inputs are needed by the system. It will provide outline details of the input screens, data capture forms, automated system feeds and more. It doesn\u2019t try to be very technical at this point instant it just an overall idea of what will be accepted into the system and how this is to be achieved.<\/p>\n

3.1.6 Outputs<\/h2>\n

A system has to produce an output in one form or another. In this section, it will describe the expected form of outputs. For example, output viewing screen, printed reports and graphs, files created and stored, and any output data feed to other system and so on.<\/p>\n

3.1.7 Processing requirement<\/h2>\n

Between the process of Input and Output, processing in the middle is required. This part of Requirement Specification defines the processing to be carried out. Processing details are include:<\/p>\n

\u2013 Procedures<\/p>\n

\u2013 Validation details<\/p>\n

\u2013 Acceptable limits of processing times<\/p>\n

3.1.8 Contract<\/h2>\n

The requirements specification is in result of a contract between the end user and the people that responsible for delivering the project.<\/p>\n

3.2 Important of Requirement Specification<\/h2>\n

It\u2019s important to note that a requirement specification contains functional and\u00a0non-functional requirements only; it does not offer design\u00a0suggestions, possible solutions to technology or business\u00a0issues, or any other information other than what the\u00a0development team understands the customer\u2019s system requirements\u00a0to be.<\/p>\n

A well-managed requirement specification could accomplish four major\u00a0goals:<\/p>\n

It provides feedback to the customer \u2013<\/p>\n

A requirement specification is the\u00a0customer\u2019s assurance that the development organization\u00a0understands the problem and issue to be solved and the\u00a0software behavior necessary to locate those problems.\u00a0Therefore, it should be written in standard language, in an explicit manner that may also include\u00a0charts, data flow diagrams, table, decision tables, and so\u00a0on.<\/p>\n

It decomposes the problem into component parts \u2013<\/p>\n

The\u00a0simple act of writing down software requirements in a\u00a0well-designed format organizes information, places borders\u00a0around the problem, solidifies ideas, and helps break down\u00a0the problem into its component parts in an orderly\u00a0fashion.<\/p>\n

It serves as a input to the design specification \u2013<\/p>\n

As\u00a0mentioned previously, the requirement specification serves as the parent document\u00a0to subsequent documents, such as the software design\u00a0specification and statement of work. Therefore, the SRS\u00a0must contain enough detail in the well-designed system\u00a0requirements so that a design solution can be planned.<\/p>\n

It serves as the parent document \u2013<\/p>\n

For testing and validation\u00a0strategies that will be applied to the requirements for\u00a0verification.<\/p>\n

4.0 Conclusion<\/h2>\n

In system analysis and design, it focuses on the improvement of creating a good system of information data. By learning the proper way of analyzing and designing \/ developing a system, it could lead us into deeper understanding about the system.<\/p>\n

In the above assignment we have learn the usage of Data Flow Diagram which serve as a guide for developer and analyst to check the flow of the system, and we also have learn that when creating a system software, a documentation regarding the software project are also an important step to do.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Other than data flow, system requirement specification also need to be focuses. A requirements specification is a document which is used as a communication medium between the customers and the supplier. When the software requirement specification is completed and is accepted by all parties, the end of the requirements engineering phase has been reached. In […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7348,5863,7336],"tags":[7341,7337,7340,7338,7339],"class_list":["post-36911","post","type-post","status-publish","format-standard","hentry","category-ace-homework-tutors-information-technology","category-information-technology","category-write-my-essay-for-me-2","tag-affordable-essay-pro-papers-uk","tag-assist-with-thesis-writing-online","tag-complimentary-essay-example","tag-online-dissertation-help-from-phd-experts","tag-top-u-s-dissertation-writing-services"],"_links":{"self":[{"href":"https:\/\/www.colapapers.com\/us\/wp-json\/wp\/v2\/posts\/36911","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.colapapers.com\/us\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.colapapers.com\/us\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.colapapers.com\/us\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.colapapers.com\/us\/wp-json\/wp\/v2\/comments?post=36911"}],"version-history":[{"count":0,"href":"https:\/\/www.colapapers.com\/us\/wp-json\/wp\/v2\/posts\/36911\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.colapapers.com\/us\/wp-json\/wp\/v2\/media?parent=36911"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.colapapers.com\/us\/wp-json\/wp\/v2\/categories?post=36911"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.colapapers.com\/us\/wp-json\/wp\/v2\/tags?post=36911"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}