Devry CIS 321 All Assignments Latest

1. Devry CIS 321 All Assignments Latest Just Click on Below Link To Download This Course: https://www.devrycoursehelp.com/product/devry-cis-321-all-assignments-latest/ Or Email us help@devrycoursehelp.com Devry CIS 321 All Assignments Latest Devry CIS 321 Week 1 Assignment Latest MILESTONE 1 – SCOPE DEFINITION _______________________________________________________________________________ _______________________ Case Background In this milestone, you will prepare a Request for System Services Form, which is the trigger for the Preliminary Investigation Phase. Also, you will use fact-finding techniques to extract and analyze information from an interview to determine project scope, level of management commitment, and project feasibility for the Equipment Check-Out System (ECS). With these facts and facts obtained from the Case Background, you will have the necessary information to complete the Problem Statement Matrix. Refer to the ECS Case Introduction in the Case Project page. Objectives After completing this milestone, you should be able to: Complete a Request for System Services form, which triggers the preliminary • investigation phase. Analyze a user interview and extract pertinent facts, which can be used to assess project • feasibility. Complete a “Problem Statement Matrix documenting the problems, opportunities, or • directives of the project. Prerequisites Before starting this milestone, the following topics should be covered:

2. The scope definition phase — Chapters 3 and 5 • Project management (optional) — Chapter 4 • Assignment Devry CIS 321 Week 2 Assignment Latest MILESTONE 2– PROBLEM ANALYSIS _______________________________________________________________________________ _______________________ Synopsis There’s an old saying that suggests, “Don’t try to fix it unless you understand it.” With those words of wisdom, the next milestone of our project is to study and analyze the existing system. There is always an existing business system, regardless of whether it currently uses a computer. The problem analysis phase provides the project team with a more thorough understanding of the problems, opportunities, and/or directives that triggered the project. Indeed, the analyst frequently uncovers new problems and opportunities. The problem analysis phase may answer the questions, “Are the problems worth solving?” and “Is a new system worth building?” The purpose of the problem analysis phase is threefold. First and foremost, the project team must gain an appropriate understanding of the business problem domain. Second, we need to answer the question, “Are these problems (opportunities and directives) worth solving”? Finally, we need to determine if the system is worth developing. The problem analysis phase provides the systems analyst and project team with a more thorough understanding of the problems, opportunities, and/or directives that triggered the project. In the process, they frequently uncover new problems and opportunities. In this milestone you will perform Cause-Effect Analysis on the Equipment Check-Out System (ECS) and document your findings using the Problems, Opportunities, Objectives, and Constraints Matrix. The PIECES framework, originally developed by James Wetherbe and then adapted by the authors, can serve as a useful tool to classify the various problems, opportunities, and directives identified in Milestone 1. Objectives After completing this milestone, you should be able to:

3. Perform a Cause-Effect Analysis to be able to thoroughly understand a system’s • problems, opportunities, and/or directives that triggered the project. Use and understand the PIECES framework for classifying problems, opportunities, and • directives. Complete the Problems, Opportunities, Objectives, and Constraints Matrix. • Complete the List of Business Activities based on Requirement analysis. • Devry CIS 321 Week 3 Assignment Latest MILESTONE 3 – PROCESS MODELING- Part I _______________________________________________________________________________ _______________________ Synopsis The requirements analysis phase answers the question, “What does the user need and want from a new system?” The requirements analysis phase is critical to the success of any new information system! In this milestone we need to identify what information systems requirements need to be defined from the system users’ perspectives. The Data flow diagram (DFD) has gained popularity as a technique for expressing system requirements for two reasons: It facilitates development, which often leads to building systems that better • satisfy user needs Data flow diagrams and narratives are easy for users to understand. • In this milestone you will first uncover external agents, processes and data flows that define the requirements for the proposed system and document that information. You will use that to build the Context Data Flow Diagrams. Objectives After completing this milestone, you should be able to: Understand and perform the techniques for requirements discovery. • Determine external agents (external entities) and their relationship with the • System, identify data flows.

4. Construct the Context DFD using VISIO. • Prerequisites Before starting this milestone, the following topics should be covered: The problem analysis phase — Chapters 3 and 5 • PIECES framework — Chapters 3 and 5 • Problem analysis techniques — Chapter 6 • Process modeling techniques — Chapter 9 • Assignment Now that we have studied the current system and analyzed some of its problems and opportunities, plus gained approval to proceed, we can now start to identify the business requirements for the system and model them. In this assignment we will use our results of the previous Milestone and transcripts of an interview with the Equipment Depot staff. The results of this activity will identify the system requirements for the proposed system. Exhibit 3.1 is a copy of the transcript of the interview. Refer to the transcript, sample forms, and results from Milestones 1 and 2 for the information necessary to complete the activities. Activities 1. Identify External entities and relationship with system 2. Identify data flows 3. Prepare Context level Data FlowDiagram Deliverable format and software to be used are according to your instructor’s specifications. Deliverables should be neatly packaged in a binder, separated with a tab divider labeled “Milestone 3”. References Transcripts of Interview – Exhibit 3.1 (see below) • Deliverables: Devry CIS 321 Week 4 Assignment Latest Milestone 4 – Data Modeling-Part I-Logical ERD

