Use this student document below

1 Systems Engineering Process Synopsis (Background). The Systems Engineering Process that I selected is systems requirements definition. In accordance with IOS 15288 and INCOSE Handbook, Section 4, the system requirements definition process is the 3d phase of the Technical Systems Engineering Processes, completed after stakeholder needs and requirements and prior to defining the systems architecture. The purpose of the systems requirement definition process is to decompose the stakeholder needs and requirements into system needs and requirements. This decomposition occurs from the Stakeholder Requirements Specification (StRS) into the System Requirements Specification (SyRS) (1, pg. 48). This transformative process moves from a user-oriented view of desired capabilities into a technical view of a solution, that meets the operational needs of the user (1, pg. 57). This is a critical step and establishes the foundation of the entire system and subsequent Technical Systems Engineering process. Within the systems requirement definition phase, there are discrete cyclical activities to derive system characteristics, attributes, functions, and performance that trace to stakeholder requirements (1, pg. 58). The iterative and recursive process includes the following activities: preparing, defining, analyzing, reviewing, and managing the system requirements. Preparing: The first activities apart of the process is preparation; information gathering, asking questions, and validating assumptions to ensure a complete understanding of how the stakeholder requirements were generated, reviewing traceability matrices, and understanding the intent of the stakeholder requirements. Defining: This phase of the process is focused around identifying system functionality, with an emphasis on refraining from straying into implementation or solution space. This also includes identifying stakeholder requirements, or other limitations, that contain constraints and capturing critical quality characteristics or critical performance measures. Analyzing: Ensuring that the initial requirements that were generated are necessary, concise, clear, implementation dependent, singular, achievable, and verifiable. This also includes ensuring traceability and alignment to the stakeholder requirements. Additionally, there should be verification criteria defined at this phase to establish key performance indicators, such as measures of performance and technical performance measures, which are measures of success at later phases of the Systems Engineering Processes.Reviewing: It is important to get relevant stakeholders' concurrence on the systems requirements. This includes design engineers, customers, end-users, functional stakeholders such as quality, safety, etc. and subject matter experts or non-advocate reviewers to ensure a robust review of the foundational pieces of the entire system satisfactorily reflect the stakeholder's intentions. Managing: Change is inevitable, so it is critical to maintain control, traceability, and accountability of the system requirements. As stated earlier, this process can become cyclical and it is important to ensure that the system requirements are maintained with configuration control throughout the entire system's lifecycle. If changes are made, ensuring that there is appropriate rationale and documentation generated and approved by the stakeholder community to maintain accurate requirement baselines. 2 Systems requirements definition applied to Systems Engineering of Systems. As mentioned above, the systems requirement definition process establishes the foundation of a technical system. This process defines the "what" a system must do by decomposing the "what" all stakeholders agreed upon. This systems requirement definition process has several key characteristics; analytical, definitive, foundational, cyclical, iterative, and recursive (1, pg. 58). These characteristics help establish a complete, clear, verifiable, and feasible requirements that appropriately trace to stakeholder requirements. Furthermore, the systems requirement definition process is the conduit to establishing what the technical system shall do. Or as Jacob Siedle states, "System requirements should be the building blocks and one of the first things established for any project" (5). It is the bridge between "what" the stakeholders want and defining the functional architecture of the technical system. This entire process embodies the application of Systems Engineer of Technical Systems by demonstrating an understanding of the bigger picture of stakeholder requirementseeds, the system's boundaries to address inputs, outputs, interfaces, and environments, the definition of what the system must do and how there is traceability back to the stakeholder's initial needs, and identification of verification methods to validate the system. Systems requirements "establish the basis of agreement between the stakeholders and developers, provides a baseline for verification, facilities transfer of the product to new users, and serves as a basis for later enhancement or alteration of the finished product" (6). It is truly a process that is thinking about every phase of the Systems Engineering process from tip to tail to ensure needs are met, design teams can create attainable technical systems, the technical system can be validated to the requirements and the stakeholder's needs. 3 Systems requirements definition applied to Engineer a Transportation System. 3.1 Impact on Systems requirements definition processThe systems requirements definition process applies to the systems engineering of a transportation system through establishing a technical framework of what the system must do and ultimately is the predecessor to generating system architecture, creating designs, and having the ability validate that the system meets the initial stakeholder's needs. INCOSE defined the process in a similar fashion stating that, "the systems requirements definition process applies to the systems engineering of a transportation system by establishing the basis for the systems architecture, design, integration, and verification (1, pg. 57)". Today's transportation systems are primarily in the operation and maintenance processes of Systems Engineering. Therefore, the impact on the systems requirement definition process when applying it to engineer a transportation system as it exists today is lessened in comparison to engineering a future transportation system. However, it is worth noting that there are several transportation system initiatives to drive innovation, affordability, and sustainability that impact the system's requirements. Therefore, the initiatives require the systems requirements to evolve, or even in some instances be expound upon, to maintain continuity with emerging stakeholder requirements, changing environments, or technological advancements. As an example, the Federal Aviation Administration has an initiative called NextGen to transform and modernize the aviation system. "For more than a decade, the FAA has worked with stakeholders in the aviation community to research, plan, build, and deploy NextGen" (2). This is an example that highlights that all of these initiatives still follow the recursive systems requirements definition process to be successful. The process continues to remain the same but the aperture of the requirement definition process is focused and targeted to new initiatives. 3.2 Improvements to the Systems requirements definition process In the near future, there are several potential improvements to the systems requirement definition process, which include incorporating artificial intelligence to perceive, synthesize and infer stakeholder requirements or evaluate system requirements, leveraging larger system of systems networks and nodes for an entire transportation system ecosystem, developing a common foundation of transportation system requirements, and establishing automated feedback loops to efficiently incorporate changes to align with affordability or technical advancements. There are already several examples of transportation systems trying to implement these types of improvements. For example, there has already been the formation of the, "Joint Planning and Development Office (JPDO) to create a unified vision of what the U.S. air transportation system should deliver for the next generation and beyond" (2). This is the first step towards driving towards commonality and creating a holistic transportation system ecosystem. This would translate to being able to leverage the larger systems networks and nodes, build off common requirements and focusing in on specific unique requirements for each specific transportation system. Additional evidence of implementing these types of improvement includes applying random parameters model to evaluate the impact of traffic (4). This example demonstrates there areopportunities to incorporate additional analytical tools and feedback loop opportunities to evaluate the impact on potential changes or refined to requirements. In the upcoming decades there will be the evolution of artificial intelligence which could help revolutionize the evaluation of these requirements and "what-ifs" to efficiently assess and recommend changes based on monte carlo data. 3.3 Your Position on How the Systems requirements definition process applies to the Transportation System. In conclusion, the systems requirements definition process relatively applies in the same way for the transportation system today as it would in the near future because the same types of activities are performed. Even with the current transportation systems in a sustainment phase, there are continued innovative changes to drive affordability and incorporate technological changes, or emerging stakeholder or environmental requirements that follow the system requirement definition process. However, these initiatives or changes for the current system result in a targeted set of systems requirement definition activities. In contrast, the systems requirement definition process for a transportation would have a holistic systems requirement definition process across the entire system versus a potential targeted subsystem or process. In the near future, there will be several improvement opportunities but the process would still apply the same way as today. While there could be automated information gathering and analysis via artificial intelligence given there have already been advancements in computer- based modeling tools to evaluate cause-effect and impact to potential changes in a cost- effective manner (4). Or there may be consolidated stakeholders, like the JPDO referenced above, which enable derivation from common set of stakeholder requirements. The resulting impact on the process itself still follows the recursive and iterative activities of preparing, defining, analyzing, reviewing, and managing the system requirements. 4 Applicability to "Going Green" to transform this process so that it incorporates Green Engineering approaches. Green Engineering is the design and use of processes and products in a way that reduces pollution, promotes sustainability, and minimizes risk to human health and the environment without sacrificing economic viability and efficiency (3). There are opportunities to transform the systems requirement definition process by incorporating green engineering approaches by in the preparing, analyzing, and defining activities. This could be accomplished with the use of analytical tools and machined learning to assess requirement impacts and "what-ifs" to obtain early learning and knowledge points on cost/environmental benefit tradeoffs. For example, the Environmental Protection Agency has integrated computer-based tools to help assess risk (3). Furthermore, this includes ensuring that a requirement has the appropriate constraints, clarity, to establish systems requirements that embody green engineering by driving conservation and waste prevention from the initial design phase throughout sustainment.Reference/ Citations [1) INCOSE, & Wiley (2015). Incose systems engineering handbook : A guide for system life cycle processes and activities. John Wiley & Sons, Incorporated. [2) Forming nextgen: From vision to reality. Forming NextGen: From Vision to Reality | Federal Aviation Administration. (n.d.). Retrieved February 19, 2023, from https://www.faa.govextgen/background/forming [3) Environmental Protection Agency. (n.d.). Green Engineering. EPA. Retrieved February 19, 2023, from https://www.epa.gov/green-engineering/about-green-engineering [4) Ahmed, H., & Parry, T. (n.d.). Applying Random Parameters Model to Evaluate the Impact of Traffic. Retrieved February 19, 2023, from https://link-springer- com.proxy1.library.jhu.edu/content/pdf/10.1007/978-3-030-34069-8_1?pdf=chapter+toc [5) Siedle, J. (2015). Systems Requirements. University of Missouri-St. Louis. Retrieved February 19, 2023, from https://www.umsl.edu/-sauterv/analysis/F2015/System%20Requirements.html.htm [6) Weck, O. (n.d.). Fundamentals of Systems Engineering: Aeronautics and Astronautics. MIT OpenCourseWare. Retrieved February 19, 2023, from https://ocw.mit.edu/courses/16-842- fundamentals-of-systems-engineering-fall-2015/1. Summarize the SE process of the selected student paper. Summarize the selected SE process of the paper in one or two paragraphs. 2. Element Being Challenged Clearly describe the element being challenged, one paragraph. 3. Counterpoint Description Clearly and concisely state the counterpoint being proposed to challenge the author's position and trace it to the element of the paper being challenged. 4. Defense of Counterpoint Support your position (counterpoint). Opinion and belief are not adequate. Demonstrate critical systems thinking skills and draw on multiple sources as part of your defense. 5. References List all references cited in your paper, including those drawn upon to support your defense