CEN 3073
Requirements Engineering and Analysis
The SEEK REQ KA
Embedded Files
Units and Topics
Units and Topics
1. Requirements fundamentals and Business Analysis SEEK REQ.rfd, SWEBOK 1-2, textbook Part I: Software Requirements: What, why, and who, Document: BRS
2. Eliciting requirements SEEK REQ.er, SWEBOK 3, textbook Part II: Requirements Development
3. Requirements analysis, specification and documentation SEEK REQ.rsd, SWEBOK 4-5, textbook Part II: Requirements Development
3.A Stakeholder requirements Model: Use Case Diagram, mockup; Document: StRS
3.B System requirements Model: Context Diagram, prototype; Document: SyRS
4. Requirements validation SEEK REQ.rv, SWEBOK 6, textbook Part II: Requirements Development; Document: SRS
5. Practical Considerations and Software Requirements Tools SWEBOK 7-8, textbook Part II: Requirements Development
Schedule
Schedule
There are face to face meetings every Tuesday or Thursday and live meetings every Friday. All meetings are recorded for anyone who can't join live.
Face to Face days: instruction, requirements engineering concepts, critical thinking, guest speakers, etc.
Online days: hands-on activities in Jira, whole group introduction then small group application
Time Management
Time Management
Expect to spend 3 hours per week in live class lessons or watching lesson recordings and 6-9 hours per week outside of class on coursework.
For most weeks, the outside of class work will breakdown like this:
Critical Thinking Discussion question: 40 min. - 1 hour
Reading the textbook and answering questions: 40 min. - 1 hour
Journals: 2-3 hours
Project Activity planning: gathering needed information, researching, and/or meeting with sponsors: 1 - 1.5 hours
Project Activity work: completing assignments that were started in class: 40 min. - 1 hour
Reading other resources and working on larger assignments like Documents, Models, and Activity Reports: 1 - 1.5 hours
More information about Time Management
Orientation, Purpose, and Structure
Orientation, Purpose, and Structure
In this course, you will dive deep into a specific software engineering knowledge area, software requirements (a.k.a. requirements analysis and specification, a.k.a. requirements engineering).
The content of this course is based on ACM and IEEE guidelines for what software engineering graduates must know. They call this SEEK, Software Engineering Education Knowledge. You may want to skim this document.
The SEEK, and this course web site, are organized hierarchically in knowledge areas (KAs), units, and topics.
The course and site are the requirements analysis and specification (REQ) KA.
The main pages of the course web site are units.
The pages contain section headings for topics.
Beyond the "Education Knowledge" that should be learned in college, the ACM and IEEE also publish a full Software Engineering Body of Knowledge (SWEBOK) with a Software Requirements KA in chapter 1. This document has actual information about the SEEK topics and should be read. Learning content from the SWEBOK that isn't on the SEEK would be a way to challenge yourself if you really want to know requirements well.
Requirements in the context of software engineering
Requirements in the context of software engineering
How Requirements Fits into Software Engineering
Context within FGCU
Context within FGCU
From FGCU ABET
The Software Engineering course sequence in the curriculum starts with CEN 3031 Software Engineering Fundamentals, which introduces students to the Software Engineering Life Cycle, including requirements analysis, software design, and software verification and validation. Then students learn in more depth the theory and practice of requirements analysis in CEN 3073 Software Specification, software design in CEN 4065 Software Architecture and Design, and verification and validation in CEN 4072 Software Testing. In each of these classes, students implement a software system to be applied to solve some real world problems.
... software development in a project and team setting. The students play an important role in managing their projects under the guidance of their instructors. With instructor approval, students form their teams which typically consist of two or three people. They need to divide the work among the team members. They are also supposed to budget the time for the software development to meet intermediate milestones, set by the instructor. In some courses, students are required or encouraged to use some software tools for project management.
Catalog Description
Covers the analysis of software requirements, and the study of requirements engineering tools and techniques. Includes requirements elicitation, gathering, formalizing, specification, and validation.
Prerequisite(s)
CEN 3031 for level Undergraduate with minimum grade of C and EGN 3641C for level Undergraduate with minimum grade of C and COP 3003 for level Undergraduate with minimum grade of C
Google Sites
Report abuse