SITEC

It's all starting to come together. The conversations get easier. It sure helps having the answers to the questions! haha!

Work Experience URL: Prescription Center - Customer Service: Contact Us

Writing Practice today... my mom and sister and I have randomly chosen some descriptives and will be writing a character prtrayal, post and critique each others writing...Let's see if I can find time between that and my regular web obsession, and work...

Rational support, documentation, user manuals

Learning those advanced features of Word was a treat. But it's time to move on. Today I discovered new templates in VIsio for UML, Web Site Mapping, and more!

For Dad's and people like him.. Keep in mind Microsoft is 1/3 the full picture, but every bit helps!

The Complete Internet Guide and Web Tutorial

How To - Word 2000 for Long Documents Part 2

How To - Word 2000 for Long Documents

Word for Windows 6.0: Managing long documents

Word Info: Working with long documents [WinWord 6 & 7]

Hi. I just turned in, for the 3rd time a document to my manager who unfortunately for me is also the CIO. I gave the document to her and to my CTO. Do I feel it's complete without any additional help? :::shrugs::::
Would I consider giving it to my client as is? :::shrugs again, thinking probably, but then they have been reviewing materials all along and this is nothing new..Just much much longer.::::
Do I think this document is my best effort as is? :::shugs again::: not really. But then I dont get impressed by technical documents. I think i left a few run on sentences, and my use of outline numbering and bullets leaves a little to be desired. Could it be improved? Probably, over time.
Could I improve it in the next hour and turn it in later? Possibly in part, but I dont want it anymore. I dont want to look at it again until it is time to take account Nancy's comments. The document is getting too unmangeable to correct online, as the diagrams don't all appear while viewing the doc. I found I had to, with the little memory I have, view it in print preview to confirm the diagrams were even there!

Cheers for now. Lift yourself for the weekend! This is painful, but slowly you will become a better writer!

Kate.

p.s. In defense, I know all the rules, and am not a bad writer, it's just that I get bored so quickly it is had to go back and correct my work over and over again. Short attention Span I say!

A Sapient Razorfish Design on Info Archictecture: AIGA : Gain

Travelling Garden Journal

Hi, Im trying to archive that use case thing.

On Writing Use Cases.

Today I have learned a little more about this thing called use cases. In my role as a business analyst, or one who anaylzes the busienss process, systems, and systems needs, I am gathering requirements to build a brand new system to allow emplyees to fill out their benefits enrollment forms online. (Can't tell you for whom!)

The Use Case descibes the system and user interaction. This serves two purposes. It shows the business users what they will be doing, and shows both the business user and the web developer what the system will be doing in return. Or more accurately, from a developers perspective, it shows when the system needs input from the user, and when the system provides data to the user.

My mission in the project begain as identifying current manual process and proposed business workflow. Having drawn up a workflow diagram, I set about to describe what was happening in the workflow, by writing a script. At the same time, I shared my diagrams and documents to date with my peers, those who have done projects from scratch, and they asked me where the Use Cases were. So I hunted down a Use Case template and noted the use of basic and alternate flows. This sounded perfect! Kill two birds with one stone,, as the syaing goes. (THough I would hate to think I would ever try to literally do that!) But none the less I set off on my merry way to write up the use cases that I one of my coworkers helped identify.

Throughout the writing process I slowly figured out when to use alternate flows, subflows, extension points, etc. One can only guess what they mean. I did a fair job, though admittedly whenat I wrote in the final uses cases may have been slightly different from the earlier ones!

Today my architect read them more thouroughly for me. He decided his initial take was a bit off from his current understanding. He also helped me realize the fine line between describing the DATA workflow, and a USERS workflow. The data has stuff happen to it prior to reaching the user, and other stuff after leaving the user, but the USe Case is to describe only the interaction between the one user and the system.

So having discussed and no re-written one of my docs, I feel better. The ideas of alternate flows are the same as from the beginning but more thourough now! And more accurate to the purpose of the scenario itself. Plus I know have a better sense as to how the description helps a designer or developer. It doesn't just show what the user does, but it shows the interaction between the user and the system. In fact it seems to talk about the passing back and forth FOR the data, but unlike the data flow, not the data itself. Did ya get that?

Until later! --kate

Sola Kate : Summer Dreams, Winter Steams!

hi. tuesday evening. I had a day of discovery as I ferreted out my beliefs and knowledge regarding the requriements phase of a project life cycle. does that mean anything to you? Write me.