There are different artifacts (documents) for Use Case Description, Mock-up Screens and System Sequence Diagram. That is because each UML diagram (or table or description, Use Case Description has no diagram) can accommodate only a few modeling elements. Analysts often need a set of UML diagrams and descriptions to evolve and represent concepts. They have to be drawn quickly and iteratively to formulate and express the business concepts and requirements. They need to be created and edited together, not in isolation. It is here claimed that the contents of these three UML artifacts can be combined into a single text-document with tables & without drawings.

1. Putcha V. Narasimham
Founder Professor & Proprietor
Knowledge Enabler Systems
205, Krishna Apts, Avenue No 6, Banjara Hills,
Hyderabad 500034 India
kenablersys@yahoo.com or putchavn@yahoo.com
Our Ref: in the footer
Date: 08APR13, 10APR13, 24JAN14
Combined
Use Case Description,
Mock-up Screens, and
System Sequence Diagram
Being competent, effective and efficient is
90% mindset and 10% toolset
---Roger Tregear
The Context
There are different artifacts (documents)
for Use Case Description, Mock-up
Screens and System Sequence
Diagram. That is because each UML
diagram (or table or description, Use Case
Description has no diagram) can
accommodate only a few modeling
elements.
Analysts often need a set of UML diagrams
and descriptions to evolve and represent
concepts. They have to be drawn
quickly and iteratively to formulate
and express the business concepts and
5 Combined Use Case Description, Mock-up Screens and System Sequence Diagram
The Best Anywhere Must Reach the Needy Everywhere
Page No 1 of 10

2. Putcha V. Narasimham
Knowledge Enabler Systems
205, Krishna Apts, Avenue No 6, Banjara Hills,
Hyderabad 500034 India
kenablersys@yahoo.com or putchavn@yahoo.com
Founder Professor & Proprietor
requirements. They need to be created
and edited together, not in isolation.
Craig Larman and Scott Ambler strongly
recommend rough sketching (on
whiteboard or flipchart) to keep the
thoughts and discussions flowing rapidly
without losing vital information
generated. Good practice but their
writing too unreadable!
Combining the Contents of
Three UML Artifact
Let us study and combine the three
artifacts.
1: Use Case Description:
A narrative of the form “System
Offers….and Actor Selects……” or “Actor
requests…..and System Provides…….”. It
is an exchange of messages between the
System and Actor.
2: Mock-up screens (dialog
boxes):
They & their contents correspond to each
message, and
5 Combined Use Case Description, Mock-up Screens and System Sequence Diagram
The Best Anywhere Must Reach the Needy Everywhere
Page No 2 of 10

3. Putcha V. Narasimham
Knowledge Enabler Systems
205, Krishna Apts, Avenue No 6, Banjara Hills,
Hyderabad 500034 India
kenablersys@yahoo.com or putchavn@yahoo.com
Founder Professor & Proprietor
3: System Sequence Diagram
(SSD):
Commented [PN1]: This is proposed and used by Craig
Larman. Scott Ambler also uses the same concept but NOT
the name.
It shows the operations (functions) of the
system which are necessary to generate
the “system messages”.
In an SSD, the System as a whole is a black-box, generating
and presenting the screens to help Actor interactively
progress to the Use Case Goal.
The contents of 1 are repeated in 2
graphically and the same have to
reappear in 3, the System Sequence
Diagram. What is new in 3 are the
“Functions or Operations” that the
System as a whole must have. At this
stage there are NO known internal
objects of the System. They have to
evolve from the business data and
requirements. See Systematic identification of
Design Classes with LIVE Objects
http://www.slideshare.net/putchavn/systematicidentification-of-design-classes-with-live-objects
It is here claimed that the contents
of these three UML artifacts can
be combined into a single textdocument with tables & without
drawings. See the next page.
5 Combined Use Case Description, Mock-up Screens and System Sequence Diagram
The Best Anywhere Must Reach the Needy Everywhere
Page No 3 of 10

4. Putcha V. Narasimham
Founder Professor & Proprietor
Knowledge Enabler Systems
205, Krishna Apts, Avenue No 6, Banjara Hills,
Hyderabad 500034 India
kenablersys@yahoo.com or putchavn@yahoo.com
--:===:===:===Format of the combined document===:===:===:-On the left
System Operations &
Messages
System Acts first to enable interaction.
So it is moved to the left.
In the middle
Dialog-boxes or
mock-up screens
and
On the Right
Actor Actions and
Messages
This is quick, easy, expandable and precise. This does not need anything
more than formatting features of MS Word +Tables. No drawings!
You can also add Business Rules, Internal Resources Structures &
Processes since the formatting is NOT rigid.
Here is an example. The focus here is on the use of MS Word for modeling. You may or
may not agree with this way of modeling. That is another issue.
The combined document used for
Video Rental Support System
System Description:
This VRSS software system supports Video Rentals Shop operations in the real
world.
The system creates and maintains data on videos available including rental &
payment details. It is used by the Manager and Salespersons (staff) of Video
Rentals Shop to rent videos and charge for them.
System allows customers (registered or unregistered) to access video information
(via the Internet or at the Shop) and borrow and pay for selected vidoes. Thre is
penalty for late returns + incentive for recommendation.
For more details see the project documentation available from
kenablersys@yahoo.com.
5 Combined Use Case Description, Mock-up Screens and System Sequence Diagram
The Best Anywhere Must Reach the Needy Everywhere
Page No 4 of 10

