Advertisement

Communicating Via Diagrams

  • Elvis C. Foster
Chapter

Abstract

In the previous chapter, we discussed information gathering. Remember, as a software engineer, you do not gather information (or anything for that matter) just for the sake of doing so. Rather, there must be a purpose, and as pointed out earlier, your objective is the preparation of the project’s second major deliverable — the requirements specification. As you will soon see, this deliverable can be quite bulky, particularly if the software system is quite complex and/or large. In software engineering, we do not like unnecessary fluff; we promote comprehensive but succinct coverage.

Keywords

Software Engineer Finite State Machine Object Type Activity Diagram State Transition Diagram 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Copyright information

© Elvis C. Foster 2014

Authors and Affiliations

  • Elvis C. Foster
    • 1
  1. 1.MAUSA

Personalised recommendations