and System Software Architecture Description (SSAD)
THAI STUDENT ASSOCIATION (THSA) WEBSITE
TEAM # 12
Poonchana Thitametakul Amrit Pal Ishita Gupta Dhwanit Purohit Niket Ashesh Khushboo Bindlish Kunal Jain Yunsheng Lei
Client Project Manager Operational Concept Engineer Prototyping Manager Requirements Engineer Systems Architect Assistant Shaper, UML Modeler IIV & V and SRE
SSAD_LCO_F07a_T12_V1.0
Version Date: 10/19/2007
System and Software Architecture Description (SSAD)
Version no 1.0
Version History
Date 10/19/07 Author Khushboo Bindlish Version 1.0 Changes made First SSAD for THSA Website Rationale Initial draft for LCO Draft
SSAD_LCO_F07a_T12_V1.0
ii
Version Date: 10/19/2007
System and Software Architecture Description (SSAD)
Version no 1.0
Table of Contents
SYSTEM AND SOFTWARE ARCHITECTURE DESCRIPTION (SSAD).........................I VERSION HISTORY .......................................................................................................II TABLE OF CONTENTS .................................................................................................III TABLE OF TABLES ..................................................................................................... IV TABLE OF FIGURES................................................................................................... VII Introduction ..................................................................................................................... 1 1.1 Purpose .................................................................................................................... 1 1.2 Standards and Conventions ..................................................................................... 1 1.3 References ............................................................................................................... 1 2. System Analysis .............................................................................................................. 3 2.1 Structure .................................................................................................................. 3 2.2 Artifacts & Information........................................................................................... 6 2.3 Behavior ................................................................................................................ 10 2.3.2.1 Idle Mode .......................................................................................................... 30 2.3.2.2 Administrator Mode .......................................................................................... 30 2.3.2.3 THSA Member Mode........................................................................................ 30 1.
SSAD_LCO_F07a_T12_V1.0
iii
Version Date: 10/19/2007
System and Software Architecture Description (SSAD)
Version 1.0
Table of Tables
Table 1 Actor 1-THSA Member.................................................................................................................................. 4 Table 2 Actor 2-New user .......................................................................................................................................... 4 Table 3 Actor 3-System Administrator ....................................................................................................................... 5 Table 4 Actor 4-Student Database ............................................................................................................................. 5 Table 5 New user sign up form .................................................................................................................................. 6 Table 6 Login Page.................................................................................................................................................... 7 Table 7 User Profile................................................................................................................................................... 7 Table 8 Picture Display ............................................................................................................................................. 8 Table 9 Calendar Notification ................................................................................................................................... 8 Table 10 Email Notification ....................................................................................................................................... 8 Table 11 Message Interface ....................................................................................................................................... 9 Table 12 List of Announcements ................................................................................................................................ 9 Table 13 Student Database ...................................................................................................................................... 10 Table 14 Use Case Description: THSA Member Login ........................................................................................... 11 Table 15 Typical Course of Action - THSA Member Login ..................................................................................... 11 Table 16 - Alternate Course of Action - THSA Member Login ................................................................................... 12 Table 17 Use Case Description: THSA member Logout.......................................................................................... 12 Table 18 Typical Course of Action - THSA member Logout.................................................................................... 13 Table 19 Use Case Description: THSA Member Send Message .............................................................................. 13 Table 20 Typical Course of Action: THSA Member Send Message ......................................................................... 14 Table 21 Use Case Description: THSA Member upload Picture............................................................................. 14 Table 22 Typical Course of Action: THSA Member upload Picture........................................................................ 15 Table 23 Alternative Course of Action: THSA Member upload Picture .................................................................. 15 Table 24 Use Case Description: THSA Member Write on wall ............................................................................... 15
SSAD_LCO_F07a_T12_V1.0
iv
Version Date: 10/19/2007
System and Software Architecture Description (SSAD)
Version 1.0
Table 25 Typical Course of Action: THSA Member Write on wall .......................................................................... 16 Table 26 Use Case Description: THSA member Post Announcements.................................................................... 16 Table 27 Typical Course of Action: THSA member Post Announcements............................................................... 17 Table 28 Alternative Course of Action: THSA member Post Announcements ......................................................... 17 Table 29 Use Case Description: THSA member Write Testimony........................................................................... 18 Table 30 Typical Course of Action: THSA member Write Testimony ...................................................................... 18 Table 31: Use Case Description: New user Sign-up ............................................................................................... 19 Table 32 Typical Course of Action New user Sign up........................................................................................... 20 Table 33 Exception Course of Action New user Sign up...................................................................................... 20 Table 34 : Use Case Description: Administrative Login .......................................................................................... 21 Table 35 Typical Course of Action - Administrative Login...................................................................................... 22 Table 36 - Alternate Course of Action - Administrative Login ................................................................................... 22 Table 37: Use Case Description: Activate New Accounts ...................................................................................... 23 Table 38 Typical Course of Action Activate New Accounts .................................................................................. 23 Table 39 Exception Course of Action Activate new accounts ............................................................................... 24 Table 40: Use Case Description: Approve Announcements .................................................................................. 24 Table 41 Typical Course of Action Approve Announcements ............................................................................... 25 Table 42 Exception Course of Action Approve Announcements ........................................................................... 25 Table 43: Use Case Description: Post Announcements ........................................................................................ 25 Table 44 Typical Course of Action Post Announcements ..................................................................................... 26 Table 45: Use Case Description: Notify by email ..................................................................................................... 26 Table 46 Typical Course of Action Notify by email .............................................................................................. 27 Table 47: Use Case Description: Backup Database................................................................................................ 27 Table 48 Typical Course of Action Backup Database........................................................................................... 28 Table 49: Use Case Description: System Recovery ................................................................................................ 28
SSAD_LCO_F07a_T12_V1.0
v
Version Date: 10/19/2007
System and Software Architecture Description (SSAD)
Version 1.0
Table 50 Typical Course of Action System Recovery............................................................................................ 29 Table 51 Available Capabilities & Processes in Idle Mode..................................................................................... 30 Table 52 Available Capabilities & Processes in Administrator Mode .................................................................... 30 Table 53 Available Capabilities & Processes in THSA Member Mode ................................................................... 30
SSAD_LCO_F07a_T12_V1.0
vi
Version Date: 10/19/2007
System and Software Architecture Description (SSAD)
Version 1.0
Table of Figures
Figure 1 THSA website System Structure ..................................................................................................................... 3 Figure 2 Information Model ......................................................................................................................................... 6 Figure 3 THSA Member Use case............................................................................................................................... 10 Figure 4New User use case ........................................................................................................................................ 19 Figure 5Administrator use case .................................................................................................................................. 21 Figure 6 Modes of Operation...................................................................................................................................... 29
SSAD_LCO_F07a_T12_V1.0
vii
Version Date: 10/19/2007
System and Software Architecture Description (SSAD)
Version 1.0
1. Introduction
1.1 Purpose
The Purpose of the SSAD document is to provide a framework for the efficient implementation of the system for THSA Website. This version of SSAD is closely related to Operational Concept Description (OCD) and System Software Requirements Definition (SSRD). This document serves as a guideline for the development team. The primary target is to conceptualize an architecture after understanding the client's requirements. The document aims to justify the initial prototype made during the LCO phase by providing a feasible architecture for the system.
1.2 Standards and Conventions
Following are the standards and conventions followed in the SSAD document: LeanMBASE Version 1.9 Templates for SSAD LeanMBASE Additional_SSAD Guidelines Version 1.7 UML version 2.0
1.3 References
LeanMBASE Version 1.9 Templates for SSAD http://greenbay.usc.edu/csci577/fall2007/site/guidelines/LeanMBASE_v1.9_templates_fo r_SSAD.doc LeanMBASE Additional_SSAD Guidelines Version 1.7 http://greenbay.usc.edu/csci577/fall2007/site/guidelines/New SSAD guidelines Part I.pdf Sample SSAD Document for LCO Draft: Team 3 Fall 2006 CSC Volunteer Tracking System http://greenbay.usc.edu/csci577/fall2007/site/guidelines/SSAD_LCO_F06a_T03_V2.1.pd f Operational Concept Description (OCD) http://greenbay.usc.edu/csci577/fall2007/projects/team12/ System and Software Requirement Description (SSRD) http://greenbay.usc.edu/csci577/fall2007/projects/team12/ Twiki SSAD_LCO_F07a_T12_V1.0 1 Version Date: 10/19/2007
System and Software Architecture Description (SSAD) http://pattaya.usc.edu/twiki/bin/view/CS577Project12/WebHome
Version 1.0
CSCI577 Rational Software Architect/Modeler Template http://greenbay.usc.edu/csci577/fall2007/site/guidelines/CS577 Rational Software Architecht Template.zip
SSAD_LCO_F07a_T12_V1.0
2
Version Date: 10/19/2007
System and Software Architecture Description (SSAD)
Version 1.0
2. System Analysis
2.1 Structure
Figure 1 THSA website System Structure
2.1.1
System
The primary purpose of the THSA Website is to provide a social tool to the members of Thai Student Association for interaction among each other. The system supports a database backend which stores the profile of each member. When a new user logs onto the system, he sends an email to the administrator requesting the permission to sign up. The administrator checks the student's credentials and allows him to sign up for the service. The members are divided into two categories viz current student and alumni. They are provided same set of services. The only difference is that a current student cannot post an announcement for alumni and vice versa. The administrator monitors the activities on the website. He has to approve the announcements before them being public. The maintainer of the site is responsible for backups and failure recovery. SSAD_LCO_F07a_T12_V1.0 3 Version Date: 10/19/2007
System and Software Architecture Description (SSAD)
Version 1.0
Following are the services provided by the system: Personalized login Ability to post topics for a community Send and receive personal messages Upload pictures Get calendar notifications for events Get email notifications Take a tour to know about THSA Administrator can manage accounts and monitor activities on the website. Data backup 2.1.2 2.1.2.1
Actor
Actor 1 THSA Member
Table 1 Actor 1-THSA Member Role Responsibility Attributes User Services
Processes
Create profiles Post announcements and messages User Profile Type of user (current student or alumni) Username and password to access the system. Login to the account Send message Upload picture Write on wall Post announcements Write testimony Post topics for whole community Send messages Upload pictures writeOnWall postAnnouncement writeTestimony
2.1.2.2
Actor 2 New User Table 2 Actor 2-New user
Role SSAD_LCO_F07a_T12_V1.0 4
User Version Date: 10/19/2007
System and Software Architecture Description (SSAD) Responsibility Attributes Services Processes Sign Up Register for the website Sign up
Version 1.0
2.1.2.3
Actor 3 System Administrator
Table 3 Actor 3-System Administrator Role Responsibility Administrator Monitor the system Screen posts before posting them online. Allow new users to register. Backup System Administrative rights access to the system. Assign appropriate rights to the users. View posts for approval Post announcements Send Email Notifications Backup data Recover System Approve posts before making them public. Allow new users to sign up after checking their credentials. Regularly monitor the website. Run scripts to backup data and recover system in case of failure.
Attributes Services
Processes
2.1.2.4
Actor 4 Student Database Table 4 Actor 4-Student Database
Role Responsibility Attributes Services Processes
Database Store user profile. Store pictures uploaded by the user. Database name and the tables. Store student data and the pictures uploaded N/A
SSAD_LCO_F07a_T12_V1.0
5
Version Date: 10/19/2007
System and Software Architecture Description (SSAD)
Version 1.0
2.2 Artifacts & Information
The system information model shown below describes all the artifacts which are a part of the system. Some of these artifacts will be used by end users and some by the client, administrator and the maintainer.
Figure 2 Information Model
2.2.1
Artifact or Information Classes
2.2.1.1 New user sign up form
Table 5 New user sign up form Type Id Role Purpose SSAD_LCO_F07a_T12_V1.0 6 Description ATF-2 Input to the System Allows the user to set his/her username and Version Date: 10/19/2007
System and Software Architecture Description (SSAD)
Version 1.0
Responsibility
Related Capability(s)
password and allows him/her to personalize the login page. Contains all information needed for becoming a user of THSA Website. It also sets the access rights of the user. CR-8 Add Users CR-4 Personal Account CR-1 User Authentication
2.2.1.2 Login Page
Table 6 Login Page Type Id Role Purpose Description ATF-3 Input to the System The login page accepts the username and password of the user and gives access to the system after authenticating the user. It also identifies the user and displays the user's profile page. Authenticates the user and gives an error message if either the username or the password is unacceptable. CR-1 User Authentication CR-4 Personal Account
Responsibility
Related Capability(s)
2.2.1.3 User Profile
Table 7 User Profile Type Id Role Purpose Responsibility Description ATF-4 Profile of each user Displays the user data and the services provided to the user. Display all information related to the user like the picture of the user, friends list of the user, user's wall, topics posted on the community to which the user belongs and user's testimonies. CR-4 Personal Account CR-6 User Wall CR-7 User Testimony 7 Version Date: 10/19/2007
Related Capability(s)
SSAD_LCO_F07a_T12_V1.0
System and Software Architecture Description (SSAD)
Version 1.0
CR-9 Group notifications and Messages
2.2.1.4 Picture Display
Table 8 Picture Display Type Id Role Purpose Description ATF-5 Output shown to the user This page displays the pictures uploaded by the user. These pictures are visible to anyone who visits the user's profile. Share pictures uploaded by the user. CR-5 Picture Uploading
Responsibility Related Capability(s)
2.2.1.5 Calendar notifications
Table 9 Calendar Notification Type Id Role Purpose Description ATF-6 Notification sent to the user. The notifications are sent to user about the upcoming events posted and approved by the administrator. Contains the information about the event, date, time and location. CR-9 Group Notifications and Messages
Responsibility Related Capability(s)
2.2.1.6 Email Notifications
Table 10 Email Notification Type Id Role Purpose Description ATF-7 Emails sent from the administrator to the user. The administrator can send email notifications to a user or a set of user 8 Version Date: 10/19/2007
SSAD_LCO_F07a_T12_V1.0
System and Software Architecture Description (SSAD)
Version 1.0
Responsibility Related Capability(s)
(community) about certain events or any desired or undesired activity. Example: If the user is posting unacceptable messages, the administrator notifies the user about this by an email. Contains the user's email address and the message which is needed to be conveyed. CR-9 Group Notifications and Messages
2.2.1.7 Message Interface
Table 11 Message Interface Type Id Role Purpose Responsibility Related Capability(s) Description ATF-8 Interface to the user The user can send or receive messages from other users. Displays the message that has been sent or receive and the sender or receiver's name CR-3 Mailing Services
2.2.1.8 List of Announcements
Table 12 List of Announcements Type Id Role Purpose Description ATF-9 Output shown to the user The announcements that have been approved by the administrator displayed. are Contains all the announcements made on the communities user belongs to after being approved by the administrator. The user has to ask for administrator's permission before posting an announcement. CR-2 User Permission CR-9 Group Notification and Messages
Responsibility
Related Capability(s)
SSAD_LCO_F07a_T12_V1.0
9
Version Date: 10/19/2007
System and Software Architecture Description (SSAD)
Version 1.0
2.2.1.9 Student Database
Table 13 Student Database Type Id Role Purpose Responsibility Related Capability(s) Description ATF-10 Database Stores user data. Stores the user's profile and the pictures uploaded by the user. CR-4 Personal Account
2.3 Behavior
This section gives details of the processes used for implementing the capabilities listed in OCD 1.5.
2.3.1
2.3.1.1
Processes
THSA member
Figure 3 THSA Member Use case
SSAD_LCO_F07a_T12_V1.0
10
Version Date: 10/19/2007
System and Software Architecture Description (SSAD)
Version 1.0
2.3.1.1.1
THSA member Login
Table 14 Use Case Description: THSA Member Login
Identifier Use-Case Name Abstract Purpose Actors Priority Capability Requirements Risks
UC - 1 THSA Member Login
No Determine authentication and privilege of the user THAI Community member M (Must have) OC-1: Login Page CR-1: User authentication Some unauthorized user may be able to intrude into the system via the login page High-Risk? N Architecturally Y Significant? Development Draft LCO Status Overview Authenticate the actor to use the system User Interface GUI Pre-conditions User's username and password exist on the system database with appropriate authentication status. Postconditions Specializes Includes Extends Extension Points User is authorized to use the system N/A N/A N/A N/A
Table 15 Typical Course of Action - THSA Member Login
Seq# 1 2 3
Actor Actions Send the username and password Click login button
System Response
Validate the username and password 11 Version Date: 10/19/2007
SSAD_LCO_F07a_T12_V1.0
System and Software Architecture Description (SSAD) 4
Version 1.0
Redirect the user to THSA website home page
Table 16 - Alternate Course of Action - THSA Member Login
Seq# 1 2 3
Actor Actions Send the wrong username or password
System Response
Validate the username and password Display An error message: "username or password are wrong" in a dialog box Click OK button Redirect the actor to the login page
4 5
2.3.1.1.2
THSA member Logout
Table 17 Use Case Description: THSA member Logout
Identifier Use-Case Name Abstract Purpose Actors Priority Capability Requirements Risks High-Risk? Architecturally Significant? Development Status Overview User Interface Pre-conditions Postconditions Specializes Includes Extends
UC- 1 THSA member Logout No To log out of the system User M (Must have) OC-1: Login Page CR-1: User authentication N/A N Y Draft LCO Log off the user from the system GUI The user has logged in to the system. The user's login session still exists The user login session is terminated. The user is detached from the system N/A N/A N/A 12 Version Date: 10/19/2007
SSAD_LCO_F07a_T12_V1.0
System and Software Architecture Description (SSAD) Extension Points N/A
Version 1.0
Table 18 Typical Course of Action - THSA member Logout
Seq# 1 2
Actor Actions Click the "log out" hypertext
System Response Redirect the actor to THSA home page
2.3.1.1.3
THSA member Send Message
Table 19 Use Case Description: THSA Member Send Message
Identifier Use-Case Name Abstract Purpose Actors Priority Capability Requirements Risks High-Risk? Architecturally Significant? Development Status Overview
UC- 3 THSA member send message No THSA user can send message to other members of community. THSA member M (Must have)
OC3- Interactive tool
CR-3 Mailing service Spam messages can be sent N Y Draft LCO
Enabling THSA member to write messages and to send to other members of community just like sending emails. User Interface GUI Pre-conditions (a) The sender's account is already in the system. (b) The receiver's account is already in the system. PostThe message is sent and will be displayed in the receiver's conditions inbox Specializes N/A Includes N/A Extends N/A Extension N/A Points
SSAD_LCO_F07a_T12_V1.0
13
Version Date: 10/19/2007
System and Software Architecture Description (SSAD)
Table 20 Typical Course of Action: THSA Member Send Message
Version 1.0
Seq# 1 2 3
Actor Actions Write a message Click on "Send massage" button
System Response
A message: "your message has been sent" is displayed on senders screen THSA member upload picture
Table 21 Use Case Description: THSA Member upload Picture
2.3.1.1.4
Identifier Use-Case Name Abstract Purpose Actors Priority Capability Requirements Risks High-Risk? Architecturally Significant? Development Status Overview
UC- 4 THSA member upload Picture No THSA user can upload pictures in his/her album. THSA member M (Must have)
OC2- User Profile
CR-5 Picture Uploading N N Y Draft LCO
Enabling THSA member to upload pictures in his/her own album. Other members of the community can see the pictures uploaded by the user. User Interface GUI Pre-conditions (a) The sender's account is already in the system. (b) The size of picture is less than maximum allowed size (5MB). PostThe picture is uploaded in the album and can be viewed by conditions the any member. Specializes N/A Includes N/A Extends N/A Extension N/A Points
SSAD_LCO_F07a_T12_V1.0
14
Version Date: 10/19/2007
System and Software Architecture Description (SSAD)
Table 22 Typical Course of Action: THSA Member upload Picture
Version 1.0
Seq# 1 2 3 4
Actor Actions Select a picture from the system Click on "upload picture" button
System Response
The size and format of picture is checked A message: "Picture has been uploaded" is displayed on user's screen
Table 23 Alternative Course of Action: THSA Member upload Picture
Seq# 1 2 3 4
Actor Actions Select a picture from the system Click on "upload picture" button
System Response
The size and format of picture is checked A message: "Wrong picture format or picture size exceeded the maximum allowed limit" is displayed on user's screen
2.3.1.1.5
THSA member Write on wall
Table 24 Use Case Description: THSA Member Write on wall
Identifier Use-Case Name Abstract Purpose Actors Priority Capability Requirements Risks High-Risk? Architecturally
UC- 5 THSA member write on wall No THSA user can write on wall other members of community. THSA member M (Must have)
OC3- Interactive tool
CR-6 User Wall N N Y 15 Version Date: 10/19/2007
SSAD_LCO_F07a_T12_V1.0
System and Software Architecture Description (SSAD) Significant? Development Status Overview
Version 1.0
Draft LCO
Enabling THSA member to write messages on the wall of other members in community. It provides members with an interface to chat with each other User Interface GUI Pre-conditions (c) The sender's account is already in the system. (d) The receiver's account is already in the system. PostThe message is sent and will be displayed at the receiver's conditions wall Specializes N/A Includes N/A Extends N/A Extension N/A Points
Table 25 Typical Course of Action: THSA Member Write on wall
Seq# 1 2 3
Actor Actions Write on wall Click on button "Post"
System Response
A message: "Post successful" is displayed on GUI screen
2.3.1.1.6
THSA member Post Announcements
Table 26 Use Case Description: THSA member Post Announcements
Identifier Use-Case Name Abstract Purpose Actors Priority Capability Requirements Risks High-Risk? Architecturally Significant? Development
UC- 6 THSA member Post Announcements No THSA user can post announcements which needs to be pre-approved by the admin THSA member M (Must have)
OC5- Announcements
CR-2 User permission N N Y Draft LCO 16 Version Date: 10/19/2007
SSAD_LCO_F07a_T12_V1.0
System and Software Architecture Description (SSAD) Status Overview
Version 1.0
Enabling THSA member to post announcements which needs to be approved by the admin before being displayed on the announcements section. These announcements can be about upcoming events like meetings, functions etc User Interface GUI Pre-conditions The sender's account is already in the system. PostIf the announcement is approved by the admin, then it is conditions displayed in the announcements section otherwise not Specializes N/A Includes N/A Extends N/A Extension N/A Points
Table 27 Typical Course of Action: THSA member Post Announcements
Seq# 1 2 3 4
Actor Actions Click on "Post announcement" button Create an announcement Click on "Submit" button
System Response
5
A message: "Request submitted for approval" is displayed on GUI screen Request is approved, announcement is posted on the announcements section
Table 28 Alternative Course of Action: THSA member Post Announcements
Seq# 1 2 3 4
Actor Actions Click on "Post announcement" button Create an announcement Click on "Submit" button
System Response
5
A message: "Request submitted for approval" is displayed on GUI screen Request is not approved and sender is notified about this
SSAD_LCO_F07a_T12_V1.0
17
Version Date: 10/19/2007
System and Software Architecture Description (SSAD) 2.3.1.1.7 THSA member Write Testimony
Table 29 Use Case Description: THSA member
Version 1.0
Write Testimony
Identifier Use-Case Name Abstract Purpose Actors Priority Capability Requirements Risks High-Risk? Architecturally Significant? Development Status Overview
UC- 7 THSA member Write Testimony No User can write a testimony for other members THSA member M (Must have)
OC3- Interactive tool
CR-7 User Testimony N N Y Draft LCO
The user can write a testimony for one of his friends or any member of the community. User Interface GUI Pre-conditions Must have an account in the system. PostTestimony is added to the receivers profile conditions Specializes N/A Includes N/A Extends N/A Extension N/A Points
Table 30 Typical Course of Action: THSA member Write Testimony
Seq# 1
Actor Actions Click on "Write testimony" link Write a testimony Click on "post" button
System Response
2
The system adds the testimony to the receivers profile
SSAD_LCO_F07a_T12_V1.0
18
Version Date: 10/19/2007
System and Software Architecture Description (SSAD)
Version 1.0
2.3.1.2 New User
Figure 4 New User use case
2.3.1.2.1
New User sign up
Table 31: Use Case Description: New user Sign-up Identifier Use-Case Name Abstract Purpose Actors UC8 New User Sign-up No To let visitors register and be a part of the Thai Club New User 19 Version Date: 10/19/2007
SSAD_LCO_F07a_T12_V1.0
System and Software Architecture Description (SSAD) Priority Capability Requirements Risks High-Risk? Architecturally Significant? Development Status Overview M(Must have)
OC2- User Profile
Version 1.0
CR8 Add user N N Y Draft LCO
New Users can fill the registration form and become a part of the Thai Club User Interface GUI Pre-conditions Visit the website and fill the registration form PostThe visitor becomes a member of the Thai Club conditions Specializes N/A Includes N/A Extends N/A Extension N/A Points
Table 32 Typical Course of Action New user Sign up
Seq# 1 2 3
Actor Actions Fills the registration form Becomes a member
System Response Accepts the form and processes it
Table 33 Exception Course of Action New user Sign up
Seq# 1 2 3
Actor Actions Fills the registration form Either sign up again or exit the website
System Response Form rejected
SSAD_LCO_F07a_T12_V1.0
20
Version Date: 10/19/2007
System and Software Architecture Description (SSAD)
Version 1.0
2.3.1.3 Administrator
Figure 5 Administrator use case
2.3.1.3.1
Administrator Login
Table 34 : Use Case Description: Administrative Login
Identifier Use-Case Name Abstract Purpose Actors Priority Capability
UC9 Administrative Login No Determine authentication and privilege of the Administrative Administrative Login M (Must have) OC-1: Login Page 21 Version Date: 10/19/2007
SSAD_LCO_F07a_T12_V1.0
System and Software Architecture Description (SSAD) Requirements Risks
Version 1.0
CR-1: User authentication Some unauthorized user may be able to intrude into the system via the login page High-Risk? N Architecturally Y Significant? Development Draft LCO Status Overview Authenticate the actor to use the system User Interface GUI Pre-conditions Administrative's username and password exist on the system database with appropriate authentication status. Postconditions Specializes Includes Extends Extension Points Administrative is authorized to use th...