5. Putcha V. Narasimham
Founder Professor & Proprietor
Knowledge Enabler Systems
205, Krishna Apts, Avenue No 6, Banjara Hills,
Hyderabad 500034 India
kenablersys@yahoo.com or putchavn@yahoo.com
Use Case Name: Enable Staff Operations
The system identifies a registered member of staff from general log-in and presents him or her
the options of work they can do. Many conditions and conditional behavior are all given in a
single presentation (over many pages of course).
Commented [PN2]: The second Use Case in the list is
taken. We need to apply it to all UCs to see how this works
out.
Preconditions: Manager of Sales person has successfully loged in. This is NOT
the general home page open to everyone. This is open only to staff.
System Action
Presents Welcome to Staff Functions (only for identified staff)
System
Message
>>> Welcome Screen #1>>>
The layout and colors are not binding. No UI designer implied
Screen #1
Commented [PN4]: Will NOT appear on the display. This
is for Screen ID
Welcome to VRSS
System
Commented [PN3]: This is from the System to Actor. The
color and direction reinforce the concept.
Staff Functions
Commented [PN5]: This can be sophisticated.
 Home
 Mange Videos
 Add New Video data
 View/Edit Video data
 Manage Customers
 View Rentals
If the staff is new. The system would say “Welcome to VRSS
Staff Functions. You are taking up these functions for the
first time. Please see demo and make sure you can carry
them out.
Welcomes to today’s business. This is the status. Please
make note of “special actions” for today. Management may
give special instructions for the day.
Return
Select what you wish to do.
De-automate:
This overrides system validations and
enables users to message the other users
and the system developers. This prevents
getting stuck when unforeseen situations
arise. Only messaging is allowed. Only the
affected services are overridden temporarily.
Not necessary but
visuals have their
charm
Commented [PN6]: This is a simple but very powerful
and safe technique to be used during development and
even during operation. This is a default option. The
message goes to the developers with the exact conditions
leading to the situation.
Many frustrating experiences of using ill-conceived
applications can be avoided with this.
Selects “Add New Video data”
Actor Actions
<<<ID and value TRUE of “Add New Video data” button<<<
Actor Message
Similarly when other options are selected the relevant interactions are given.
5 Combined Use Case Description, Mock-up Screens and System Sequence Diagram
The Best Anywhere Must Reach the Needy Everywhere
Page No 5 of 10
Commented [PN7]: If you think it is too techy, it may be
left blank. The client / users do not need to know it but the
system will not work unless the data and information of the
message are precise to this detail.

