Study Guide Exam for MIS 3320 FINAL 2024/2025

Study Guide Exam for MIS 3320 FINAL 2024/2025 What is a system analyst? responsible for the analysis and design of information systems; translates a business problem into an information system solution; like an architect SDLC - what is it? Framework that identifies all the activities required to research, build, deploy, and often maintain an information system Predictive approach Requirements well understood and well defined, low technical risk, can be planned in advance, system can be developed according to the plan; Client knows what they want Adaptive approach Requirements and needs uncertain, high technical risk, iterative, must be flexible and adapt (spiral model and iterative development); Client does NOT know what they want Waterfall model One phase begins when another phase completes; specifications are frozen problems; system requirements locked in; limited user involvement Modified waterfall The modified waterfall allows for phases to overlap as well as the ability to go backwards; shortened the development time - faster Spiral model Iterative approach; spiral until project completed then deploy; client is able to see something sooner; multiple feasibility checkpoints Incremental development Iterative approach; system is built in small increments and partially deployed in certain steps; as integration is completed, it is integrated to the whole - some functionality gets into the user's hands much earlier Agile Development A guiding philosophy and set of guidelines for developing information systems in an unknown, rapidly changing environment Coupling Qualitative measure of how closely the classes in a design class diagram are linked; strive for low level Cohesion the consistency of the functions within a single class and is a qualitative measure of its focus or unity of purpose; strive for high level Methodologies comprehensive guideline to follow for completing every SDLC activity; describe everything the developer needs to produce Tools Software to create models or other project components (record info to write code) Techniques A collection of guidelines that specify a method for how to carry out a development activity or task (how team will do the work) Models Abstraction used to separate out aspect like diagrams (specify requirements) Main purpose of analysis Understand and specify what needs to be accomplished Main purpose of design defines and describes the system which solves the need Scrum objective to be quick, agile, and intense at to go the entire distance. Responsive to high changing dynamic environments (some projects never reach completion) What is a sprint? a time controlled mini-project that implements a specific portion of a system; scope cannot be changed; usually 2 weeks Scrum Master Scrum project manager - ensures the team follows the Scrum process (a process owner not a product owner); a facilitator; removes impediments; resolves issues Product Owner client stakeholder who controls the product backlog; prioritizes it Development Team responsible for building the increment; 5 to 9 members with cross-functional skills; self-organizing teams What happened with the Project Leader role? Scrums do not employ project managers because the development team is self organizing Product Backlog a prioritized list of user requirements used to choose work to be done in a Scrum project; i.e. user stories Sprint Backlog list of user stories committed to the current sprint; includes the tasks for each product backlog item (PBI) Increment potentially shippable product; product owner decides when to release Task Board for each user story in the sprint backlog; list and classify all tasks as: To Do, In Progress, or Done Sprint Burndown Chart shows the amount of work remaining in one sprint; each development member must report daily the effort remaining on each task Sprint Planning Meeting create the sprint backlog; 8 hours before the spring Daily Standup 15 minutes at the beginning of each day; Daily status update between the development team: Yesterday, Today, Barriers; Attended by: Scrum Master, Development Team, Product Owner Sprint Planning Meeting Part 1 Part I: Product Owner presents the desired set of User Stories & the acceptance criteria for each story; development team asks questions for clarity Sprint Planning Meeting Part 2 Part II: Development Team takes each story & breaks them into tasks; creates time estimates per task; finalizes the user stories they can commit to. Sprint Review/Demo inspect and adapt the product; new items are added to the product backlog Sprint Retrospective 3-hours at the end of the Sprint; process improvement - lessons learned, successes and failure; Attended by: Scrum Master, Development Team Backlog Grooming/Refinement to identify and clarify user stories for the next sprint User Stories describe the functionality being requested by the client User Story Format