CSE 5232
Transcript Abbreviation:
SW Rqmts Analys
Course Description:
Information systems analysis; object-oriented analysis models and tools; use cases, system modeling using UML; requirements specification development; term project.
Course Levels:
Undergraduate (1000-5000 level)
Graduate (5000-8000 level)
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: 3241 or 3901 or 3902 or 3903 (560) or 5241 (670).
Electronically Enforced:
No
Exclusions:
Not open to students with credit for 3232 (616).
Course Goals / Objectives:
Master applying an object-oriented methodology to the analysis of a real-world problem.
Be competent with writing use cases to model functional requirements.
Be competent with using UML use case, class, sequence and collaboration diagrams to model data and behavior requirements.
Be competent with organizational dynamics as it applies to projects.
Be competent with the system lifecycle approach and its phases.
Be familiar with software engineering issues such as correctness, reliability, productivity.
Be familiar with the distinction between analysis and design activities and skills.
Be familiar with working with a team to produce requirements specification document.
Be familiar with the purpose, structure and contents of a requirements specification document.
Be familiar with non-functional requirements such as security, integrity, response time and reliability.
Be familiar with using a UML tool.
Check if concurrence sought:
No
Contact Hours:
| Topic | LEC | REC out-of-class | REC in-class | Weekly LAB out-of-class | Weekly LAB in-class |
|---|---|---|---|---|---|
| Software engineering, software development life cycle, traditional vs object-oriented analysis | 7.0 | 0.0 | 0 | 0.0 | 0 |
| Teamwork and organizational dynamics | 2.0 | 0.0 | 0 | 0.0 | 0 |
| Data flow diagramming (as context model) | 4.0 | 0.0 | 0 | 0.0 | 0 |
| UML (use case diagram, sequence diagram, collaboration diagram, state chart diagram, class diagram) | 15.0 | 0.0 | 0 | 0.0 | 0 |
| Requirements elicitation (face-to-face meetings and presentations to real-world client) | 8.0 | 0.0 | 0 | 0.0 | 0 |
| Total | 36 | 0 | 0 | 0 | 0 |
Grading Plan:
Letter Grade
Course Components:
Lecture
Grade Roster Component:
Lecture
Credit by Exam (EM):
No
Grades Breakdown:
| Aspect | Percent |
|---|---|
| Homework (4) | 20% |
| Quizzes (2) | 20% |
| Team project (including weekly progress reports, presentation, drafts and final document -- weighted by peer evaluation) | 35% |
| Final Exam | 25% |
Representative Textbooks and Other Course Materials:
| Title | Author | Year |
|---|---|---|
| An Introduction to Object-Oriented Analysis | Brown |
ABET-CAC Criterion 3 Outcomes:
| Significant contribution (7+ hours) | 1 | Analyze a complex computing problem and to apply principles of computing and other relevant disciplines to identify solutions. |
| Substantial contribution (3-6 hours) | 2 | Design, implement, and evaluate a computing-based solution to meet a given set of computing requirements in the context of the program’s discipline. |
| Significant contribution (7+ hours) | 3 | Communicate effectively in a variety of professional contexts. |
| Substantial contribution (3-6 hours) | 4 | Recognize professional responsibilities and make informed judgments in computing practice based on legal and ethical principles |
| Significant contribution (7+ hours) | 5 | Function effectively as a member or leader of a team engaged in activities appropriate to the program’s discipline |
| Substantial contribution (3-6 hours) | 6 | 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:
| Significant contribution (7+ hours) | 1 | an ability to identify, formulate, and solve complex engineering problems by applying principles of engineering, science, and mathematics |
| Substantial contribution (3-6 hours) | 2 | 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 |
| Significant contribution (7+ hours) | 3 | an ability to communicate effectively with a range of audiences - pre-2019 EAC SLO (g) |
| Substantial contribution (3-6 hours) | 4 | 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 |
| Significant contribution (7+ hours) | 5 | 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 |
| Some contribution (1-2 hours) | 7 | an ability to acquire and apply new knowledge as needed, using appropriate learning strategies |
Embedded Literacies Info: