Welcome to the comprehensive study guide for Arizona State University’s CSE 360: Introduction to Software Engineering. This foundational course is a critical milestone for Computer Science and Software Engineering majors at ASU. Exam 1 is the first major assessment, designed to test your grasp of the fundamental principles that govern how complex software systems are built, managed, and maintained.

This course moves beyond simple programming and introduces the rigorous processes required in professional software development. Whether you are taking this course in person at the Tempe campus or online through ASU Online, this exam evaluates your ability to think like a software engineer from day one. Mastering these initial concepts is essential not only for passing this course but for succeeding in all subsequent upper-division software classes and in your future career.

What the Course Entails and Exam Details

CSE 360 establishes the vocabulary, methodologies, and lifecycle concepts used in the industry. Exam 1 typically covers approximately the first three to four weeks of the semester, focusing on the "why" and "how" of software engineering.

To succeed on Exam 1, you must have a solid command of the following core topics covered in lectures and the required textbook (often Object-Oriented Software Engineering: Using UML, Patterns, and Java by Bernd Bruegge and Allen H. Dutoit, or similar ASU-selected materials):

• The Software Life Cycle (SDLC): You need to know the various models, including Waterfall, Spiral, and Agile methodologies. Be prepared to compare and contrast them, understanding the advantages and disadvantages of each and when they are appropriately applied in industry projects.
• Requirements Engineering: This is a crucial topic. You must understand the difference between functional and non-functional requirements. You will be tested on how to elicit, analyze, and document these requirements clearly using techniques like FURPS+ (Functionality, Usability, Reliability, Performance, Supportability).
• UML Modeling Fundamentals: Exam 1 almost certainly involves Unified Modeling Language (UML). You must be fluent in creating and interpreting basic class diagrams (showing classes, attributes, methods, and relationships like association, inheritance, and composition) and use case diagrams (showing actors, use cases, and system boundaries).
• The Software Process: Understanding the maturity of software processes, often introduced via frameworks like CMMI (Capability Maturity Model Integration), is frequently included.
• Professional Ethics: Software engineers operate under a code of ethics. You should be familiar with the ACM/IEEE Software Engineering Code of Ethics and be able to apply it to hypothetical scenarios.

What to Expect in the Final Exam

The specific format of Exam 1 (e.g., multiple choice, short answer, diagrams) is determined by your specific instructor (e.g., Prof. J. Chen, Prof. H. Davulcu, etc.). However, across all sections, Exam 1 is designed to be rigorous and comprehensive.

• Exam Format: The exam is typically a mix of question types. Expect multiple-choice questions testing definitions and concepts, scenario-based questions where you must choose the best methodology or ethical path, and drawing or analysis questions where you must create or interpret basic UML diagrams.
• Time Limit: For in-person students, this is usually a standard 50-minute or 75-minute class period. For ASU Online students, the exam is typically administered via a secure online proctoring service (like Honorlock or Respondus Monitor) and may have a slightly longer time window, often around 60 to 90 minutes.
• Passing Score: The passing score is determined by the course syllabus and standard ASU grading policies. A "C" or better is typically required to advance in the major. You should aim for a high score on Exam 1, as it sets the foundation for your grade in this demanding course.
• Materials: This is almost always a closed-book, closed-notes exam unless your instructor specifies otherwise.

 How to Study and Exam Centers

Success on CSE 360 Exam 1 requires active studying, not just passive reading.

• Master the Terminology: The biggest hurdle for many students is the sheer volume of new vocabulary. Create flashcards for every definition (e.g., "User Story," "Association," "Coupling," "Cohesion," "SRS").
• Practice UML Diagramming: Do not just look at UML diagrams in the book; draw them. Take a simple system (like a library system or an ATM) and sketch out the class diagram and a use case diagram from scratch. Your diagrams must use correct notation (arrows, multiplicity, etc.).
• Review Lecture Slides and Recitation Materials: ASU instructors often pull key concepts and examples directly from their lecture decks and recitation worksheets. These are highly targeted study guides.
• Form Study Groups: Explaining concepts like Agile vs. Waterfall to a peer is one of the best ways to solidify your own understanding and identify gaps in your knowledge.
• Take Advantage of Office Hours: If you are confused about a UML relationship or the difference between verification and validation, go to your professor’s or TA's office hours immediately.
• Where and How to Take the Exam:
• In-Person Students: You will take the exam in your regularly scheduled classroom or a designated alternate testing location on the ASU Tempe, Polytechnic, or West campus, as proctored by your instructor and TAs.
• ASU Online Students: You will take the exam remotely using an online proctoring service (such as Honorlock or Respondus Monitor). You are required to have a functioning webcam, microphone, and a stable internet connection, and you must perform a mandatory environment scan before beginning the test. Details will be provided in your Canvas course shell.

 Job Opportunities from the Course

CSE 360 is not just an academic hurdle; it provides the foundational knowledge required for highly sought-after roles in the tech industry. Understanding these core engineering principles is essential for landing internships and full-time positions.

This course unlocks career paths such as:

• Software Engineer: Responsible for the full life cycle of software development.
• Software Developer: Focuses on building and coding applications based on defined requirements.
• Systems Analyst: Works to analyze and improve complex business systems, often focusing on requirements and process modeling.
• Quality Assurance (QA) Engineer: Ensures the software meets specified quality standards and requirements (V&V).
• Technical Project Manager: Uses SDLC knowledge to plan, initiate, and manage software projects.
• UI/UX Designer: Understands user requirements and translates them into effective system designs.
• IT Consultant: Advises organizations on how to use information technology to meet their business objectives.