ACM-SW study plan

Distinguish architectural styles (layered, client-server, pipe-and-filter, MVC) and match each to a stated quality attribute

Derive functional requirements and use cases from a written stakeholder scenario

Write non-functional requirements as measurable quality-attribute scenarios (stimulus, response, measure)

Sketch a component-and-connector view plus a module decomposition for one small system

Apply design principles (abstraction, information hiding, separation of concerns, coupling/cohesion) to critique a given module structure

Select and justify a design pattern for a stated problem, naming its trade-offs

Trace each requirement to at least one design element and flag untraceable ones

Identify requirement conflicts and write a resolution with rationale

Implement a small module from a written interface spec using defensive coding and clear naming

Write unit tests that achieve branch coverage on that module and justify chosen test inputs

Refactor a duplicated code block using extract-method and verify behavior is preserved via tests

Configure a static-analysis or lint pass and interpret its findings

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

Write integration tests for a multi-component flow and distinguish them from unit tests

Perform a code review against a checklist and classify defects by severity

Plan a regression suite for a described change and justify what is included or excluded

Classify maintenance types (corrective, adaptive, perfective, preventive) for a set of change requests

Execute a refactoring or bug-fix change while keeping the regression suite green

Set up version control branching and tag a release for the sample project

Write a change request and impact analysis for one modification

Build a work breakdown structure and estimate effort for a small project using at least two techniques

Identify project risks with likelihood/impact and specify a mitigation for each

Map a described process to a lifecycle model and justify the choice

Define process and product metrics that would detect a stated quality problem

Apply a software quality model to evaluate a described product against stated characteristics

Explain how process maturity or continuous improvement applies to a given team scenario

Resolve an ethics scenario using a professional code of ethics, naming the conflicting obligations

Distinguish professional responsibility, conflict of interest, and public-safety duties in a case

Complete a timed full-length practice set and score each domain separately

Re-study the two weakest domains using targeted drills until error rate drops

Rehearse explaining a design trade-off, a test strategy, and an ethics decision aloud

Consolidate a one-page formula and terminology sheet for rapid recall