5. MILESTONE 4 – DATA MADELING – Part I (Logical ERD) ________________________________________________________________________ The requirements analysis phase answers the question, “What does the user need and want from a new system?” The requirements analysis phase is critical to the success of any new information system! In this milestone we need to identify what information systems requirements need to be defined from the system users’ perspectives and draw graphical, logical models to document the data requirements for a new and improved system. Data modeling is a technique for organizing and documenting a system’s data. Data modeling is sometimes called database modeling because a data model is usually implemented as a database. Data is viewed as a resource to be shared by as many processes as possible. As a result, data must be organized in a way that is flexible and adaptable to unanticipated business requirements – and that is the purpose of data modeling. In this milestone, you will first discover those entities in the system that are or might be described by data. Then you will define each entity you identify in respect to the business in an Entity Definition Matrix. Then you will do the data model tutorial in doc sharing that will prepare you for doing the logical entity relational diagram (ERD). Objectives After completing this milestone, you should be able to: • Understand and perform the techniques for entity discovery. • Define each entity with respect to the business and complete an entity definition matrix. • Perform the necessary data modeling techniques to organize and document the data requirements for the proposed system. • Construct the Context data model (Logical ERD). Prerequisites Before starting this milestone, the following topics should be covered: • Data modeling — Chapters 8 and 14.

6. • Milestone 1-3 Solutions (provided by your instructor) Assignment Now that we have studied the current system and analyzed some of its problems and opportunities, plus gained approval to proceed, we can now start to identify the business data requirements and graphically model them. In this assignment, we will use our results of the previous milestones, samples of forms we have collected, and a copy of a transcript of an interview with Dan Stantz’s staff. The results of this activity will identify the business data requirements for the proposed system. Activities 1. Complete an Entity Definition Matrix. Analyze each of the forms referenced by the user interview and make assumptions where necessary. (Note: While it is appropriate to make assumptions, you should document those assumptions and include them in your submission to your instructor.) If you create the matrix in Excel, paste it into a Word document prior to submission. 2. Complete the Visio tutorial which walks you through how to create an Entity Relationship Diagram (ERD), located in Doc Sharing. When you have completed the tutorial, paste the diagram you have created to the end of the Word document that already holds your Entity Definition Matrix. 3. Prepare a Context Data Model. Deliverable format and software to be used are according to your instructor’s specifications. Deliverables should be neatly packaged in a binder, separated with a tab divider labeled “Milestone 4-Part I”. References • Milestone 1-3 Solutions – provided by your instructor • Case Study Introduction • Transcripts of Interviews with Equipment Depot staff o Exhibit 4.1 • Exhibit 4.2-4.4 (see below)

7. Deliverables: Entity Definition Matrix: Due: __/__/__ Time:_______ Context Data Model: Due: __/__/__ Time:_______ ADVANCED OPTION For the advanced option, assume that the proposed system must also handle the tracking accounts receivable and payments on customer statements. Your instructor will specify additional system requirements for this part of the system. Modify your initial Entity Definition Matrix to be able to handle this system requirement. Entity Definition Matrix: Due: __/__/__ Time:_______ Milestone’s Point Value: _______ Exhibit 4.1 The following is a copy of the transcript of an interview between you and Oscar Barrett. The goal of this interview was to obtain sample forms used for processing check-ins and check-outs and to be able to ask questions about them in order to discover data entities of the business system. Scene: You have arranged to drop by the Equipment Depot to pick up samples of forms used to process check-ins and check-outs.Oscar Barrett was willing to collect them and answer any questions that you might have. Oscar: Hi. I assume you are here to pick up the forms. You: Yes. Is this a good time? irtually impossible to track. A particular wrench does not have a serial number on it! But since it is relatively inexpensive and virtually impossible to track, we don’t even attempt to do so. We simply want to keep track of the fact that the employee checked out a wrench. We don’t care which wrench. We only care that we get the wrench back. You: OK. Two kinds of equipment and slightly different information kept for each. But everything has an Equip ID. Oscar: Right. For tracked equipment we only have one piece with that Equip ID. With untracked we could have several.

