{"id":3375,"date":"2018-01-19T15:32:24","date_gmt":"2018-01-19T20:32:24","guid":{"rendered":"http:\/\/community.mis.temple.edu\/mis5203sec001sec701sp2018\/?page_id=3375"},"modified":"2018-03-17T14:29:18","modified_gmt":"2018-03-17T18:29:18","slug":"week-8-mar-15-2018","status":"publish","type":"page","link":"https:\/\/community.mis.temple.edu\/mis5203sec001sec701sp2018\/week-8-mar-15-2018\/","title":{"rendered":"Week 8 &#8211; Mar. 15, 2018"},"content":{"rendered":"<p><strong>Class Slides:<\/strong><\/p>\n<ul>\n<li><a href=\"http:\/\/community.mis.temple.edu\/mis5203sec001sec701sp2018\/files\/2018\/03\/Structured_Data_Modeling.pdf\">Structured_Data_Modeling<\/a><\/li>\n<li><a href=\"http:\/\/community.mis.temple.edu\/mis5203sec001sec701sp2018\/files\/2018\/03\/EDI.pdf\">Electronic Data Interchange (EDI)<\/a><\/li>\n<\/ul>\n<p style=\"text-align: left;\"><a href=\"https:\/\/foxtemple.mediasite.com\/Mediasite\/Play\/ca6a84eb5f0b4671b605b62ca3651ed41d\"><strong>Class Video<\/strong><\/a> &#8211; Audio Only. Unfortunately the video was not recorded.<\/p>\n<p><a href=\"http:\/\/community.mis.temple.edu\/mis5203sec001sec701sp2018\/files\/2018\/03\/Example.xlsx\">Transaction File Integrity Check Example (Excel)<\/a><\/p>\n<h2>Electronic Data Interchange (EDI)<\/h2>\n<p>The material covered can be found in the CISA Review Manual, Section 3.7.2 Electronic Data Interchange, pages 188 through 191.<\/p>\n<h2><strong>Structured Data Analysis<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">\u201cIn\u00a0Unit 6, you learned how to model and analyze two important views of an information system: (1) the flow of data between manual or automated steps and (2) the decision logic of processing data. None of the techniques discussed so far, however, has concentrated on the data that must be retained in order to support the data flows and processing described. For example, you learned how to show data stores, or\u00a0data at rest,\u00a0in a data flow diagram (DFD). The natural\u00a0structure\u00a0of data, however, was not shown. DFDs, use cases, and various processing logic techniques show\u00a0how, where,\u00a0and\u00a0when\u00a0data are used or changed in an information system, but these techniques do not show the\u00a0definition, structure,\u00a0and\u00a0relationships\u00a0within the data. Data modeling develops these missing, and crucial, descriptive pieces of a system.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In fact, some systems developers believe that a data model is the most important part of the statement of information system requirements. This belief is based on the following reasons. First, the characteristics of data captured during data modeling are crucial in the design of databases, programs, computer screens, and printed reports. For example, facts such as these\u2014a data element is numeric, a product can be in only one product line at a time, a line item on a customer order can never be moved to another customer order, customer region name is limited to a specified set of values\u2014are all essential pieces of information in ensuring data integrity in an information system.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Second, data, not processes, are the most complex aspects of many modern information systems and hence require a central role in structuring system requirements. Transaction processing systems can have considerable process complexity in validating data, reconciling errors, and coordinating the movement of data to various databases. Current systems development focuses more on management information systems (such as sales tracking), decision support systems (such as short-term cash investment), and business intelligence systems (such as market basket analysis). Such systems are more data intensive. The exact nature of processing is also more ad hoc than with transaction processing systems, so the details of processing steps cannot be anticipated. Thus, the goal is to provide a rich data resource that might support any type of information inquiry, analysis, and summarization.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Third, the characteristics about data (e.g., length, format, and relationships with other data) are reasonably permanent and have significant similarity for different organizations in the same business. In contrast, the\u00a0paths and design of data flow are quite dynamic. A data model explains the inherent nature of the organization, not its transient form. Therefore, an information system design based on a data orientation, rather than a process or logic orientation, should have a longer useful life and should have common features for the same applications or domains in different organizations. Finally, structural information about data is essential for automatic program generation. For example, the fact that a customer order has many line items on it instead of just one line item affects the automatic design of a computer screen for entry of customer orders. Although a data model specifically documents the file and database requirements for an information system, the business meaning, or semantics, of data included in the data model has a broader effect on the design and construction of a system.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The most common format used for data modeling is\u00a0entity-relationship (E-R) diagramming.\u00a0A similar format used with object-oriented analysis and design methods is\u00a0class diagramming,\u00a0which is included in a special section at the end of this chapter on the object-oriented development approach to data modeling. Data models that use E-R and class diagram notations explain the characteristics and structure of data independent of how the data may be stored in computer memory. A data model is usually developed iteratively, either from scratch or from a purchased data model for the industry or business area to be supported. Information system (IS) planners use this preliminary data model to develop an enterprise-wide data model with very broad categories of data and little detail. Next, during the definition of a project, a specific data model is built to help explain the scope of a particular systems analysis and design effort. During requirements structuring, a data model represents conceptual data requirements for a particular system. Then, after system inputs and outputs are fully described during logical design, the data model is refined before it is translated into a logical format (typically a relational data model) from which database definition and physical database design are done. A data model represents certain types of business rules that govern the properties of data. Business rules are important statements of business policies that ideally will be enforced through the database and database management system ultimately used for the application you are designing. Thus, you will use E-R and class diagramming in many systems development project steps, and most IS project members need to know how to develop and read data model diagrams. Therefore, mastery of the requirements structuring methods and techniques addressed in this chapter is critical to your success on a systems development project team.<\/span><span style=\"font-weight: 400;\">\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Valacich, J. S., &amp; George, J. F. (2017).\u00a0<\/span><i><span style=\"font-weight: 400;\">Modern systems analysis and design <\/span><\/i><span style=\"font-weight: 400;\">(8th ed.). Boston: Pearson.<\/span><\/p>\n<h3><strong>Activities<\/strong><\/h3>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Read: <\/span>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Modern Systems Analysis and Design<\/span>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Chapter 8 &#8211; Structuring System Data Requirements<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Participate in this week\u2019s class and online discussions<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Complete written assignment 8.1 (WA-8.1)<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Complete practical assignment 8.1 (PA-8.1)<\/span><\/li>\n<\/ul>\n<h3><strong>Objectives<\/strong><\/h3>\n<ol>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">explain the role of conceptual data modeling in the overall analysis and design of an information system;<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">describe the information gathering process for conceptual data modeling;<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">describe how to represent an entity-relationship model and be able to define the terms:\u00a0<\/span><i><span style=\"font-weight: 400;\">entity type, attribute, identifier, multivalued attribute, and relationship;<\/span><\/i><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">distinguish among unary, binary, and ternary relationships as well as associative entities, providing an example of each;<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">define supertypes and subtypes, showing how to represent these entity types with entity-relationship diagramming notation;<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">define four basic types of business rules in a conceptual data model; and<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">explain the role of prepackaged database models (patterns) in data modeling.<\/span><\/li>\n<\/ol>\n<h3><strong>Topics<\/strong><\/h3>\n<ol>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Conceptual Data Modeling<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Gathering information for Conceptual Data Modeling<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">E-R Modeling<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Super-types and Sub-types<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Business Rules<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Database Patterns<\/span><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>Class Slides: Structured_Data_Modeling Electronic Data Interchange (EDI) Class Video &#8211; Audio Only. Unfortunately the video was not recorded. Transaction File Integrity Check Example (Excel) Electronic Data Interchange (EDI) The material covered can be found in the CISA Review Manual, Section 3.7.2 Electronic Data Interchange, pages 188 through 191. Structured Data Analysis \u201cIn\u00a0Unit 6, you learned [&hellip;]<\/p>\n","protected":false},"author":4914,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","jetpack_post_was_ever_published":false,"footnotes":""},"class_list":{"0":"post-3375","1":"page","2":"type-page","3":"status-publish","5":"entry"},"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/P9BfYF-Sr","jetpack_likes_enabled":true,"jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/community.mis.temple.edu\/mis5203sec001sec701sp2018\/wp-json\/wp\/v2\/pages\/3375","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/community.mis.temple.edu\/mis5203sec001sec701sp2018\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/community.mis.temple.edu\/mis5203sec001sec701sp2018\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/community.mis.temple.edu\/mis5203sec001sec701sp2018\/wp-json\/wp\/v2\/users\/4914"}],"replies":[{"embeddable":true,"href":"https:\/\/community.mis.temple.edu\/mis5203sec001sec701sp2018\/wp-json\/wp\/v2\/comments?post=3375"}],"version-history":[{"count":5,"href":"https:\/\/community.mis.temple.edu\/mis5203sec001sec701sp2018\/wp-json\/wp\/v2\/pages\/3375\/revisions"}],"predecessor-version":[{"id":3509,"href":"https:\/\/community.mis.temple.edu\/mis5203sec001sec701sp2018\/wp-json\/wp\/v2\/pages\/3375\/revisions\/3509"}],"wp:attachment":[{"href":"https:\/\/community.mis.temple.edu\/mis5203sec001sec701sp2018\/wp-json\/wp\/v2\/media?parent=3375"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}