Notes for 2/10/09
- Technically contract term, region, and are attributes.
- Can we make them parameters?
- I don’t see why we couldn’t make them attributes.
- Requirements Document
- Locking and unlocking should be removed.
- There are comments Erika added to latest version. Take a look.
- There is no way to attributes to features.
- This was an oversight the use case should simply e reused.
- Business Rules can be applied at any level.
- If you were in the product view you could add it at the product level, but its not only applied to the product/product catalog
- As long as you can apply it on all levels it’s fine.
- User Interfaces
- Button for each Product/element has changed. (see view Product). This is incorrect on the product catalog view.
- So it’s like an explorer on the left? Yes
- Live Search
- Live Search acts as a filter in order to limit results (On the right)
- Is live Search something we need? Yes it might be helpful.
- The location of the search ox may not be intuitive. May need to be moved.
- How far does the list on the left go down
- Example is seen on the product
- You can double click and keep going down.
- Were you imaging multiple hierarchies to be expanded at once?
- We were thinking of having it. The way we have it
- Have an expand all from here, at like a product level, or feature level.
- We were thinking you could view all products on the right so you can scroll through on the right.
- We can have expand and minimize info
- It would be on the bottom of the nice to have list.
- Focus should be on functionality and not how nice it looks first and foremost.
- Erika was thinking about having as little white space as possible.
- If we can condense it for the presentation it could be a big help.
- The parameters of a feature can be sorted.
- Search for parameter waivabilty = yes and return that.
- Look into expanding search functions.
- Ranked high at top of nice to have list.
- The actual title of an element would show up.
- I think just seeing the version in the catalog is fine.
- Maybe just by doing on just that level is fine.
- What if we made it selectable from the product version, or we can have it display all versions at once.
- It could be a sub part of the hierarchy. Select a catalog select version, select product.
- What if we pick the catalog. And then pops it open.
- What about a Red Warning?
- It gets tricky cause when do you apply it.
- Conditional Attribute
- The attributes would be shown as a hierarchy, not reflected in blueprint prototype.
- Multiple Select on list is only for a define list of values or only a string.
- The user is never getting an actual value, evaluating them is not a function of the tool.
- There would be some default and not a false.
- It would be plausible to add a reference not on the file level and give a warning.
- Should we ever allow circular reference?
- Warning but do not limit.
- Same as a condition can be condensed or other view.
- So add condition is a row.
- Business rules are just tacked on
- Think about not sending huge info over the page.
- Think about scalabity. As making it an ility in the QA. That is what we need to think about. It there are other corcerns add it it into another section, Think about supplemental section.
- Think about fault tolerance.
- It still might be on separate files. Tak about it. Keep it on feature evel maybe. Weigh pros and cons.
- Think about what we are sending over.
- Erika will email out commented version.
- We will take a look at redefining search and how we display catalogs, (loading them, opening them)
- Add attributes to product catalog level
- A string is just a string, do not not need to limit length or anything.
- Add some notification to show that a product doesn’t exist in a version of product.
- Nice to have joint linking or joint expanding, not rewuired.
- A granular list of priorities would be nice.
- So when we collapse, collapse it to a single row.
- Make sure we have a collapse all row.
- Also allows us to have
- Rename as manage condition as to remove edit and add go to the same screen.
- For stuff next week, whatever we decide to step through add more screen shots. As to give context.
- Define what we mean by architectural views, other sections, specific without over writing.
- Usability
- So instead of saying instead of interfaces describe it different. “ad hoc” process and methods.
- Stratergy should be a way to present the information wheter its intuitive or not.
- Simplicity
- Add more desciption other than a ssystem. Rename this as intuituive-ility
- Perhaps combine with usability.
- Flexabiltiy
- Wording is wrong? May need to rethink.
- Low coupling
- The ocking needs to come up a level. Be on the product.
- Think about locking on the architecture.
- Add rejected solutions (paragraphs) and why we chose the current one.
- Fix Blueprint colors to make more readable.
- Practice presentation
- Action Items (w/ person responsible and dues dates)
- Remove locking of system on requirements document.
- Add attributes to product Catalog level
- View Erika’s Comment
- Change prototype for view product catalog.
- Rename section 2 of achitecture as architectural drivers, or add that in descrption.
- Send presentation draft to Erika by Friday morning