History of Warfare the Second World War in the East the History of Warfare
World of warfare
-
Upload
- -
Category
News & Politics
-
view
253 -
download
0
description
Transcript of World of warfare
World Of
Warfare
A search engine of
war history SFTW-372 Course Project
Sun Li: D-A7-2924-2
Zhan Bo Han: D-A7-2892-9
Zhu Yi Cheng: D-A7-2917-0
Chen Mo: D-A6-2865-3
Chen Xi: D-A7-2809-3
Index
1. Introduction: ................................................................................................................................. 3
1.1 System introduction ............................................................................................................ 3
1.2 Data storage architecture .................................................................................................... 3
2. Overall Diagrams ........................................................................................................................... 4
2.1 Overall Use Case Diagram ................................................................................................... 4
2.2 Overall Class Diagram .......................................................................................................... 4
3. Sub functions................................................................................................................................. 5
3.1 Add Records ........................................................................................................................ 5
3.1.1 Add War ................................................................................................................... 5
3.1.2 Add Battle ................................................................................................................. 7
3.1.3 Add Location .......................................................................................................... 10
3.1.4 Add Individual ........................................................................................................ 11
3.1.5 Add Contribution .................................................................................................... 13
3.1.6 Add Organization .................................................................................................... 15
3.2 Delete Operations ............................................................................................................. 18
3.2.1 Delete War ............................................................................................................. 18
3.2.2 Delete Battle ........................................................................................................... 20
3.2.3 Delete Location ...................................................................................................... 22
3.2.4 Delete Organization ................................................................................................ 24
3.2.5 Delete Individual .................................................................................................... 26
3.2.6 Delete Contribution ................................................................................................ 28
3.3 Modify Operations ............................................................................................................ 30
3.3.1 Modify War ............................................................................................................ 30
3.3.2 Modify Battle .......................................................................................................... 32
3.3.3 Modify Location ..................................................................................................... 34
3.3.4 Modify Individual ................................................................................................... 35
3.3.5 Modify Contribution ............................................................................................... 37
3.4. Search Operations ............................................................................................................ 39
3.4.0 Search By Keyword ................................................................................................. 39
3.4.1 Search War ............................................................................................................. 40
3.4.2 Search Battle .......................................................................................................... 41
3.4.3 Search Location ...................................................................................................... 43
3.4.4 Search Organization ............................................................................................... 44
3.3.5 Search Individual .................................................................................................... 46
3.4.6 Search Contribution ............................................................................................... 47
3.4.7 Search Participant .................................................................................................. 49
1. Introduction:
1.1 System introduction
Our analysis pattern is a search engine of war in the history. It will help users refer to the
detail information of wars in the history recorded in the database. And it’s maintained by some
administrators who have a login username and password. Our UML pattern includes use case
model, sequence diagram and class diagram
1.2 Data storage architecture
The system’s data class includes “war”, “battle”, “participant”, “Individual”, “Organization”,
“Contribution” and “Location”. The detailed information is listed as below:
Data Name Description
War It’s the union of all the small battles. For example, a war can be the “World War
II”. It has attributes of [Name, Begin, End, Reason, Result]
Battle It refers to every small conflict during a war. For example the invading towards
the Summer Palace during the “World War II”. One war may have several
battles, while one battle only belongs to one war. It has attributes of [Name,
Begin, End, Reason, Result]
Participant It refers to the two sides of every battle (As we assume every battle has two
sides, and currently there is no exception we can find). A participant may
contain many countries or organization. For example, in the invading towards
the Summer Palace, one participant is China, the other one is the union of
England and France. It has attributes of [ForceDevoted(how many force this
participant has), FinalState(Win or Lose)].
Location It’s the place that a battle taking place. It has attributes of [Name,
Landform(land, sea ,mountain…)]
Organization The countries or other organization take part in a war or some battles.
Organization may have relations with many participants and wars. It has
attributes of [Name, Begin, End, Description]
Individual It refers to famous guys in an organization. It has attributes of [Name, Gender,
Birth, Death, Birthplace]
Contribution It is the contribution that one individual did towards a participant in a battle. It
has attributes of [Position(the individual’s position in that participant),
Description]
2. Overall Diagrams
To have an overview about our project, let’s firstly refer to the overall diagrams
2.1 Overall Use Case Diagram
Below is the overall use case diagram showing the main functions of our system: Add
Records, Modify Records, Delete Records and Search Records. The administrators can refer to all
the functions while the customer can only use the search function.
2.2 Overall Class Diagram
The class diagram is shown as below. It presents the relationships between the seven data
record classes.
Administrator
Customer
Add Records
Modify Records
Delete Records
Search Records
3. Sub functions
3.1 Add Records
3.1.1 Add War
Use Case:
Add record
Add war Add battle
Add location Add organization Add individual
Add participant Add contribution
Scope:
The World Of Warfare system
Level:
User goal
Primary Actor:
Administrator
Stakeholders and Interests:
-System administrators: hope to add a war record
Preconditions:
The records inside the system are already consistent
Success Guarantee:
- The war name is not reduplicate, the begin and end of the war are in date format, the war contains no less
than 1 battle
1. Administrator provides the basic information of war: name, begin, end, reason,
result
2. Administrator submits and the system asks him to confirm
3. Administrator confirms and system check
4. System confirms the war record is valid and system generates a new warID and
create new War records with basic information and warID
Extension
2a. Administrator doesn’t want to confirm immediately
a. 1. Go back to main flow 2
4a. System finds new records are not complete or not valid
1. System tells administrator about the error and reasons
2. System warns administrator, and requires him/her to modify inputs.
3. Go back to main flow 2
Sequence Diagram:
3.1.2 Add Battle
Use Case:
Scope:
The World Of Warfare system
Level:
User goal , sub-function
Primary Actor:
Administrator
Stakeholders and Interests:
-System administrators: hope to add a battle record
Preconditions:
The records inside the system are already consistent
Success Guarantee:
- The battle name is not reduplicate, the begin and end of the battle are in date format, the participant
of the battle must belong to the war
1. Administrator adds the basic information of Battle: name, begin, end, result,
location name, war name it belongs to
2. Administrator provides two participant information both with the organization
names they belong to , provides the location name of the battle
3. Administrator submits and the system asks him to confirm
4. Administrator confirms and system checks
5. System confirms the battle information is valid
6. system generates two pids for two participants, get war ID according to war name,
get location ID according to location name, get organization ids according to
organization names, generate a new bid
7. Create two participant records with pid, ForceDevoted, FinalState, Organization id,
battle id, war id
8. Create battle record with two pids, war id, location id, and its basic information
2a. If the location does not exist
1. Add a location record
2. Connects to the record
3. Go back to main flow 2
2b. Administrator wants to modify any record entered previously
1. Tell the system to modify the corresponding record in the list
2. System accepts and administrator modifies the corresponding information
3. Administrator finishes and system asks administrator for confirmation
a. Administrator confirms
i. System modify the record in the list
ii. Go back to main flow 2
b. Administrator cancels the confirmation
i. Go back to extension flow 2a.2
3a. Administrator doesn’t want to confirm immediately
c. 1. Go back to main flow 2
5a. System finds new records are not complete or not valid
1. System tells administrator about the error and reasons
2. System warns administrator, and requires him/her to modify inputs.
3. Go back to main flow 2
Sequence Diagram:
3.1.3 Add Location
Use Case:
Scope:
The World Of Warfare system
Level:
User goal
Primary Actor:
Administrator
Stakeholders and Interests:
-System administrators: hope to add a location record
Preconditions:
The records inside the system are already consistent
Success Guarantee:
- The location name is not reduplicate
1. Administrator adds the basic information of contribution: name, landform
2. Administrator links to a battle
3. Administrator submits and the system asks him to confirm
4. Administrator confirms and system checks
5. System confirms the location record is valid
3a. Administrator doesn’t want to confirm immediately
a) 1. Go back to main flow 1
5a. System finds new records are not complete or not valid
1. System tells administrator about the error and reasons
2. System warns administrator, and requires him/her to modify inputs.
3. Go back to main flow 2
Sequence Diagram:
3.1.4 Add Individual
Use Case:
Scope:
The World Of Warfare system
Level:
User goal
Primary Actor:
Administrator
Stakeholders and Interests:
-System administrators: hope to add a individual record
Preconditions:
The records inside the system are already consistent
Success Guarantee:
- The individual name is not reduplicate ,birth and death should be in date format or unknown, gender should
be male or female
1. Administrator adds the basic information of individual: name , birth, death, gender,
birthplace
2. Administrator links to an organization, and system adds the newly entered
organization record in a waiting list
Repeat 2 until all wanted organizations are added
3. Administrator submits and the system asks him to confirm
4. Administrator confirms and system checks
5. System confirms the individual record is valid
2a. Administrator wants to delete an individual entered previously
1. Tell the system to delete the corresponding record
2. System asks administrator for confirmation
a. Administrator confirms
i. System remove the entered organization from the list
ii. Go back to main flow 2
b. Administrator cancels the confirmation
i. Go back to main flow 2
2b. Administrator wants to modify an organization entered previously
1. Tell the system to modify the corresponding record in the list
2. System accepts and administrator modifies the corresponding information
3. Administrator finishes and system asks administrator for confirmation
a. Administrator confirms
i. System modifies the entered organization in the list
ii. Go back to main flow 2
b. Administrator cancels the confirmation
i. Go back to extension flow 2b.2
2c. If the organization does not exist
1. Add an organization record
2. Connects to the record
3. Go back to main flow 2
3a. Administrator doesn’t want to confirm immediately
d. 1. Go back to main flow 1
5a. System finds new records are not complete or not valid
1. System tells administrator about the error and reasons
2. System warns administrator, and requires him/her to modify inputs.
3. Go back to main flow 2
Sequence Diagram:
3.1.5 Add Contribution
Use Case:
Scope:
The World Of Warfare system
Level:
User goal
Primary Actor:
Administrator
Stakeholders and Interests:
-System administrators: hope to add a contribution record
Preconditions:
The records inside the system are already consistent
Success Guarantee:
- birth and death should be in date format or unknown, gender should be male or female
1. Administrator adds the basic information of contribution: position, description
2. Administrator links to an individual and a participant
3. Administrator submits and the system asks him to confirm
4. Administrator confirms and system checks
5. System confirms the individual record is valid
3a. Administrator doesn’t want to confirm immediately
e. 1. Go back to main flow 1
5a. System finds new records are not complete or not valid
4. System tells administrator about the error and reasons
5. System warns administrator, and requires him/her to modify inputs.
6. Go back to main flow 2
Sequence Diagram:
3.1.6 Add Organization
Use Case:
Scope:
The World Of Warfare system
Level:
User goal
Primary Actor:
Administrator
Stakeholders and Interests:
-System administrators: hope to add a organization record
Preconditions:
The records inside the system are already consistent
Success Guarantee:
- The organization name is not reduplicate
1. Administrator adds the basic information of organization
2. Administrator submits and the system asks him to confirm
3. Administrator confirms and system checks
4. System confirms the organization information is valid
5. System generate a new organization id
6. System create a new Organization record using organization id, information name and
landform
2a. Administrator doesn’t want to confirm immediately
a. 1. Go back to main flow 1
4a. System finds new records are not complete or not valid
1. System tells administrator about the error and reasons
2. System warns administrator, and requires him/her to modify inputs.
3. Go back to main flow 2
Sequence Diagram:
3.2 Delete Operations
3.2.1 Delete War
Use Case:
Scope:
The World Of Warfare system
Level:
User goal
Primary Actor:
Administrator
Stakeholders and Interests:
-System administrators: hope to delete some war records
Preconditions:
-The records inside the system are already consistent
-The list of war records that are to be deleted has been got by the previous action
Success Guarantee:
- The war records and corresponding records are successfully deleted and no logic conflicts exist.
2. Delete command is passed to the system to delete the target records
3. The system shows the list of war records and related battle records that would be
deleted together, and ask the administrator for configuration
4. Administrator confirm the deletion
5. System does the “delete battle” to delete the related battle records and other
related records. And then the responding war records are deleted and the result is
shown to the administrator
Extension
3a. Administrator wants to refer to the detail information of a record in the deletion list
1. Administrator chooses one of the records in the list
2. The system shows the information of the chosen information
3. Administrator finishes viewing and informs the system. The system goes back to the
deletion.
3b. Administrator wants to cancel the deletion
2. Administrator pass the cancel command to the system
3. System goes back to the search scenario and locates to the previous war
searching result, waiting for the administrator to do the next action.
3b. Administrator wants to cancel the deletion
1. Administrator pass the cancel command to the system
2. System go back to the search scenario and locate to the previous war searching
result, waiting for the administrator to do the next action
4a. the “battle deletion” is unsuccessful.
1. System warns the administrator about the failure both with its reason,
administrator cancels the deletion and goes back to the previous war searching
result, waiting for the administrator to do the next action.
Sequence Diagram:
3.2.2 Delete Battle
Use Case:
Scope:
The World Of Warfare system
Level:
User goal , sub-function
Primary Actor:
Administrator
Stakeholders and Interests:
-System administrators: hope to delete some battle records
Preconditions:
-The records inside the system are already consistent
-The list of battle records that are to be deleted has been got by the previous action
Success Guarantee:
- The battle records and corresponding records are successfully deleted or modified and no logic conflicts
exist.
1. Delete command is passed to the system to delete the target records
2. The system shows the list of battle records and related participant records that
would be deleted together, the related location records and war records that would
be modified , and ask the administrator for configuration
3. Administrator confirm the deletion
4. System does the “modify location” and “modify war” to delete the relation between
the records to be deleted and the corresponding location records and war records
5. System does the “delete participant” to delete the related participant records. And
then the responding battle records are deleted and the result is shown to the
administrator
Extension
3a. Administrator wants to refer to the detail information of a record in the deletion or
modification list
1. Administrator chooses one of the records in the list
2. The system shows the information of the chosen information
3. Administrator finishes viewing and informs the system. The system goes back to the
deletion.
3b. Administrator wants to cancel the deletion
1. Administrator pass the cancel command to the system
2. System goes back to the previous action scenario, waiting for the administrator
to do the next action
4a. some modification is unable to complete
1. System warns the administrator about the failure both with its reason,
administrator undo the modification that has done
2. System cancels the deletion and goes back to the previous action scenario,
waiting for the administrator to do the next action
5a. the “deletion partcipates” is unsuccessful.
1. System warns the administrator about the failure both with its reason,
administrator undo the modification in step 4
2. System cancels the deletion and goes back to the previous action scenario,
waiting for the administrator to do the next action
Sequence Diagram:
3.2.3 Delete Location
Use Case:
Scope:
The World Of Warfare system
Level:
Sub-function
Primary Actor:
Administrator
Stakeholders and Interests:
-System administrators: hope to add a contribution record
Preconditions:
The records inside the system are already consistent
-The list of location records that are to be deleted has been got by the previous action
Success Guarantee:
- The location records are deleted and no battle records related to these location records exist
1. Delete command is passed to the system to delete the target records
2. The system shows the list of location records that would be deleted, and ask the
administrator for configuration
3. Administrator confirm the deletion
4. System checks whether there exist battle record related to these locations
5. System deletes the corresponding location records and the result is shown to the
administrator
Extension
3a. Administrator wants to refer to the detail information of a record in the deletion list
1. Administrator chooses one of the records in the list
2. The system shows the information of the chosen information
3. Administrator finishes viewing and informs the system. The system goes back to
the deletion.
3b. Administrator wants to cancel the deletion
1. Administrator pass the cancel command to the system
2. System goes back to the search scenario and locate to the previous battle
searching result, and waiting for the administrator to do the next action
4a. there still are battle records related to the location records to be deleted
1. System warns the administrator about the failure both with its reason,
administrator u and asks the administrator whether delete these related battle
records
a. The administrator wants to delete the related battle records
1. System do the “delete battle”, then back to location deletion
b. The administrator wants to give up the deletion
1. System cancels the deletion and goes back to the previous action
scenario, waiting for the administrator to do the next action
Sequence Diagram:
3.2.4 Delete Organization
Use Case:
Scope:
The World Of Warfare system
Level:
Sub-function
Primary Actor:
Administrator
Stakeholders and Interests:
-System administrators: hope to add a contribution record
Preconditions:
The records inside the system are already consistent
-The list of organization records that are to be deleted has been got by the previous action
Success Guarantee:
- The organization records are deleted, corresponding participant records and individual records are
successfully modified and no logic conflicts exist
1. Delete command is passed to the system to delete the target records
2. The system shows the list of organization records that would be deleted, related
participant and individual records that would be deleted, and ask the administrator
for configuration
3. Administrator confirm the deletion
4. System does the “modify participant” and “modify individual” to delete the relation
between the records to be deleted and the corresponding participant records and
individual records
5. System deletes the corresponding contribution records and the result is shown to
the administrator
Extension
3a. Administrator wants to refer to the detail information of a record in the deletion list
1. Administrator chooses one of the records in the list
2. The system shows the information of the chosen information
3. Administrator finishes viewing and informs the system. The system goes back to
the deletion.
3b. Administrator wants to cancel the deletion
1. Administrator pass the cancel command to the system
2. System goes back to the search scenario and locate to the previous battle
searching result, and waiting for the administrator to do the next action
4a. some modification is unable to complete
1. System warns the administrator about the failure both with its reason,
administrator undo the modification that has done
2. System cancels the deletion and goes back to the previous action scenario,
waiting for the administrator to do the next action
Sequence Diagram:
3.2.5 Delete Individual
Use Case:
Scope:
The World Of Warfare system
Level:
User goal
Primary Actor:
Administrator
Stakeholders and Interests:
-System administrators: hope to add a individual record
Preconditions:
The records inside the system are already consistent
-The list of individual records that are to be deleted has been got by the previous action
Success Guarantee:
- The individual records and corresponding records are successfully deleted or modified and no logic conflicts
exist
1. Delete command is passed to the system to delete the target records
2. The system shows the list of individual records and contribution records that would
be deleted together, participant and organization records that would be modified,
and ask the administrator for configuration
3. Administrator confirm the deletion
4. System does the “modify participant” and “modify organization” to delete the
relation between the records to be deleted and the corresponding participant
records and organization records
5. System does the “delete contribution” to delete the related contribution records.
And the corresponding individual records are deleted and the result is shown to the
administrator
Extension
3a. Administrator wants to refer to the detail information of a record in the deletion or
modification list
1. Administrator chooses one of the records in the list
2. The system shows the information of the chosen information
3. Administrator finishes viewing and informs the system. The system goes back to the
deletion.
3b. Administrator wants to cancel the deletion
1. Administrator pass the cancel command to the system
2. System goes back to the search scenario and locate to the previous battle
searching result, and waiting for the administrator to do the next action
4a. some modification is unable to complete
1. System warns the administrator about the failure both with its reason,
administrator undo the modification that has done
2. System cancels the deletion and goes back to the previous action scenario,
waiting for the administrator to do the next action
5a. the “deletion contribution” is unsuccessful.
1. System warns the administrator about the failure both with its reason,
administrator undo the modification in step 4
2. System cancels the deletion and goes back to the previous action scenario,
waiting for the administrator to do the next action
Sequence Diagram:
3.2.6 Delete Contribution
Use Case:
Scope:
The World Of Warfare system
Level:
Sub-function
Primary Actor:
Administrator
Stakeholders and Interests:
-System administrators: hope to add a contribution record
Preconditions:
The records inside the system are already consistent
-The list of contribution records that are to be deleted has been got by the previous action
Success Guarantee:
- The contribution records are deleted, corresponding records are successfully modified and no logic conflicts
exist
1. Delete command is passed to the system to delete the target records
2. The system shows the list of individual records that would be deleted, related
participant and individual records that would be modified, and ask the administrator
for configuration
3. Administrator confirm the deletion
4. System does the “modify participant” and “modify individual” to delete the relation
between the records to be deleted and the corresponding participant records and
individual records
5. System deletes the corresponding contribution records and the result is shown to
the administrator
Extension
3a. Administrator wants to refer to the detail information of a record in the deletion or
modification list
1. Administrator chooses one of the records in the list
2. The system shows the information of the chosen information
3. Administrator finishes viewing and informs the system. The system goes back to
the deletion.
3b. Administrator wants to cancel the deletion
1. Administrator pass the cancel command to the system
2. System goes back to the search scenario and locate to the previous battle
searching result, and waiting for the administrator to do the next action
4a. some modification is unable to complete
1. System warns the administrator about the failure both with its reason,
administrator undo the modification that has done
2. System cancels the deletion and goes back to the previous action scenario,
waiting for the administrator to do the next action
Sequence Diagram:
3.3 Modify Operations
3.3.1 Modify War
Use Case:
Scope:
The World Of Warfare system
Level:
User goal, sub-function
Primary Actor:
Administrator
Stakeholders and Interests:
Modify record
Modify war Modify battle
Modify location Modify organization Modify individual
Modify participant Modify contribution
System administrators: Wants to modify the data of incorrect war records
Preconditions:
The administrator has found the record to be modified, and it is displayed on the screen
Success Guarantee:
-Administrator’s modifications are successful and the data is stored.
- After modification, the war name is not reduplicate, the begin and end of the war are in date
format, the war contains no less than 1 battle
Main Success Scenario(or Basic Flow):
1. Administrator selects the war record to be modified
2. Administrator modifies the record, and system asks for confirmation, and administrator
confirms
3. System modifies the corresponding records in database and signals task completion
Extensions(or Alternative Flows):
1a. Administrator selects an unwanted record
1. Administrator chooses to undo
2. Go back to main flow 1
2a. Administrator doesn’t want to confirm immediately
1. Go back to main flow 1
3a. System fails to modify a record
1. System inform the administrator the failure information, normally post condition not
satisfied
2. System asks the administrator whether to retry or quit
2a. The administrator wants the system to retry
1. Go back to main flow 3
2b. The administrator wants to quit
1. The system goes back to initial state
Sequence Diagram:
3.3.2 Modify Battle
Use Case:
Scope:
The World Of Warfare system
Level:
User goal , sub-function
Primary Actor:
Administrator
Stakeholders and Interests:
- System administrators: Wants to modify the data of incorrect battle records
Preconditions:
The records inside the system are already consistent
Success Guarantee:
- After modification, the battle name is not reduplicate, the begin and end of the battle are in date format, the
participant of the battle must belong to the war
9. Administrator selects the battle to be modified
10. Administrator modify the information of battle
11. Administrator submits and the system asks him to confirm
12. Administrator confirms and system checks
13. System confirms the war record is valid and system save the record
2a. If the administrator wants to modify location link
4. Link to another location record
5. Go back to main flow 2
3a. Administrator doesn’t want to confirm immediately
f. 1. Go back to main flow 2
5a. System finds modified records does not satisfy the post condition
System tells administrator about the error and reasons
4. System warns administrator, and requires him/her to modify inputs.
5. Go back to main flow 2
Sequence Diagram:
3.3.3 Modify Location
Use Case:
Scope:
The World Of Warfare system
Level:
Sub-function
Primary Actor:
Administrator
Stakeholders and Interests:
- System administrators: Wants to modify the data of incorrect location records
Preconditions:
The records inside the system are already consistent
Success Guarantee:
-After modification, the location name is not reduplicate
1. Administrator selects the location to be modified
2. Administrator modifies the basic information of contribution: name, landform, and link
to battle
3. Administrator submits and the system asks him to confirm
4. Administrator confirms and system checks
5. System confirms the location record is valid
2a. If the administrator wants to modify participant link
1. Link to another battle record
2. Go back to main flow 2
3a. Administrator doesn’t want to confirm immediately
g. 1. Go back to main flow 2
5a. System finds modified records does not satisfy the post condition
System tells administrator about the error and reasons
1. System warns administrator, and requires him/her to modify inputs.
2. Go back to main flow 2
Sequence Diagram:
3.3.4 Modify Individual
Use Case:
Scope:
The World Of Warfare system
Level:
User goal , sub-function
Primary Actor:
Administrator
Stakeholders and Interests:
- System administrators: Wants to modify the data of incorrect individual records
Preconditions:
The records inside the system are already consistent
Success Guarantee:
- After modification, birth and death should be in date format or unknown, gender should be male or female
6. Administrator selects the individual to be modified
7. Administrator modifies the basic information of individual: name , birth, death,
gender, birthplace, and links to participant
8. Administrator submits and the system asks him to confirm
9. Administrator confirms and system checks
10. System confirms the individual record is valid
2a. If the administrator wants to modify participant link
1. Link to another participant record
2. Link to the corresponding organization record
3. Go back to main flow 2
3a. Administrator doesn’t want to confirm immediately
h. 1. Go back to main flow 2
5a. System finds modified records does not satisfy the post condition
System tells administrator about the error and reasons
3. System warns administrator, and requires him/her to modify inputs.
4. Go back to main flow 2
Sequence Diagram:
3.3.5 Modify Contribution
Use Case:
Scope:
The World Of Warfare system
Level:
Sub-function
Primary Actor:
Administrator
Stakeholders and Interests:
- System administrators: Wants to modify the data of incorrect contribution records
Preconditions:
The records inside the system are already consistent
Success Guarantee:
-After modification, the attributes of contribution record should not be blank
1. Administrator selects the contribution to be modified
2. Administrator modifies the basic information of individual: position discreption
3. Administrator submits and the system asks him to confirm
4. Administrator confirms and system checks
5. System confirms the individual record is valid
3a. Administrator doesn’t want to confirm immediately
i. 1. Go back to main flow 2
5a. System finds modified records does not satisfy the post condition
System tells administrator about the error and reasons
1. System warns administrator, and requires him/her to modify inputs.
2. Go back to main flow 2
Sequence Diagram:
3.4. Search Operations
3.4.0 Search By Keyword
Use Case:
Scope:
The World Of Warfare system
Level:
User goal
Primary Actor:
Administrator ,Customer
Stakeholders and Interests:
-System administrators: hope to search a record by key word to modify or delete
-Customer: hope to search a record by key word
Preconditions:
The records inside the system are consistent
Success Guarantee:
null
1. User input the keyword
2. User submits information, system checks the query
Search record
Search battle
Search war
Search
individual
Search by
keyword
Search
organization
Search
location
Search date
Search
participant
Search
contribution
3. System search in database and displays all information about the corresponding
record
Extension:
2a.
1. system find that the query submitted is empty
a. inform the user to input some keywords to search
b. go back to main flow 1
Sequence Diagram:
3.4.1 Search War
Use Case:
Scope:
The World Of Warfare system
Level:
User goal
Primary Actor:
Administrator ,Customer
Stakeholders and Interests:
-System administrators: hope to search a war record to modify or delete
-Customer: hope to search a war
Preconditions:
The records inside the system are consistent
Success Guarantee:
Begin end should be in date format
1. User provides some of the wars’ information: name, begin, end, reason, result
2. User submits information, system checks the query
3. System search in database and displays all information about the corresponding
record
Extension:
2a.
1. system find that the query submitted is empty
a. inform the user to input some keywords to search
b. go back to main flow 1
Sequence Diagram:
3.4.2 Search Battle
Use Case:
Scope:
The World Of Warfare system
Level:
User goal
Primary Actor:
Administrator
Stakeholders and Interests:
-System administrators: hope to search a battle record to modify or delete
-Customer: hope to search a battle
Preconditions:
The records inside the system are consistent
Success Guarantee:
Begin and end should be in date format
1. User provides some of the battle’s information: name, begin, end, reason, result
2. User submits information, system checks the query
3. System search in database and displays all information about the corresponding
record
Extension:
2a.
1. system find that the query submitted is empty
a. inform the user to input some keywords to search
b. go back to main flow 1
Sequence Diagram:
3.4.3 Search Location
Use Case:
Scope:
The World Of Warfare system
Level:
User goal
Primary Actor:
Administrator ,Customer
Stakeholders and Interests:
-System administrators: hope to search a location by key word to modify or delete
-Customer: hope to search a location record
Preconditions:
The records inside the system are consistent
Success Guarantee:
null
1. User provides some of the location’s information: name, landform
2. User submits information, system checks the query
3. System searches in database and displays all information about the corresponding
record
Extension:
2a.
1. system find that the query submitted is empty
a. inform the user to input some keywords to search
b. go back to main flow 1
Sequence Diagram:
3.4.4 Search Organization
Use Case:
Scope:
The World Of Warfare system
Level:
User goal
Primary Actor:
Administrator ,Customer
Stakeholders and Interests:
-System administrators: hope to search an organization by key word to modify or delete
-Customer: hope to search an organization by key word
Preconditions:
The records inside the system are consistent
Success Guarantee:
Begin and end should be in date format
1. User provides some of the organization’s information: name, begin, end, description
2. User submits information, system checks the query
3. System searches in database and displays all information about the corresponding
record
Extension:
2a.
1. system find that the query submitted is empty
a. inform the user to input some keywords to search
b. go back to main flow 1
Sequence Diagram:
3.3.5 Search Individual
Use Case:
Scope:
The World Of Warfare system
Level:
User goal ,
Primary Actor:
Administrator
Stakeholders and Interests:
-System administrators: hope to search an individual to modify or delete
-Customer: hope to search an individual
Preconditions:
The records inside the system are consistent
Success Guarantee:
Birth ,death should be in date format. Gender should be male or female.
1. User provides some of the individual’s information: name, birth, death, gender,
birthplace
2. User submits information, system checks the query
3. System searches in database and displays all information about the corresponding
record
Extension:
2a.
1. system find that the query submitted is empty
a. inform the user to input some keywords to search
b. go back to main flow 1
Sequence Diagram:
3.4.6 Search Contribution
Use Case:
Scope:
The World Of Warfare system
Level:
User goal
Primary Actor:
Administrator ,Customer
Stakeholders and Interests:
-System administrators: hope to search a contribution record to modify or delete
-Customer: hope to search a contribute
Preconditions:
The records inside the system are consistent
Success Guarantee:
null
1. User provides some of the contribution’s information: position description
2. User submits information, system checks the query
3. System search in database and displays all information about the corresponding
record
Extension:
2a.
1. system find that the query submitted is empty
a. inform the user to input some keywords to search
b. go back to main flow 1
Sequence Diagram:
3.4.7 Search Participant
Use Case:
Scope:
The World Of Warfare system
Level:
User goal
Primary Actor:
Administrator ,Customer
Stakeholders and Interests:
-System administrators: hope to search a participant record to modify or delete
-Customer: hope to search a participant
Preconditions:
The records inside the system are consistent
Success Guarantee:
ForceDevoted should be a range of number, FinalStates should be win or lose or tie.
1. User provides some of the participant’s information: ForceDevoted, FinalState
2. User submits information, system checks the query
3. System search in database and displays all information about the corresponding
record
Extension:
2a.
1. system find that the query submitted is empty
a. inform the user to input some keywords to search
b. go back to main flow 1
Sequence Diagram: