Info Sys Finals Reviewers PDF

TOPIC 1 |​ System Life Cycle ○​ A good outline can catch problems SYSTEM LIFE CYCLE before they affect ​ Is a conceptual model used in development. PM...

TOPIC 1 |​ System Life Cycle ○​ A good outline can catch problems SYSTEM LIFE CYCLE before they affect ​ Is a conceptual model used in development. PM that describes the stages involved in an IS Development 2.​ ANALYSIS / FEASIBILITY Project. ​ Definition: determines ​ From an initial Feasibility Study the project’s feasibility to the maintenance of the (technical, operational, completed application. and economic aspects). ​ Purpose: to translate 7 PHASES OF SDLC high-level plans and 1.​ PLANNING / INITIATION goals into actionable ​ Definition: the ideas and bridge the gap foundation of the whole between project SDLC scheme. conception and actual ​ Purpose: to clearly development. define the project's target ​ Objectives: and assess how to solve ○​ Analyze the specific problems using system software solutions. requirements ​ Objectives: ○​ Assess project ○​ Problem feasibility Identification ​ Actual Process: ○​ Resource and Cost ○​ Gather Estimation information ○​ Requirement ​ System & Gathering Client ○​ Setting requirements Expectations & ​ Market Goals research ​ Actual Process: ○​ Analyzation ○​ Outline of objectives ​ Evaluate ○​ Drawing a rough existing plan prototype/s ○​ Pre-analysis using ○​ Assessment of AI simulation tools project’s feasibility ○​ Resource ​ Final Output: estimation and ○​ Software allocation Requirements ○​ Setting of deadlines Specification and time frames (SRS) Document ​ Pro Tip: A good outline ​ Detailed description of  the system’s ○​ Conducting a purpose, security risk features, and assessment functionalities ○​ Formulating a , acting as a strategy to move guide for the current data to the development new system team. 4. DEVELOPMENT 3. DESIGN ​ Definition: referred to as ​ Definition: is centered the coding stage, it is on visualization. where coding begins to ○​ The systems take place or where architect is teams write the actual responsible for code. designing the ​ Objectives: system and ○​ Develop making the first Functional, software prototype Efficient, and to show how it User-Friendly should look and Software function. ○​ Utilize Appropriate ○​ The design phase Programming is a key milestone Language in software ○​ Adhere to SDD development, and Coding marking the shift Guidelines from concepts to real outputs. ​ Fundamental Aspects ​ Actual Process: Developers Cover: ○​ Coding ○​ System Interface ​ Writing code ○​ User Interface as ○​ Security instruction. ○​ Databases ○​ Debugging ○​ Network and its ​ Identifying requirements and fixing ​ Elements to Consider errors. in the Design to ​ Methodologies: Mitigate Risk: ○​ Traditional ○​ Identifying Approach potential risks ​ Highly structured approach  focused on ​ Best Practices: coding. Ex.: ○​ Start Testing Early (Shift-Left Testing) 1.​ Waterfall ○​ Maintain Clear and 2.​ Agile Testable 3.​ Spiral Requirements 4.​ Iterative ○​ Utilize Code 5.​ V-Model Analysis Tools 6.​ Big Bang ​ Types of Testing: ○​ Unit Testing ○​ Modern ​ testing Approach individual ​ Low-code / components no-code for expected 1.​ Tools for functionality. building ○​ Integration software Testing with ​ ensuring that minimal or different without modules coding. work together ​ AI-assisted seamlessly. developmen ○​ System Testing t ​ evaluating 1.​ Automate the complete parts of the system to coding verify process compliance using AI. with functional 5. TESTING and ​ Definition: a critical non-functiona stage aimed at ensuring l that the software requirements application meets. specified requirements ○​ Acceptance and functions correctly. Testing ​ Processes: ​ validating the ○​ Bug detection software ○​ Vulnerability against user testing expectations ○​ Defect and error identification 6. IMPLEMENTATION performance, and ​ Definition & Purpose: adapt the system This stage starts after to changing user acceptance and requirements after testing of the system. it has been The designed system deployed. is brought to life and ​ Processes: put into operation. The ○​ Continuous system is set up to Monitoring support the planned ○​ Maintenance business operations Activities ​ Objectives: ​ Corrective ○​ successfully deploy Maintenance: the newly Addressing issues developed system ​ Adaptive ○​ deliver a reliable, Maintenance: efficient, and Modifying the user-friendly system system. ​ Perfective ​ Processes: Maintenance: ○​ System Deployment Enhancing the ○​ User Onboarding system's ○​ Performance performance Evaluation ○​ Ongoing Support ○​ Production Readiness 6 BASIC TYPES OF SDLC MODELS 7. MAINTENANCE ​ Definition & Purpose: 1.​ WATERFALL MODEL The developers begin ​ Definition: A linear, practicing any structured, and sequential activities required to approach to software handle issues reported development and project by end-users as part of management where each the maintenance stage has its separate mode. Developers are project plan and is strictly responsible for related to the previous and implementing any next steps changes that the ​ About this model: software might need ○​ Used in projects after deployment. with long timelines ​ Objectives: where there are ○​ address issues, well-defined goals improve and project  requirements with ​ Definition: Combines the little room for Waterfall and Iterative errors models. It uses repeated ○​ Considers that cycles or loops to refine one phase can be software progressively, started after the making it ideal for complex completion of the projects with evolving previous phase requirements and high with extensive uncertainty. documentation ​ 4 Phases of Spiral ○​ Shows a high ○​ Planning degree of ​ Determine structure and objectives clarity but is rigid, ​ Define goals, with no feedback explore path. alternatives, and identify 2.​ ITERATIVE MODEL constraints. ​ Definition: Combines the ○​ Risk Analysis sequential steps of the ​ Identify and Waterfall Model with the resolve risks flexibility of iterative design ​ Foresee which allows for challenges and improvements and changes plan mitigation to be made at each stage ○​ Development instead of waiting until the ​ Testing end of project. ​ Build strategies ​ About this model: and implement ○​ Repeating development solutions. cycles where each ○​ Evaluation iteration builds upon the ​ Plan the next previous one iteration ○​ Gets early feedback from ​ Review outcomes users and get feedback. ○​ Often favored for its adaptable flow where 4.​ V-MODEL changes are ​ Definition: Short for comparatively easier to Verification and Validation accommodate Model; is a variation of the ○​ Can be Waterfall Model where each resource-consuming due phase has a corresponding to multiple iterations testing phase. This model’s approach minimizes major 3.​ SPIRAL MODEL  issues by addressing bugs at ○​ No clarification about the each stage. user’s expectations. ​ Verification Phase ○​ No strict guidelines on ○​ Business requirement product release or analysis delivery date. ○​ System Design ○​ Architecture Design 6.​ AGILE MODEL ○​ Module Design ​ Definition: The most popular ○​ Coding Phase SDLC methodology among ​ Validation Phase developers. It strongly ○​ Unit Testing focuses on collaboration ○​ Integration Testing between cross-functional ○​ System Testing teams and the ○​ Acceptance Testing implementation of small changes based on regular 5.​ BIG BANG MODEL client feedback. ​ Definition: It’s the simplest ​ Phases SDLC model because it ○​ Plan doesn’t require any planning. ○​ Design This model combines the ○​ Develop efforts, time, and resources ○​ Test to build a product per ○​ Deploy customer requirements. ○​ Review However, it may happen that ○​ Launch the end product might not ​ Methods meet the actual needs. ○​ Scrum ​ Can be phased out in 3 ○​ Crystal points: ○​ Kanban ○​ Integrate each ○​ Extreme Programming individual’s modules to (XP) give a unique integrated ○​ Dynamic Software overview. Development Method ○​ Test each module (DSDM) separately to identify any ○​ Lean Software error or defects Development ○​ If any error found then ○​ Feature Driven separate that module Development (FDD) and identify the cause of the error BENEFITS OF SYSTEM LIFE CYCLE ​ When to use it and where ​ Enhances Product Quality not to: ​ Improves Project Management ○​ Developing a project ​ Manages Risk Effectively ○​ Newer requirements ​ Enhances Communication and ○​ Changing requirements Collaboration  ​ Enables Efficient Resource Utilization TOPIC 2 |​ System Analysis and ​ Flexibility and Adaptability Design System Analysis and Design requirements for new ​ A structured approach used to system. develop, maintain, and improve ○​ Outcome: Detailed information systems within an requirements specification. organization. ○​ Key activities: ​ Identify business System Analyst needs. ​ Plan, develop, and maintain ​ Gather and information systems. document user ​ Manages IT projects and/or report requirements. to other department ​ Analyze existing systems and Benefits of Systems Analysis and processes. Design ​ Identify system ​ Better Decision-Making boundaries and ​ Improved Efficiency interfaces. ​ Cost-Savings ​ Create process ​ Alignment to Business Goals models and data flow diagrams. The Systems Development Life Cycle ○​ Requirement Gathering (SDLC) Techniques 1.​ Planning (Planning Phase) ​ Interviews ○​ Definition: Define project ​ Surveys scope, goals, and ​ Observation feasibility. ​ Document Analysis ○​ Key activities: ​ Joint Development ​ Identify business ​ Prototyping needs. 3.​ System Design (Ddesign Phase) ​ Conduct preliminary ○​ Definition: Create a investigations. blueprint for the new ​ Perform feasibility system. study (technical, ○​ Outcome: Detailed system economic, design specification. operational). ○​ Key activities: ​ Develop project ​ Develop system schedule and architecture. budget. ​ Design user 2.​ System Analysis (Analysis interfaces. Phase) ​ Create database ○​ Definition: Understand schema. current system and define ​ Define security measures.  ​ Plan system Project Management in Systems integration. Analysis and Design ○​ User Interface Design ​ Key components: Principles ○​ Scope management ​ Consistency ○​ Time management ​ Accessibility ○​ Cost management ​ Simplicity ○​ Quality management ​ Efficiency ○​ Risk management ​ Feedback ​ Tools: ​ Error Prevention ○​ Gantt charts 4.​ Implementation ○​ PERT diagrams ○​ Definition: Build, test, and ○​ Project Management deploy the new system. Software ○​ Outcome: Fully functional ​ Importance: and operational system. ○​ Ensures project stays on ○​ Key activities: track and meets objectives ​ Develop software components. Tools and Techniques in Systems ​ Conduct unit, Analysis integration, and 1.​ Data Flow Diagrams (DFD) system testing. ○​ Definition: Visualize data ​ Perform user movement within a system. acceptance testing ○​ Characteristics ​ Train end-users. ​ Graphical ​ Deploy the system. Representation ○​ Software Development ​ Problem analysis Approaches ​ Abstraction ​ Hierarchy 5.​ Operation and Maintenance ​ Data Flow (Maintenance Phase) ​ Ease of ○​ Definition:Ensure ongoing understanding system functionality and ​ Modularity relevance. 2.​ Entity-Relationship Diagrams ​ Corrective (ERD) ​ Adaptive ○​ Definition: A flowchart that ​ Perfective shows relationships ​ Preventive between entities (people, ○​ Key activities: objects, concepts) in a ​ Monitor system system. performance. ○​ Used in : Designing and ​ Fix bugs and debugging relational address issues. databases in software, ​ Implement system business, education, and updates and research. enhancements. 3.​ Unified Modeling Language ​ Provide user (UML) support.  ○​ Definition: Standard providing a matrix of rows notation for object-oriented and columns for defining an analysis and design. issue and possible actions. ○​ Examples: 9.​ Pseudocodes ​ Class Diagram ○​ Uses structural rules of a ​ Use Case Diagram normal programming ​ Sequence Diagram language, but professionals ​ Activity Diagram use it for human 4.​ Use Case Diagrams interpretation instead of ○​ Visual representation of machine interpretation. system functionality from the user’s perspective, Database Design in Systems Analysis highlighting how users 1.​ Conceptual design (actors) interact with the 2.​ Logical design system. 3.​ Physical design 5.​ Activity Diagrams ○​ Visualize workflows and System Security and Controls business processes, 1.​ Authentication showcasing the sequence ○​ Definition: Process of of activities, decision verifying the identity of a points, and flow of control user or system before within a system. granting access to 6.​ Data dictionaries resources ○​ A structured receptacle for ○​ Methods: data elements in a system. ​ Password-based It stores descriptions of all ​ Biometric-based data elements in data flow ​ Two-Factor diagrams. These data Authentication (2FA) elements may include ​ Token-based processes, details and 2.​ Authorization definitions of data flows, ○​ Definition: The process of data stores and data within granting users access those data stores. rights based on their 7.​ Decision trees identity and role within the ○​ Assist businesses with system. defining complex ○​ Implementation: relationships and decisions ​ Role-Based Access in an organized diagram. It Control (RBAC) illustrates the relationship ​ Attribute-Based of each condition to its Access Control action, which allows (ABAC) analysts to consider ​ Policy-Based decision sequences and Access Control identify the best one. 3.​ Encryption 8.​ Decision tables ○​ Definition: Protecting data ○​ Improves the general confidentiality understanding of a complex ○​ Types: logical relationship by  ​ Symmetric ○​ Adheres to legal Encryption frameworks like data ​ Asymmetric protection and privacy laws. Encryption ○​ Avoids legal repercussions 4.​ Auditing and upholds organizational ○​ Definition: Tracking reputation. system activities and 3.​ Stakeholder Interests and changes Impact ○​ Features: ○​ Balances competing ​ Log Management interests among end-users, ​ Intrusion Detection management, and teams. ​ Audit Trails ○​ Promotes fairness, 5.​ Disaster recovery transparency, and ○​ Definition: Planning for accountability. system restoration after 4.​ Consequences and Unintended catastrophic events Effects ○​ Components: ○​ Considers broader impacts ​ Backup Systems on society, individuals, and ​ Recovery Plans the environment. ​ Redundancy ○​ Mitigates risks like 6.​ Compliance algorithmic biases and job ○​ Definition: Adhering to displacement. relevant laws and 5.​ Professional Integrity and regulations (e.g., GDPR, Reputation HIPAA) ○​ Upholds high ethical ○​ Examples of Regulations: standards and ​ GDPR (General professionalism. Data Protection ○​ Builds trust and fosters Regulation) long-term relationships in ​ HIPAA (Health the industry. Insurance Portability and Accountability Emerging Trends in Systems Analysis Act) and Design ​ PCI DSS (Payment 1.​ Cloud computing Card Industry Data ○​ Shift towards cloud-based Security Standard) systems and services ○​ Implications in Systems Ethical Considerations in Systems Analysis and Design: Analysis and Design ​ Scalability 1.​ User Trust and Privacy ​ Cost Efficiency ○​ Ensures sensitive user data ​ Collaboration is protected. 2.​ Internet of Things (IoT) ○​ Builds trust by preventing ○​ Integration of physical unauthorized access and devices with information misuse. systems 2.​ Compliance with Laws and ○​ Implications in Systems Regulations Analysis and Design ​ Data Integration  ​ Automation TOPIC 3 |​ Structured Analysis ​ User Interfaces Methodology 3.​ Artificial Intelligence and Machine Learning STRUCTURED ANALYSIS ○​ Enhancing system ​ It utilizes graphical diagrams to capabilities and develop and portray systems decision-making specifications ○​ Implications in Systems Analysis and Design STRUCTURED ANALYSIS ATTRIBUTES ​ Enhanced 1.​ GRAPHICAL (visual Decision-Making representation) ​ Personalization 2.​ HIERARCHICAL (top-down ​ Automation of approach) Repetitive Tasks 3.​ LOGICAL (visual representation) 4.​ Big Data 4.​ MODULAR (self-contained ○​ Analyzing large volumes of modules) structured and unstructured data STRUCTURED ANALYSIS BENEFITS ○​ Implications in Systems ​ Improved communication Analysis and Design ​ Early identification of issues ​ Data Storage and ​ Reduced development time Processing ​ Enhanced system design ​ Real-Time Analytics ​ Data Visualization STRUCTURED ANALYSIS TOOLS 5.​ Mobile-first design 1.​ DATA FLOW DIAGRAM ○​ Prioritizing mobile device ○​ Definition: Also known as compatibility in system the "bubble chart", DFD is a development technique developed by ○​ Implications in Systems Larry Constantine to Analysis and Design express the requirements ​ Responsive Design of a system in a graphical ​ User Experience form. (UX) ○​ Elements of Data Flow ​ Cross-Platform Diagram Compatibility ○​ Level in Data Flow Diagram ​ Level 0 - Context Diagram ​ Definition: provides an  overview of the entire system ○​ Two Attributes of Data ​ Level 1 - Process Dictionary Decomposition ​ Active ​ Definition: ​ Definition: provides a automaticall more y updates detailed view when of the changes are system made to a ​ Level 2 - Deeper database's Dives data ​ Definition: ​ Passive breaks down ​ Definition: the typically sub-process used for es identified reference in the level 1 purposes, DFD such as in ​ Level 3 - analytics Increasing projects Complexity ​ Definition: 3.​ DECISION TREES most ○​ Definition: A decision tree detailed is a diagram that shows level of DFD alternative actions and conditions within horizontal 2.​ DATA DICTIONARY tree framework. It depict ○​ Definition: A structured the relationship of each repository of data elements condition and their in the system wherein, permissible actions. plays an important role in building a database. 4.​ DECISION TABLES ○​ Definition: Presented as a matrix, decision tables ○​ Three classes of data consist of rows and dictionary columns that are utilized to ​ Data Elements describe complex logical ​ Data Structure relationships in a precise ​ Data Flows and and easily understandable Data Stores manner.  5.​ Evaluating alternatives 6.​ Selecting the best design 5.​ STRUCTURED ENGLISH 7.​ Creating a structure ○​ Definition: Structured specification English is a simplified procedural language that STRUCTURED ANALYSIS PROCESS uses natural language and (Techniques from the 3 Orthogonal Views) logic to describe processes. 1.​ FUNCTIONAL VIEW ○​ Definition: define the work that has been done and the flow of data between things done 6.​ PSEUDOCODE ○​ Definition: Pseudocode is a plain-English representation of programming logic that 2.​ DATA VIEW does not conform to any ○​ Definition: comprises the specific programming entity relationship diagram language. Pseudocode serves as an alternative to flowcharts, providing a clear and concise way to outline a program’s structure and logic. 3.​ DYNAMIC VIEW ○​ Definition: state transition diagrams and defines when things happen and the conditions under which they may happen. STRUCTURED ANALYSIS PROCESS ​ MAJOR STEPS 1.​ Studying the current business environment 2.​ Modeling the old logical system 3.​ Modeling a new logical system 4.​ Modeling a new physical environment  ​ Digital Pens ​ Optical Character DATA MODELLING Recognition/Reader ​ Definition: The process of ​ Web Camera creating a visual representation of ​ Magnetic Ink an organization's data, including Character what data is collected, how it's Recognition related, and how it' it is stored and ○​ Objectives analyzed ​ To design data entry ​ Benefits and input ○​ Simplifies the data procedures ○​ Reduce redundancy ​ To reduce input ○​ Improving data integrity volume ○​ Enables data sharing ​ To design source ○​ Improves business reports documents for data ​ Data Modelling has: capture or devise ○​ Physical Data Model other data capture ​ Definition: A methods physical data model ​ To design input data specifies how the records, data entry data model will be screens, user built in the interface screens, database. etc. ○​ LOGICAL DATA MODEL ​ To use validation ​ Definition: A data checks and develop model that provides effective input a detailed, controls structured ​ Output description of data ○​ Definition: Output design elements and the refers to the systematic connections approach of defining, between them. formatting, and delivering information generated by a Input and Output Design system to its users. The ​ INPUT primary goal is to ensure ○​ Definition: Input design is the output is effective, the process of converting meaningful, and tailored to raw data from the users the user's needs. into computer-based ○​ Examples format. It acts as the ​ Visual Output connector between the Devices information system and the ​ Audio Output user. Devices ○​ Examples ​ Physical Output ​ Keyboard and Devices Mouse ​ Data Transmission ​ Punch Cards Output Devices ​ Barcode Scanner  ​ Touch/Interactive focuses on the design of Output Devices system architecture and ​ Projection and sees the total look of the Lighting Devices system as it unveils the ​ Specialized Output aims and uppermost layout Devices of the system. ○​ Objectives ○​ Key Focus: ​ Provide Accurate ​ Structure and Reliable ​ Behavior Information ​ Detailed Design ​ Meet User ○​ Definition: process of Requirements further breaking down each ​ Facilitate system module into Decision-Making detailed specifications. ​ Enhance Usability ○​ Key Focus: and Accessibility ​ Defining Functions ​ Support Multiple ​ Data Structure Formats ​ Interdependencies ​ Conceptual Data Modelling TYPES OF SYSTEM DESIGN Design ​ Logical Design ○​ Definition: helps system ○​ Definition: mainly analysts understand the concerned with developing organization’s data a model of the structure from an abstract requirements of the point of view. This type of system’s users in a form modeling helps to that is easy to understand. guarantee that the system ○​ Key Elements: will answer both existing ​ Inputs and future requirements for ​ Outputs data. ​ Data Stores ​ Entity Relationship Model ​ Data Flow ○​ Definition: the perspective ​ Physical Design of looking at the E-R model ○​ Definition: concerned with is in relation to how the the technical aspect, it various entities (real-world focuses on the tangible items) interconnect within equipment, the programs, the system. network facilities, and other ○​ Key Elements: physical components of ​ Entity system integration. ​ Relationship ○​ Key Steps ​ Attributes ​ Specify ​ Plan APPLICATIONS OF STRUCTURE ​ Devise ANALYSIS METHODOLOGY IN ​ Update INDUSTRIAL ENGINEERING ​ Architectural Design (not included on their ppt) ○​ Definition: refers to high-level design that