Skip to main content
SpringerLink
Log in

Technical measures for translating user needs to system requirements: a case study of a typical high-performance fighter aircraft

  • Published:
Sādhanā Aims and scope Submit manuscript

Abstract

Developing a usable system involves more than considering the user interface. The system should also fit into a context of use and meet user requirements. Successful project depends on meeting the needs and requirements of users or stakeholders throughout the system life cycle. The challenge is to represent user needs and user contexts, so that technical designers can use them directly. This paper highlights the importance of technical process/measures to be adapted in Systems Engineering (SE) for representing user needs and translating them into system requirements, with the goal of meeting user needs much before the delivery of the final system. Since technical measures process is an important part of the needs analysis phase in SE, emphasis is given on the use of technical measures as one of the best practices in SE with real world examples. It is also brought out on how technical measures are effective in performance evaluation of the system, and how they can be used in modelling and simulation to verify and validate the user's needs.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Log in via an institution

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Figure 1
Figure 2
Figure 3
Figure 4

(adapted from Ref [15]). (c) Take off distance plot for simulation vs flight test.

Figure 5

(adapted from Ref [15]). (b) Landing distance plot for simulation vs flight test.

Figure 6
Figure 7

Similar content being viewed by others

Abbreviations

Vstall :

Minimum flight speed

VTo :

Takeoff or liftoff speed

W:

Weight of the aircraft

ρ :

Air density

L:

Lift

CLmax :

Max coefficient of lift

S:

Wing surface area

D:

Drag

h:

Height of the aircraft above ground

T:

Thrust

SG :

Ground run

SR :

Rotation distance

STR :

Transition distance

SCL :

Climb distance

SA :

Air distance

SFR :

Free roll distance

SB :

Braking distance

VTD :

Touch down speed

V50 :

Speed at a height of 50 ft

Vs :

Stall speed

a:

Deceleration

m:

Meter

ft:

Feet

kms:

Kilometers

References

  1. ISO/IEC/IEEE International Standard—Systems and software engineering—System life cycle processes," in ISO/IEC/IEEE 15288 First edition 2015-05-15 , vol., no., pp. 1–118, 15 May 2015. https://doi.org/10.1109/IEEESTD.2015.7106435

  2. Coble J M, Karat J and Kahn M G “Maintaining a Focus on User Requirements Throughout the Development of Clinical Workstation Software”, In: Proceedings of the CHI'97, pp. 170-177, https://doi.org/10.1145/258549.258698

  3. Kyng M 1995 “Making representations work”, Communications of the ACM, Vol 38, Issue 9, 1995,pp 46-55, https://doi.org/10.1145/223248.223261

  4. Rumbaugh J 1994 “Getting started :Using use cases to capture requirements”, Journal of Object-Oriented Programming, September 1, Vol. 7, pp 8-12,23

  5. Systems Engineering Handbook, 2015, Fourth EditionINCOSE-TP-2003-002-04

  6. Garry J Roedler, Cheryl Jones, 2005 “INCOSE Technical Measurement guide”

  7. Guide to Systems Engineering Body of Knowledge (SEBoK) 2017, V1.8, March

  8. PSM. 2000. Practical Software and Systems Measurement (PSM) Guide, version 4.0c. Practical Software and System Measurement Support Center. Available at: http://www.psmsc.com/PSMGuide.asp

  9. “NASA Systems Engineering Handbook”, NASA/SP-2007-6105 Rev1, 2007

  10. “NASA Systems Engineering Process and Requirements”, NPR 7123.1B, 2013

  11. Noel Sproles, “Formulating measures of effectiveness”, John Wiley & Sons, Inc. Systems Engineering, Vol. 5, No. 4, 2002

  12. “Systems Engineering Fundamentals”, Defence Systems Management 1999 College Press, Fort Belvoir Virginia

  13. Leite M J and Mensh D R 1999 Definition of Evaluation Criteria for System Development Acquisition Modeling and Simulation. Naval Engineers Journal 111: 55–64. https://doi.org/10.1111/j.1559-3584.1999.tb01219.x

    Article  Google Scholar 

  14. Chowhan K S 2016 A Configurable Simulation Framework to Aid the System Design of Precision Landing and Take-Off System for High Performance Flying Vehicle. INCOSE International Symposium 26: 250–263. https://doi.org/10.1002/j.2334-5837.2016.00329.x

    Article  Google Scholar 

  15. Nicolai L M and Carichner G ProQuest, Fundamentals of aircraft and airship design. Volume 1, Aircraft design. Reston, Va.: American Institute of Aeronautics and Astronautics, 2010

  16. Cooper Harper 1969, ‘The Use of Pilot Rating in the Evaluation of Aircraft Handling Qualities’, NASA TND-5153

Download references

Author information

Authors and Affiliations

  1. Department of Aerospace Engineering, Indian Institute of Technology Bombay, Mumbai, 400076, India

    Kishan S Chowhan & Hemendra Arya

  2. Aeronautical Development Agency, Bangalore, 560017, India

    Kishan S Chowhan & Girish S Deodhare

Authors
  1. Kishan S Chowhan
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Hemendra Arya
    View author publications

    You can also search for this author in PubMed Google Scholar

  3. Girish S Deodhare
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Kishan S Chowhan.

Rights and permissions

Reprints and permissions

About this article

Check for updates. Verify currency and authenticity via CrossMark

Cite this article

Chowhan, K.S., Arya, H. & Deodhare, G.S. Technical measures for translating user needs to system requirements: a case study of a typical high-performance fighter aircraft. Sādhanā 47, 100 (2022). https://doi.org/10.1007/s12046-022-01873-8

Download citation

  • Received:

  • Revised:

  • Accepted:

  • Published:

  • DOI: https://doi.org/10.1007/s12046-022-01873-8

Keywords

Search

Navigation