Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - kelly_sumrall

Pages: 1 ... 3 4 [5]
61
General Board / Various elements not showing in the package browse
« on: June 20, 2002, 01:10:26 pm »
While experimenting, I added a new sequence element to a package.  It does not show in the package browser, but does show in the documentation and in the database.  I don't want to delete it from the database for fear of braking a relation.  Im I missing something?  How can I keep my project clean when the elements don't show in the project browser (explorer)?

62
Uml Process / Re: Which diagram is best to present system flow?
« on: July 13, 2006, 05:34:39 am »
Excellent idea Barry. I think I'll give it a try.

63
Uml Process / Re: Which diagram is best to present system flow?
« on: July 13, 2006, 05:13:08 am »
I recently created an activity diagram for a process flow similar to what Stefan suggested. The problem I ran into was when showing the printed black and white version to people, there was no clear distinction between user actions and system action. I did have the actions stereotyped (<<user>>, <<system>>), but they just blended in and served little use. I tried coloring the action elements, but that made some hard to read. Does anybody know of a practical solution to this.

64
Uml Process / Re: How to document an interactive/brochure websit
« on: August 02, 2006, 02:53:08 pm »
I am starting to see the error of my ways here. I'm new to the process of documenting requirements and have somehow gotten stuck with trying to put everything in a use case. That does not work. I need to learn how to determine what warrants its own use case and what just needs to be recorded as a requirement.
For example, if a site has secure sections that require authentication, how do you go about documenting the login requirements in a Word, or in EA? If the pages are secured via account permissions, the browser can handle all the login details for you, such as browsing a corporate intranet with IE. If the site uses a user id/password lookup login mechanism, that will require substantially more requirements documentation to answer questions about how errors are displayed, should you prevent login attempts after so many tries, etc.
Where/how do you document (or store in EA) these types of requirements so that the client can accept them and sign off on them?

65
Uml Process / Re: How to document an interactive/brochure websit
« on: July 13, 2006, 01:20:05 pm »
Bruce,

I've thinking about your opinion on Logging In never being a use case. That makes sense to me if it is at least a step in a more general use case. If that is the case, how do you go about documenting the log in requirements, such as using a userid/password combo or windows authentication?

66
Uml Process / Re: How to document an interactive/brochure websit
« on: July 13, 2006, 04:55:13 am »
Bruce,

Thanks for the reply. If these interactions don't qualify as use cases (and I'm not arguing that they do), how do you go about documenting the behavior and requirements of something like this? I treated each one as a use case, and while creating the scenarios, I actually discovered some alternate behaviors that my colleagues and I didn't think about during the initial brainstorming. How would you recommend documenting something like this so that the client could understand? It took us a couple of hours to get to a point where we all started envisioning  the same pattern, beforehand, we all had our own individual idea of how the site would function for the various user groups.

Quote
4. Why would a LoggedInUser invoke the LogIn "use case".  This seems to imply that you hae to be LoggedIn before you can LogIn

Good catch. It always helps to have another set of eyes.

