System Modeling & Requirement Analysis Essay Example for Free

System Modeling Requirement Analysis Essay a)Discuss the strengths and the limitation of the traditional systems development life cycle (SDLC). Systems development life cycle or software development life cycle is a conceptual model. The systems development life cycle describes the stages in an information system development project (Marios Alexandrou 2011, para.1) which from begin till the end and maintenance of system. The objectives of traditional systems development life cycle are to ensure end-state solutions meet user requirement in support of business strategies goals (FrankKlucznik 2006, para.1) and provides detailed guides of all aspect of system development or scope to managers. Commonly, the traditional systems development life cycle has 5 phases. First phase is planning which identify and analysis what to do. Second is analysis, analyse the requirement of system. Third is design the usability, detail and architectural of system. Next is implementation or programming through software testing and testing code. The last is support to maintain the system. Strengths The traditional systems development life cycle is familiar and easy model to develop a system. This is because the most of designers and programmers familiar with traditional systems development life cycle. Besides that, many people understand and easy to learn the approach of traditional systems development life cycle which the steps are clearly outlined (Tayntor Christine B 2007). The traditional systems development life cycle is a systematic approach, so the software or system is created or a well planned pattern (Greekinterview 2008). Using traditional systems development life cycle approach in development of system will organise and manage the task for the system clearly and organised. The traditional systems development life cycle that emphasises on project control creates formal documentation. The formal documentation ensures the system requirement can be traced back to state business. The formal documentation also records the phases of traditional systems development life cycle, then the managers can used to maximise management control and used as references for next creation of system. During the traditional systems development life cycle, it creates many intermediate products during the phases of systems development. These intermediate products will be reviewed by both managers and users. The intermediate products tested by users or customers to check whether the system meets their requirements. The traditional systems development life cycle was useful for building large and complex system. The large and complex system requires a lot of plan and traditional systems development life cycle approach can solve these problems. The traditional systems development life cycle approach was highly structure and well-defined. Therefore, the system can be planned properly by using traditional systems development life cycle approach. Limitation However, the traditional systems development life cycle is a time consuming approach. Since the traditional systems development life cycle at least has 5 phases to create a system. Each phase requires a few days till some months to complete it. So it takes a few months or years to create system when run these phases for creation of system. In addition, it takes time to create documentation which need record the process of each phase. The traditional systems development life cycle is a costly or expensive approach for system development. Each phase of the approach requires a lot of money. The costs that used in each phase are the error of the process, cost for process and cost for experts that run the phase of the approach. Documentation in traditional systems development life cycle is costly to create because it needs to create in each phase and maintain the documentation. The traditional systems development life cycle may create generation of unnecessary document (Tayntor Christine B 2007). It will happen when people followed the process of each phase slavishly. These mostly happen to the inexperienced managers and staff that believe that all the processes are required to be documentation. The traditional systems development life cycle is an inflexible approach to develop a system where it hard and lack of responds to change of system development. Cutter (2000) states the traditional system development life cycle is full-short in the new e-business environment. They (traditional systems development life cycle) are unable to keep up with fast-paced ever-changing e-business project. Therefore these approach cannot use for easy creep scope of system development. The other limitation in traditional systems life cycle is the customer or user is involved only periodically (Tayntor Christine B 2007) in phase of the system development. The traditional systems development life cycle was mainly participant in the developing system while the users or customers only test the product at the end and less chances to give feedback for the system development. This may lead misunderstanding between designers, programmers, managers and customers about the requirements and functions of the system to be made.