CSIS Chapter 12 & 14 Notes PDF

Chapter 12: System Acquisition and Development Two Approaches to Software Acquisition: Buy Off-the-Shelf Software: ○ Advantages: Quicker Deployment: Software is ready for use, reducing time spent on development. Lower Risk: Less uncertainty since...

Chapter 12: System Acquisition and Development Two Approaches to Software Acquisition: Buy Off-the-Shelf Software: ○ Advantages: Quicker Deployment: Software is ready for use, reducing time spent on development. Lower Risk: Less uncertainty since the software has already been tested and used by other organizations. ○ Disadvantages: High Maintenance & Support Costs: Ongoing updates, bug fixes, and technical support may be expensive. May Not Fully Align with Needs: The software may not match the organization's specific workflows or business processes, leading to inefficiencies or the need for significant customization. Build Custom Software: ○ Advantages: Tailored to Needs: Custom software is designed to fit the specific needs, processes, and goals of the organization. Potential Competitive Advantage: If the software is unique, it can offer a competitive edge over others. ○ Disadvantages: High Costs: Building custom software is often more expensive than buying off-the-shelf software due to development, testing, and maintenance costs. Long Development Time: Custom software can take months or even years to develop, delaying its deployment and benefits. Ongoing Support Required: Even once built, custom software needs ongoing maintenance, troubleshooting, and updates. Waterfall System Development Approach: Overview: ○ Sequential Process: The waterfall model follows a linear, step-by-step process where each phase must be completed before moving to the next. Management reviews each phase to ensure quality and adherence to the scope, costs, and schedule. ○ Phases in the Waterfall Model: Investigation (System Investigation): Purpose: Understand the problem or opportunity. Techniques: Joint Application Development (JAD) (structured meetings to accelerate investigation), Functional Decomposition (breaking down processes), Feasibility Analysis (technical, economic, legal, operational, and schedule feasibility). Key Phases: The waterfall system development process includes six phases: investigation, analysis, design, construction, integration and testing, and implementation, with a final step of operation, maintenance, and disposition. Review at Each Phase: After each phase, a review is conducted to assess scope, costs, schedule, and benefits, ensuring the project remains on track. Feasibility Analysis: The system investigation phase assesses technical, economic, legal, operational, and schedule feasibility. Joint Application Development (JAD): JAD is a structured meeting process used in the investigation, analysis, and design phases to enhance efficiency and effectiveness. Analysis: Purpose: Define what the system must do to solve the problem.  Focus on gathering data on the existing system, determining the requirements for the new system, and investigating possible alternatives. Importance of defining and prioritizing system requirements—incorrect or missed requirements can lead to delays and cost overruns. Data-Flow Diagrams (DFD): Used to represent the flow of data in the current system and design of the new system. Design: Purpose: Create technical specifications for how the system will solve the problem. Includes details on system outputs, inputs, user interfaces, hardware/software, databases, telecommunications, and security controls. Results in a complete set of specifications that guide the system’s construction. Construction: Purpose: Build the system based on design specifications. Activities: Coding software, creating databases, performing initial testing (unit testing, integration testing). Integration & Testing: Purpose: Ensure all components work together and meet requirements. Activities: Comprehensive testing, including system testing, volume testing, and user acceptance testing. Implementation: Purpose: Deploy the system to users. Activities: User preparation (training), site preparation (hardware setup), installation, and cutover (system go-live). ○ Post-Implementation Phases: Operation: System is used under real-world conditions; ongoing monitoring is essential.  Maintenance: Continuous improvement and updates to meet evolving needs. Disposition: Disposing of hardware, closing contracts, and archiving data as the system is decommissioned. Agile Development Approach: Overview: ○ Iterative & Incremental Development: The system is developed in short cycles called "sprints," lasting from 2 weeks to 2 months. Each sprint delivers a working version of the system with prioritized features. ○ Characteristics: Evolving Requirements: Unlike waterfall, agile assumes requirements will change and evolve over time, so flexibility is key. Focus on Collaboration and Speed: The goal is to quickly deliver software that can be improved upon based on feedback and emerging needs. Agile Development's Characteristics: Agile development is an iterative process that focuses on delivering systems in incremental "sprints," with the flexibility to adapt to emerging requirements. Scrum Framework: Emphasizes teamwork, rapid progress, and stakeholder collaboration. Scrum roles include Scrum Master, Scrum Team, and Product Owner. Extreme Programming (XP): An agile method that focuses on incremental development with short cycles to improve productivity. DevOps: The integration of development and IT operations to improve software delivery speed and reliability. ○ Key Agile Frameworks and Concepts: Scrum: A widely used agile framework that organizes work into small, manageable chunks (sprints). Roles:  Scrum Master: Facilitates the team’s work and removes obstacles. Product Owner: Represents stakeholders and aligns the team’s work with business goals. Scrum Team: A small, cross-functional team responsible for all aspects of development (investigation, analysis, design, coding, testing). Extreme Programming (XP): Focuses on continuous improvement through shorter development cycles, emphasizing customer feedback and rapid adaptation. DevOps: A practice that combines development and IT operations to enable faster and more reliable software deployment, crucial for agile development's success. Buying Off-the-Shelf Software: Considerations: 1. Modification Efforts: The cost and effort required to modify the software to fit into the organization’s environment must be evaluated. 2. Compatibility: Consider how well the new software integrates with existing systems, and whether additional software is needed to facilitate the integration. 3. Cost/Time Comparison: Building custom software can be expensive and time-consuming, making purchasing a more attractive option for many organizations. 4. Customization Costs: When buying off-the-shelf software, the costs and efforts required for modifying the software to fit the organization’s needs must be factored in. 5. RFI (Request for Information): A preliminary assessment tool used to evaluate vendors and software packages during system analysis. Evaluation Process: Preliminary Assessment: Evaluate the marketplace to determine if existing software can meet the organization's needs. Request for Information (RFI): A document sent to vendors outlining the organization’s requirements and requesting information on their software's capabilities and resources.  Vendor Evaluation: Preliminary Evaluation: Shortlist vendors based on initial criteria. Final Evaluation: Involves a deeper dive into vendor proposals, demonstrations, and discussions with existing customers to assess software performance, support, and customization options. Chapter 14: Ethical, Legal, and Social Issues of Information Systems Principle: Computer-Related Waste and Mistakes Computer-related waste and mistakes contribute to unnecessary costs and lost profits in organizations. ○ Computer Waste: The inappropriate use of technology and resources across both public and private sectors. Results from poor integration of Information Systems (IS) components, leading to duplication and overcapacity. Inefficient procedures, thoughtless disposal of useful resources, and misuse of computer time for personal use also contribute to waste. ○ Computer Mistakes: Errors, failures, and issues that produce incorrect or valueless output. Caused by inappropriate processing instructions, inaccurate data entry, mishandling of output, and poor systems design. Preventing Waste and Mistakes: ○ Establish, implement, monitor, and review effective policies and procedures. ○ Develop manuals and training programs to help prevent waste and mistakes. ○ Regular training for individuals and workgroups and providing documents covering the use and maintenance of computer systems can help reduce errors.  ○ Monitoring and Corrective Action: Routine practices should be monitored to ensure adherence to established procedures. Corrective actions should be taken when necessary. ○ Review Existing Policies: Periodically review policies and procedures to ensure they are adequate and effective. ○ Training and Manuals: Emphasized the importance of developing training programs for individuals and teams, as well as manuals, to avoid waste and mistakes. ○ Routine Monitoring: The need to consistently monitor and enforce adherence to established practices within organizations. Balancing Privacy and Information Use Balancing Needs vs. Rights: Technology use requires balancing the needs of those using information with the rights of those whose data is being used. ○ Privacy Concerns: A significant social issue in the context of information systems, especially regarding terrorism, cyberattacks, and the monitoring of individuals. ○ Workplace Privacy: Employers use technology to manage employee productivity and protect IS resources, which includes monitoring email, web browsing, and instant messaging. Many employers have policies that eliminate any expectation of privacy when using company-owned computers or systems. ○ Health and Wellness Programs: The rise of workplace health programs has prompted calls for updated regulations on how personal data, including health data, is used and monitored. ○ Wearable Technology: New privacy concerns arise as employers encourage or require the use of wearable devices that monitor employees' health and location. ○ Public Internet Privacy: Some believe the Internet offers no privacy, and users do so at their own risk. Others argue that companies should implement strict privacy procedures to prevent invasions of privacy. Companies selling or sharing customer and employee data raises concerns about privacy.  ○ Fairness in Information Use: Privacy rights emphasize knowledge, control, notice, and consent, where individuals should know what data is collected, have the ability to correct errors, and consent to how their data is used. ○ Parental Control: Some companies provide filtering software to help parents control what their children access on the Internet. ○ Business Privacy Policy: Organizations should develop clear policies regarding privacy rights for customers and employees, addressing database access, email monitoring, and electronic surveillance. ○ Federal Laws and Privacy: Various federal laws addressing personal privacy issues, especially regarding data collection and monitoring by the government, employers, and organizations. ○ Data Collection for Security vs. Privacy Rights: The tension between data collection for increased security and concerns over privacy violations. ○ Parental Controls for Online Safety: Companies provide filtering software to help control what children can access on the internet. Designing Jobs and Equipment to Prevent Health Issues Health Risks from Computers: Jobs requiring extensive computer use can lead to a sedentary lifestyle, which increases the risk of health problems. Ergonomics: The study and design of computer equipment and workspaces aimed at reducing health issues and improving efficiency. ○ Ergonomic principles help to mitigate harmful effects and enhance the efficiency of information systems. ○ Repetitive Strain Injury (RSI) Prevention: Includes maintaining good posture, addressing pain issues promptly, performing stretching and strengthening exercises, and seeking proper treatment. Ethical Behavior in Information Systems  Ethics and Professional Standards: Many professionals adhere to a code of ethics that outlines essential principles and core values for their work. ○ Ethical Issues: Ethics pertains to determining what is right or wrong in a given situation. Ethical computer users go beyond avoiding illegal activities, considering the broader impact of their actions (e.g., internet usage, IS activities) on other individuals and organizations. ○ Ethical Dilemmas: In decision-making, conflicting values often arise, leading to ethical dilemmas where the fairest option isn't always clear. ○ Laws vs. Ethics: Laws provide guidelines but do not always dictate ethical behavior. Just because something is legal doesn’t make it ethical. ○ Codes of Ethics: Many professional organizations and associations, such as the Association for Computing Machinery (ACM), have developed guidelines and codes of ethics for their members to follow. ○ IS Professional Integrity: IS professionals are encouraged to join relevant computer-related associations and commit to adhering to detailed ethical codes, ensuring responsible and ethical behavior in their work. ○ Ethical Dilemmas in Decision-Making: The challenges involved in resolving value conflicts between stakeholders to make ethical decisions. ○ Codes of Ethics for IS Professionals: The need for IS professionals to subscribe to ethical codes, such as those developed by the Association for Computing Machinery (ACM).