
Computer Science 301 · 3 credits · NCCRS
Software Engineering
Process models, agile, requirements, design, user interfaces, testing, reliability, estimation and distributed systems.
Home › Courses › Software Engineering vs Systems Analysis
Software Engineering (Computer Science 301) is about how software is built: process models, agile, requirements, design, testing, reliability, estimation and change control. System Analysis and Design (Computer Science 390) takes the analyst's side: studying a business, modeling requirements in UML, designing interfaces and databases, then testing and project management. Both cover agile, requirements and testing; NCCRS recommends System Analysis and Design at the upper division and Software Engineering at the lower.

Computer Science 301 · 3 credits · NCCRS
Process models, agile, requirements, design, user interfaces, testing, reliability, estimation and distributed systems.

Computer Science 390 · 3 credits · NCCRS
The analyst's role, agile, requirements and UML, interface and database design, testing, risk and project management.
From the syllabi: what only one course covers, and where they meet.
| Software Engineering | System Analysis and Design | |
|---|---|---|
| Course code | Computer Science 301 | Computer Science 390 |
| Chapters | 15 chapters | 9 chapters |
| Instructional hours | 59.5 hours | 44.5 hours |
| Point of view | The engineer building software | The analyst studying a business system |
| Testing | Testing methods; verification and validation | Integration testing, verification, types of testing |
| NCCRS level | Associate or lower division | Upper division |
| Prerequisites | None listed in either syllabus | |
| Final exam | 100 multiple-choice questions | |
Both are self-paced: quizzes and the assignment are open-book, the final is proctored, and 70 or higher passes.
Building software: Software Engineering. Analyzing business systems: System Analysis and Design.


Software Engineering looks at software from the builder's side: process models, agile, requirements, object-oriented and component design, testing, reliability, estimation and change control. System Analysis and Design looks from the analyst's side: understanding a business, modeling requirements in UML, designing interfaces and databases, and managing implementation and the project. They meet on agile, requirements, testing and project management.
Both cover software testing. System Analysis and Design has a chapter on implementation, testing and maintenance, with lessons on integration testing, verification against the requirements and the different types of software testing. Software Engineering teaches testing methods alongside rapid development and software evolution, and has a chapter on verification, validation and dependability.
NCCRS recommends System Analysis and Design for 3 semester hours in the upper division baccalaureate category, in Software Engineering, Informatics, Information Technology, MIS or Computer Science. Software Engineering is recommended for 3 semester hours in the associate or lower division category, in Computer Science or Information Technology. Neither syllabus lists a prerequisite.
Software Engineering: NCCRS recommends 3 semester hours, lower division, in Computer Science among other subjects. System Analysis and Design: NCCRS recommends 3 semester hours, upper division, in Software Engineering among other subjects.
Software Engineering: Computer Science or Information Technology. System Analysis and Design: Software Engineering, Informatics, Information Technology, MIS, or Computer Science. Your college decides which requirement each one fills.
Software Engineering is longer by its syllabus. Software Engineering: 15 chapters and 59.5 instructional hours. System Analysis and Design: 9 chapters and 44.5 instructional hours. Both are self-paced, so you finish as fast or as slow as you want.
No. Neither syllabus lists a prerequisite, so you can start with any of them.
Each ends with 100 multiple-choice questions; Software Engineering after 15 chapters, System Analysis and Design after 9.
No: neither is on the ACE list. Software Engineering has an NCCRS recommendation for 3 semester hours in Computer Science; System Analysis and Design has an NCCRS recommendation for 3 semester hours in Software Engineering. Not being on the ACE list never means not recommended for credit.
Introduction to Artificial Intelligence. In the “Software and AI” order on the Computer Science courses page, it follows System Analysis and Design. Your program may set its own order.
As soon as your dashboard shows Software Engineering at 100%. The last assignment takes about 48 hours to be checked, so leave about two days after you submit it, then request the transcript.
Yes, online: under light proctoring (no camera) if you already have 70% before it, otherwise under full proctoring. The quizzes and the assignment are open-book; the Software Engineering final is not.
ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Search your school in Find My College and ask your registrar which courses Computer Science 301 and 390 would count as. For the registrar: Software Engineering's NCCRS recommendation lists Computer Science and System Analysis and Design's NCCRS recommendation lists Software Engineering.
ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.



















Plus many more partner colleges and ACE and NCCRS cooperating colleges.
Find My College →ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
UPI Study facts are from our course catalog, syllabi and course rules.