• Log In
  • Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Sys & Infrast Lifecycle Mngt 1

Information Technology Audit and Cybersecurity, Temple University

Sys & Infrast Lifecycle Mngt 1

MIS 5203.001 ■ Spring 2021 ■ Wade Mackey
  • Home
  • Syllabus
    • Gradebook
  • Announcements
  • Course Work
    • 1 – Intro/SDLC
    • Planning
      • 2 – Prjct Mngmt & Governance
      • 3 – Business Case & Feasibility
    • Analysis
      • 4 – Requirements Determination
      • 5 – Process Modeling
      • 6 – Data Modeling
      • 7 -Test One
    • Design
      • 10 – HCI (UI)
      • 8 – Database
      • 9 – Software
      • 11 – Test Two
    • Implementation
      • 12 – Architecture
      • 13 – Development & Testing
      • 14 – Migration & Deployment
      • Test 3: Implementation
  • Projects
    • Project 1: Business Case Development
    • Project 2: SDLC
    • Project 3: Systems Design
    • Project 4: Process Re-engineering
    • Project 5: Controls

Unit 1 Reading – Mettus

January 28, 2021 Leave a Comment

It’s easy to think of the Systems Development Lifecycle as a circular, sequential series of steps that repeats. That’s what I would think of when I first saw any graphics or pictures representing the SDLC. One thing I took away from Chapter 1 of Modern Systems Analysis and Design is that that isn’t really the case. As the book states, “the specific steps and their sequence are meant to be adapted as required for a project, consistent with management approaches.” At any point you can go back to the previous phase. Or activities from different phases can be completed at the same time. I thought the figure that shows a spiral, representing how a project keeps going back into each phase in increasing levels of detail was a better representation than just a circle. I wonder if this makes for a more adaptable project than a structured approach going through the phases in order. I also think it’s important to note that each phase (Planning, Analysis, Design, Implementation, and Maintainance) has deliverables and milestones. It’s not just about delivering a final product at the end of implementation. 

Reader Interactions

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Primary Sidebar

RECENT ANNOUNCEMENTS

Week 14 Implementation Plan Risks – Prince Patel

What Are the Risks of an Implementation Plan? As is the case with any … [More...] about Week 14 Implementation Plan Risks – Prince Patel

Week 13 Smoke Testing- Prince Patel

Smoke Testing Smoke testing is performed on the ‘new’ build given by … [More...] about Week 13 Smoke Testing- Prince Patel

Week 12 (FaaS) Function as a Service! – Prince Patel

You all must have heard IaaS, PaaS & SaaS. But let me introduce you to … [More...] about Week 12 (FaaS) Function as a Service! – Prince Patel

Week 10 What is Guerrilla Usability Testing? – Prince Patel

Guerrilla testing In guerrilla testing, test subjects are chosen … [More...] about Week 10 What is Guerrilla Usability Testing? – Prince Patel

Week 9 Dev-ops Software Development Methodology – Prince Patel

DevOps development methodology DevOps is not just a development … [More...] about Week 9 Dev-ops Software Development Methodology – Prince Patel

Week 8 Database Design Steps – Prince Patel

How to Design Database: Steps of Designing Database Database designing … [More...] about Week 8 Database Design Steps – Prince Patel

[More Announcements...]

Copyright © 2025 · Department of Management Information Systems · Fox School of Business · Temple University