1. The LEO-ID system shall determine the orbit of LEO microsatellite targets (LMTs) that meet the...

Transcribed Image Text:

1. The LEO-ID system shall determine the orbit of LEO microsatellite targets (LMTs) that meet the LMT Specifications defined in Table X1. (Comment: Hereafter, all references to LMTs are limited to LMTs that meet the specifications defined in Table X1). 2. The LEO-ID system shall determine the orbit of LMTs that meet the LMT Observational Conditions Specifications. 3. The LEO-ID system shall have the capability to determine the orbits of up to 50 LMTs. 4. The LEO-ID system shall define the orbits of LMTs using standard formats. 5. The LEO-ID system shall estimate the orbits of LMTs to acceptable accuracies. 6. The LEO-ID System shall be user friendly and shall provide complete system backups. 7. The LEO-ID System will provide modularity for easy replacement. 8. The LEO-ID System shall meet all performance requirements 24 hours/day, 7 days/week. 9. The LEO-ID System shall track and report problems quickly 10. The LEO-ID System shall output Daily LMT Data Set (DLDS) from the MOC subsystem, via standard user interfaces 11. The LEO-ID System shall provide users with important information 12. The LEO-ID System shall make observations of targets that are in line-of-sight of SV1, as defined in Table X5 [table includes the following line-of-sight definition: 10-degree half- angle cone centered on SV1's plus (+) and minus (-) velocity vectors] 13. The SVI shall operate in LEO at altitudes of 500 km 14. The LEO-ID System shall operate with SV1 in LEO with inclinations of 35 15. The LEO-ID System shall not be susceptible to hacking 16. The LEO-ID System shall operate in all weather conditions 17. The MOC shall implement artificial intelligence-based algorithms executing on Cray supercomputers Perform requirements analysis of the requirements set provided above. Consider each of the six identified requirements evaluation criteria, and for each criterion identify one requirement from the list that satisfies it (pass), and one requirement that does not meet the criterion (fail). Be sure to note the requirement number for each and explain your reasoning below. Note: for technical areas outside your comfort zone, simply provide your assessment based on your engineering/technical judgement. 1. Necessary: a. Fail: (list a requirement number, and explain why it failed with respect to this criterion) b. Pass: (list a requirement number, and explain why it passed with respect to this criterion) 2. Implementation Independent: a. Fail: b. Pass: 3. Unambiguous: a. Fail: b. Pass: 4. Achievable: a. Fail: b. Pass: 5. Singular: a. Fail: b. Pass: 6. Verifiable: a. Fail: b. Pass: Module 6 Homework consists of 3 problems for a total of 100 points. Note: In addition to reading the text and lecture slides, you should review the Guide for Writing Requirements, Requirements Working Group, International Council on Systems Engineering (INCOSE), INCOSE-TP-2010-006-01, 17 April, 2012, available in Module 6 folder on Blackboard. (An updated version is available for INCOSE members from the INCOSE Book Store: https://connect.incose.org/pages/store.aspx Background: You are involved in the development of a new system called "LEO-ID." For this assignment, you are being asked to interpret a needs statement, analyze and assess requirements, perform functional analysis, and generate functional analysis artifacts and diagrams, specifically an OV-1 and a Context Diagram. Needs Statement: With the advent of low-cost spacecraft and launch services, there is a proliferation of microsatellites in LEO, and existing tracking systems are not able to determine the orbits of many of these spacecraft. The impact is that space system operators are left with a deficit in space situational awareness, increasing the risk of spacecraft collisions. There is a need for a new system to determine the orbits of multiple LEO microsatellite targets (LMTs) to augment existing systems and provide the data to users. Requirements: Your sponsor has performed a Needs Analysis, an architecture analysis and trade study/AoA, and has developed a ConOps and an initial system concept including the partitioning of system elements. The sponsor has provided specific system requirements for your system, LEO-ID, that will guide, and bound, your systems analysis and functional analysis activities. A subset of these requirements includes: 1. The LEO-ID system shall determine the orbit of LEO microsatellite targets (LMTs) that meet the LMT Specifications defined in Table X1. (Comment: Hereafter, all references to LMTs are limited to LMTs that meet the specifications defined in Table X1). 2. The LEO-ID system shall determine the orbit of LMTs that meet the LMT Observational Conditions Specifications. 3. The LEO-ID system shall have the capability to determine the orbits of up to 50 LMTs. 4. The LEO-ID system shall define the orbits of LMTs using standard formats. 5. The LEO-ID system shall estimate the orbits of LMTs to acceptable accuracies. 6. The LEO-ID System shall be user friendly and shall provide complete system backups. 7. The LEO-ID System will provide modularity for easy replacement. 8. The LEO-ID System shall meet all performance requirements 24 hours/day, 7 days/week. 9. The LEO-ID System shall track and report problems quickly 10. The LEO-ID System shall output Daily LMT Data Set (DLDS) from the MOC subsystem, via standard user interfaces 11. The LEO-ID System shall provide users with important information 12. The LEO-ID System shall make observations of targets that are in line-of-sight of SV1, as defined in Table X5 [table includes the following line-of-sight definition: 10-degree half- angle cone centered on SV1's plus (+) and minus (-) velocity vectors] 13. The SVI shall operate in LEO at altitudes of 500 km 14. The LEO-ID System shall operate with SV1 in LEO with inclinations of 35 15. The LEO-ID System shall not be susceptible to hacking 16. The LEO-ID System shall operate in all weather conditions 17. The MOC shall implement artificial intelligence-based algorithms executing on Cray supercomputers Perform requirements analysis of the requirements set provided above. Consider each of the six identified requirements evaluation criteria, and for each criterion identify one requirement from the list that satisfies it (pass), and one requirement that does not meet the criterion (fail). Be sure to note the requirement number for each and explain your reasoning below. Note: for technical areas outside your comfort zone, simply provide your assessment based on your engineering/technical judgement. 1. Necessary: a. Fail: (list a requirement number, and explain why it failed with respect to this criterion) b. Pass: (list a requirement number, and explain why it passed with respect to this criterion) 2. Implementation Independent: a. Fail: b. Pass: 3. Unambiguous: a. Fail: b. Pass: 4. Achievable: a. Fail: b. Pass: 5. Singular: a. Fail: b. Pass: 6. Verifiable: a. Fail: b. Pass: Module 6 Homework consists of 3 problems for a total of 100 points. Note: In addition to reading the text and lecture slides, you should review the Guide for Writing Requirements, Requirements Working Group, International Council on Systems Engineering (INCOSE), INCOSE-TP-2010-006-01, 17 April, 2012, available in Module 6 folder on Blackboard. (An updated version is available for INCOSE members from the INCOSE Book Store: https://connect.incose.org/pages/store.aspx Background: You are involved in the development of a new system called "LEO-ID." For this assignment, you are being asked to interpret a needs statement, analyze and assess requirements, perform functional analysis, and generate functional analysis artifacts and diagrams, specifically an OV-1 and a Context Diagram. Needs Statement: With the advent of low-cost spacecraft and launch services, there is a proliferation of microsatellites in LEO, and existing tracking systems are not able to determine the orbits of many of these spacecraft. The impact is that space system operators are left with a deficit in space situational awareness, increasing the risk of spacecraft collisions. There is a need for a new system to determine the orbits of multiple LEO microsatellite targets (LMTs) to augment existing systems and provide the data to users. Requirements: Your sponsor has performed a Needs Analysis, an architecture analysis and trade study/AoA, and has developed a ConOps and an initial system concept including the partitioning of system elements. The sponsor has provided specific system requirements for your system, LEO-ID, that will guide, and bound, your systems analysis and functional analysis activities. A subset of these requirements includes: