• 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

Week 9 Presentation

March 18, 2021 1 Comment

5203_09_Software_Design

Reader Interactions

Comments

  1. Elias Harake says

    March 19, 2021 at 10:08 am

    In this week’s reading assignment, an interesting takeaway that I think is important to mention is about a system development methodology. According to the textbook, a systems development methodology is a structure that an organization uses to plan and control the development of information systems and software and new business applications. The textbook also mentions three different types of models that can be used for a system development methodology. These three models are known as Traditional waterfall, V-shaped, and Iterative. According to the book, the traditional SDLC (waterfall) model and variants of the model normally involve a life cycle verification approach that ensures that potential mistakes are corrected early and not solely during final acceptance testing. V-shaped models focus on the relationship between development phases and testing levels. V-Shape models are the most vague testing, the unit test and occurs immediately after programs have been written in code. And the iterative model is a cyclical process in which business requirements are developed and tested until the entire application is designed and tested to be launched. During each iteration, the development process goes through each phase, from requirements through testing, and each subsequent cycle incrementally improves the processes and efficiencies of the system.

    Reply

Leave a Reply to Elias Harake 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