Cs251 Fundamantals of Database Systems Ip 1 - 5

The system development life cycle is a formal four-step process that can be followed in order to identify a problem and solve it. The first step is

As part of our MIS 4163 class, we are going to work in a project that will prepare a system design for the application we select. Our team, the Purple Pirates, is a team composed of 5 people. We have selected to put together the design for a service order and invoicing application for an auto repair business. We have named our project ARS which stands for Auto Repair System.

Testing of the entire system will be performed to verify that all parts and counterparts are functional. This is the testing that is made prior to release. Tests performed in this stage verify for the following:

In this process a particular system is selected and information is gathered about the processes involved in the system, the communication and co-ordination with other departments through interviews, questionnaires and documents. Data management, Medication management and infection control are three areas which are evaluated by this method.

Another factor to ensure success is to train the IT personnel on the system’s applications and processes. How well the IT personnel understand the systems is extremely relevant to the success of system implementation. The involvement of IT personnel, who have knowledge regarding the application requirements, increases the ability of the team to correctly and quickly specify the requirements. Experienced IT personnel on a team help ensure others understand terminology and have more of an understanding of the stakeholders needs (Havelka and Lee, April 25, 2002).

Another way of successfully gathering information is by building a prototype or model of the system, so that users can test or get an idea of what the finished product will be like. With this they can determine issues, problems, or inconsistency with the system. Another important part of gathering information is organizing it so that it can be understood and put to proper use. I propose categorizing the requirements into functional requirements, operational requirements, technical requirements, and transitional requirements. The functional requirements define how the user thinks the system is functioning overall, the operational requirements define what background processes need to be executed in order for the system to work optimally over a period of time, the technical requirements define what technical issues that must be addressed in order to successfully implement the system, and the transitional requirements define the processes or steps needed to implement the system smoothly and successfully. ("Mind Tools", 2012).

A: In the software lifecycle there are 4 phases that are derived from the old System Development Life Cycle (SDLC) and they are as follow; Planning, Implementation, Maintenance, and the Removal process. The planning phase is defined by all planning activities including the analysis of the software to be installed, verification of its compatibility, supported methods of installations, and the identification of any risks associated with the software and the desired deployment method. The Implementation phase is used to prepare for deployment such as; creating a shared access location for files and creating or using the appropriate package files. After all these steps have been

This way the IT department can understand what the higher level and lower level employees need for system stability and a better graphical interface. Another plan of action would include the method of Systems Development Life Cycle or SDLC. The phases of this method are planning, analysis, system design, implementation and operation. First we must plan on what exactly we are trying to accomplish. We know we need to upgrade the Riordan Manufacturing system. Next we must analyze the system and look for problematic errors. A project proposal can be essential to launching a system analysis (Farah, 2013). These are things to keep in mind: understand the business situation or problem, understand the significance to the problem in the organization, think of alternate solutions, the use of computer information systems for solutions, find people interested in the solving the problem (Farah, 2013). This plan is used to decrease redundancies, errors, and increase security. Finding all the weak spots in the company will help in the improvement of integrating an updated efficiently functioning system. Feasibility is important to account for when upgrading the system. Integrating a CRM will help to work with customers and understand their needs and wants to benefit the company and the relationship with their customers. Designing the system will involve knowing what kind of software is needed to store and

Which is requirements needed, after all the information the team will analyze to determine software requirements and generate a report. Then we move to the selection and design, this will occur when the team creates several designs and share with everyone on the project. We will identify any weakness, if we have any successful prototypes it should show how the software will operate. Implementation phase should proceed without any issues if there is any it must be correct during this time. A planned out schedule should allow for any unexpected incidents. When the implementation stage is complete we move to operation when our software has been designed and does what it was designed to do. We will do a review and evaluation which consist of performance, cost and

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

The information system’s requirements in the systems planning phase are based on a case summary, potential interview questions, and the systems analyst’s experience in systems planning. One must not only generate requirements based specifically on what users’ state they want or need. Analysts must also generate requirements based on insight into the overall organization and project goals.

normally initiate software testing as they write codes. This most naturally, is dependent on the

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

After the proposed system is analyzed and designed, the actual implementation of the system occurs. After implementation, working system is available and it requires timely maintenance.

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).