Management Information Systems deck

SDLC typical order

Planning; requirements; design; build; test; deploy; maintain.

Requirements gathering methods

Interviews surveys observation document analysis workshops.

Feasibility study checks

Financial technical and organizational feasibility.

Verification

Confirm the system was built correctly to spec.

Validation

Confirm the right system was built for user needs.

Agile vs Waterfall

Agile is iterative; Waterfall is sequential.

Stakeholders

End users managers developers sponsors customers.

DFD purpose

Shows data moving between processes stores and external entities.

ERD purpose

Shows entities attributes and relationships for database design.

Class diagram purpose

Shows classes attributes methods and relationships in OOP.

Encapsulation

Hide internal state; expose behavior through methods.

Abstraction

Hide complexity; show essentials.

Inheritance

Subclass reuses and extends superclass behavior.

Polymorphism

Same interface; different implementations.

Class vs object

Class is blueprint; object is an instance.

Primary key in databases

Uniquely identifies a record.

Normalization goal

Reduce redundancy and improve data integrity.

Data redundancy risk

Duplicates cause inconsistency and update anomalies.

NoSQL databases

Non-relational stores like document key-value column graph.

OLAP used for

Analytics and business intelligence queries.

Scrum roles

Product Owner Scrum Master Developers.

Scrum artifacts

Product backlog sprint backlog increment.

Kanban purpose

Visualize workflow and limit work in progress.

Project life cycle

Initiate; plan; execute; monitor and control; close.

Scope creep

Uncontrolled growth of requirements over time.

IT infrastructure

Hardware software networks cloud and services.

OSI model purpose

Conceptual layers describing network communication.

Cloud models

SaaS; PaaS; IaaS.

Authentication vs authorization

Authentication verifies identity; authorization grants permissions.

Role-based access control

Permissions based on user roles.

Role play prep time

20 minutes preparation before presenting.

Role play presentation time

7 minutes interactive presentation with judges.

Role play allowed materials

Two note cards; no tech props or reference materials.

Role play must include

Problem definition; alternatives with pros and cons; recommendation; implementation plan.

Implementation plan elements

Timeline team roles training testing rollout controls metrics.