The document outlines 11 functional requirements for a graphical user interface for the SCIMITAR software: 1. Prepare a scene by opening a file or metafile entry and setting resolution parameters. 2. Set the resolution by entering or loading parameters and making the scene active. 3. Update a metafile entry by creating a new entry and storing resolution parameters. 4. Set the workspace by saving or restoring resolution parameters from a loaded file.

1. SOFTWARE REQUIREMENTS
SPECIFICATION
Tittle : SCIMITAR Graphical User Interface

2. MATHEMATICS 3
TR1413
NUR HASANAH BINTI SARIJUDIN
A141979
TK2

3. 1.0 : STATEMENT OF
FUNCTIONAL REQUIREMENT

4. 1- PREPARE SCENE
• Description:
– The user chooses a scene file from the file system or via a
Metafile entry, sets its resolution parameters and makes
the scene active in the system. The user can optionally
save or retrieve parameters from a workspace file.
• Precondition:
– SCIMITAR base window is displayed.
• Trigger Condition:
– The user selects the Open Scene option under the File
menu.

5. 2- SET RESOLUTION
• Description:
– The user sets the appropriate resolution parameters for
the scene to be displayed as active. The user can either
enter the data or loaded it from the Metafile database.
• Precondition:
– The user selects a file or a metafile entry on the Open
Scene window.
• Trigger Condition:
– The user clicks the Open button on the Open Scene
window.
– The user clicks the Left-Arrow button on the Open Scene
window.

6. 3- UPDATE METAFILE
• Description:
– The user creates a new metafile entry for a new scene file
and stores its resolution parameters.
• Precondition:
– The Open Scene window is displayed and a file is selected
from the Browse area.
• Trigger Condition:
– The user clicks the Left-Arrow button on the Open Scene
window.

7. 4- SET WORKSPACE
• Description:
– The user saves the resolution parameters that have been
set for the active workspace or restores parameters from
the loaded workspace file.
• Precondition:
– SCIMITAR Base scene is displayed.
• Trigger Condition:
– The user selects the Save Workspace scene from the File
menu.
– The user clicks the Restore to Defaults button on the
Footprints tab under the Detection window.

8. 5- ADD OBSCURANT
• Description:
– The user adds obscurants to the active scene. The user can add
White Phosphorous obscurant or run the COMBIC92 and
PILOT81 obscurant routines to add other types of obscurants.
• Precondition:
– There is an active scene loaded in the system.
• Trigger condition:
– The user selects White Phosphorous from the Obscurants
walking menu under the Image Tools menu.
– The user selects COMBIC92 from the Obscurants walking menu
under the Image Tools menu.
– The user selects PILOT81 from the Obscurants walking menu
under the Image Tools menu.

9. 6- CHANGE RESOLUTION
• Description:
– The user changes the resolution of the active scene.
• Precondition:
– There is an active scene loaded in the system.
• Trigger condition:
– The user selects the Change Resolution option under the
Image Tools menu.

10. 7- ANALYZE SCENE
• Description:
– The user runs detection routines on an active scene and
obtains detection data that can be saved to image files (for
Aimpoint viewing) or result files (for exporting to Excel
worksheets). The user can modify the active scene prior to
detection run by adding obscurants and/or changing its
resolution.
• Precondition:
– The Base window is displayed; a scene has been loaded.
• Trigger condition:
– User selects Detection under the Image Tools menu.

11. 8- SET FOOTPRINTS
• Description:
– The user sets one or more footprints by specifying their
size and position(s) over the active scene.
• Precondition:
– There is an active scene loaded in the system and the user
has selected a detection.
• Trigger condition:
– The user selects the Footprints tab under the Detection
window.

12. 9- SET TARGETS
• Description:
– The user sets targets by specifying their size, outline and
location over the active scene.
• Precondition:
– There is an active scene loaded in the system and the user
has selected a detection.
• Trigger condition:
– The user selects the Targets tab under the Detection
window.

