CIS 321 DEVRY Course,CIS 321 DEVRY Tutors,CIS 321 DEVRY Assignments Flashcards
CIS 321 Week 7 Milestone 5 and Milestone 6
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-week-7-milestone-5-and-milestone-6
CIS 321 Week 7 Milestone 5 and Milestone 6
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-week-7-milestone-5-and-milestone-6
MILESTONE 5 – Process Modeling – Part III (User Interface)
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:
- Output design – Chapter 15
- Input design – Chapter 16
- 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.
- 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.
- 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.
For more Assignments visit
http://www.uopassignments.com
CIS 321 Week 6 Milestone 5 Part 2
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-week-6-milestone-5-part-2
For more Assignments visit
http://www.uopassignments.com
CIS 321 Week 6 Milestone 5 Part 2
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-week-6-milestone-5-part-2
For more Assignments visit
http://www.uopassignments.com
CIS 321 Week 5 Milsestone 4 Part 2
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-week-5-milsestone-4-part-2
CIS 321 Week 5 Milsestone 4 Part 2
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-week-5-milsestone-4-part-2
Synopsis
- Level 0 Data flow Diagram
Objectives
After completing this milestone, you should be able to:
- Create a Level 0 (System) Data Flow Diagram
- Create a Child Data Flow Diagram
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
- Develop Level 0 DFD. Make assumptions where necessary.
- Draw one Child Diagram using the Level 0 diagram.
- 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
For more Assignments visit
http://www.uopassignments.com
CIS 321 Week 4 Milestone 4 Part 1
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-week-4-milestone-4-part-1
CIS 321 Week 4 Milestone 4 Part 1
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-week-4-milestone-4-part-1
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.
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 the preliminary data analysis provided below. The results of this activity will identify the business data requirements for the proposed system.
Activities
- Complete an Entity Definition Matrix. Analyze each of the forms from the previous milestone and the preliminary data analysis provided below 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.
- 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.
- 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 .
For more Assignments visit
http://www.uopassignments.com
CIS 321 Week 3 Milestone 3
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-week-3-milestone-3
CIS 321 Week 3 Milestone 3
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-week-3-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.
• 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. The results of this activity will identify the system requirements for the proposed system.
Refer to sample forms (below), and results from Milestones 1 and 2 for the information necessary to complete the activities.
Activities
- Identify External entities and relationship with system
- Identify data flows
- Prepare Context level Data Flow Diagram
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:
Context level DFD: Due: __/__/__
Time: \_\_\_\_\_\_\_
ADVANCED OPTION
For the advanced option, compile the process description to note processes’ input and output.
For more Assignments visit
http://www.uopassignments.com
CIS 321 Week 2 Milestone 2
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-week-2-milestone-2
CIS 321 Week 2 Milestone 2
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-week-2-milestone-2
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 Employee Benefits System (EBS) 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:
- 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.
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
- Milestone 1 Solution
Assignment
Now that we have completed the preliminary investigation of the system and gained approval to proceed, we can attempt to gain a better understanding of the current system.
In this assignment we will use our results of Milestone 1, plus the Case background information, in order to perform cause-effect analysis. The results of this activity will provide us a better understanding of the problems, opportunities, and constraints of the current system.
Activities
- To complete the Problems, Opportunities, Objectives, and Constraints Matrix, using facts presented in the case introduction. Use the PIECES framework as a model to classify the problems, opportunities, and directives.
- To compile a List of business activities based on business requirements. It has to include the main tasks which have to be implemented.
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 2”.
References and Templates
- Problems, Opportunities, Objectives, and Constraints Matrix Template (link on Week 3 iLab page)
- Case Introduction
Deliverables:
Problems, Opportunities, Objectives,
and Constraints Matrix:
For more Assignments visit
http://www.uopassignments.com
CIS 321 Week 1 Milestone 1
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-week-1-milestone-1
CIS 321 Week 1 Milestone 1
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-week-1-milestone-1
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:
- The scope definition phase — Chapters 3 and 5
- Project management (optional) — Chapter 4
Assignment
The Maintenance Department receives computing support from the GB Manufacturing Information Systems Services Department (ISS). You are to assume that you work as a systems analyst with ISS.
You have been asked by Dan Stantz to analyze and design the Equipment Depot system to manage equipment check-in and check-out. In this assignment you first need to assist Dan Stantz in preparing a “Request for Systems Services.” Secondly, by analyzing the interview transcripts, you will determine the feasibility of the project, level of management commitment, and project scope by using fact-finding techniques and the necessary communication skills to compose the “Problem Statement Matrix.”
Mr. Stantz was gracious enough to allow us to record our interview session, and Exhibit 1.1 is a copy of the transcripts. Refer to the “Case Background” above and to the interview transcript in Exhibit 1.1 for the information necessary to complete the following activities.
Activities
- To complete the Request for System Services Form, use information from the case background. Make assumptions where necessary.
- To complete the Problem Statement Matrix Form, use the interview with Dan Stantz and the case background for the basis of your information. Make assumptions where necessary. Place yourself in the shoes of Mr. Stantz. Which problems do you believe have the highest visibility, and how should they be ranked? Try to determine the annual benefits. State assumptions and be prepared to justify your answers! Finally, what would be your proposed solution based on the facts you know now?
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 1”.
For more Assignments visit
http://www.uopassignments.com
CIS 321 iLab 7
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-ilab-7
CIS 321 iLab 7
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-ilab-7
Primitive Diagram for the Check-Out Equipment Event Structured English (pseudocode) for the Check Equipment Event Validate Employee elementary processes Data Structure Design (see figure 9-10) for data input and data output for the Validate Employee elementary process
For more Assignments visit
http://www.uopassignments.com
CIS 321 iLab 6
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-ilab-6
CIS 321 iLab 6
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-ilab-6
Event Decomposition Diagram for the ECS Event Diagram for Check-Out Equipment Event System Level Data Flow Diagram for the Check In/Out System
For more Assignments visit
http://www.uopassignments.com
CIS 321 iLab 5
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-ilab-5
CIS 321 iLab 5
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-ilab-5
Fully Attributed ERD for ECS Case
For more Assignments visit
http://www.uopassignments.com
CIS 321 iLab 4
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-ilab-4
CIS 321 iLab 4
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-ilab-4
Output from Visio Tutorial Fully Attributed Entity Relationship Diagram (ERD) Entity Definition Matrix
For more Assignments visit
http://www.uopassignments.com
CIS 321 iLab 3
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-ilab-3
CIS 321 iLab 3
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-ilab-3
Use-Case Glossary Use-Case Model Diagram Use-Case Narrative for the Check-Out Use Case
For more Assignments visit
http://www.uopassignments.com
CIS 321 iLab 2
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-ilab-2
CIS 321 iLab 2
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-ilab-2
Cause and Effect Analysis System Improvement Objectives
For more Assignments visit
http://www.uopassignments.com
CIS 321 iLab 1
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-ilab-1
CIS 321 iLab 1
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-ilab-1
Request for System Services Form Problem Statement Matrix Form.
For more Assignments visit
http://www.uopassignments.com
CIS 321 Entire Course (All iLabs and Milestones)
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-entire-course
CIS 321 Entire Course (All iLabs and Milestones)
To Buy This material Click below link
http://www.uopassignments.com/cis-321/cis-321-entire-course
CIS 321 iLab 1
CIS 321 iLab 2
CIS 321 iLab 3
CIS 321 iLab 4
CIS 321 iLab 5
CIS 321 iLab 6
CIS 321 iLab 7
CIS 321 Week 1 Case Study
CIS 321 Week 1 Milestone 1 Solution
CIS 321 Week 2 Milestone 2 Solution
CIS 321 Week 3 – Milestone 3 Part 1 Solution 2
CIS 321 Week 3 Milestone 3 Part 1 – Solution
CIS 321 Week 4 Milestone 4 Part 1 Solution
CIS 321 Week 5 Milsestone 4 Part 2 Solution
CIS 321 Week 5 Milsestone 5 Part 1 Solution
CIS 321 Week 6 Milestone 5 Part 2
CIS 321 Week 7 Assignment Overview
CIS 321 Week 7 Milestone 5 Part 3 Solution
CIS 321 Week 7 Milestone 6 Solution
For more Assignments visit
http://www.uopassignments.com
