Revision History
Date
10/6/2006
Description
Added detail (fields) to UC 3.0 and 5.0, added use case to “update user profile.”
Editor
Cynthia
10/16/2006 Renumbered use cases, added additional scope information to introduction, added
additional fields to profile (UC 3.0), added fields to search (UC 6.0), modified UC 7.0
and 8.0, removed UC 10.0 (delete)
Cynthia
10/23/2006 Added password reminder requirement
Cynthia
1
Table of Contents
Introduction .................................................................................................................................................................... 3
Use Case Objectives ....................................................................................................................................................... 3
Actors ............................................................................................................................................................................. 3
Use Case Specifications ................................................................................................................................................. 4
UC 1.0 User Registration ........................................................................................................................................... 4
UC 1.1 Password Reminder Mechanism .................................................................................................................... 4
UC 2.0 Log In............................................................................................................................................................. 5
UC 3.0 Set Up User Profile ........................................................................................................................................ 5
UC 4.0 View Personal Profile .................................................................................................................................... 6
UC 5.0 Update Personal Profile ................................................................................................................................. 6
UC 6.0 Search ProNet ................................................................................................................................................ 7
UC 7.0 Look Up a Member ........................................................................................................................................ 7
UC 8.0 Look Up/Search Results ................................................................................................................................ 8
UC 9.0 Access User Profiles ...................................................................................................................................... 8
Approval ..................................................................................................................................................................... 9
2
ProNet Business Requirements
Project Name
ProNet
Description
This document details the business requirements for the ProNet professional
networking application.
Introduction
The ProNet application is a professional networking database intended to be used by current and future MnSCU institution
alumni. ProNet would allow alumni to enter information about their current and past work experience and expertise, and
then allow users to search the database for individuals or for certain skills sets/expertise.
In the future, ProNet may allow non-alumni to use the system, for example, employers may use ProNet to post jobs or to
search for alumni who are qualified to fill jobs. Also as a possible future enhancement, ProNet may be integrated with
other systems, particularly systems in the ISEEK Solutions portfolio.
Intended Users
ProNet will be made available to alumni from all MnSCU institutions including four-year colleges, (two-year) community
colleges, and technical schools.
Use Case Objectives
This document uses Use Case definitions to define the business requirements of the ProNet application. Each Use Case
definition describes in detail all of the different ways the system will be used. Additionally, each use case will identify
user/other system interaction with the ProNet system, define detailed business requirements and scope, and define technical
requirements.
Actors
An actor is someone or something outside the system that interacts with the system. Actors may initiate use-cases,
communicate through a use-case, or both. Every use-case must have an actor initiating it, but not every actor initiates a usecase.
Actor
MnSCU
Alum
Description
Graduates from any of the MnSCU institutions and the intended primary user of the system.
MnSCU alumni will populate the database with their information and they will also be the primary
users of the database.
Use Case Specifications
Each use case specification:
 Describes what the system does, not how it is done
 Is a sequence of actions performed by a system
 Yields an observable result of value to a particular actor
 Identifies all business requirements associated to the use case
 Identifies technical rules associated with the business requirements
3
UC 1.0 User Registration
Summary
ProNet system users must establish a username and a password to use the ProNet
system.
Triggers
Individual wishes to use ProNet.
Basic Course of Events
1.
2.
Alternate Paths
If the user has already registered, the user may proceed directly to authentication.
Preconditions

User has not registered with ProNet.
Post conditions

User is able to access application.
User navigates to ProNet.
User is prompted to register for the system.
Business Rules:
 At user registration, a username and password must be established.
 Additional fields required upon system registration include first name, last name, address, telephone number, e-mail
address.
 Optional fields that may be completed upon system registration will be detailed in a separate use case.
UC 1.1 Password Reminder Mechanism
Summary
ProNet will have a mechanism to e-mail passwords back to users who have
forgotten them.
Triggers
Individual asks for a password reminder.
Basic Course of Events
1.
2.
3.
Alternate Paths
None
Preconditions

User has registered with ProNet.

A username and password must be associated with the e-mail address entered
by the user for the reminder to be sent.

User receives e-mail message at specified address.
Post conditions
User indicates that s/he forgot password.
User is prompted to enter his/her e-mail address.
The username and password is sent to that e-mail address.
Business Rules:
 The message that will be sent to the user will contain the following text:
Subject: ProNet Username and Password Reminder
Body: You requested that your ProNet username and password be sent to this e-mail address. Your username is
<username> and your password is <password>.
4
UC 2.0 Log In
Summary
Triggers
Access to the ProNet application should be password protected.
Basic Course of Events
1.
2.
Alternate Paths
If the user has not already registered for the system, the user should be prompted
to do so.
Preconditions

User has registered with ProNet.
Post conditions

User is able to access application.
User wishes to log into the system.
User navigates to ProNet.
User is prompted for a Internet ID and password.
Business Rules:
 There are no varying levels of access to ProNet; authentication to the system will allow every user the same level of