13. 10- VIEW AIMPOINTS
• Description:
– The user views thumbnails of detection results and selects
each one to see the full-sized version. The user can save
the result images to a bitmap file.
• Precondition:
– There is an active scene loaded on the system, a detection
routine has been run and the detection results have not
been cleared.
• Trigger condition:
– The user clicks the View Aimpoints button under the
Detection tab of the Detection window.

14. 11- SAVE DETECTION RESULTS
• Description:
– The user saves the detection results to a results file
that can be further exported into an Excel worksheet.
• Precondition:
– There is an active scene loaded on the system, a
detection routine has been run and the detection
results have not been cleared.
• Trigger condition:
– The user clicks the Save Results button under the
Detection tab of the Detection window.

15. 2.0 : MATHEMATICAL STATEMENT
OF THE FUNCTIONAL
REQUIREMENT

16. 1- PREPARE SCENE
• Propositional Calculus:
open_scene: the user chooses a scene file
file_system: from file system
metafile_entry: from metafile entry
open_scene => file_system ⊻ metafile_entry
set_scene: the user set opened scene
set_resolution_parameters: set scene resolution parameters
scene_active: makes scene active in the system
set_scene => set_resolution_parameters ^ scene_active

17. • Predicate Calculus:
open(scene): the user chooses a scene file
select(file_system): from file system
select(metafile_entry): from metafile entry
open(scene) => select(file_system) ⊻ select(metafile_entry)
set(scene): the user set opened scene
set(resolution_parameters): set scene resolution parameters
active(scene): makes scene active in the system
set(scene) => set(resolution_parameters) ^ active(scene)

18. 2- SET RESOLUTION
• Propositional Calculus:
set_resolution: the user set resolution
set_resolution_parameters: set scene resolution parameters
scene_active: makes scene active in the system
set_resolution => set_resolution_parameters ^
scene_active
set_resolution_parameters: set scene resolution parameters
enter_parameters: enter resolution parameters
load_metafile: load parameters from metafile database
set_resolution_parameters => enter_parameters ⊻
load_metafile

19. • Predicate Calculus:
set(resolution): the user set resolution
set(resolution_parameters): set scene resolution parameters
active(scene): makes scene active in the system
set(resolution) => set(resolution_parameters) ^
active(scene)
set(resolution_parameters): set scene resolution parameters
enter(parameters): enter resolution parameters
load(metafile): load parameters from metafile database
set(resolution_parameters) => enter(parameters) ⊻
load(metafile)

20. 3- UPDATE METAFILE
• Propositional Calculus:
create_metafile: the user creates a new metafile entry
enter_resolution_parameters: enter resolution parameters
store_resolution_parameters: enter resolution parameters
create_metafile => enter_resolution_parameters ^
store_resolution_parameters

21. • Predicate Calculus:
create(metafile): the user creates a new metafile entry
enter(resolution_parameters): enter resolution parameters
store(resolution_parameters): enter resolution parameters
create(metafile) => enter(resolution_parameters) ^
store(resolution_parameters)

22. 4- SET WORKSPACE
• Propositional Calculus
set_active_workspace: the user set for active workspace
save_resolution_parameters: save the resolution parameters
that have been set
restore_resolution_parameters_: restore resolution
parameters from loaded workspace file
set_active_workspace => save_resolution_parameters v
restore_resolution_parameters

23. • Predicate Calculus
set(active_workspace): the user set for active workspace
save(resolution_parameters): save the resolution parameters
that have been set
restore(resolution_parameters): restore resolution
parameters from loaded workspace file
set(active_workspace) => save(resolution_parameters) v
restore(resolution_parameters)

24. 5- ADD OBSCURANT
• Predicate Calculus
add_obscurant: the user adds obscurants to the active scene
add_white_phosphorous: add white phosphorous obscurant
run_COMBIC92: run COMBIC92 obscurant routines
run_PILOT81: run PILOT81 obscurant routines
add_obscurant => add_white_phosphorous v
(run_COMBIC92 ^ run_PILOT81)

