Chapter 6: Implementation Phase - System Analysis and Design Fundamentals (CSC 1403) PDF

Chapter 6: Implementation Phase System Analysis and Design Fundamentals (CSC 1403)  After completing the topic, students should be able to: Learning 1. Explain deliverables of implementation phase objectives 2. List the type of testing 3. List type of installation...

Chapter 6: Implementation Phase System Analysis and Design Fundamentals (CSC 1403)  After completing the topic, students should be able to: Learning 1. Explain deliverables of implementation phase objectives 2. List the type of testing 3. List type of installation 2   The implementation phase is the stage where the developed system is deployed within the organization. 6.0  It involves activities such as coding, software testing, system installation, documentation, user training, and post- Implementation implementation support. Phase Overview  The main goal is to ensure the system functions smoothly and meets user requirements. 3 6.0 Implementation Phase Overview developed system is deployed FIGURE 6-1 Systems development life cycle with implementation phase highlighted 4  6. 1 STEP IN IMPLEMENTATION PHASE 6.1.1 Coding / Code 6.1 6.2.1 Program Documentation Step In Implementation Phase 5  6.1.1 Coding / Code 6.1.1 Definition: Coding is the process of writing instructions in a programming language to create software or applications. Coding/Code Purpose: To transform the system design into a functional system by creating the code that will execute the planned tasks. 6  6.1.1 Coding / Code Key Activities: a) Writing code based on the system design documents. b) Debugging and testing the code to ensure it works as expected. c) Using best practices like code commenting, modularization, and 6.1.1 error handling for maintainable and efficient code. Coding/Code Tips: a) Always follow coding standards to make your code readable and reusable. b) Use version control systems (e.g., Git) to track changes and collaborate with others. c) Regularly test your code to identify and fix bugs early. 7  6.2.1 Program Documentation Definition: Program documentation involves creating detailed information about the program's design, code, and usage. 6.2.1 Program Purpose: Documentation i. To help future developers, users, and maintainers understand and work with the software. ii. To serve as a reference for debugging, updating, or enhancing the program. 8  6.2.1 Program Documentation Key Activities: a) Writing user manuals to guide end-users on how to operate the program. b) Creating technical documentation such as flowcharts, algorithms, and database schemas. 6.2.1 Program c) Including in-code comments to explain the functionality of specific sections of the code. Documentation Tips: i. Keep the documentation simple and clear for the intended audience (users or developers). ii. Update the documentation whenever changes are made to the program. iii. Use tools like Javadoc, Sphinx, or Markdown for creating professional documentation. 9  6. 2 SOFTWARE TESTING 6.2.1 Software Application Testing 6.2.2 Master Test Plan 6.2 6.2.3 Types of Testing Software Testing 6.2.4 Testing Process 6.2.5 Acceptance Testing 10  6.2.1 Software Application Testing Definition: Software testing is the process of evaluating a software application to ensure it meets the specified requirements and is free of defects. Purpose: To verify the functionality, performance, and reliability 6.2.1 Software of the software before deployment. Application Key Points: I. Identifies bugs or errors that need fixing. Testing II. Ensures the software works as expected under different conditions. Tips: I. Test frequently during development to catch issues early. II. Use both manual and automated testing methods for thorough evaluation. 11  6.2.2 Master Test Plan Definition: A master test plan is a detailed document outlining the strategy, objectives, schedule, resources, and scope of testing activities. Purpose: To provide a clear roadmap for the testing process. To ensure all aspects of the application are tested systematically. 6.2.2 Master Key Elements: Test Plan Objectives and scope of testing. Roles and responsibilities of the testing team. Tools and techniques to be used. Risk analysis and mitigation plans. Tips: Keep the test plan aligned with the project goals. Regularly update the plan based on testing progress. 12  6.2.3 Types of Testing Unit Testing: Focuses on individual components or functions to ensure they work as intended. Integration Testing: 6.2.3 Types of Ensures that different modules or components interact correctly. Testing System Testing: Verifies that the entire system meets the specified requirements. Performance Testing: Evaluates the application's speed, scalability, and stability under various conditions. User Acceptance Testing (UAT): Conducted with end-users to verify the software meets their needs. 13  6.2.4 Testing Process Planning: Identify the scope, objectives, and resources for testing. Designing Test Cases: Create test cases that cover all possible scenarios, including edge cases. Executing Tests: 6.2.4 Testing Run the test cases on the application. Process Recording Results: Document the outcomes of each test case. Reporting Bugs: Identify and report any defects found during testing. Retesting: Verify that the fixed issues are resolved and no new bugs have been introduced 14  6.2.5 Acceptance Testing Definition: Acceptance testing ensures the software meets the end-user or client requirements and is ready for deployment. Types of Acceptance Testing: 1. Alpha Testing: Conducted internally by the development team. 6.2.5 2. Beta Testing: Performed by a small group of actual users in a real-world environment. Acceptance Testing Key Points:  Focuses on usability, functionality, and performance.  Helps gain user confidence in the software. Tips:  Engage end-users early in the testing process.  Document feedback to implement necessary changes. 15  6. 3 Installation 6.3.1 Types of Installation (Direct Installation, Direct Installation, 6.3 parallel Installation) Installation 16  Definition: Installation is the process of setting up software on the user’s system so that it can function correctly. It involves copying files, configuring settings, and preparing the system for use. Purpose: To make sure that the software is properly installed, configured, and ready to use on the target machines or environments. 6.3 Installation Key Activities: Preparing the installation environment. Running the installation process to ensure software setup is correct. Configuring settings for optimal performance and usability. 17  6.3.1 Types of Installation There are several types of installation methods used depending on the project requirements and environment: 1.Direct Installation Definition: The new software is installed directly over the old version or onto a fresh system. 6.3.1 Types of When to Use: Installation 1. When the system does not need to support the old version anymore. 2. When users do not need to continue using the previous version. Advantages: 1. Simple and fast installation process. 2. No need to maintain multiple versions. Disadvantages: 1. Risk of losing data or settings from the previous version if not handled correctly. 2. Can cause downtime if issues arise during installation. 18  6.3.1 Types of Installation There are several types of installation methods used depending on the project requirements and environment: 2. Parallel Installation Definition: The new software is installed alongside the existing version, allowing both 6.3.1 Types of versions to run simultaneously. When to Use: Installation When the system must continue running the old version while testing or transitioning to the new one. When users need time to adapt to the new version without disrupting ongoing work. Advantages: No risk of data loss from the old version. Allows users to test the new version while still having access to the old version. Disadvantages: Requires more system resources, as both versions run at the same time. Users may face confusion with two versions available. 19  6.3.1 Types of Installation There are several types of installation methods used depending on the project requirements and environment: 3. Phased Installation Definition: The new software is installed in stages, usually starting with a small group of users 6.3.1 Types of When to Use: or systems before being rolled out to the entire organization or user base. Installation When it is important to minimize risks by testing the new version in a limited environment before full deployment. When there are a lot of users, and it's not feasible to install the software on all systems at once. Advantages: Allows for troubleshooting and adjustments before full rollout. Reduces the risk of widespread issues. Disadvantages: Can slow down the implementation process as it takes place in stages. May create inconsistency between users with different versions. 20  6. 4 SYSTEM DOCUMENTATIONS 6.4.1 Types of Documentation 6.4 6.4.1.1Internal Vs External Documentation System 6.4.1.2 System Vs User Documentation Documentation 21  6. 4 SYSTEM DOCUMENTATIONS Definition: System documentation refers to the written materials that describe the design, development, and operation of a software system. It serves as a reference for developers, maintainers, and 6.4 users, ensuring the system functions properly and can be updated or modified when needed. System Documentation Purpose: ✓To provide a detailed record of the software’s structure, behavior, and usage. ✓To ensure that other developers or maintainers can understand, manage, and enhance the system in the future 22  6.4.1 Types of Documentation System documentation can be categorized into different types based on the target audience and the purpose it serves. Below are the key distinctions: 1. Internal Documentation Definition: Internal documentation is intended for developers, system administrators, or other technical teams involved in the development, 6.4.1 Types of maintenance, or debugging of the system. Purpose: To provide detailed information about the code, logic, Documentation architecture, and design of the system. Key Elements: (6.4.1.1 InternalVs Code comments to explain the purpose and functionality of different code External blocks. Design diagrams (e.g., flowcharts, UML diagrams) to represent system Documentation) architecture. Database schema descriptions and relationships. Tips: Use consistent and clear naming conventions. Comment the code effectively so that other developers can understand the logic and make future changes. 23  6.4.1 Types of Documentation System documentation can be categorized into different types based on the target audience and the purpose it serves. Below are the key distinctions: 2. External Documentation Definition: External documentation is created for users, 6.4.1 Types of stakeholders, or other non-technical audiences to understand how to interact with the system. Documentation Purpose: To guide users in installing, configuring, and using the software. (6.4.1.1 InternalVs Key Elements: External User manuals, installation guides, and setup instructions. Documentation) Troubleshooting guides, FAQs, and help sections. System requirements and compatibility details. Tips: Keep the language simple and avoid technical jargon. Include screenshots or visuals to help users understand complex steps. 24  6.4.1 Types of Documentation System Documentation Definition: System documentation focuses on the internal workings of the software system. It is meant for developers, testers, and administrators to understand and maintain the system. 6.4.1 Types of Purpose: To ensure the system can be easily modified, maintained, and extended. Documentation Key Elements: (6.4.1.2 System Vs User Architecture design, class and function descriptions. Documentation) Database design, including data models and relationships. System workflows and code-level comments. Tips: Ensure the documentation reflects the actual system design and is regularly updated to match any changes to the codebase. Include system performance details and areas where optimization is needed. 25  6.4.1 Types of Documentation User Documentation Definition: User documentation is created for end-users who will interact with the system. It focuses on guiding them on how to use the system effectively. 6.4.1 Types of Purpose: To help users understand how to operate the software, resolve common issues, and take full advantage of the system’s features. Documentation Key Elements: (6.4.1.2 System Vs User Installation and setup instructions. Documentation) Step-by-step guides for using different features of the software. Example scenarios and case studies to demonstrate how the system can be used. Tips: Keep it user-friendly, with clear explanations and easy-to-follow steps. Provide examples and use cases to help users understand how to solve common problems. 26  6. 4 SYSTEM DOCUMENTATIONS Both internal and external documentation are critical for the successful development and use of software. 6.4.1 Types of Internal documentation helps developers maintain and improve Documentation the system, while external documentation ensures that end- users can effectively operate the system. (CONCLUSION) Additionally, system and user documentation serve different purposes but are both necessary for the overall success of the software. 27  6. 5 USER TRAINING AND SUPPORT 6.5.1 Types Of Training Methods 6.5 6.5.2 Support Issues User Training and Support 28  6. 5 USER TRAINING AND SUPPORT Definition: User training and support refer to the activities and resources provided to help end-users understand, use, and 6.5 troubleshoot the software effectively. This is crucial to ensure that users can take full advantage of the software's capabilities User Training and and resolve any issues they might encounter. Support Purpose: To provide users with the knowledge and skills they need to use the system effectively. To ensure users receive the necessary assistance when facing challenges or issues. 29  6.5.1 Types of Training Methods 1. Instructor-Led Training (ILT) Definition: Training where an instructor or trainer teaches users in a structured, classroom-like environment, either in person or virtually. When to Use: 6.5.1 Types of 1. When there is a need for direct interaction and real-time feedback. 2. When training large groups or specific teams. Training Advantages: 1. Allows for personalized instruction and clarification of doubts. Methods 2. Can adapt to the specific needs of the audience. Disadvantages: 1. Requires scheduling and can be time-consuming. 2. More costly due to the need for trainers and resources. 30  6.5.1 Types of Training Methods 2. Self-Paced Training Definition: Users complete training modules on their own time, often using online materials such as video tutorials, e-learning platforms, or manuals. When to Use: 6.5.1 Types of 1. 2. When users need flexibility in learning at their own pace. For large numbers of users or when it’s difficult to conduct in-person Training training. Advantages: Methods 1. 2. Flexible and can be done at the user's convenience. Cost-effective, as there’s no need for instructors or scheduled classes. Disadvantages: 1. Users may feel isolated or lack support if they have questions. 2. Less direct interaction and feedback from instructors. 31  6.5.1 Types of Training Methods 3. On-the-Job Training (OJT) Definition: Training that takes place in the user’s working environment, with the user learning by performing tasks using the software under the guidance of a mentor or supervisor. 6.5.1 Types of When to Use: 1. When users need hands-on experience and practical understanding of the Training 2. software. When training needs to be integrated into the daily workflow. Methods Advantages: 1. Practical, real-world training in the user’s own environment. 2. Allows for immediate application of skills learned. Disadvantages: 1. May disrupt regular work processes. 2. Requires knowledgeable mentors or supervisors. 32  6.5.1 Types of Training Methods 4. Workshops and Seminars Definition: Group training sessions that focus on a specific topic or aspect of the software. 6.5.1 Types of When to Use: 1. When users need to learn about new features or more Training advanced aspects of the software. Methods Advantages: 1. Interactive and can cover multiple topics quickly. 2. Group learning environment encourages collaboration. Disadvantages: 1. Can be too fast-paced for some learners. 2. May not address individual needs. 33  6.5.1 Types of Training Methods 5. Online Help and Tutorials Definition: Web-based resources such as help documentation, FAQs, video tutorials, and forums that provide users with on- demand learning. 6.5.1 Types of When to Use: Training 1. When users need quick, self-guided help. 2. For common tasks or troubleshooting. Methods Advantages: 1. Accessible anytime and anywhere. 2. Helps users solve problems on their own. Disadvantages: 1. Can be overwhelming if not well organized. 2. Users may not always find the solution to their problem without help. 34  6.5.2 Support Issues Support issues are the challenges or problems users encounter when using the system. Proper support should address these issues quickly and efficiently. 6.5.2 Support 1.Technical Issues Definition: Problems related to the system’s performance, Issues compatibility, or functionality. Examples: 1. Software crashes, errors, or bugs. 2. Problems with system configuration or setup. 3. Compatibility issues with other software or hardware. Support Actions: 1. Provide troubleshooting steps or solutions. 2. Offer patches, updates, or bug fixes. 35  6.5.2 Support Issues Support issues are the challenges or problems users encounter when using the system. Proper support should address these issues quickly and efficiently. 6.5.2 Support 2. User Errors Issues Definition: Mistakes or misunderstandings caused by users not knowing how to use the software correctly. Examples: Incorrect data entry or misuse of features. Difficulty navigating or understanding the interface. Support Actions: Offer user training or clarification on the correct procedures. Provide step-by-step guides or instructional videos. 36  6.5.2 Support Issues Support issues are the challenges or problems users encounter when using the system. Proper support should address these issues quickly and efficiently. 6.5.2 Support 3. Access and Permission Issues Issues Definition: Problems related to user access rights, permissions, or login issues. Examples: Users being unable to log in or access certain features. Permission errors preventing users from completing tasks. Support Actions: Verify user credentials and access rights. Resolve issues related to user roles or permissions. 37  6.5.2 Support Issues Support issues are the challenges or problems users encounter when using the system. Proper support should address these issues quickly and efficiently. 6.5.2 Support 4. System Updates and Maintenance Issues Definition: Ongoing issues related to keeping the software up-to-date or ensuring it remains functional after updates. Examples: Problems arising after installing updates or patches. Issues with system performance or security after maintenance. Support Actions: Communicate scheduled updates and maintenance windows. Provide solutions to restore functionality after updates. 38  6.5.2 Support Issues Support issues are the challenges or problems users encounter when using the system. Proper support should address these issues quickly and efficiently. 6.5.2 Support 5. Customization and Configuration Support Definition: Problems related to the software’s customization Issues or configuration based on the user’s specific needs. Examples: Difficulty adjusting settings or preferences. Challenges in setting up reports or features according to specific requirements. Support Actions: Offer configuration guides or step-by-step tutorials. Provide expert assistance for complex customizations. 39 6.5 CONCLUSION User Training and Training and support are crucial for helping users maximize the benefits of the software. The right training method should Support be chosen based on the user’s needs, and timely support should be available to resolve any issues that arise. By (CONCLUSION) providing clear training and efficient support, users can use the software effectively and reduce frustration during their experience. 40  6. 6 DOCUMENTATION OF IMPLEMENTATION PHASE 6.1.1 Documentation 6.6 Documentation of Implementation Phase 41  6.6 Documentation of Implementation Phase Definition: Documentation during the implementation phase involves recording all the activities, processes, decisions, and 6.6 technical details related to the actual deployment and execution of the software. This documentation serves as a reference for future Documentation maintenance, updates, and troubleshooting, as well as for ensuring that the system is deployed properly. of Implementation Purpose: To ensure that the development and deployment process is well- Phase documented and transparent. To provide clear instructions and records for users and developers regarding the installation, configuration, and operation of the software. To support ongoing maintenance, troubleshooting, and system improvements after implementation. 42  6.6 Documentation of Implementation Phase Documentation during the implementation phase typically includes the following key components: 1.System Design Documentation 6.1.1 1. What it Includes: Detailed descriptions of the system architecture, components, and design decisions made during development. Documentation 2. Purpose: To guide developers and administrators in understanding the overall structure and design of the software. It also helps when making updates or troubleshooting issues. 3. Key Points: 1. System architecture diagrams, data flow diagrams (DFD), and entity- relationship diagrams (ERD). 2. Details about key components, such as databases, servers, and third- party integrations. 43  6.6 Documentation of Implementation Phase Documentation during the implementation phase typically includes the following key components: 2. Installation Documentation 6.1.1 What it Includes: Instructions on how to install the software, including any prerequisites, configuration steps, and setup Documentation procedures. Purpose: To ensure the system can be properly installed and configured in the target environment. Key Points: Step-by-step installation guide. System requirements and dependencies. Troubleshooting steps for common installation problems. 44  6.6 Documentation of Implementation Phase 3. User Documentation What it Includes: Information for end-users on how to operate and use the system effectively. This could include user manuals, FAQs, 6.1.1 and help guides. Documentation Purpose: To ensure users understand how to interact with the software and can resolve common issues without needing external support. Key Points: User interface descriptions, feature explanations, and common workflows. Troubleshooting tips and frequently asked questions (FAQs). 45  6.6 Documentation of Implementation Phase 4. Test Documentation What it Includes: Documentation of the testing process, including the test cases, test results, and any issues identified during testing. 6.1.1 Documentation Purpose: To record the quality assurance efforts and ensure that the software is free of bugs and performs as expected. Key Points: Test plans, test cases, and test results. Issue logs and resolution reports for bugs found during testing. 46  6.6 Documentation of Implementation Phase 5. Configuration and Customization Documentation What it Includes: Detailed information on any customizations or configurations made to the system during or after installation. 6.1.1 Documentation Purpose: To document the changes made to the system for future reference, especially if custom configurations are required for different user needs or environments. Key Points: Configurable parameters, settings, and customization options. Instructions on how to modify configurations or add new features. 47  6.6 Documentation of Implementation Phase 5. Maintenance and Support Documentation What it Includes: Guidelines and procedures for ongoing maintenance and support, including how to handle updates, resolve 6.1.1 issues, and ensure system stability. Documentation Purpose: To ensure that the system can be properly maintained and supported after it is deployed. Key Points: Scheduled maintenance procedures. How to apply patches or updates. Contact information for support and escalation procedures. 48  6.6 Documentation of Implementation Phase 6. Backup and Recovery Documentation What it Includes: Procedures for backing up and recovering the 6.1.1 system in case of failure or data loss. Documentation Purpose: To ensure data integrity and availability in case of unexpected issues. Key Points: Backup schedules and methods. Recovery plans and how to restore data from backups. 49  Conclusion:  Effective documentation in the implementation phase ensures that the system is deployed correctly, users can operate it efficiently, and the software can be maintained and updated with 6.1.1 minimal issues. Documentation  By documenting each aspect of the implementation process system design, installation, testing, user support, and maintenance,organizations can ensure a smooth transition from development to full-scale use.. 50