CMSC 345: Software Engineering Principles and Techniques

Software Engineering Principles and Techniques covers the full software development life cycle — from initial concept through testing and maintenance.

What CMSC 345 covers

(Formerly CMIS 330.) Prerequisite: CMSC 115 (or CMIS 141). A study of software engineering from initial concept through design, development, testing, and maintenance of the product. Discussion covers software development life-cycle models. The goal is to analyze, customize, and document multiple processes to solve information technology problems.

Topics include configuration management, quality, validation and verification, security, human factors, and organizational structures.

Typical CMSC 345 assignments

Expect an assignment requiring you to apply a specific software development life-cycle model to a given IT problem, addressing configuration management or validation/verification.

Key topics in CMSC 345

• Software development life-cycle models
• Configuration management
• Validation and verification
• Security and human factors in software engineering

Writing tips for CMSC 345

Follow the assignment instructions and rubric line by line

UMGC assignments for CMSC 345 are graded against a specific rubric or grading criteria your instructor provides — every requirement has to be visibly addressed. Skipping a requirement because it seems minor is one of the most common reasons a strong submission loses points.

Working, tested code matters as much as the write-up

Computer Science courses like CMSC 345 usually grade both the code itself (does it compile, run, and produce correct output) and the accompanying documentation or design write-up. A well-written report attached to code that doesn't run will still lose significant points.

Document your design decisions, not just the final code

Strong CMSC submissions explain the reasoning behind design choices — why a particular data structure, algorithm, or architecture was chosen — not just the final implementation. Evaluators check whether you understand the tradeoffs, not just whether the code works.

Why students seek help with CMSC 345

Students sometimes describe a general software process without applying a specific, named life-cycle model to the given problem — the rubric typically wants that specific model applied, not a generic process description.

How GradeEssays helps with CMSC 345

Share your IT problem scenario and rubric, and your writer will build a response applying a specific, named software development life-cycle model.

Prerequisites and course context

CMSC 345 requires Introductory Programming (CMSC 115) or CMIS 141. It was formerly numbered CMIS 330, and is itself one accepted path to the CMSC 495 capstone (paired with CMSC 320). Note: students may receive credit for only one of CMIS 330, CMIS 388A, or CMSC 345.

Related courses