CSE 5231
Transcript Abbreviation:
Software Eng
Course Description:
Software engineering issues, techniques, methodologies and technologies; software lifecycle activities: requirements analysis, architecture, design, testing, deployment, maintenance; project management; enterprise software systems; frameworks.
Course Levels:
Undergraduate (1000-5000 level)
Graduate
Designation:
Elective
General Education Course
(N/A)
Cross-Listings
(N/A)
Credit Hours (Minimum if “Range”selected):
2.00
Max Credit Hours
(N/A)
Select if Repeatable:
Off
Maximum Repeatable Credits
(N/A)
Total Completions Allowed
(N/A)
Allow Multiple Enrollments in Term:
No
Course Length:
14 weeks (autumn or spring)
12 weeks (summer only)
Off Campus:
Never
Campus Location:
Columbus
Instruction Modes:
In Person (75-100% campus; 0-24% online)
Prerequisites and Co-requisites:
Prereq: 3901 or 3902 or 3903 (560).
Electronically Enforced:
No
Exclusions:
Not open to students with credit for 3231 (757).
Course Goals / Objectives:
Be competent with structured and agile software engineering frameworks; specifically structured and agile software engineering methodologies for requirements identification, analysis, architecture, design, testing, deployment and project managemen
Be familiar with the characterization of enterprise software systems
Be familiar with frameworks for analyzing the business context of enterprise IT systems, the concept of Business-IT alignment and related issues, and Enterprise Architecture
Be exposed to the trends impacting enterprise systems
Be exposed to the need for frameworks for software engineering
Check if concurrence sought:
No
Contact Hours:
| Topic | LEC | REC | LAB | LAB Inst |
|---|---|---|---|---|
| Characteristics of enterprise softw. sys.: scale, heterogeneity, distribution, federation by nature, lack of complete knowledge; organizational challenges; external drivers. | 1.5 | 0.0 | 0.0 | 0 |
| Understanding the business and the relationship between the business and information technology - business strategy, business-IT alignment and enterprise architecture. | 3.0 | 0.0 | 0.0 | 0 |
| Software engineering process – broadly characterized as structured or agile processes. Scenario-driven, Incremental and iterative development. Introduction to work-products and work-product-oriented development. Agile principles. | 2.5 | 0.0 | 0.0 | 0 |
| Requirements gathering. Structured and agile requirements work-products. | 4.0 | 0.0 | 0.0 | 0 |
| Analysis – domain, problem and solution analysis. Exposure to UML. Structured and agile analysis work-products. CRC-card based analysis. | 4.0 | 0.0 | 0.0 | 0 |
| Architecting softw. intensive sys: Designing, evaluating architectures; non-functional requirements & quality attributes in arch. Quality-driven design. Structured & agile architecture work-products. | 6.0 | 0.0 | 0.0 | 0 |
| Software project management: Structured and Agile project planning and management, linear and parametric software estimation, Risk planning. Software configuration management. Agile boot camp – LEGO-based workshop on Agile development. | 6.0 | 0.0 | 0.0 | 0 |
| Software design: Responsibility-driven design concepts, application of responsibility-driven design in design patterns and enterprise technology frameworks, designing applications using enterprise technology frameworks. | 6.0 | 0.0 | 0.0 | 0 |
| Testing: Testing methodologies for enterprise systems. Testing in agile methodologies. | 4.0 | 0.0 | 0.0 | 0 |
| Deployment, Maintenance and Management: IT Infrastructure Library (ITIL) practices for infrastructure management. | 2.0 | 0.0 | 0.0 | 0 |
| Case studies in software engineering | 2.5 | 0.0 | 0.0 | 0 |
| Total | 41.5 | 0 | 0 | 0 |
Grading Plan:
Letter Grade
Course Components:
Lecture
Grade Roster Component:
Lecture
Credit by Exam (EM):
No
Grades Breakdown:
| Aspect | Percent |
|---|---|
| Class participation | 10% |
| Workshop participation | 10% |
| Team Project | 30% |
| In-class Quizzes | 30% |
| Final examination | 20% |
Representative Textbooks and Other Course Materials:
| Title | Author | Year |
|---|---|---|
| Software Engineering | Sommerville | |
| Software Engineering, A Practitioner’s Approach | Pressman | |
| Developing Object-Oriented Software, An Experience-Based Approach, 1997. | Object-Oriented Technology Center, IBM |
ABET-CAC Criterion 3 Outcomes:
| Outcome | Contribution | Description |
|---|---|---|
| 1 | Substantial contribution (3-6 hours) | Analyze a complex computing problem and to apply principles of computing and other relevant disciplines to identify solutions. |
| 2 | Substantial contribution (3-6 hours) | Design, implement, and evaluate a computing-based solution to meet a given set of computing requirements in the context of the program’s discipline. |
| 3 | Some contribution (1-2 hours) | Communicate effectively in a variety of professional contexts. |
| 4 | Some contribution (1-2 hours) | Recognize professional responsibilities and make informed judgments in computing practice based on legal and ethical principles |
| 5 | Some contribution (1-2 hours) | Function effectively as a member or leader of a team engaged in activities appropriate to the program’s discipline |
| 6 | Substantial contribution (3-6 hours) | Apply computer science theory and software development fundamentals to produce computing-based solutions. |
ABET-ETAC Criterion 3 Outcomes
(N/A)
ABET-EAC Criterion 3 Outcomes:
| Outcome | Contribution | Description |
|---|---|---|
| 1 | Substantial contribution (3-6 hours) | an ability to identify, formulate, and solve complex engineering problems by applying principles of engineering, science, and mathematics |
| 2 | Substantial contribution (3-6 hours) | an ability to apply engineering design to produce solutions that meet specified needs with consideration of public health, safety, and welfare, as well as global, cultural, social, environmental, and economic factors |
| 3 | Some contribution (1-2 hours) | an ability to communicate effectively with a range of audiences - pre-2019 EAC SLO (g) |
| 4 | Some contribution (1-2 hours) | an ability to recognize ethical and professional responsibilities in engineering situations and make informed judgments, which must consider the impact of engineering solutions in global, economic, environmental, and societal contexts |
| 5 | Some contribution (1-2 hours) | an ability to function effectively on a team whose members together provide leadership, create a collaborative and inclusive environment, establish goals, plan tasks, and meet objectives |
| 7 | Some contribution (1-2 hours) | an ability to acquire and apply new knowledge as needed, using appropriate learning strategies |
Embedded Literacies Info
(N/A)
Attachments
(N/A)
Additional Notes or Comments
(N/A)