System Analysis and DesignSystem analysis and design (SAD) is an exciting, active field in which analysts continually learn new techniques and approaches to develop systems more effectively and efficiently. System analysis and design consists of four major phases and they are the planning phase, the analysis phase, the design phase and the implementation phase.
The planning phase is the fundamental two-step process of understanding why an information system should be developed and creating a plan for how the project team will develop it. The deliverables from this phase is the project plan. The analysis phase answers the questions of who will use the system, what the system will do, and where and when it will be used. A system proposal is the deliverable of this phase. The design phase decides how the system will operate. The final stage is the implementation phase, during which the system is actually built or purchased in the case of packaged software design.
The system development life cycle (SDLC) is the process of understanding how information system can support business needs, designing the system, building it, and delivering it to users.
The system analyst plays a key role in information systems development projects. The system analyst assists and guides the project team so that the team develops the right system in an effective way. System analysts also identify the needs of the organization and design systems to implement those changes. Analysts must have the technical skills to understand the organizations existing technical environment, the new systems technology foundation, and the way in which both can fit into an integrated solution. Often, analysts need to communicate effectively, one-to-one with users and business managers and with programmers.
In many ways building an information system is like building a house. It starts with a basic idea, which is then transformed into a simple drawing that is shown to the customer until the customer agrees about what he or she wants. A set of blue prints is then designed that presents much detailed information about the system to be developed.
The SLDC has a similar set of four fundamental phases: planning, analysis, design, and implementation. (Dennis, Wixom, Roth, 2009, p10)The planning phase is the fundamental process of understanding why an information system should be built and determining how the project team will go about building it. It has two steps: project initiation and project management. During project initiation, the systems business value to the organization is identified – how it will lower cost or increase revenues. The feasibility analysis examines key aspects of the proposed project like:- technical feasibility ( can we build it), the economic feasibility (will it provide business value) and the organizational feasibility ( if we build it will it be used). The system request
The conceptual design phase covers all aspects of how the system will be built. The first step of the conceptual design phase is to formulate the design elements on the basis of feedback.
The final step takes place to decide on the final specifications of the system. The design of the system can be decided by having a technical meeting between two or more team members. The meeting can take place on Sunday, October 31, 2006 at the SABR Building in the same building as the project.
Once there, a team member who is planning a project in the project area will review and submit a design proposal before it is developed.
This is where the team members and the technical team come into the team and discuss the new proposed system. The final draft can be shared among the members of the technical team, who will also help discuss the design proposal for the project. (Lefeveri, Cunha, et al., 2015, p11)
As the project gets to a consensus stage, the team members and the technical team meet and work out a final draft. Â These are then sent off to the project manager for approval to start the final design. Once the final design is in place, the committee decides about the final design and sends copies to the SABR Building where the final draft for the project can be shared with the technical team who will work out the actual design decision-making process for the project. Once the final draft for the project is completed, a technical team member reviews the final draft and sends it directly to the SABR Building where it will be finalized and sent to their responsible engineer, to whom it can then be delivered to the public.
It is important to mention that the final code cannot be tested on public or server-side code. The final code analysis is done on a private server system. It is not possible to test code on public, but the following considerations should apply.
A lot of work has been done before. Even after the final code analysis has been done, the technical team cannot guarantee that the final code analysis will not cause code changes on the server side.
It is not possible to implement a design that results in a change to the system or functionality of the system without the help of a team member. In some cases they do not get to solve this problem. A team member will need help with the design of the final code analysis and will make certain that the final code analysis is not done by itself by the project engineer and is made public. However sometimes the final code analysis is implemented by a member of the team and can even be used for research. However, the complete code cannot be tested completely on either the server- or client-side code, and the team member can only verify that there have been no code changes and that the final code analysis and tests did not affect the server’s or client-side code.
In other cases (aside from design failure) the final code analysis could also be done by the team member when there is nothing on