8. You: Do you need the system to track the quantity you have of each kind of equipment? Oscar: Good question. We haven’t until now. If someone calls us up see if we have something in stock we just put him or her on hold and go look. But it would be nice if the computer had a total and could subtract the outstanding loans. Sometimes I’ve suspected people of sneaking in here and raiding our inventory. And maybe your system could even allow people in another plant to check our inventory online before they trudge over here. You: We’re still working out the system requirements. I’ll write that down. Let’s finish the check-out form. I assume “qty in” and “qty out” for large equipment is always one? Oscar: That’s correct . . . in fact sometimes we don’t even enter a quantity, since it can’t possibly be more than one. You: Is “damage” recorded for check-ins or for check-outs or for both? Oscar: Just for check-ins. If something is damaged enough to not work properly we fix it before it goes out again. Minor damage we just ignore. We don’t care what it looks like as long as it works. You: OK. Now this employee registration…(see Exhibit 4.4) looks pretty understandable. I see you track supervisor. Oscar: Right. If someone isn’t returning something we go to the supervisor. Devry CIS 321 Week 5 Assignment Latest MILESTONE 4 – DATA MADELING – Part II (Physical ERD) ________________________________________________________________________

9. Data Modeling and Analysis (continued) This week you are building on the previous week’s activity. Please make sure to review the Milestone 4, Part I Solution (located in Doc Sharing) before continuing with the Milestone 4, Part II activity. The synopsis below is the same as the synopsis for Week 4. It is shown below for your convenience. The requirements analysis phase answers the question, “What does the user need and want from a new system?” The requirements analysis phase is critical to the success of any new information system! In this milestone we need to identify what information systems requirements need to be defined from the system users’ perspectives and draw graphical, logical models to document the data requirements for a new and improved system. Data modeling is a technique for organizing and documenting a system’s data. Data modeling is sometimes called database modeling because a data model is usually implemented as a database. Data is viewed as a resource to be shared by as many processes as possible. As a result, data must be organized in a way that is flexible and adaptable to unanticipated business requirements – and that is the purpose of data modeling. In this milestone, you will first discover those entities in the system that are or might be described by data. Then you will define each entity you identify in respect to the business in an Entity Definition Matrix. Then you will do the data model tutorial in doc sharing that will prepare you for doing the Fully-Attributed data model (Physical ERD) for ECS. Objectives After completing this milestone, you should be able to: Understand and perform the techniques for entity discovery. • Define each entity with respect to the business and complete an entity definition • matrix. Perform the necessary data modeling techniques to organize and document the • data requirements for the proposed system. Construct the Fully Attributed data model. • Prerequisites

10. Before starting this milestone, the following topics should be covered: Data modeling – Chapters 8 and 14. • Milestone 1-3 Solution – provided by your instructor • Milestone 4, Part I Solution – provided by your instructor • Assignment Now that we have studied the current system and analyzed some of its problems and opportunities, plus gained approval to proceed, we can now start to identify the business data requirements and graphically model them. In this assignment, we will use our results of the previous milestones, samples of forms we have collected, and a copy of a transcript of an interview with Dan Stantz’s staff. The results of this activity will identify the business data requirements for the proposed system. Activities 1. Create a Physical ERD (Fully-Attributed data model) for the ECS case. Deliverable format and software to be used are according to your instructor’s specifications. Deliverables should be neatly packaged in a binder, separated with a tab divider labeled “Milestone 4-Part II”. References Transcripts of Interviews with Equipment Depot staff o Exhibit 4.1 (see Milestone 4, Part I • Description) Exhibit 4.5 (see below) • Deliverables: Fully-Attributed ERD: Due: __/__/__ Devry CIS 321 Week 6 Assignment Latest Milestone 5 – Process Modeling – Part II – Exploded DFD MILESTONE 5 – PROCESS MODELING – Part II (Exploded DFD)

11. _______________________________________________________ Part 1 Synopsis 1.Level 0 Data flow Diagram T he requirements analysis phase answers the question, ‘What does the user need and want from a new system?’ The requirements analysis phase is critical to the success of any new information system! In this milestone we need to identify what information systems requirements need to be defined from the system users’ perspectives. The Data Flow Diagram (DFD) is a graphical representation of system which shows systems structure and components. The DFD shows how the data transforms in the system, what the source of the input is and what is the destination. Also, the DFD presents data structure and how it’s stored. In this milestone you will explode the Context level DFD to Level 0 DFD to show sub-systems (processes). The Level 0 DFD shows internal data stores and how data flows through the processes. 2. 2.Child diagram definition C hild level diagrams show details and are built till needed level of details is reached. First, we show the information system as a single process on the Context diagram. Then, we decompose and show more details until all processes are functional primitives. Not all processes are exploded to the same number of levels- it’s not required to explode all processes to the same level. The main target is to reach the functional primitive which will be translated into units of program code. Objectives After completing this milestone, you should be able to: 1. Create a Level 0 (System) Data Flow Diagram 2. Create a Child Data Flow Diagram

