Cis 555 Week 4 Assignment 2 Automated Teller Machine (Atm) Cis555 Week 4 Assignment 2 Automated Teller Machine (Atm)

In this work related project analysis various information will be for gathering information. Some of the areas that will be covered are; methods of searching, interviewing techniques to gather the information, agreement for articulating requirements, and strategies to gather information for computerization. Requirements must

* Analyze the key ways that entity relationship modeling helps database developers overcome potential design challenges and

There are several techniques used in the documentation process. As a system analyst I would propose to the members of this group a straightforward standardized approach. A reasonable suggestion for this project would be to use the Procedure Manual technique for documenting this system. The Procedure Manuals will provide instructions on how to operate and understand how the system works. These manuals are also used as a guide that can be updated at different intervals for future users. Procedure Manuals are also made available to users via the Web. This new approach has made it convenient for users to seek support in a much faster way by offering a FAQ page, and online chat (Kendall & Kendall, 2011). In

1. What is the problem being addressed? Where, when and to what extent does the problem(s) occur? What is the scope of the project? Has another improvement team tried to solve this or a similar problem? What did they learn?

8. Eliminate vendors not worthy of further consideration, communicate and agree with the project sponsor and communicate this to the respective vendors. If vendors are eliminated from the process, due to uncertainty in their offering, be sure to clarify these with the vendor first before proceeding and document the outcomes.

4. Provide a workflow diagram in Visio or equivalent software to illustrate how the system will work.

For the company DesignIT, I would use a LAN type of network (for local-area network). This networks several computers, a mail (exchange) server, a database server and a file share server in one building and interconnects with each switch or backbone. I chose this for this small space because it is less than 100 square feet and is all within a single dwelling. This way the employees can all share their resources with one another, an intranet, database and printers.

Describe the Problem: Describe the situation surrounding your problem/project in detail and include the stakeholders, their expectations, and the impact of the project on them.

Consider the overall purpose of the system and at least two system options or alternative versions of the system capable of satisfying organisational requirements.

a. Describe what your team designed. A diagram model is used to explain the design’s structure and function. Includes an overall image and more detailed, “zoomed in” images/diagrams of special features.

* Write clearly and concisely about issues in IT project management using proper writing mechanics and technical style conventions.

According to Glass, resources are acceptable if 15-30 of the project effort was spent on the requirements definition. In regards to correctly obtaining valid sources of knowledge without saturating requirements, it was found that involving customers, consulting all resources and involving highly skilled people was the most successful approach. Furthermore, processes that involved the concentration of prioritization, traceability and validation of requirements was also recommended.

3. How should risk quantification problems be resolved if there exist differences of opinion between the customer and the contractors?

Justification: This information provides the reader with strategic context for the follow on reading. It explains the differences between the design documents and explains how each provides a unique picture of the solution.

The interview session has been done by include an open-ended and closed-ended question which are related to the implemented project. Next, sampling technique is executed by system analyst who does evaluation to the current system or prototype. These processes give feedback in evaluation form that filled after tested the system. Lastly, observation is performed by using questionnaire form. According to Burch (1992), the questionnaire is analyzed and transform into structured form that easy to understand. After all information has been collected, structuring of system requirement takes place. It focused on development process modeling which perform “graphically representing the process, or actions, that capture, manipulate, store, and distribute data between a system and environment” (Hoffer, George, & Valacich, 2012, p. 182). In this step, Data flow diagram (DFD) is structured by system analyst using special tools and techniques to create a decision table. According to Hoffer, George and Valacich (2012), decision table is a “diagram of process logic where the logic is reasonably complicated” (p. 200). This table is useful to help system analyst to make a decision toward the project. Then all information’s gained from this phase are documented in System Analysis Report (SAR) that acts as a guideline or reference to the future system development project (Burch, 1992).