This forum is my only link to people with the skill and experience of documenting requirements I have (can't communicate with a book), so please be liberal with suggestions.

Kelly

67
Uml Process / How to document an interactive/brochure website?
« on: July 12, 2006, 08:29:47 am »
I want to capture requirements for a new web project. This seems to be so basic, that I am a little embarrassed to be asking for advice, but, I want to get it right and show my colleagues in the office how good documentation can help a project. That being said, here is my situation.

I’m building a web site that is presented to three different user groups: Public User, Member User, and Administrative User. Here is a simple UC diagram. What are the thoughts of the forum members? I'm open to any critisism, as long as it is educational.

I think this is a common scenario and could be used as a “real world pattern” example on the wiki.



Use Cases...


[size=16]Browse Public Pages[/size]
User performs UC: Navigate to HomePage.
User requests a public page.
System displays the page.

[size=16]Create an Account[/size]
User makes a request to create a new account.
System displays Account Credentials setup page (username/password).
User supplies unique username and password.
System displays the profile page.
User fills in form fields.
[User submits form.]
System creates user account.
System displays the Logged In Homepage.

Alt:
Username is not unique.
At [User submits form.], System determines the username is not unique.
System creates suggestions.
System displays Account Credentials setup page with message indicating the user must enter a different username and offers suggestions.
[User submits form.]

Password does not match requirements.
At [User submits form.], System determines the password does not meet the requirements.
System displays Account Credentials stup page with message indicating the problem with the password.
[User submits form.]

[size=16]Browse Member Pages[/size]
[User requests a member page.]
System determines the user is logged in.
System displays the member page.

Alt:
User is not logged in.
At [User requests a member page.], System determines the user is not logged in. (This can happen if the request is coming from a bookmark or by typing the url directly.)
System performs UC: Log In

[size=16]Browse Administrative Pages[/size]
[User requests an administrative page.]
System determines the user is logged in.
System determines the user is a member of the administrative group.
System displays the administrative page.

Alt:
User is not logged in.
At [User requests an administrative page.], System determines the user is not logged in.
System performs UC: Log In

User is not a member of the administrative group.
System displays an error page with a message indicating the user is trying to access a protected page and they do not have permission.

[size=16]Log In[/size]
User makes a request to log in.
System displays the login page.
[User fills in the form.]
[User submits the form.]
System verifies account information.
[System displays member page.]

Alt:
Invalid Credentials
At [User submits the form.], System determines there is no account matching the submitted information.
System displays the login page with a message indicating the username or password is incorrect.

Login request comes from a redirect.
At [System displays member page.], system determines the login request came from an attempt to view a member page by a non logged in user.
System displays the originally requested member page.

[size=16]Navigate to HomePage[/size]
[User navigates to the HomePage.]
System determines the user is not logged in.
System displays the public page.

Alt:
User is logged in.
After [User navigates to the HomePage.], System determines User is logged in.
System determines User is not a member of the administrative group.
System displays Member HomePage.

User is logged in and member of administrative group.
After [User navigates to the HomePage.], System determines User is logged in.
System determines User is a member of the administrative group.
System displays Administrative HomePage.


68
Uml Process / Re: How to doc a simple scenario with few interact
« on: July 26, 2006, 06:31:27 am »
Thanks for the kind words (Tftkw) Bruce.  I'm actually still modifying (refactoring in Dev speak) this one. I'm wanting to combine UC: Browse Current Newsletter and UC: Browse Archived Newsletter into one use case since they share the same steps. I'm adding UC: Confirm Email to compliment UC: Signup to Receive Newsletters via Email since I now need to confirm the email used for sign up. I'll post them for further discussion/criticism when they are completed.

Kelly

69
Uml Process / How to doc a simple scenario with few interactions
« on: July 25, 2006, 05:31:53 am »
Hello Group,

I'm getting stumped trying to capture some of the subtleties of a simple feature. Here is my situation; I am designing a web site. The customer wants a section where visitors can go and read newsletters written by a member of the company. From that page, the visitor can read the current newsletter, open archived newsletters, and add their email to the newsletter mailing list. This is typical functionality that we should all be familiar with, but pretending that we’re not familiar with it, how would you go about capturing these requirements?
I'm currently working on the use cases for the site, but I don’t know how to capture this in a use case. This functionality seems to have three different user goals: browse current newsletter, browse archived newsletter (could even have an archive search feature, which would definitely be its own use case), and add email to mailing list. These user goals seem too simplistic to write as individual user goal oriented use cases, but, when taken together, indicate the developer (me) will need to write a fair amount of code. Take the following for example:

UC: Browse Current Newsletter
This use case is triggered when Visitor initiates a request to read a newsletter without specifying a specific date.

Visitor makes a request to read a newsletter.
System locates current newsletter and displays it.
Use Case Ends

UC: Browse Archived Newsletter
This use case is triggered when Visitor initiates a request to read a newsletter and specifies a specific date.

Visitor makes a request to read newsletter YYMM
System locates the newsletter and displays it.
Use Case Ends

Alternate Flow
System cannot find newsletter

System displays message indicting the newsletter cannot be found.

UC: Signup to Receive Newsletters via Email
This use case is triggered when Visitor submits email to System

Visitor submits in email and CAPTCHA.
[Verify CAPTCHA]
System verifies CAPTCHA.
[Add Email]
System adds email to mailing list.
System displays previous newsletter page with acceptance email.
Use Case Ends

Alternate Flow
CAPTCHA verification fails.
At [Verify CAPTCHA], System determines CAPTCHA is incorrect.

System displays previous newsletter page with error message indicating the CAPTCHA does not match what is expected.
Use Case Ends

Email already exists.
At [Add Email], System determines the list already contains the supplied email address.

System displays previous newsletter page with message indicating the email is already a part of the mailing list.
Use Case Ends


It just doesn’t seem right to create documentation like this. There’s no substance to it. So, what would be a way to capture/document user goals that don’t have much interaction with the system?

70
Uml Process / Re: Where to Store Narratives in EA
« on: July 13, 2006, 06:13:52 am »
Mike,

Have you figured out what you are trying to accomplish? If not, you could create a document template. From your resources tab, right-click Templates > RTF Style Templates and select Create RTF Style Template. You can copy an existing template to give you a head start, although if you are new to this, there is a big learning curve.

Does that help?

Kelly

71
Uml Process / Re: Set Element Classifier missing Base Types
« on: August 19, 2003, 05:42:45 am »
What is an Entity and how does it compare to a Class or an Object?

72
Uml Process / Re: Derive sequence diagrams from robustness diagr
« on: July 09, 2003, 06:34:23 am »
I don't know of a way to automate or transform a robustness diagram to an equivelant sequence diagram.  As I understand it, the robustness diagram is like a proof of concept, or a strating point to the more detailed sequence diagram.
You can however, change the robustness entities to entities of another class.  Just right click on the robustness object and select 'set Instance Classifier...' from the context menu.  This will bring up a dialog of available classes for you to choose.  This should get you started in your transformations.

73
Uml Process / Re: A first contribution on the PUP/EUP
« on: December 10, 2002, 12:20:33 pm »
Guys, I've got a simple question.  What is the desire here.  It's not to create a whole new process is it?  There are already a ton of well documented processes, UP, Agile, OMG Model Driven Architecture, and others.  I don't understand any of these as well as I understand code.  If I did, I don't think I would be excited about this topic.  I think that instead of defining a new process, we need to relate existing practices into the EA/ReqPro products.  If it turns out to be a process in its own right, then so be it.

74
Uml Process / Re: A first contribution on the PUP/EUP
« on: December 09, 2002, 06:29:37 am »
I don't know what exactly is being said here, but I am interested.  I am self taught programmer and I am new to the design and management philosophies of software engineering, but I recognize it as a vital part of the process.  I spend about 50+ hours a week developing (very little design) code for the project I am on.  Many more hours trying to understand how I can use UML in my designs.  No one at my company has any knowledge of UML, and everybody is too busy doing things tha way they have for years to learn.  Therefore, our documentation is very sparse and not standard.  I am very interested in getting involved in the xUP forum that is being proposed.  I have often thought we need a special section just for that purpose.  Count me in, even if all I can do is ask the dumb questions.  I look forward to understanding that wich I currently don't understand. ;D

Pages: 1 ... 3 4 [5]