System Design Essay Example for Free

System Design Essay The basis for most systems analysis and design methodologies is the system development life cycle or SDLC. It is sometimes called the waterfall method because the model visually suggests work cascading from step to step like a series of waterfalls. The first step is problem definition. The intent is to identify the problem, determine its cause, and outline a strategy for solving it. Given a clear problem definition, analysis begins. The objective of analysis is to determine exactly what must be done to solve the problem. Typically, the system’s logical elements (its boundaries, processes, and data) are defined during analysis. The objective of design is to determine how the problem will be solved. During design the analyst’s focus shifts from the logical to the physical. Processes are converted to manual procedures or computer programs. Data elements are grouped to form physical data structures, screens, reports, files, and databases. The hardware components that support the programs and the data are defined. The system is created during development. Programs are coded, debugged, documented, and tested. New hardware is selected and ordered. Procedures are written and tested. End-user documentation is prepared. Databases and files are initialized. Users are trained. Once the system is developed, it is tested to ensure that it does what it was designed to do. After the system passes its final test and any remaining problems are corrected, the system is implemented and released to the user. After the system is released, maintenance begins. The objective of maintenance is to keep the system functioning at an acceptable level. a. Prototyping Software prototyping is the creation of prototypes or a rudimentary working model of a product or information system, usually built for demonstration purposes or as part of the development process. In the systems development life cycle (SDLC) Prototyping Model, a basic version of the system is built, tested, and then reworked as necessary until an acceptable prototype is finally achieved from which the complete system or product can now be developed. A prototype typically simulates only a few aspects of the features of the eventual program, and may be completely different from the eventual implementation. The conventional purpose of a prototype is to allow users of the software to evaluate developers proposals for the design of the eventual product by actually trying them out, rather than having to interpret and evaluate the design based on descriptions. Prototyping can also be used by end users to describe and prove requirements that developers have not considered. Prototyping has several benefits: The software designer and implementer can obtain feedback from the users early in the project. The client and the contractor can compare if the software made matches the software specification, according to which the software program is built. It also allows the software engineer some insight into the accuracy of initial project estimates and whether the deadlines and milestones proposed can be successfully met. In this project the Waterfall Systems Approach Method is being used. The systems approach is a problem-solving method that breaks a complex problem into pieces, designs a solution for each piece, and then integrates the solution into a complete system (Dewitz, 1996). As applied to information systems, the systems approach decomposes a system into subsystems and with its environments. In the waterfall model time spent early on making sure that requirements and design are absolutely correct will save much time and effort later. Thus, the thinking of those who follow the waterfall process goes, one should make sure that each phase is 100% complete and absolutely correct before proceeding to the next phase of program creation. Program requirements should be set in stone before design is started otherwise work put into a design based on incorrect requirements is wasted. Also the waterfall model has a simple approach and is more disciplined. The model itself progresses linearly through discrete, easily understandable and explainable phases and thus is easy to understand; it also provides easily mark able milestones in the development process. The systems approach recognizes two major activities: analysis and design. b. System Analysis Systems analysis is the process of studying an existing system – whether manual or automated – and its’ environment. The purposes of analysis are to understand the components and functions of the current system, to identify the organization’s information and processing needs, and to determine the characteristics of a new system to meet these needs (Dewitz, 1996). In the System Analysis phase, Preliminary Investigation, Problem Analysis (studying the existing system), Requirement Analysis (identifying the information needs and what the new system should perform) and Feasibility Study (determining whether the system is feasible for the proposed system) will be performed. System design is the key phase within the system development cycle. It consist of devising specifications for an information system (IS) that best fit a company’s current and expected circumstances (Wilkinson. J. W Cerullo. M. J, 1997). The design may involve an improvement to an existing IS or may pertain to the initial IS for a company. Systems design basically is the reassembling of the components and functions of the IS to satisfy the organization’s information needs most effectively and efficiently. 1. Project Deliverables Following are the Project Deliverables for the Hardware Tracking reporting System. Deliverable Name Deliverable Description DBMS The completed project will produce a DBMS for hardware tracking reporting and replace the current paper based system User training manual A training manual that can be used for training of new staff or the re-training of existing staff in the use of the system Troubleshooting manual A troubleshooting manual that can be used to troubleshoot and possibly resolve any issues that may occur in the daily use of the system Reference manual A reference manual that can be used for quick reference a. Project Milestones Following are the major milestones for the Hardware Tracking reporting System.