TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Yes, I was talking about documenting 'Delete user' and 'modify
user' in the user's manual. I am not comfortable with the idea of
grouping the two functions (Modify User and Delete User) under
Create User. This is due to the fact that the next logical step
after creating a user is to create a role. Modify user function
would be used to change the user password etc.
Regards,
Dinesh
John Posada
wrote:-------------------------------------------------
I don't understand your question.
You HAVE those two functions assigned...they are on the list. Are
you
talking about Delete user and Modify user?
Structure it this way:
A) User:
1 Create User
1.1 Modify User
1.2 Delete User
B) Role:
2 Create Role
2.1 Modify Role
2.2 Delete Role
3 Assign User to a Role
You create a user, you then create a role, you then assign a User
to a Role.
While doing this, you may need to modify the user or delete a
user.
John Posada
Senior Technical Writer
Barnes&Noble.com
jposada -at- book -dot- com
NY: 212-414-6656
Dayton: 732-438-3372
"Alright, nobody move! I've got a dragon here, and I'm not afraid
to use it"
---------- Donkey
-----Original Message-----
From: Dinesh Nair [mailto:nair1975 -at- rediffmail -dot- com]
Sent: Monday, March 17, 2003 2:19 AM
To: TECHWR-L
Subject: organizing content based on logical flow of tasks
Hi all,
To increase the usability factor of a manual, we know that the
manual's
content structure should be based on tasks. But here I am stuck
with a
peculiar problem; the application is designed like this -
create user
modify user
delete user
create role
assign role to a user
Now if I structure the content according to a logical task-based
flow
1. create user
2. create role
3. assign role to the user
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Order RoboHelp X3 and receive a $100 mail-in rebate, plus FREE
RoboScreenCapture, WebHelp Merge Module and iMarkupSoftware, for a total
giveaway value of $473! Order here: http://www.ehelp.com/techwr-l
Help celebrate TECHWR-L's 10th Anniversary starting this month!
Check out the contests at http://www.raycomm.com/techwhirl/special/contests/
Happy birthday to you, happy birthday to you, happy birthday TECHWR-L....
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
