Notes for 1/20/09


Jen (systems analyst), Brion (programmer), Sarah (systems analyst)

Overview of Project (Phil):

Review of Textual Business Requirements (Rob):

Review of Definition Visualization (Tom):


Review of Sample Use Cases (Joe):

“User is only able to edit something if they have it locked. Take advantage of SVN’s functionality…”  (Erika)

“It is a likely scenario that multiple users will be editing the same product catalog but different products” (Erika)

“The other thing to worry about is contract terms, and pricing may be dependent on the contract term. ” (Erika)

“Say you have this product that has this feature that relies on something in this other
project and then you have another version of the product, how do you handle that?”


“Considering removing the requirement to version individual products, since we don’t really need that, and leave everything at the catalog level.” (Erika)

“There won’t ever be a situation where we would want to have a product that exists in multiple catalogs that is updated across catalogs if it is updated in one” (Erika)

“There isn’t really a situation where we would ever add a new product to an old catalog” (Brion)

“It’s probably fine to just have the ability to create a product only when within a catalog” (Brion)

“Still want to be able to compare products across catalog versions. Don’t want to be able to compare products between two different catalogs” (Erika/Brion)


Rob’s idea: (that’s what they do now, so good call)
Product ID – constant
Product version – changes with catalog version

“Our rules don’t cross catalogs”

Some other common business rules:

“maybe in an ideal world we would lock people out form editing previous versions, but we don’t have to really worry about that” (Brion)
            - functionally there is no difference between old versions and a current version

Each time we make a change to a product we will be having a commit under the hood in SVN.

“Nice to have”

Each entity will have its own file.

Business rules need to be versioned (along with products and product catalogs)


Questions (Mark):




They ask:

“Do you think we need a type for the attribute?” (Erika)

“What do the business rules do?” (Brion)

“How does the concept of waivability fit in to this definition?” (Brion)