Skip to main content Accessibility help
×
Hostname: page-component-586b7cd67f-rdxmf Total loading time: 0 Render date: 2024-11-27T01:35:39.481Z Has data issue: false hasContentIssue false

Appendix A - Conventions Used in This Textbook

Published online by Cambridge University Press:  05 March 2016

Hassan Gomaa
Affiliation:
George Mason University, Virginia
Get access

Summary

For improved readability, certain conventions are used in this book. These are the naming conventions used in this book and the conventions for message sequence numbering on interaction diagrams.

NAMING CONVENTIONS USED IN THIS BOOK

For improved readability, the conventions used for depicting names of classes, objects, and so on in the figures are sometimes different from the conventions used for the same names in the text. In the figures, examples are shown in Times New Roman font. In the body of the text, however, examples are shown in a different font to distinguish them from the regular Cambria Math font. Some specific additional conventions used in the book vary depending on the phase of the project. For example, the conventions for capitalization are different in the analysis model (which is less formal) than in the design model (which is more formal).

REQUIREMENTS MODELING

In both figures and text, use cases are shown with initial uppercase and spaces in multiword names – for example, Cook Food.

ANALYSIS MODELING

The naming conventions for the analysis model are as follows.

CLASSES

Classes are shown with an uppercase initial letter. In the figures, there are no spaces in multiword names – for example, HeatingElement. In the text, however, spacing is introduced to improve the readability – for example, Heating Element.

Attributes are shown with a lowercase initial letter – for example, weight. For multiword attributes, there are no spaces between the words in figures, but spaces are introduced in the text. The first word of the multiword name has an initial lowercase letter; subsequent words have an initial uppercase letter – for example, sensorValue in figures and sensor Value in text.

The type of the attribute has an initial uppercase letter – for example, Boolean, Integer, or Real.

OBJECTS

An object may be depicted in various ways, in particular as:

  1. An individual named object. In this case, the first letter of the first word is lowercase, and subsequent words have an uppercase first letter. In figures, the objects appear as, for example, aWarningAlarm and anotherWarningAlarm. In the text, these objects appear as a Warning Alarm and another Warning Alarm.

Type
Chapter
Information
Publisher: Cambridge University Press
Print publication year: 2016

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure [email protected] is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

  • Conventions Used in This Textbook
  • Hassan Gomaa, George Mason University, Virginia
  • Book: Real-Time Software Design for Embedded Systems
  • Online publication: 05 March 2016
  • Chapter DOI: https://doi.org/10.1017/CBO9781139644532.025
Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

  • Conventions Used in This Textbook
  • Hassan Gomaa, George Mason University, Virginia
  • Book: Real-Time Software Design for Embedded Systems
  • Online publication: 05 March 2016
  • Chapter DOI: https://doi.org/10.1017/CBO9781139644532.025
Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

  • Conventions Used in This Textbook
  • Hassan Gomaa, George Mason University, Virginia
  • Book: Real-Time Software Design for Embedded Systems
  • Online publication: 05 March 2016
  • Chapter DOI: https://doi.org/10.1017/CBO9781139644532.025
Available formats
×