12. Prerequisites Before starting this milestone, the following topics should be covered: Process Modeling – Chapter 9 • Assignment As a systems analyst or knowledgeable end-user, you must learn how to draw data flow diagrams to model business process requirements. The preliminary investigation and problem analysis phases of the methodology have been completed and you understand the current system’s strengths, weaknesses, limitations, problems, opportunities, and constraints. You have already built the Context models (Milestone 3) to document business requirements for the new system. You now need to build the Level 0 (System) DFD and corresponding process models. Activities 1. Develop Level 0 DFD.Make assumptions where necessary. 2. Draw one Child Diagram using the Level 0 diagram. 3. Continue decomposition of one process up to primitive processes (Level 2, Level 3, etc.) Deliverable format and software to be used are according to your instructor’s specifications. Deliverables should be neatly packaged in a binder, separated with a tab divider labeled “Milestone 5-Part II”. References Context Data Flow Diagram Narrative – Exhibit 5.1 • Deliverables: Level 0 Data flow Diagram Due:__/__/__ Time:______ Child level diagrams: Due: __/__/__ Time:_______ ADVANCED OPTIONS Time:_________

13. PART 2 SYNOPSIS EACH PROCESS FROM PRIMITIVE DFD MAY BE DEVELOPED AS THE INDIVIDUAL MODULE. The software design technique which is based on the composing software from separate, interchangeable components is known as the module. Modular design is a way to organize the complex system as a set of distinct components. Components may be developed, tested independently and then plugged together. Modular design is supported by three types of logic: – Sequential; – Decision making or control; – Iteration or repetition. Sequential– execution of steps one after another. Decision making– execution of step depends on results of condition or set of conditions. Decision making is also called the selection or control. Iteration– execution of steps is repeated until the specific condition changes. Iteration is also called as repetition or looping. In this milestone you will write the Structured English for primitive process. OBJECTIVES After completing this milestone, you should be able to: 1. Write the Structured English for primitive process. PREREQUISITES Devry CIS 321 Week 7 Assignment Latest iLab Milestone 5 – Process Modeling – Part III – User Interface MILESTONE 5 – PROCESS MODELING – Part III (User Interface)

14. SYNOPSIS Management and users make important decisions based on system outputs. Outputs present information to system users. Outputs, the most visible component of a working information system, are the justification for the system. These outputs are produced from data that is either retrieved from databases or, more often, input by users. Good input and output design can make the difference in whether or not an information system is used effectively. User interface design provides a roadmap or dialog that integrates the inputs and outputs. In this milestone you will design outputs, inputs, and user interface for the Customer Response System. OBJECTIVES After completing this milestone, you should be able to: • Design a GUI output screen and printed computer outputs. • Design a GUI input screens that use the proper screen-based controls. • Design a GUI screen that integrates the above outputs and inputs. PREREQUISITES Before starting this milestone the following topics should be covered: 1. Output design – Chapter 15 2. Input design – Chapter 16 3. User interface design – Chapter 17 ASSIGNMENT The goal of this project is to design outputs, inputs, and a user interface to track employee data. ACTIVITIES 1. Design at least one of the following outputs for the Equipment Check-Out System: transaction (external/turnaround), detail report (internal), summary report (internal), and exception report (internal). Your instructor will indicate what specific outputs you are to design. 2. Design at least one of the following inputs for the Equipment Check-Out System: source document, client/server screens (e.g., Windows), and web screens. Your instructor will indicate what specific inputs you are to design.

15. 3. Design a user interface that integrates the above outputs and inputs. [Note: this requirement is for the main system screen and all subsequent screens that may be used to arrive at the screens designed for Activity 1 and 2.] The above designs should represent prototypes (thus, include sample data in your designs). To develop the prototypes, use any available tool: Visio, CASE tool, personal DBMS (e.g., Access), or RAD tool (e.g., Visual Basic, MS Visual Studio). Your instructor may indicate what specific design tool you should use. Your instructor will specify deliverable format and software to be used. Deliverables should be neatly packaged in a binder, separated with a tab divider labeled “Milestone 5-Part III” and accompanied with a Milestone Evaluation Sheet. References: Previous narratives and supplied forms Optional Guidelines or additional technical requirements such as data dictionary. Templates See on-line learning center website for the textbook. Deliverables: Input Design Form: Due: __/__/__ Time:_______ Output Design Form: Due: __/__/__ Time:_______ User Interface Form: Due: __/__/__ Time:_______ Milestone’s Point Value: _________ Download File Now