Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
In this chapter we will continue our discussion on overview and basics of software quality engineering. Precisely, we will talk about the quality assurance. In this lecture we learned about: Identify the four phases, how it came about, methodology alternatives. | Business System Development CSC581 Lecture 2 Systems Development Life Cycle (SDLC) 2 Summary of the previous lecture We introduced the course and its content in our previous lecture. We talked about an Information System (IS) and more specifically we talked about the Systems Analysis & Design. We have also seen different types of IS and briefly talked about the SDLC Outlines Systems development life cycle Identify the four phases How it came about Methodology alternatives Alternatives to Traditional Waterfall SDLC Objectives To understand the need of a formal process To understand and distinguish between Alternatives to Traditional Waterfall SDLC Why do we need a formal process Why do we need a formal process? Failures occur (too) often Creating systems is not intuitive Projects are late, over budget or delivered with fewer features than planned The System Analyst is the key person Designs a system to add value Must understand the business processes Job is rewarding, yet challenging | Business System Development CSC581 Lecture 2 Systems Development Life Cycle (SDLC) 2 Summary of the previous lecture We introduced the course and its content in our previous lecture. We talked about an Information System (IS) and more specifically we talked about the Systems Analysis & Design. We have also seen different types of IS and briefly talked about the SDLC Outlines Systems development life cycle Identify the four phases How it came about Methodology alternatives Alternatives to Traditional Waterfall SDLC Objectives To understand the need of a formal process To understand and distinguish between Alternatives to Traditional Waterfall SDLC Why do we need a formal process Why do we need a formal process? Failures occur (too) often Creating systems is not intuitive Projects are late, over budget or delivered with fewer features than planned The System Analyst is the key person Designs a system to add value Must understand the business processes Job is rewarding, yet challenging Requires specific skill sets Systems Development Life Cycle (SDLC) 7 Systems Development Life Cycle (SDLC) Traditional methodology for developing, maintaining, and replacing information systems Phases in SDLC: Planning Analysis Design Implementation Maintenance 8 Standard and Evolutionary Views of SDLC SDLC Planning Phase Identify, analyze, prioritize, and arrange IS needs SDLC Analysis Phase Study and structure system requirements SDLC Design Phase Convert recommended solution to system specifications Logical design: functional features described independently of computer platform Physical design: logical specifications transformed to technology-specific details SDLC Implementation Phase Code, test, install, and support the information system SDLC Maintenance Phase Systematically repair and improve the information system The Heart of the Systems Development Process Current practice combines analysis, design, and implementation into a single iterative and parallel process of .
