Artifacts Involved in the Requirements Phase
page 6 of 8
by Uday Denduluri
Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days): 40953/ 89

Use Case Document

Use case is a Unified Modeling Language (UML) technique to capture the requirements in form of a figure. A use case diagram displays relationships between Actors and a Use case. An actor represents a user or another system that will interact with the system. A Use case is the system that we are currently showing. Let us see some Use case diagrams before we actually go through the UML documents.

Figure 2 shows a use case which explains all the operations of a customer from getting a catalogue for ordering and finally getting the confirmation of the same.

Figure 2

Use case document is the supporting document for the use case diagram. It has the description of the use case diagram. It has the following sections.

·         Brief Description – 2 to 3 sentences about the use case

·         Pre-conditions – conditions before the use case actually started

·         Basic flow – the basic control flow

·         Alternative flow – the alternative control flow

·         Post conditions – the condition after the use case executes

View Entire Article

User Comments

Title: Ms   
Name: Angelina Peters
Date: 2009-02-19 10:44:38 AM
I understand your frustration Mr Brown, but instead of blasting would have appreciated if you correct wherever he has messed up and edit it
Title: Mr.   
Name: PeterB
Date: 2007-06-12 11:02:36 AM
I am very irritated to see this kind of foolish article in this kind of sites.

Editors would have been smart and practical enough to understand and also edit the articles dealing with the SDLC or any phase of the Project. is creating all the mess with his vague or may be quite limited experience in the SDLC related matters.

I Just looked his article dealing with Artifacts in Design Phase, Which is completely vague and worst within a single word.

What does the mean of BPA and why is that mentioned as the standard artifact of requirement phase?

however it is understood that SDLC can be customized by different organizations to deliver additional artifacts according to their style of work.

But this fellow tried to take the same as the standard artifact and sending his waves of BIASED knowledge across the community.

I am sure any moderate or experienced Dev Folk after going through this article they will check for BPA across the internet, Don't worry it is a customized artifact but shouldn't be discussed as the standard artifact in this kind of articles.

I am surprised how blunt editor could edit and confirmed article for publishing as the requirements phase article never talk about RTM: Requirements Traceability Matrix and lot more mandatory artifacts.

It gives me the doubt that editor may be very good literate but not a practical hands on guy.

I am sure about what I've said.

If author has any point to talk to me give me the reverse message here.

If any one of you guys knows the mail id of the editor, I would URGE you guys to send this content as the mail to the editor

Mr. Peter Brown.

Product Spotlight
Product Spotlight 

Community Advice: ASP | SQL | XML | Regular Expressions | Windows

©Copyright 1998-2024  |  Page Processed at 2024-06-24 9:12:11 AM  AspAlliance Recent Articles RSS Feed
About ASPAlliance | Newsgroups | Advertise | Authors | Email Lists | Feedback | Link To Us | Privacy | Search