Đang chuẩn bị liên kết để tải về tài liệu:
Lecture Systems analysis and design with UML (3/e) - Chapter 13: Construction

This chapter discusses the activities needed to successfully build an information system: programming, testing and documenting the system. Programming is time consuming and costly, but except in unusual circumstances, it is the simplest for the systems analyst because it is well understood. For this reason, the system analyst focuses on testing (proving that the system works as designed) and developing documentation. | Chapter 13: Construction Objectives Be familiar with the system construction process. Understand different types of tests and when to use them. Understand how to develop documentation. Introduction Construction is the development of all parts of the system, documentation, and new operating procedures Programming is the largest, but least risky part of systems development A program is not considered finished until the test for that program is passed. MANAGING PROGRAMMING Assigning Programmers First, group together related classes, then assign each group to a programmer Time required is proportional to number of programmers The more programmers, the more coordination, which means less time is spent actually coding Best to use a small team of programmers Divide complex projects into autonomous parts Coordinating Activities Weekly project meetings Create and enforce standards Divide resources into three areas: Development Testing Production Implement change control measures Managing the | Chapter 13: Construction Objectives Be familiar with the system construction process. Understand different types of tests and when to use them. Understand how to develop documentation. Introduction Construction is the development of all parts of the system, documentation, and new operating procedures Programming is the largest, but least risky part of systems development A program is not considered finished until the test for that program is passed. MANAGING PROGRAMMING Assigning Programmers First, group together related classes, then assign each group to a programmer Time required is proportional to number of programmers The more programmers, the more coordination, which means less time is spent actually coding Best to use a small team of programmers Divide complex projects into autonomous parts Coordinating Activities Weekly project meetings Create and enforce standards Divide resources into three areas: Development Testing Production Implement change control measures Managing the Schedule Time estimates must be revised as construction proceeds Build a 10% error margin into all schedules Scope creep occurs when new requirements are added to the project after the system design was finalized Risk assessments can help predict problems before they derail the project DESIGNING TESTS Testing The purpose of testing is to uncover as many errors as feasible It is impossible to prove the system error-free It is too expensive to look for all possible bugs Four stages of testing Unit tests Integration tests System tests Acceptance tests Testing and Object Orientation Encapsulation and Information-Hiding Polymorphism and Dynamic-Binding Inheritance Reuse Object-Oriented Development Process and Products Test Planning Testing takes place throughout the development of an object-oriented system Test plans define a series of tests to be conducted Each test has a specific objective and describes specific test cases to examine Stubs are hard-coded placeholders that allow testing .