45 courses with the subject SWENG, each shown exactly as we captured it from the college's catalog, with every element we hold. Where the wording looks broken, that is our reading of the catalog, not the college's text.
Supporting Courses and Related Areas Supporting Courses and Related Areas: Require a grade of C or better Select 6 credits of 400-level (below 490) CMPSC courses 6 CMPSC 121 and MATH 140 are prerequisites for CMPSC 122.
/Maximum of 18 Supervised off-campus, nongroup instruction including field experiences, practica, or internships. Written and oral critique of activity required. Enforced Prerequisite at Enrollment: Prior approval of proposed assignment by instructor
/Maximum of 18 Creative projects, including research and design, that are supervised on an individual basis and that fall outside the scope of formal courses.
/Maximum of 9 Formal courses given infrequently to explore, in depth, a comparatively narrow subject that may be topical or of special interest.
/Maximum of 12 Courses offered in foreign countries by individual or group instruction.
Provides an introduction to the principles of software engineering and includes complementary instruction in one programming language. Enforced Prerequisite at Enrollment: Senior standing or above
Software engineering principles including life cycle, dependability, process modeling, project management, requires specification, design analysis, implementation, testing, and maintenance. SWENG 411 Software Engineering (3) This is an introductory course in software engineering, addressing the software development process, including aspects such as software requirements documentation, design specification, implementation, system integration, testing, and maintenance by individuals and teams. Topics include software process modeling, requirements elicitation and documentation, software architecture design and analysis, detailed design and programming, graphical user interface (GUI's) design and prototyping, software quality Undergraduate - The Pennsylvania State University 2026-2027 4865 assessment, software testing, software maintenance and evolution management, personal and team-based development. In lab students gain practical experience by completing programming assignments and utilizing computer-aided software engineering (CASE) tools for their personal projects tailored to each stage of the software life cycle. A semester long team-based project is required that reinforces teamwork fundamentals and the concepts covered in lecture. The projects and assignments provide an opportunity for student teamwork, document writing, and oral presentations. Enforced Prerequisite at Enrollment: CMPSC 122 and Concurrent: SWENG 311
The analysis and design of software systems using canonical design patterns. SWENG 421 Software Architecture (3)This course introduces the frequently-used software infrastructures in software development by experienced engineers. The formal UML notations are utilized to design software architecture and help communicate the design visually. Students will learn the real practice of architectural styles, design patterns and design reuse. As to certain complex problems, alternative architectures will be proposed and their design trade offs will be evaluated. For instance, students compare two-tier with three-tier client/server architectures for distributed systems, and employ multi- process and multi-thread concurrent architectures for high performance computation systems. Moreover, students learn to conduct high level quality analysis from the design artifacts. The quality evaluation will focus on a number of attributes, including reusability, extendibility and performance. A great deal of effort is placed on the major categories of design types containing dozens of separate design patterns. Students first review the most fundamental design patterns. Afterwards, they apply creational patterns to effectively create objects, partitioning patterns to categorize objects, structural patterns to allocate objects, behavioral patterns to interface the communication between objects, and concurrent patterns to handle tasks simultaneously. These skills will enable students to extend their own knowledge after graduation by giving them the skills to learn new patters on their own. Finally, students will integrate their programs with native code applications to enlarge the application domains. To achieve best reusability, they also learn modular designs to develop component-based software. These help them meet today's software needs of cross applications and architectures. Enforced Prerequisite at Enrollment: SWENG 411
Introduction to methods of software verification, validation, and testing; mathematical foundations of testing, reliability models; statistical testing. SWENG 431 Software Verification, Validation, and Testing (3) Provides a background necessary for verification, validation, and testing of software systems. Verification addresses the question: 'are we building the product right?' In other words, does the product meet the engineering specifications? Validation addresses whether the right product is being built and if it meets the design requirements. The testing aspect of the course addresses many of the methods available to test software systems. The levels of testing explored are 1) unit level (each module is tested independently), 2) integration testing (where the modules are integrated together and tested as a complete system), and 3) acceptance testing (the testing requirements of the users). Following this, specific
The design and implementation of real time systems. SWENG 452W Embedded Real Time Systems (3) Real time operating systems is the study of hardware/software systems in which timing constraints must be met for correctness. Real time systems are embedded in applications ranging from the antilock brakes in cars to the flight control systems for jetliners. Students are first introduced to the concept of systems with real time constraints by examining case studies. The unified modeling languages (UML) with real time extension is introduced allowing students to capture the constraints present in the systems in a variety of models allowing the problem to be described at several levels of abstraction. Tasks and messages are introduced as programming structures which can satisfy the constraints described by the UML models. With a basic understanding of real time systems and how to implement them, the focus of the course shifts away from these technical concerns towards understanding the documentation of the requirements using the Volere Requirements Specification template. All the writing assignments in the class will revolve around Volere in one way or another. Increasingly complex case studies will give the class the opportunity to explore more sophisticated inter-task communications mechanisms as well as common pitfalls present in RTOS applications. Students will learn how to verify the correctness of their applications in order to guarantee that the real time constraints can be met when the system is deployed. Discussion will turn to application programmer interfaces used by hardware vendors to port hardware into a RTOS. The class will end by designing and building a complex RTOS by a team of students using the techniques learned in the class. The project will outline the needs of the RTOS application in a project proposal using the Volere template. The proposal will be developed iteratively with the faculty member until its scope and definition are clear. This proposal will be developed into a complete requirement specification including a time-line and identification of development benchmarks. This system resulting from the development will be documented in the final report write-up. Enforced Prerequisite at Enrollment: CMPSC 472 or CMPSC 473 or CMPEN 441 Writing Across the Curriculum
Software systems are becoming an integral part of our daily life. In many domains the failure of a software system in not acceptable. Such a failure will have catastrophic effects. Hence, the quality of such software systems becomes so crucial. This course introduces software quality, the associated quality factors, software errors and the software quality assurance system. As software systems advance in complexity so does the threats that they face. Hence, the security of these systems has become so essential. Traditionally, security has been thought off as an add-on to an existing system. In this course, students will understand that this is not sufficient. Students will learn to consider security throughout the development process by extending the traditional software development life cycle and UML. For the requirements phase, this course will teach students to collect secure requirements, perform security requirements planning, and perform vulnerability mapping. For the design phase, this course will teach students to design a secure software architecture and perform architectural risk analysis. For the implementation phase this course will introduce students to secure coding. For the testing phase, the course will introduce students to secure testing. Finally students will be introduced to secure deployment and secure maintenance. A semester long team-based project will be part of this course to practice the concepts covered in the class. Enforced Prerequisite at Enrollment: SWENG 411
This course introduces the students to a contemporary computing paradigm called "service-oriented computing." SWENG 465 Web Services (3) This course focuses on a new computing paradigm called "service- oriented computing", which has been greatly impacting a wide array of software systems. It covers "service-oriented architecture." Students will not only gain an in-depth understanding of the concepts and technical issues underpinning Web services, but also gain hands-on experience of the development of software systems built upon Web services. Enforced Prerequisite at Enrollment: SWENG 311 or CMPSC 221
* level) Technical Elective (300, 400- 3 General Education Course * level) (GA/GH/GS) General Education Course 3 General Education Course (GA/GH/GS) (GA/GH/GS) General Education Course 1.5 (GHW) 16.5 15 Total Credits 126-127 * Course requires a grade of C or better for the major ‡ Course requires a grade of C or better for General Education # Course is an Entrance to Major requirement † Course satisfies General Education and degree requirement Course will satisfy Writing Across the Curriculum requirement. CMPEN 271, CMPEN 275, and CMPSC 360 must be completed prior to Credits the third-year to ensure that fall semester third- year prerequisites are 3 met. 4 University Requirements and General Education Notes: 2 US and IL are abbreviations used to designate courses that satisfy 4 Cultural Diversity Requirements (United States and International Cultures). 16 W, M, X, and Y are the suffixes at the end of a course number used to designate courses that satisfy University Writing Across the Curriculum Credits requirement. General Education includes Foundations (GWS and GQ), Knowledge Domains (GHW, GN, GA, GH, GS) and Integrative Studies (Inter-domain) 3 requirements. N or Q (Honors) is the suffix at the end of a course number used to help identify an Inter-domain course, but the inter-domain 3-4 attribute is used to fill audit requirements. Foundations courses (GWS and GQ) require a grade of 'C' or better. Program Notes: 16-17 • Only students who have gone through the entrance to major (ETM) process and have been accepted into this major may register for third- and fourth-year courses.
Capstone group design projects in software engineering. SWENG 481 Software Design Projects (3) In this course students complete their group senior design project started in SWENG 480. Design groups meet regularly with a faculty advisor to report progress and resolve technical issues. Oral and written progress reports are expected at selected times. The class culminates with a final technical defense of the project. Enforced Prerequisite at Enrollment: SWENG 480
/Maximum of 12 Supervised student activites on research projects identified on an individual or small-group basis.
/Maximum of 18 Supervised off-campus, nongroup instruction including field experiences, practica, or internships. Written and oral critique of activity required. Enforced Prerequisite at Enrollment: Prior approval of proposed assignment by instructor
/Maximum of 18 Creative projects, including research and design, that are supervised on an individual basis and that fall outside the scope of formal courses.
/Maximum of 9 Formal courses given infrequently to explore, in depth, a comparatively narrow subject that may be topical or of special interest.
/Maximum of 12 Courses offered in foreign countries by individual or group instruction.
This course provides a foundation in software enginering techniques for developing secure software systems.
Practical benefits of a Database Management System; three-stage process to create and implement a relational database to meet defined requirements.
33 Total Credits 12 Financial Data Analytics Option Capstone Course
The principles of service oriented architecture; modeling, design and implementation of services; mapping business processes to services. SWENG 569 Service Oriented Architecture (3)Service- Oriented Architecture (SOA) is a design principle for guiding the design, development, deployment, and sustaining of flexible and agile IT solutions. SOA has become increasingly viable because of the widespread adoption of Web services technology that makes creating SOA practical and cost effective. SOA essentially makes IT agile, interoperable, and more responsive. This course is structured to be appropriate for graduate students in software or systems engineering, or information science. Many of the topics covered in this course may be applied to a wide variety of research areas. Usually this course would cover the following topics: 1) Model, design, and implement SOA; 2) Create agile and reusable SOA; 3) Automate business processes by mapping to the architectural model; 4) Orchestrate services and execute processes with the Business Process Execution Language (BPEL); 5) Achieve interoperability within SOA using proven design patterns and/ or best practices; and 6) Implement loosely coupled services using WSDL-first techniques. Students will be evaluated on their understanding of the course material by completing one examination (20%), weekly assignments (40%), and an individual project with presentation (40%).
Description of tools and techniques in the software development lifecycle; Mitigation and managing time-to-market and quality of large software systems. permission
A holistic, systems-based approach to design and analysis of real-time systems; design and implementation of a small real-time system. instructor or division approval
Application of genetic algorithms to problems in engineering and science including combinatorial optimization, multi-criteria optimization, biology chemistry, and neural networks. on approval of department
This class examines well-known heuristics, principles and patterns in the design and construction of reusable frameworks, packages and components. SWENG 585 Pattern Oriented Design (3) This course studies the heuristics, principles and patterns of object-oriented design in the construction of extendable frameworks, reusable packages and pluggable components. Topics covered include Riel's object-oriented design heuristics, Martin's principles of class and package design, the "Gang of Four" design pattern catalog, refactoring and framework evolution.
Total Credits 9 All courses must be completed with a minimum grade of C or better and an overall GPA of 3.0. Graduate - The Pennsylvania State University 2026-2027 831
Techniques for the analysis and visualization of large software systems to assess the quality of the design and architecture. SWENG 588 Program Understanding (3)It is a general observation that software engineers learn about software design, programming languages, paradigms, patterns and tools, and are expected to produce high quality designs and code, often without ever having seen good examples. This approach is akin to teaching students the syntax of the English language and writing techniques and then expecting them to become expert writers without ever having read great literary works. The course in Program Understanding seeks to educate graduate software engineering students beyond their understanding of code syntax and best construction practices with analytical evaluation of "great works" of software code. This approach includes manual code reading, the use of visualization techniques, and automated approaches to assessment of design and code quality.
/Maximum of 15 Supervised student activities on research projects identified on an individual or small-group basis.
/Maximum of 9 Creative projects, including nonthesis research, that are supervised on an individual basis and which fall outside the scope of formal courses. Graduate - The Pennsylvania State University 2026-2027 1407
/Maximum of 9 Formal courses given on a topical or special interest subject which may , be offered infrequently; several different topics may be taught in one year or semester.
Analysis and construction of project plans for the development of complex software products; how to manage change and cost control.
Evaluate and design interactive products that support how people work and communicate from both a theoretical and practical perspective.
Students must sequence their courses so all undergraduate degree requirements are fulfilled before taking courses to count solely towards the graduate degree. Students are expected to complete the undergraduate degree requirements within the typical time to degree for the undergraduate major. In the semester in which the undergraduate degree requirements will be completed, IUG students must apply to graduate, and the undergraduate degree should be conferred at the next appropriate Commencement. If students accepted into the IUG program are unable to complete the M.S.E. degree, they are still eligible to receive their undergraduate degree if all the undergraduate degree requirements have been satisfied.
Total Credits 9 All courses must be completed with a minimum grade of C or better and an overall GPA of 3.0.
This course provides a rigorous formal framework and practical information on the testing of software throughout its life cycle. Emphasis will be placed on software testing activities throughout the software lifecycle, testing of object-oriented and non-object-oriented software, and on formal methodologies for software testing. Documentation of software testing activities will also be covered.
This course is a thorough treatment of the theoretical and practical aspects of discovering, analyzing, modeling, validating, testing and writing requirements for systems of all kinds, with an intentional focus on software-intensive systems. The course will bring to bear a variety of formal methods, social models, and modern requirements writing tools to be useful to the theorist and practicing engineer. Students will be led through a series of weekly activities that culminate in the delivery of a complete software requirements specification project for a hardware/ software system (first in draft, then in final form). The project is broken down into four subprojects, Requirements Elicitation, Requirements Analysis and Representation, Requirements Validation and Testing, and Final Requirements Documentation. Cross-listed with: SYSEN 886
Architecture is an abstract view of a software system distinct from the details of how such a system is implemented. A robust architecture is key to developing software systems that meet quality expectations (such as performance, scalability, availability, maintainability, etc.) of their stakeholders. This course introduces basic concepts of software architecture, architectural design principles, and patterns. Students also learn how to document and evaluate software architectures, and reuse architectural assets through software product lines. This course is structured to be appropriate for graduate students in software or systems engineering. Many of the topics covered in this course may be applied to a wide variety of research areas. Students will be evaluated on their understanding of the course material by completing one examination (25%), weekly assignments (35%), and an individual project with presentation (40%).
design and development of mobile computing-based applications and services utilizing current and emerging mobile computing technologies. The purpose of this course is to provide students with an advanced and hands-on exploration of mobile computing paradigms. Mobile computing addresses the mobility needs of business operations and management in organizations, with the increasing trend of leveraging a variety of deployed enterprise information systems. Hence, well- designed and developed mobile applications can meet the needs of business mobility on both the service provider and the customer sides. This course is designed to explore and discuss approaches to the design and development of mobile applications. It builds an awareness of the business need for operational agility and mobility, and the value of existing IT investments in organizations. Specifically, this course investigates the fundamental design and development of mobile applications and services using platform technologies; area topics include mobile application and services design patterns, user interface, animation, location & mapping, and integration. Through working on exercises, labs, and projects, students will be able to identify and apply appropriate mobile platform technologies in their assignments and will gain skills and coding experience in the development of adaptable and sustainable mobile application solutions. Consequently, with this course, students will learn mobile development environments, application and service design and development, device emulators, data and mobility management, and enterprise solution-based integration. Cross Listings: IST 888 will be added as a cross-listed course. Cross-listed with: IST 888
Total Credits 36 All students will complete their program of study with a capstone project that provides students with an opportunity to apply their knowledge of the software engineering theories, methods, processes, and tools learned throughout their program, in a culminating and summative experience. Students complete the capstone project while enrolled in SWENG 894.
Source: Pennsylvania State University-Penn State Erie-Behrend College's catalog, linked per course · table learning_unit · CourseShelf publish 59
