Object Oriented Analysis and

design
Use case diagram

Dispatch
Catalog
Use Case Description
• Complements Use Case Diagram
• A breakdown of a single use case (e.g., sequence of steps included in
the use case “Look up item availability”);
• In contrast to Use Case Diagram, Use Case Description captures
variations of a Use Case
• Example: “Create new order” can be done via a. customer’s
phoning + clerk’s help or b. customer’s Internet ordering
with no clerk = 2 scenarios
Level of Use Case Description
• Three levels of detail:
• Use Case Brief description
• Summary of what system does in response to actor’s actions
• Use Case Intermediate description
• Shows steps in use case, if-then
• Use Case Full description
• Includes Brief description, expands intermediate description, shows scenarios
Brief Description of Use Case Create New
Order

customer’s record,
Intermediate Use Case Description
Full Use Case Description
• Superset of intermediate and brief descriptions
• Shows steps (“Flow of Events”) broken down to the actor and the
system side – useful!
Software Project Stake holders
• A project stakeholder is any individual or an organization that is
actively involved in a project, or whose interest might be affected
(positively or negatively) as a result of project execution or
completion.
Software Project Stake holders
Some characteristics:
– They may have different influence and varying level of
responsibility during the project
– They may play different roles
– They may have positive or negative influence on the project
– They may be difficult to identify
– Their lack of intervention may negatively influence the project(need for
identification and involvement)
•Remark: the project manager and the project team are project
stakeholders, although the term is often used to refer to the “other”
stakeholders
Software Project Stake holders
Types of Stakeholders
• The project manager
• The project team
• The project sponsor
• The performing organizations
• The partners
• The client
• The “rest”: anyone who might be affected by the project outputs
Software Team Organization
Development teams are organized to
• promote communication among the team members and between the
team and interested external parties
• Match required skills against needs of the project
• Enhance overall productivity of the team
Software Team Organization
• Hierarchical Team Organization
• Teams report to managers
• Managers report to one or more levels of higher managers
Software Team Organization
• Agile Teams
• Small teams, often sharing a workspace
• Typically, one team manager
• Often includes customers/stakeholders or their designated
representative as a team member.
• Team sets their own best practices
• selects tools
• SWAT Teams (Skilled With Advanced Tools)
• Small team, sharing a common workspace
• Heavy tool support
• Team leader is “first among equals”
Problems and challenges
• Major issues in organizing a development team are
• Communication
• maximize communication within the team
• establish responsive communication points with stakeholders
• Staffing
• does the team contain all the skill sets required to complete the work?
• Productivity
• are we making effective use of our team members’ skills?
Example (Online Shopping)
• Web Customer actor uses some web site to make purchases online. Top level use cases are View Items, Make Purchase and Client
Register. View Items use case could be used by customer as top-level use case if customer only wants to find and see some
products. This use case could also be used as a part of Make Purchase use case. Client Register use case allows customer to
register on the web site, for example to get some coupons or be invited to private sales. Note, that Checkout use case is included
use case not available by itself - checkout is part of making purchase.
• Except for the Web Customer actor there are several other actors which will be described below with detailed use cases.
• View Items use case is extended by several optional use cases - customer may search for items, browse catalog, view items
recommended for him/her, add items to shopping cart or wish list. All these use cases are extending use cases because they
provide some optional functions allowing customer to find item.
• Customer Authentication use case is included in View Recommended Items and Add to Wish List because both require the
customer to be authenticated. At the same time, item could be added to the shopping cart without user authentication.
•
Checkout use case includes several required uses cases. Web customer should be authenticated. It could be done through user
login page, user authentication cookie ("Remember me") or Single Sign-On (SSO). Web site authentication service is used in all
these use cases, while SSO also requires participation of external identity provider.
• Checkout use case also includes Payment use case which could be done either by using credit card and external credit payment
service or with PayPal.