access as every other user. Although different user classes may be set up in the future (e.g., employers may post jobs
to ProNet and may require a different level of access), the initial release of the system will have only one user class.
 ProNet will exist independently of other systems, so will also have its own, independent log-in mechanism.
UC 3.0 Set Up User Profile
Summary
Users’ profiles in ProNet will consist of information about current and past
employment, education, and expertise.
Triggers
User wishes to set up his/her user profile.
Basic Course of Events
Alternate Paths
After authentication, the user chooses to “update profile.”
The user may also enter profile information upon system registration.
Preconditions

User has authenticated.
Post conditions

User is able to view updated profile.

Other system users are able to view the updated profile.
Business Rules:
 The user profile will consist of information about education, job history (including current position), and expertise,
including the following fields:
 Educational institution
 Current employer name
 Current employer city
 Current employer state
 Current employer industry
 Current title
 Current role
 Past employer(s) 1
 Past employer(s) 1 industry
 Previous title 1
 Previous role 1
 Past employer(s) 2
 Past employer(s) 2 industry
 Previous title 2
 Previous role 2
 Past employer(s) 3
 Past employer(s) 3 industry
 Previous title 3
5






Previous role 3
Preferred method of contact
Release of personal information
Networking goals
Additional involvement
Personal statement
UC 4.0 View Personal Profile
Summary
Users’ profiles in ProNet will consist of information about current and past
employment, education, and expertise.
Triggers
User wishes to view his/her user profile.
Basic Course of Events
Alternate Paths
After authentication, the user chooses to “view profile.”
None
Preconditions

User has authenticated.
Post conditions

None
Business Rules:
 Users may view their own profiles and see them in the same way that other users would see them.
UC 5.0 Update Personal Profile
After initial profile set-up, users may update their ProNet profiles.
User wishes to modify his/her user profile.
After authentication, the user chooses to “update profile.”
None
Summary
Triggers
Basic Course of Events
Alternate Paths
Preconditions

User has authenticated.
Post conditions

User is able to view updated profile.

Other system users are able to view the updated profile.
Business Rules:
 The user may overwrite old information with new information in any field except username, password, first name, and
last name.
 The user may remove data from fields and save the update without data in those fields as long as the newly removed
data isn’t from any required fields.
6
UC 6.0 Search ProNet
Summary
Triggers
Any user may search ProNet by certain criteria.
Basic Course of Events
Alternate Paths
After authentication, the user chooses to “search.”
None
Preconditions

User has authenticated.
Post conditions

User is able to view search results.

User is able to modify search.
User wishes to search ProNet
Business Rules:
 Users may search ProNet by any or all of the following criteria:
 Home city
 Home state
 Educational institution
 Flag: search current or all employment fields
 Employer
 Employer City
 Employer State
 Employer Industry
 Job Title
 Job Role
 Networking Goals
 Personal Statement Keywords
UC 7.0 Look-Up A Member
Summary
Triggers
Any user may look up a ProNet member.
Basic Course of Events
Alternate Paths
After authentication, the user chooses to “look up a member.”
None
Preconditions

User has authenticated.
Post conditions

User is able to view results of the look-up.
User wishes to look up a member of ProNet
Business Rules:
 “Member look-up” is a search, but one that uses characteristics of individuals to identify an individual rather than to
identify a set of users.
 Members may be looked up by username, name, or by e-mail address.
7
UC 8.0 Look-Up/Search Results
Summary
Triggers
Member look-ups and searches produce a page of results.
Basic Course of Events
1.
2.
Alternate Paths
In the case that only a single result is returned in the search or look-up, the results
page can be bypassed and the user can be immediately directed to the user’s
profile.
Preconditions

User has searched/browsed.
Post conditions

User is able to view a set of results indicating ProNet users who satisfy the
characteristics of the search or look-up.
User has searched or looked up a ProNet user.
User searches or looks up a member.
Results are returned.
Business Rules:
 The results set should include enough data to distinguish one ProNet user from another. Results should display the
following fields:
 Username
 Name
UC 9.0 Access User Profiles
Summary
Triggers
ProNet member profiles may be viewed by ProNet users.
Basic Course of Events
1.
2.
3.
Alternate Paths
1. User browses.
User has searched or browsed to identify a ProNet user.
User searches.
Search results are returned.
User selected a single result to view.
2. User selects a single user to view.
Preconditions

User has searched/browsed.
Post conditions

User is able to view ProNet user profile.
Business Rules:
 After viewing a profile, the user can return to the list of search/browse results.
8
Approval
Role
SME
SME
SME
Designer/Developer
Developer
Developer
Project Manager
Document Author
Signature/Date
Name/Title/Department/Campus
Roxie
Analyst
MnSCU Development
Tia
Director
Minnesota State University, Rochester
Nate
Account Manager
ISEEK Solutions
Royce
Designer
MnSCU-IT
Tim
Developer
MnSCU-IT
Jack
Developer
MnSCU-IT
_____________
Project Manager
MnSCU-IT
Cynthia
Business Analyst
MnSCU-IT
9