Test 1 FINAL Past Paper

***EXAM 1*** ***Chapter 1:*** ***Define information systems analysis and design*** ***1.2 Describe the information systems development life cycle*** ***(SDLC)*** ***1.3 Describe the agile methodologies, eXtreme, Programming, and Scrum*** ***1.4 Explain object-oriented analysis and design and t...

***EXAM 1*** ***Chapter 1:*** ***Define information systems analysis and design*** ***1.2 Describe the information systems development life cycle*** ***(SDLC)*** ***1.3 Describe the agile methodologies, eXtreme, Programming, and Scrum*** ***1.4 Explain object-oriented analysis and design and the*** ***Rational Unified Process (RUP)*** The distinction between system software and application software often comes down to their roles and how close they are to the hardware. ### **System Software (Lower Level)** - - - - ### **Application Software (Higher Level)** - - - - In a nutshell; system software acts as a bridge between the hardware and application software, which is why it's considered lower level. Application software sits on top of this layer, making it a higher level as it relies on the system software to function. ### ### ### **Systems Development Methodology** - - ### **Systems Development Life Cycle (SDLC)** - - 1. 2. 3. 4. 5. 6. 7. How to remember it: Pandas Always Dance In March" Here's how it breaks down: - - - - - The **Planning** phase of the Information Systems Development Life Cycle (SDLC) is crucial as it sets the foundation for the entire project. Here's a breakdown of what happens during this phase: 1. 2. 3. 4. 5. The **analysis phase** ensures that all stakeholders have a clear understanding of the project's goals and requirements before moving forward the analysis phase of the SDLC is all about understanding and detailing the system requirements. Here's a closer look at what happens during this phase: 1. 2. 3. This phase ensures that the new system will meet user needs and improve upon or replace existing systems effectively. The **Design phase** of the SDLC involves transforming the analysis into detailed specifications for the new system. Here's a breakdown of this phase: 1. 2. - - 3. - - This phase ensures that the system's design is both comprehensive and feasible, setting the stage for the next phase: Implementation ### **Implementation** - - ### **Maintenance** - - **Analysis-Deisgn Code Test Loop:** Traditional Practice- The Analysis-Design-Code-Test Loop is more aligned with the Waterfall approach, where each phase is distinct and follows a set order. **Water Fall: Sequential Process**: The Waterfall model follows a linear and sequential approach. Each phase (Planning, Analysis, Design, Implementation, Maintenance) must be completed before moving on to the next. - Planning, Analysis, logical, physical, Implementation, and Maintainence. **Agile methodology**: **Iterative and Incremental**: Agile breaks the project into small, manageable units called iterations or sprints. Each iteration includes elements of planning, analysis, design, coding, and testing. ***Agile Manifesto:*** - - - - - - - - - - - - - - If your project involves... -unpredictable or dynamic requirements -responsible and motivated developers -customers who understand the process more Your project might be a better fit with agile. NOT EVERY PROJECT IS FIT FOR AGILE. ***Chapter 2:*** ***Learning Objectives:*** ***2.1 Explain Outsourcing*** ***2.2 Describe six different sources of software*** ***2.3 Discuss how to evaluate off-the-shelf software*** ***2.4 Explain reuse and it's role in software development*** Introduction: In the past, organizations primarily developed software internally and from the ground up. Nowadays, there are numerous sources for software. The current focus is on identifying and acquiring various pieces and components to assemble the application you need to create. **Outsourcing** involves delegating some or all responsibilities for an organization's information systems applications and operations to an external company. Reasons for outsourcing include: - - - - - Negatives: -Global Communities: Outsourcing can lead to challenges in managing a global workforce. Differences in time zones, cultural norms, and communication styles can create misunderstandings and inefficiencies1. 1. 2. 3. 4. 5. Sources of software can be categorized into six major groups: 1. 2. 3. Pro: less maintenance and is more consistent and holds more accurate data 1. Pros: faster access to applications, frees internal staff, and lower cost to corporations. Cons: security reasons and reliability 1. Two ways to make money: provides maintenance and service, and release a premium version. 1. Pros: full control, customizations, immediate availability Cons: Labor costs, limited expertise In contrast of In-House Development, you have off-the-shelf.. **Off- the-Shelf:** Off-the-shelf software refers to pre-packaged software solutions that are readily available for purchase and use by the general public. These solutions are designed to cater to a wide range of users and typically require minimal customization. **How does one decide? It is based on cost, functionality, and vendor support.** Cost: (you compare the difference between in house cost and off the shelf) Functionality: the tasks that can be performed by users that are essential to the company Vendor Support: how much can a vendor support and provide Also if you were to pick in house development, ask yourself.. How flexible do I want it to be? Do I want it to have a rigid structure, or should I allow more customization? You also need to document everything so it can help your employees navigate the software and so that it can assist your IT with installing, configuration, and troubleshooting. Chapter 3: 3.1 Explain the process of managing an information systems project, including project initiation, project planning, project, execution, and project closedown 3.2 Describe how to represent and schedule project plans using Gantt charts and network diagrams 3.3 Explain how commercial project management software packages can be used to assist in representing and managing project schedules Introduction: Project management is the most important aspect of an information systems development project. Effective Project Manager = meet customer's expectations and completed on time and budget Simple Vocab: **Project Manager:** systems analyst with an abundant skill set in management, leadership, technical, conflict, management, and customer relationships. They are responsible for initiating, planning, executive, and closing down a project. **Project:** planned undertaking of related activities to reach an objective with a beginning and an end. **Feasibility Study:** a study that determines whether a requested system makes economic and operational sense for an organization. - - - - **Phases of PM:** **-Initating** **-Planning (Think back SDLC: analysis, design)** **-Executing (Development, testing, implementation)** **-Closing** **Agile / Project Manager** **Understand\*\*\*** **The schedule must be flexible due to changes (unlike waterfall that is structured)** Quality is assessed both after each iteration (scrum/XP extreme) or through continuous methodologies such as Kanban. These methodologies have emerged in response to increasingly complex requirements and uncertain technological environments. Here are some key points about these approaches: 1. - - - - 2. - - - 3. - - - 4. - - - Both incremental development and the concept of a walking skeleton are related to agile methodologies. 1\. Incremental Development and Agile: - - - - 1. - - - - What Is Agile Methodology? (A Beginner\'s Guide) \[2024\] Asana - - - - Agile Job Positions : The team (Developers, Scrum, Agile team), Scrum Master, PM (hybrid positions), Product owner, and Product Manager Scrum Master: - - - - - **Scrum Master- related vocab:** Product Backlog: a prioritized list of requirements Product Owner: the client stakeholder who controls the the product backlog Scrum Master: facilitator of scrum projects Scrum Sprint: centers around velocity (incremental delivery) , timebox (fixed time iternation), and ability to get the product into the market.  Project Manager: - - - - Agile Stakeholders- Product Owners - - - - - - - Product Manager -A product manager in IT projects defines the product vision, prioritizes features, and collaborates with cross-functional teams to ensure the product meets customer needs and business goals. (product success) Extreme Programming (XP): ONLY FOR SOFTWARE PROJECTS Takes the best practices of software development and extends them "to the extreme" Focus intensely on proven industry practices Combine them in unique ways to get better results XP Practices: Planning -- based on user stories Testing -- thorough testing at every step Pair Programming -- watch, inspect, trade off Simple Designs -- Agile modeling principles Refactoring -- remove redundancy and eliminate unused functionality Owning the code collectively -- egoless development, anyone can review and improve code Continuous integration -- grow the software continuously On-site customer -- get sign-off as you go System metaphor -- what should the final system look like Small releases (like scrum sprints) -- turn over touser frequently Forty-hour work week -- don't overload the developers Coding standards -- follow standards for code **Kanban Approach** The Kanban approach is a popular Agile methodology used to manage and improve work processes. Kanban focuses on visualizing work, limiting work in progress (WIP), and enhancing flow efficiency. In Kanban, tasks are represented as cards on a Kanban board, which is divided into columns that represent different stages of the workflow. The key principles of Kanban include: - - ***Differences between a Scrum Master and a Kaban leader*** ### **Kanban Leader** - - - - - - ### **Scrum Master** - - - - - **Agile Scheduling:** Agile projects often use product roadmaps to plan their work. These roadmaps list feature requests and include details like priority, status, and recent updates. Some tools also show requirements and milestones for each feature. Companies usually have a public roadmap that provides a high-level overview. \*\*\*Discussed in- class **Internal Product Roadmap**: is a detailed plan used within a company to guide the development of a product. It includes specific feature requests, priorities, statuses, and recent updates. This roadmap helps the development team stay on track and ensures everyone is aligned on the project's goals and progress. **External Product Roadmap:**on the other hand, is a high-level overview shared with customers and stakeholders. It highlights the major features and milestones planned for the product, giving an idea of what to expect in the future. This roadmap helps manage customer expectations and keeps them informed about the product's direction. A release schedule is more detailed than a product roadmap. It outlines the specific releases needed to launch a **new product**. Note that this schedule is for new product launches, not for maintaining or fixing issues in products that are already live. **MVP AND MFF** **Minimum Viable Product (MVP)**: This is the earliest version of a product that allows you to learn the most from customers with the least effort. The goal is to find out if you're building the right thing and what value it might provide. Examples include prototypes or basic apps that help you understand the "what" and "how" of your product. **Minimum Marketable Feature (MMF)**: This is a version of the product that delivers actual value to customers. It aligns with the Agile principle of continuously delivering value through software. It's important to note that MVP is often mistakenly defined as what MMF provides. The key difference is that MVP is about learning, while MMF is about delivering value. **Hybrid Projects:** Some companies claim to use Agile, but they often use a mix of Agile and Waterfall methods, known as a hybrid approach. This hybrid method combines elements of both to manage projects. Project and technical leaders should choose the best methodology to ensure the success of a product or project. A hybrid approach is common during the transition to Agile because it offers a more gradual change. However, if a company is committed to moving to Agile but sticks with hybrid methods, they might become complacent, and the hybrid approach could become the new norm. Ultimately, a company should follow its strategic vision to decide on the best approach. **Chapter 4:** **4.1 Describe the project identification and selection process** **4.2 Describe the corporate strategic planning and** **information systems planning process** **4.3 Describe the three classes of Internet electronic commerce applications: business-to-consumer, business-to-employee, and business-to-business** 1. - - - 2. - - 3. - - - - **Project Identification and Selection Process** 1. - 2. - 3. - - **[Why are projects needed?]** ### ### ### **System Vision Document** #### **Problem Description** - - - #### **System Capabilities** - - - #### **Business Benefits** - - - - ### ### **\*\*Characteristics of Alternative Methods for Making Information Systems Identification and Selection Decisions** **Possible Evaluation Criteria When Classifying and Ranking Projects**  ### - ### Mission statement -- statement that makes it clear what ### business a company is in. - ### Objective statement -- series of statements that express ### an organization's qualitative and quantitative goals for ### reaching a desired future position **Identifying potential development projects** ▪ By key member of top management ▪ By steering committee (top-down source) ▪ By user departments (bottom-up source) ▪ By development group or senior IS manager \*\*\* I have no idea if this will be on the exam **\*\*\*Competitive Strategy: method in which an organization attempts to achieve it's mission and objectives.** **\*\*\*Three strategies:** 1. 2. 3. **\*\*\*Generic Competitive Strategies** **Information systems planning (ISP) -- orderly means of assessing the information needs of an organization and defining new systems, databases, and technologies that will best satisfy those needs** **Top-down planning** -- generic methodology that attempts to gain a broad understanding of the information systems needs of the entire organization Advantages: -- Broader perspective -- Improved integration -- Improved management support -- Better understanding ** Bottom-up planning** -- generic information systems planning methodology that identifies and defines IS development projects based upon solving operational business problems or taking advantage of some business opportunities. Top-Down Planning Advantages  **\*\*\***