This document provides an introduction to printing and reporting features in Rational Rose 98i. It outlines objectives to print diagrams and specifications and use reports, including usage reports, instance reports, access violation reports, SODA reports, participant reports, and documentation reports. The document describes setting printer options, printing diagrams and specifications, viewing page breaks, and generating various reports. It concludes with an exercise to run the different reports.
In ArcGIS, a data model describes the thematic layers used in the applications (for example, hamburger stands, roads, and counties); their spatial representation (for example, point, line, or polygon); their attributes; their integrity rules and relationships (for example, counties must nest within states).
This document contains some basic scenarios which should be tested while testing any BI (Business Intelligence) reports.
Prepared By:
Rakesh Hansalia
in.linkedin.com/in/rakeshhansalia/
In ArcGIS, a data model describes the thematic layers used in the applications (for example, hamburger stands, roads, and counties); their spatial representation (for example, point, line, or polygon); their attributes; their integrity rules and relationships (for example, counties must nest within states).
This document contains some basic scenarios which should be tested while testing any BI (Business Intelligence) reports.
Prepared By:
Rakesh Hansalia
in.linkedin.com/in/rakeshhansalia/
Explore the various ways to create asset specifications. Learn how to standardize and track all types of asset data including work order/asset relationships and reporting.
How to add a file to an application in service nowMy Guide
Created by www.myguide.org, Create your own Guides with videos via www.myguide.org
Tour : How to Add a File to an Application in ServiceNow
1. Welcome to MyGuide
2. Search for "Studio" in filter navigator box
3. Click on "Studio"
4.
5. Click on "Create New"
6. Some relevant information
7. Use the Search field to locate the application file type of your choice, or browse the categories
8. Select the application file type
9. Click on "Create"
10. Configure the file options. Fields preceded by an asterisk are required
11. Click on "Controls"
12. Controls Section
13. When you are done with all changes, click on "Submit"
Created by www.myguide.org, Create your own Guides with videos via www.myguide.org
Project Overview
Project Requirements
Our PROG 24178 project is a group project in which two students collaborate equally to create an
object-oriented program of medium complexity. It should be a GUI program that uses principles,
best practices and technologies learned in the course. Certain elements are a required part of
your project, for example it must implement a GUI of reasonable complexity, use a dynamic data
structure like ArrayList, Has multiple classes with defined class relationships, exception handling,
and use file input and/or output (further details below in General Requirements).
The rest is up to you.
Each student group will choose their own idea for their application and submit a project proposal
outlining their idea. For the GUI portion of the project, you will use the JavaFX platform. You can
design your GUI graphically with SceneBuilder, or implement it dynamically in code. This choice,
along with other detailed plans, must be clearly stated in the project proposal.
Above all your project should be interesting and fun, so try to choose an idea you find interesting
or potentially useful. Dont make your project too big or ambitious, remember it should take about
as much time as two or three assignments. If you feel your project may be too big then you could
simplify certain portions or leave parts for future implementation. For example, a GUI button could
display a message Not yet implemented. After you are done, you may want to add your project to
your SLATE ePortfolio (Sheridan co-curricular record) to show off to others.
General Requirements
GUI Portion: The project will consist of at least 2 GUI windows or dialogs (minimum one per team
member). In JavaFX this means at least 2 stages, where each stage has its own separate FXML
file and controller class. Error messages or simple confirmation dialogs dont count.
Non-GUI Portion: Minimum one class per team member so minimum two back-end (data
management) classes, not counting GUI classes or controller classes.
File I/O: Either file input, output, or both. For example, a program that manages information about
customers of a business could store the customer information in a file and then re-load the file
next time your run the program.
Data structures: ArrayList (dynamic array) or HashMap. For example a multi-player game could
use an ArrayList of Player objects to store information about all the players. Often (but not always)
you may use a dynamic data structure like ArrayList to store information you read from a file. Dont
use regular Java arrays.
Exception Handling: For full marks your project should contain enough exception handling and
error recovery so that bad user input (or bad input files etc.) dont crash the program. You should
display a user-friendly error message instead.
Commenting: The code shall be commented as follows.
Each Java class shall have a header comment which lists the principal author(s) of the code and
briefly describes what the code in the file is.
Explore the various ways to create asset specifications. Learn how to standardize and track all types of asset data including work order/asset relationships and reporting.
How to add a file to an application in service nowMy Guide
Created by www.myguide.org, Create your own Guides with videos via www.myguide.org
Tour : How to Add a File to an Application in ServiceNow
1. Welcome to MyGuide
2. Search for "Studio" in filter navigator box
3. Click on "Studio"
4.
5. Click on "Create New"
6. Some relevant information
7. Use the Search field to locate the application file type of your choice, or browse the categories
8. Select the application file type
9. Click on "Create"
10. Configure the file options. Fields preceded by an asterisk are required
11. Click on "Controls"
12. Controls Section
13. When you are done with all changes, click on "Submit"
Created by www.myguide.org, Create your own Guides with videos via www.myguide.org
Project Overview
Project Requirements
Our PROG 24178 project is a group project in which two students collaborate equally to create an
object-oriented program of medium complexity. It should be a GUI program that uses principles,
best practices and technologies learned in the course. Certain elements are a required part of
your project, for example it must implement a GUI of reasonable complexity, use a dynamic data
structure like ArrayList, Has multiple classes with defined class relationships, exception handling,
and use file input and/or output (further details below in General Requirements).
The rest is up to you.
Each student group will choose their own idea for their application and submit a project proposal
outlining their idea. For the GUI portion of the project, you will use the JavaFX platform. You can
design your GUI graphically with SceneBuilder, or implement it dynamically in code. This choice,
along with other detailed plans, must be clearly stated in the project proposal.
Above all your project should be interesting and fun, so try to choose an idea you find interesting
or potentially useful. Dont make your project too big or ambitious, remember it should take about
as much time as two or three assignments. If you feel your project may be too big then you could
simplify certain portions or leave parts for future implementation. For example, a GUI button could
display a message Not yet implemented. After you are done, you may want to add your project to
your SLATE ePortfolio (Sheridan co-curricular record) to show off to others.
General Requirements
GUI Portion: The project will consist of at least 2 GUI windows or dialogs (minimum one per team
member). In JavaFX this means at least 2 stages, where each stage has its own separate FXML
file and controller class. Error messages or simple confirmation dialogs dont count.
Non-GUI Portion: Minimum one class per team member so minimum two back-end (data
management) classes, not counting GUI classes or controller classes.
File I/O: Either file input, output, or both. For example, a program that manages information about
customers of a business could store the customer information in a file and then re-load the file
next time your run the program.
Data structures: ArrayList (dynamic array) or HashMap. For example a multi-player game could
use an ArrayList of Player objects to store information about all the players. Often (but not always)
you may use a dynamic data structure like ArrayList to store information you read from a file. Dont
use regular Java arrays.
Exception Handling: For full marks your project should contain enough exception handling and
error recovery so that bad user input (or bad input files etc.) dont crash the program. You should
display a user-friendly error message instead.
Commenting: The code shall be commented as follows.
Each Java class shall have a header comment which lists the principal author(s) of the code and
briefly describes what the code in the file is.
To set print options Select the File:Print Setup menu command. The default printer must be accessible.
To print Rational Rose diagrams Select the File:Print Diagrams menu command. Select the desired options. Click the OK button to print the selected diagrams. The default printer must be accessible.
To print specifications Select the File:Print Specifications menu command. Select the desired specifications. Click the OK button to print the selected specifications and close the Print Specifications window. The default printer must be accessible.
To view page breaks Select the View:Page Breaks menu command. This is helpful if the diagram contains a lot of classes. Trick: Select the Fit to Window button to zoom in and you can see all the pages. You may need to relocate classes for a cleaner printed page.
To run the Show Usage Report Select the desired element on a diagram (actor, use case, package, class, object, component, or node). Select the Report:Show Usage menu command. To navigate to a selected diagram in the Show Usage report Click to select the diagram in the Show Usage report. Click the Browse button. To close the Show Usage report Select the Cancel button.
To run the Show Instances Report Select the desired class on a class diagram. Select the Report:Show Instances menu command. To navigate to a selected diagram in the Show Instances report Click to select the diagram in the Show Instances report. Click the Browse button. To close the Show Instances report Select the Cancel button.
To show objects not assigned to classes Open a sequence or a collaboration diagram. Select the Report:Show Unresolved Objects menu command. To navigate to a selected diagram in the Show Unresolved Objects report Click to select the diagram in the Show Unresolved Objects report. Click the Browse button. A sequence diagram or a collaboration diagram must be the current diagram for this report to appear in the Report submenu.
To show messages not assigned to operations Open a sequence or a collaboration diagram. Select the Report:Show Unresolved Messages menu command. To navigate to a selected diagram in the Show Unresolved Messages report Click to select the diagram in the Show Unresolved Messages report. Click the Browse button. A sequence diagram or a collaboration diagram must be the current diagram for this report to appear in the Report submenu.
To run the Show Access Violations Report Select the Report:Show Access Violations menu command. An access violation occurs when: 1) a class in one package references a class in another package but there is no relationship between the packages 2) a class references a class in another package whose export control is set to implementation.
To generate a report using Rational SoDA Select the Report:SoDA Report menu command. Select the desired report. Click the OK button.
To show all the components, classes, and operations that participate in a use case Click to select a use case on a use case diagram. Select the Report:Show Participants in UC menu command. To control what type of element is displayed Click the Components, Classes, and Operations checkboxes to toggle the selection. To navigate to a selected element in the Participants report Click to select the element in the Participants report. Click the Gotoit button to go to the selected element in the Browser. To open the specification for a selected element in the Participants report Click to select the element in the Participants report. Select the Open it button.
To generate a data dictionary Select the Report:Documentation Report menu command. Select the desired options. Selected the Generate Selected button to generate the report for the items selected in the Browser. Select the Generate button to generate the report for all classes in the model.