|
-
Contribute to the development of sections of systems engineering documentation such as System Engineering Plans, Initial Capabilities Documents, Requirements specifications, and Interface Control Documents
|
-
Manage system requirements and derived requirements to ensure the delivery of production systems that are compatible with the defined system architecture(s) – Department of Defense Architecture Framework (DoDAF), Service-oriented Architecture (SOA), etc
|
-
Assist with the development of system requirements, functional requirements, and allocation of the same to individual hardware, software, facility, and personnel components
|
-
Coordinate the resolution of action items from Configuration Control Board (CCB) meetings, design reviews, program reviews, and test reviews that require cross-discipline coordination
|
|
-
Participate in the development of system engineering documentation, such as System Engineering Plans, Initial Capabilities Documents, Requirements Specifications, and Interface Control Documents
|
|
|
|
-
Derive lower-level requirements from higher-level allocated requirements that describe in detail the functions that a system component must fulfill, and ensure these requirements are complete, correct, unique, unambiguous, realizable, and verifiable
|
|
-
Participate in establishing and gaining approval of the definition of a system or component under development (requirements, designs, interfaces, test procedures, etc.) that provides a common reference point for hardware and software developers
|
-
Define the methods, processes, and evaluation criteria by which the systems, subsystems and work products are verified against their requirements in a written plan
|
|
-
Develop derived requirements for Information Assurance Services (Confidentiality, Integrity, Non repudiation, and Availability); Basic Information Assurance Mechanisms (e.g., Identification, Authentication, Access Control, Accountability); and Security Mechanism Technology (Passwords, cryptography, discretionary access control, mandatory access control, hashing, key management, etc.)
|
|
-
Provide technical direction for the development, engineering, interfacing, integration, and testing of specific components of complex hardware/software systems to include requirements elicitation, analysis and functional allocation, conducting systems requirements reviews, developing concepts of operation and interface standards, developing system architectures, and performing technical/non-technical assessment and management as well as end-to-end flow analysis
|
|
|
-
Develop scenarios (threads) and an Operational Concept that describes the interactions between the system, the user, and the environment, that satisfies operational, support, maintenance, and disposal needs
|
|
-
Conduct quantitative analysis in non-functional system performance areas like Reliability, Maintainability, Vulnerability, Survivability, Produceability, etc.)
|
|
|
|
-
Establish a process to formally and proactively control and manage changes to requirements, consider impacts prior to commitment to change, gain stakeholder buy-in, eliminate ambiguity, ensure traceability to source requirements, and track and settle open actions
|
|
|
|
|
-
Support the development and review of Joint Capability Integration Development System (JCIDS) documents (i.e., Initial Capability Document, Capabilities Description Document, IA Strategy)
|
-
Provide technical direction for the development, engineering, interfacing, integration, and testing of all components of complex hardware/software systems to include requirements elicitation, analysis and functional allocation, conducting systems requirements reviews, developing concepts of operation and interface standards, developing system architectures, and performing technical/non-technical assessment and management as well as end-to-end flow analysis
|
|
|
|
|
-
Fully define interfaces in terms of origination, destination, stimulus, and data characteristics for software; and electrical and mechanical characteristics for hardware
|
|
-
Develop alternative courses of action, workarounds, and fall-back positions with a recommended course of action for each risk, and monitor and re-evaluate risks at appropriate milestones. Monitors risks using earned value management (EVM) data
|
-
Maintain knowledge of current and evolving agency, national, and international standards applicable to the system development of interest. Apply and enforce use of suitable standards to ensure consistency and interoperability of developer hardware and software
|
-
Ensure effective, periodic review and control of the evolving configuration of a system, both hardware and software components and associated documentation, during the life of the system
|
|
-
As a participant within an Analysis of Alternatives (AoA) effort, recommend a preferred solution based on selection criteria adjusted for reasonableness and validity of assumptions, technology limitations, environmental impact, and life-cycle costs
|
-
Develop system design alternatives that consider life cycle cost, reuse, complexity, risk, system expansion, and growth
|
|