View
72
Download
0
Category
Tags:
Preview:
DESCRIPTION
SDMS Project Phase II. Duk-Jin Kim Tu Peng Yan Shi. Agenda. Process Issues System Functional Requirements System Non-Functional Requirements Prototype Next step. Process Role-Actor Diagram. for prototyping [Kotonya&Sommerville98]. Process Activity Diagram. - PowerPoint PPT Presentation
Citation preview
SDMS Project Phase II
Duk-Jin KimTu PengYan Shi
Agenda
Process Issues System Functional Requirements System Non-Functional Requirements Prototype Next step
Process
Role-Actor Diagram
ROLES
Understandproblem
Establishoutline
requirements
Selectprototyping
system
Developprototype
Evaluateprototype
ACTIONS
Req. engineerDomain expert
End-userReq. engineer
End-user
Softwareengineer
Project manager
Req. engineerSoftwareengineer
End-userDomain expertReq. engineer
Software engineer
for prototypingfor prototyping [Kotonya&Sommerville98]
Process
Activity Diagram
All three members in our team play the following roles: Requirement Engineers Project Managers Software Engineers Domain Experts End Users
Process
Roles
Monitoring Meeting is required in the Project 1 specification Should be included in the virtual meeting
functions Will be included in the future
development
Issues
System Functional Req.
Use Case Diagram
participant
administrator
initiatorplan meeting
login/logoff
<<include>>
view meeting
set preference/exclusion
<<include>>
<<include>>
conflict resolution
<<include>>
<<include>>
replan meeting
<<include>>
<<extend>>
database
System Functional Req.
Class Diagram
PolicypolicyIDcontent
apply()
MeetingController
planMeeting()replanMeeting()Notify()
Controller
LoguserNamepassword
getUserName()getPassword()register()logIn()logOff()
MeetingmeetingDatemeetingBeginTimemeetingDurationmeetingLocationparticipant : Participant[ ]meetingThememeetingIDinitiatorIDdateRange
getDate()getBeginTime()getDuration()getLocation()getParticipants()getTheme()getID()getInitatorID()getDateRange()setDateRange()setDate()setBeginTime()setDuration()setLocation()setParticipants()setTheme()setID()...
operate
conflictResolutionprefernce : Preferenceexclusion : Exclusionpolicy : Policyresolution
resolve()
ParticipantuserNamepasswordauthorizationpreferenceDatepreferenceLocationexclusionDateexclusionLocation
getUserName()getPassword()getAuthorization()resetPassword()getPreferenceDate()getPreferenceLocation()getExclusionDate()getExclusionLocation()setPreferenceDate()setPreferenceLocation()...
ParticipantController
setPreference()setExclusion()
operate
System Functional Req.
Sequence Diagram – Login/logoff
Controller Log
Login(usr,pwd)
boolean
Logoff
System Functional Req.
Sequence Diagram – PlanMeetingMeetingController
m1:Meeting
Participant
ParticipantController
<<create>>
setDateRange(dates)
setParticipants(participant [ ])
setLocation(place)
Notify(participant)
<<create>>
setAuthorization(auth)
setPreferenceDate(date)
setExclusionDate(date)
getPreferenceDate()
getExclusionDate()
dates prefered
dates excluded
proposeDate()
{propose success}Notify(particiment,meeting)
{propose fail}replanMeeting()
System Functional Req.
Activity Diagram
open index page
register
not a user
login
is a usernot match
view status
set preference and exclusion
plan meeting
check schedule participant
change needed
change not needed initiator
new
replan meeting
existing and conflict
action needed
logoff
action not needed
matchreset passwordpassword reset needed
System Functional Req.
SADT Acti-gram
SDMS
0
User name
Password
Meeting participant
Meeting date
Meeting Location
User Validation Conflict PolicyConstraints
Initiator Participants Server
System Functional Req.
SADT Acti-gram (Conti.)
0
Meeting participant
Meeting date
Meeting Location
User Validation Conflict PolicyConstraints
Initiator Participants Server
Login/logoff1
Interaction2
Plan Meeting3
Conflict Resolution4
Re-plan Meeting5
System Non-Functional Req.
Softgoal Interdependency Graph
Performance
quick meetingdetermination
quick info.sharing
quick between dete and actual
Usability
accommodate decentralized requests
physical consistency
- -
Extensibility
handle explicit priorities among dates in pref. sets
handle explicit dependencies between meeting date and meeting location
variations in date formats, address formats, interface language
participation through delegation
-+
Customizability
Private &Professional meetings
Customizable Flexibility
Rescheduling dynamically
accommodate evolving data
Flexible
Security
Softgoal Interdependency Graph NFRs
non-privileged participant should not be aware of constraints stated by other participants
Prototype
Login
Prototype
View Meeting Status
Prototype
Propose a Meeting
Prototype
Preference and Exclusion Set
Next Step Further improvement of SR Developing the prototype
Thank You!
Duk-Jin KimTu PengYan Shi
Nov 2006
Recommended