Course Outline

SYSE 530 : System Requirements Analysis and Modeling

Preview Workflow

Viewing: SYSE 530-WW : System Requirements Analysis and Modeling

Last approved: Mon, 11 Jan 2016 19:31:12 GMT

Last edit: Mon, 11 Jan 2016 19:31:11 GMT

SYSE 530-WW
Campus
Worldwide
College of Aeronautics (WAERO)
SYSE
530
System Requirements Analysis and Modeling
3
This course is concerned with the development, definition, and management of requirements for system or product. Topics include the system requirements process, requirements elicitation techniques, alternative requirements analysis techniques, requirements specification, requirements verification and validation, requirements management, and requirements standards and tools. Issues such as stakeholder identification, risk analysis, trade off analysis as it relates to the requirements will be covered.

This is a required course in the Master of Systems Engineering degree program. This course is intended to examine the processes and techniques used to determine customer needs and expectations for a system. Elaborate those needs and expectations into system concepts. Analyze and validate needs, expectations, and concepts to create a complete formally specified set of system requirements suitable for use by the customer and the developer in the realization of the system

Upon course completion, students will be able to:1. Describe the essential elements of systems requirements engineering and its place in the larger system engineering process2. Describe and understand various levels of system requirements and specifications3. Understand and apply requirements engineering techniques, tools, and conceptual models that will aid in analyzing system requirements4. Develop, analyze, and critique requirements and specifications5. Define processes for performing requirements engineering6. Measure and improve processes related to requirements engineering

Located on the Daytona Beach Campus, the Jack R. Hunt Library is the primary library for all students of the Worldwide Campus. The Chief Academic Officer strongly recommends that every faculty member, where appropriate, require all students in his or her classes to access the Hunt Library or a comparable college-level local library for research. The results of this research can be used for class projects such as research papers, group discussion, or individual presentations. Students should feel comfortable with using the resources of the library. 


Web & Chat: http://huntlibrary.erau.edu
Email:  library@erau.edu
Text: (386) 968-8843
Library Phone:  (386) 226-7656 or (800) 678-9428
Hourshttp://huntlibrary.erau.edu/about/hours.html
 

N/A
N/A

Written assignments must be formatted in accordance with the current edition of the Publication Manual of the American Psychological Association (APA) unless otherwise instructed in individual assignments.

ActivityPercent of Grade
Input Grading Item100

Undergraduate Grade Scale

90 - 100% A
80 - 89% B
70 - 79% C
60 - 69% D
0 - 60% F

Graduate Grade Scale

90 - 100% A
80 - 89% B
70 - 79% C
0 - 69% F
Written and oral communication, as well as computer skills are emphasized in each course offered throughout the Worldwide Campus.
Topic 1. Stakeholder Requirements Definition Est. Hrs. 5 Student Outcomes: a. Analyze where the requirements process fits into the overall systems engineering process. b. Define the characteristics of a requirement versus a specification. c. Identify stakeholders and their role in the requirements process. d. Describe key inputs, process activities, and outputs of the stakeholder definition process. Topic 2. Requirements Elicitation and Definition Outputs Est. Hrs. 5 Student Outcomes: a. Apply appropriate tools, techniques, and processes to identify stakeholders and elicit top-level requirements and expectations such as needs, wants, and desires b. Identity stakeholders and Concepts of Operations Topic 3. Requirements Analysis Process - Process Activities Est. Hrs. 5 Student Outcomes: a. Analyze the function and content of the requirements analysis process b. Determine verifiable requirements c. Define CONOPS documents Topic 4. Requirements Analysis Process - Process Outputs Est. Hrs. 5 Student Outcomes: a. Develop a QFD matrix to determine system specifications b. Write multi-level requirements c. Develop a Requirements Verification and Traceability Matrix RVTM Topic 5. Architectural Design Est. Hrs. 4 Student Outcomes: a. Evaluate a QFD matrix to determine system specifications b. Develop and analyze a system architecture Topic 6. Implementation & Integration Est. Hrs. 4 Student Outcomes: a. Analyze the importance and associated requirements of the implementation process within systems engineering b. Diagram a system that illustrates how subsystems are integrated and their interfaces Topic 7. Verification & Validation Est. Hrs. 4 Student Outcomes: a. Differentiate between the functions of the verification and validation processes b. Define and defend verification and validation flaws in systems development projects Topic 8. Modeling & Simulation Est. Hrs. 4 Student Outcomes: a. Assess the proper complexity and implementation of M&S tools appropriate for application to the requirements process b. Illustrate the connectivity between system elements using N2 diagrams c. Develop a Design of Experiments Topic 9. Transition, Operation, Maintenance Est. Hrs. 4 Student Outcomes: a. Explain how to successfully plan for the transition of a system and the linkages between information gathered in operation and maintenance processes b. Explain where requirements fit into the Systems Engineering Plan
Dr. Brian Sanders - 4/1/2015
sanderb7@erau.edu
Dr. Bruce Conway - 4/1/2015
conwaybr@erau.edu
Dr. Bruce Conway - 4/1/2015
conwaybr@erau.edu
Dr. Kenneth Witcher - 4/1/2015
kenneth.witcher@erau.edu
PO#NameDescription
1-4 Master of Systems Engineering PO1 Systems Thinking: Students will understand systems concepts, including the relations among subsystems; will understand the needs of the super-system and their impact on system development; and will understand how the business (enterprise) and technology environment influences system development and its effect on its operating and social environment.

PO2 Holistic Lifecycle View: Students will be able to analyze stakeholder needs to establish and manage system requirements throughout its life cycle. Students will also be able to evaluate the impact of system requirements in terms of the draw of developmental and operational resources, and the interaction of the system with its environment

PO3 System Design: Students will understand different types of system architectures; will be able to examine alternatives in developing system concepts; will understand the need for designing for a system’s life cycle; and will understand the processes for validating and verifying a system’s design and transition to operation.

PO4 Systems Engineering Management: Students will understand the coordination of system life cycle activities and the concurrent development of systems elements; will understand the timely integration of both enterprise functions and system specialties into a system’s development; will understand how to define a life cycle process for a given system; and will understand the role of systems engineering planning, monitoring, and controlling, and the logistics and operations associated with a system development and implementation.
Key: 237