Lesson 6

All too often, developers run into a problem with all kinds of assumptions about their own understanding of the problem.
We all know the dangers of making unfounded assumptions. So why do it? Take the time to evaluate closely the problem statement and to ask users questions.
Doing this will help you establish the context, scope, and constraints for the project. Promote quality communication and set a positive pattern of interaction for the rest of the project. In this module, you learned:

1. The importance of clarifying the problem statement
2. How to recognize context statements
3. How to recognize scope statements
4. How to recognize and address constraints
5. The importance of a data dictionary
6. How to set up a data dictionary

Goal setting takes time and energy, and you cannot be successful without a compelling project goal.
The extremely critical first step in creating software for each of your projects is to set a clear and compelling goal.
Questions:

1. What is the desired end result of your project?
2. What problem will this project solve?
3. What need will it fill?
4. How will this project change the way we do our business?

Many people managing in a project environment cannot readily answer these questions. Consider the result of this lack of knowledge.

1. Data dictionary: A data dictionary defines the vocabulary of the problem domain. Entries in the data dictionary can and will change over the course of a project, but they should change only when everyone involved in the project agrees to the change. Use a data dictionary to ensure consistent, high-quality communication.
2. Problem statement:A concise description of the project problem or challenge.
3. System: System refers to the set of all functions and resources that support the goal of the users.

Click the Quiz link below to take a short multiple-choice quiz on the material covered in this module.
Data Dictionary - Quiz