Industrial Engineer Information Processing study plan

Diagram the software development life cycle phases (requirements, design, implementation, testing, maintenance) and label the artifacts each phase produces

Compare waterfall, prototype, spiral, and iterative development models by listing two trade-offs for each

Write one-paragraph definitions, from memory, for modularization, cohesion, coupling, abstraction, and information hiding

Classify ten sample design situations as high or low cohesion and coupling and justify each label in one sentence

Sketch UML use case, class, sequence, and state diagrams for a small library-loan scenario and label every relationship type

Distinguish structured analysis and object-oriented analysis by listing the core models each produces

Explain the purpose of design patterns and describe three creational, three structural, and three behavioral patterns

Apply the MVC architecture to a described screen-based application and map each component to its responsibility

Trace a short program's control flow through sequence, selection, and iteration constructs and predict its output before running it

Write and execute small programs using arrays, records, and parameter passing by value and by reference

Compare procedural, object-oriented, and event-driven programming paradigms with two distinguishing features each

Explain compilation, interpretation, and linking stages and the role of the loader

Define test levels (unit, integration, system, acceptance) and match each to its entry and exit criteria

Design black-box test cases using equivalence partitioning and boundary value analysis for a stated input rule

Write white-box test cases achieving statement and branch coverage for a small function and calculate each coverage percentage

Classify maintenance types (corrective, adaptive, perfective, preventive) across eight change requests

Build an entity-relationship diagram for a described business rule set, resolving one many-to-many relationship into associative entities

Convert the ER diagram into normalized relations in third normal form and state why each step removes a dependency anomaly

Write SQL statements for data definition, single and multi-table queries, joins, grouping, and subqueries

Explain transactions, ACID properties, and the isolation levels with one anomaly each prevents

Distinguish conceptual, logical, and physical database design and list the decisions made at each level

Explain indexing, primary and foreign keys, and views, and choose an index for two stated query patterns

Describe system architecture tiers (client-server, three-tier) and where each database component sits

Outline capacity planning inputs: transaction volume, storage growth, and response-time targets

Map the implementation lifecycle from installation and data migration through cutover and acceptance

Write a rollback and data-migration checklist for a described system replacement

Explain backup types (full, incremental, differential) and design a recovery procedure meeting a stated recovery point and recovery time objective

Interpret availability, reliability, and response-time metrics and compute each from a small sample log

Summarize IT service management concepts: service level agreements, incident versus problem management, and change control

Explain the CIA triad and select appropriate controls for confidentiality, integrity, and availability scenarios

Identify common threats (malware, phishing, SQL injection, denial of service) and the countermeasure for each

Take two timed mixed-domain practice sets and log every missed item by domain

Re-review the three weakest logged items per domain using your own notes