EdSoft
 software design group

2. Systems Requirements: Overview

Memorandum

 

From: Project Manager
To: Junior Software Engineers
Re: System Requirements

By the start of our project meeting next week, it would be helpful if you could decide what classes are implied by your set of use cases – btw, thanks for the good start.  Also, describe relationships between classes, list behaviors/functions that are required for objects of a class. And list the variables that will be members of each class. 

Your having done this thinking before the meeting will put our discussion on track and confirm for us that you are on top of your project.                                                                                               

To help me easily see what you have, draw a diagram in which each class is represented by a box, with the functions and variables listed inside the box. Lines between the boxes represent the relationships between classes. This is a simplified UML class diagram.

Continue the good work.

 

 

Up Arrow