ISM 301 Chapter 12: Construction Phase PDF
Document Details
Uploaded by PoignantWisdom2930
null
Tags
Summary
This document outlines the construction phase of the systems development lifecycle. It emphasizes the importance of programming, testing, and documentation within the phase. Different types of documentation are discussed, including system and user documentation, reference materials, procedures manuals, and tutorials. Various testing methods, from unit testing to acceptance testing, are also explained.
Full Transcript
CH12: CONSTRUCTIO N ISM 301 SDLC Idea Drawing Blueprint Construction Planning Analysis Development Implementation CONSTRUCTION PHASE FOCUSES ON BUILDING THE SYSTEM: TESTING AND DOCUMENTATION ARE CRUCIAL PROGRAMMING, TESTING, AND TO ENSURE QUALI...
CH12: CONSTRUCTIO N ISM 301 SDLC Idea Drawing Blueprint Construction Planning Analysis Development Implementation CONSTRUCTION PHASE FOCUSES ON BUILDING THE SYSTEM: TESTING AND DOCUMENTATION ARE CRUCIAL PROGRAMMING, TESTING, AND TO ENSURE QUALITY AND USABILITY, OFTEN DOCUMENTATION. REQUIRING MORE TIME THAN PROGRAMMING. PROGRAMMING MANAGEMENT Systems analysts play a more involved role in the oversight, testing, and coordinating of the development process. Efficient programming requires careful assignment of modules, robust coordination, and schedule management. Documentation: Two types System documentation (for developers and analysts) User documentation (for end users). Good documentation is crucial for system usability and maintenance, including reference materials, procedures manuals, and tutorials. Testing in Systems Development: Testing ensures that the system works as intended and meets user needs. It includes functional and non-functional aspects like security and performance. Types of tests: unit tests, integration tests, system tests, and acceptance tests. DEVELOPING DOCUMENTATION System Documentation: Helps developers and analysts understand and maintain the system. System documentation is largely a by‐product of the systems analysis and design process and is created as the project unfolds. Each step and phase produces documents that are essential in understanding how the system is or is to be built, and these documents are stored in the project binder(s). User Documentation: Guides users on system operations, including: Reference Documents: For specific tasks (e.g., “How to reset a password”). Procedures Manuals: For broader processes (e.g., “How to create monthly reports”). Tutorials: For learning system fundamentals. Structuring documentation Example: reference documents TESTING IN SYSTEMS DEVELOPMENT Purpose of Testing: To uncover discrepancies between what the system does and what it should do. Focus on identifying errors early to save costs and improve quality. Key Testing Types: Unit Testing: Tests individual components, like classes or methods. Integration Testing: Ensures that modules work together, focusing on data flow and interactions. System Testing: Examines the entire system’s ability to meet functional and non-functional requirements. Acceptance Testing: Conducted by end users to verify the system meets their needs, including: Alpha Testing: Using test data. Beta Testing: Using real-world data under close observation. END OF CHAPTER THANK YOU