25. • Predicate Calculus
add(obscurant): the user adds obscurants to the active scene
add(white_phosphorous): add white phosphorous obscurant
run(COMBIC92): run COMBIC92 obscurant routines
run(PILOT81): run PILOT81 obscurant routines
add(obscurant) => add(white_phosphorous) v
(run(COMBIC92) ^ run(PILOT81))

26. 6- CHANGE RESOLUTION
• Propositional Calculus
change_resolution: the user changes the resolution of the
active scene
set_new_resolution: set new resolution
change_resolution => set_new_resolution

27. • Predicate Calculus
change(resolution): the user changes the resolution of the
active scene
set_new(resolution): set new resolution
change(resolution) => set_new(resolution)

28. 7- ANALYZE SCENE
• Propositional Calculus
obtain_detection: the user obtains detection data
save_as_image_files: save detection data to image files
save_as_result_files: save detection data to result files
obtain_detection => save_as_image_files v save_as_result_files
modify_active_scene: the user modify the active scene
add_obscurant: adding obscurants
change_resolution: changing active scene resolution
modify_active_scene => add_obscurant v change_resolution

29. • Predicate Calculus
obtain(detection): the user obtains detection data
save_as(image_files): save detection data to image files
save_as(result_files): save detection data to result files
obtain(detection) => save_as(image_files) v save_as(result_files)
modify(active_scene): the user modify the active scene
add(obscurant): adding obscurants
change(resolution): changing active scene resolution
modify(active_scene) => add(obscurant) v change(resolution)

30. 8- SET FOOTPRINTS
• Propositional Calculus
set_footprint: the user sets one or more footprints
specify_size: specifying footprint size
specify_position: specifying footprint position
set_footprint => specify_size ^ specify_position

31. • Predicate Calculus
set(footprint): the user sets one or more footprints
specify(size): specifying footprint size
specify(position): specifying footprint position
set(footprint) => specify(size) ^ specify(position)

32. 9- SET TARGETS
• Predicate Calculus
set_target: the user sets targets
specify_size: specifying target size
specify_outline: specifying target outline
specify_location: specifying target location
set_target => specify_size ^ specify_outline ^
specify_location

33. • Predicate Calculus
set(target): the user sets targets
specify(size): specifying target size
specify(outline): specifying target outline
specify(location): specifying target location
set(target) => specify(size) ^ specify(outline) ^
specify(location)

34. 10- VIEW AIMPOINTS
• Propositional Calculus
view_aimpoint: the user view full-sized aimpoints
view_thumbnail: view thumbnails of detection results
select_thumbnail: select each one thumbnail
view_aimpoint => view_thumbnail ^ select_thumbnail

35. • Predicate Calculus
view(aimpoint): the user view full-sized aimpoints
view(thumbnail): view thumbnails of detection results
select(thumbnail): select each one thumbnail
view(aimpoint) => view(thumbnail) ^ select(thumbnail)

36. 11- SAVE DETECTION RESULTS
• Propositional Calculus
obtain_result_file: the user obtain results file
save_detection: saves the detection results
obtain_result_file => save_detection
obtain_excel_worksheet: the user obtain excel worksheet
export_result_file: saves the detection results
obtain_excel_worksheet => export_result_file

37. • Predicate Calculus
obtain(result_file): the user obtain results file
save(detection): saves the detection results
obtain(result_file) => save(detection)
obtain(excel_worksheet): the user obtain excel worksheet
export(result_file): saves the detection results
obtain(excel_worksheet) => export(result_file)

38. 3.0 : COMMENT ABOUT THE
TRANSLATION PROCESS FROM NATURAL
LANGUAGES STATEMENTS TO
MATHEMATICAL STATEMENTS.

39. • The translation process from natural language
statements to mathematical statements are widely
used in computer programming:
- Mathematical language act as problem solving for
programmer to do programming by translating the
mathematical statements into high-level language.
- We need to identify the idea first before we could
translate the natural language statement into
mathematical statements
- After we know the mathematical statements, then we
can compile it into high-level language and do the
programming.