6. Putcha V. Narasimham
Founder Professor & Proprietor
Knowledge Enabler Systems
205, Krishna Apts, Avenue No 6, Banjara Hills,
Hyderabad 500034 India
kenablersys@yahoo.com or putchavn@yahoo.com
System Action
Selects the screen to be presented (here #2) and presents it.
System
Message
>>> Screen # 2 with instructions >>>
The layout and colors are not binding. No UI design implied
Add Video
Screen #2
System Generated
System generated
Pull-down menu and select one category
Video ID:
Video Price
Video
Category:
Description:
Enter Description here
Reset
Clears entries
Submit
System accepts entries
Cancel
to previous screen
Want to add one more Video?
YES
Reuse Sc #2
Commented [PN8]: When this option is used, the system
keeps track of all the videos added and informs “you have
added 2nd or 3rd or 4th Video.
NO of CLOSE,
to previous menu
Deautomate
Customer should know full account of all the actions taken
without having to check.
Possibility 1
Enters Video Title & Description and Presses Submit
Actor Actions
<<<Field / button IDs and contents and commands<<<
Actor Message
System Action
System
Message
Accepts and saves data for further processing
>>> Video Title & Description are saved.
Want to add another Video? See Screen #2>>>
The layout and colors are not binding. No UI designer implied
Screen #2 is not repeated
but it will display the message
5 Combined Use Case Description, Mock-up Screens and System Sequence Diagram
The Best Anywhere Must Reach the Needy Everywhere
Page No 6 of 10
Commented [PN9]: This was not originally thought of but
is added as the dialog and possibilities evolved. It may be
possible to reorganize and simplify. Corporate style /
conventions of UI may be applied. Some BAs may be
familiar and give right specifications.

7. Putcha V. Narasimham
Founder Professor & Proprietor
Knowledge Enabler Systems
205, Krishna Apts, Avenue No 6, Banjara Hills,
Hyderabad 500034 India
kenablersys@yahoo.com or putchavn@yahoo.com
Possibility 2
Enters some data in some fields and presses Reset
Actor Actions
<<<Field contents and Button Ids<<<
Actor Message
System Action
Resets all fields and presents blank Screen #2 with the following message
System
Message
>>> All entries are cleared. Fill Screen #2 or quit>>>
Possibility 3
Presses Cancel
Actor Actions
<<<Field / button IDs and contents<<<
Actor Message
System Action
Takes back to Welcome page in this case
System
Message
>>> Welcome Screen #1>>>
Possibility 4
Presses YES, want to add more videos
Actor Actions
<<< Id of button YES<<<
Actor Message
System Action
Presents Screen #2 again
System
Message
>>> Welcome Screen # 2 add one more video >>>
The layout and colors are not binding. No UI designer implied
5 Combined Use Case Description, Mock-up Screens and System Sequence Diagram
The Best Anywhere Must Reach the Needy Everywhere
Page No 7 of 10
Commented [PN10]: A suitable place for this message
must be provided on Screen #2. It should be clear that the
system is expecting one more video to be added.

8. Putcha V. Narasimham
Founder Professor & Proprietor
Knowledge Enabler Systems
205, Krishna Apts, Avenue No 6, Banjara Hills,
Hyderabad 500034 India
kenablersys@yahoo.com or putchavn@yahoo.com
Possibility 5
Presses NO --- back to previous menu
Actor Actions
<<< Id of button NO<<<
Actor Message
System Action
Windows 8 explanation of why the log in failed is very
helpful. It asked for password for Microsoft services. I was
under the impression it was Note Book PC access password.
Presents Screen #1 again
System
Message
>>> Welcome Screen #1>>>
The layout and colors are not binding. No UI designer implied
==:===:===END of Format of the combined document===:===:==
---III---
5 Combined Use Case Description, Mock-up Screens and System Sequence Diagram
The Best Anywhere Must Reach the Needy Everywhere
Commented [PN11]: The buttons HAVE TO BE
meaningfully labeled and ALSO explained. This is necessary
for the user to know what happens if the button is pressed.
Page No 8 of 10
Analysts and designers cannot CORRECTLY guess what all
the users would be thinking at various stages of their
interaction with the system.

9. Putcha V. Narasimham
Founder Professor & Proprietor
Knowledge Enabler Systems
205, Krishna Apts, Avenue No 6, Banjara Hills,
Hyderabad 500034 India
kenablersys@yahoo.com or putchavn@yahoo.com
Appendix I
System Sequence Diagram
Here is a System Sequence Diagram (SSD) per Craig Larman and Scott Ambler.
There is NO significant graphic information. It must have taken a long time creating it. I did not
do it. My student Ajaz Ali has done it. A table can give all this information in more readable and
editable form.
This is NOT a standard UML Diagram but it is very useful. It shows the System as single blackbox object interacting with an Actor for a Use Case. Based on the “Messages” of a Use Case
Dialog this SSD is helps identify possible functions or operations the System must have.
Then one can proceed to identify internal objects.
5 Combined Use Case Description, Mock-up Screens and System Sequence Diagram
The Best Anywhere Must Reach the Needy Everywhere
Page No 9 of 10

10. Putcha V. Narasimham
Founder Professor & Proprietor
Knowledge Enabler Systems
205, Krishna Apts, Avenue No 6, Banjara Hills,
Hyderabad 500034 India
kenablersys@yahoo.com or putchavn@yahoo.com
The diagram is OK but the messages have to be more elaborate and precise. All messages are
essentially references to other diagrams / screens. Much has to be recalled or imagined.
We need to see the screen mock-ups also but a single diagram cannot show all the screens
of a Use Case Dialog.
This combined document captures many minute details and presents them in multiple
pages.
===========================
Origin and chronology of this paper:
08APR13:
Started working on System Sequence Diagram TABLE. Here is how I opened it. Now
that will change.
Diagrams are very expressive but they are tough to create / edit and time
consuming. Try MS Word TABLES, they are quick, easy and precise.
Well, we do not even need tables if only THREE columns are sufficient. You can use
Left, Centre and Right Justifications for the three columns. And you have all the
space on the page!
Thought SSD Table would be a great idea. Started implementing it and found it to be
too constraining. Tables have to be inserted into tables. Space is less and a lot of
space was getting wasted. So, I used Left and Right justification and centered
the Tables. So, there is no need for outer table. The main screens can have all the
space they want on a page. The open format is really flexible. No need to mess with
tables.
11APR13
Well, Tables have their charm. I am using separate unconnected tables for System
Actions and Messages and Actor Actions and Messages.
24 JAN 14
Martin Crisp kindly reviewed and made some encouraging comments but observed
that the mock-up screens need more sophistication for which his “Power Story” is better.
I agree but I am trying to do the best that a Word document allows--not competing
with Power Story or other tools.
This is NOT very satisfactory. So, I hoped to improve it before publishing. Many
LinkedIn discussions came up and I had to refer to this document. So, I am uploading it
to slidesahre after minor editing. Constructive inputs are welcome.
---III--5 Combined Use Case Description, Mock-up Screens and System Sequence Diagram
The Best Anywhere Must Reach the Needy Everywhere
Page No 10 of 10