Add new Branches
Show details of all flats
Show details of all houses Technical Report
Modify Branches
Add properties
<<includes>>
<<includes>>
<<includes>>
<<includes>>
Modify Properties
Delete Branches
<<includes>>
Delete Properties
<<includes>>
<<includes>>
<<includes>>
Login
View all sold properties
<<includes>>
Administrator
Query properties by their address
Branch Secretary
<<includes>>
<<includes>>
<<extends>>
Show details of all properties
<<includes>>
Incorrect Login Refuse Login
Record sales price of properties and remove from list when sold
Documentation
Identifier and name: UC1 Login
Initiator: Administrator and Branch Secretary
Goal: Login and access the system
Precondition: Login page displays a text box for user to enter username and password
Post-condition: Initiator can access the property sales system
Assumptions: Initiator works forthe national property sales company
Main success scenario:
- Display login page with username and password text fields
- Initiator goes to the login in page
- In the given text fields, initiator enters the username and password
- IF the username and password is correct THEN
the admin will have access to the branch and properties and the secretary will have access to the properties in the branches.
- ELSE initiator will be refused access to the system and be required to try and login again
- END IF
Extends: Incorrect login refuse login
Identifier and name: UC2 Incorrect login refuse login
Initiator: Administrator and Branch Secretary
Goal: Refuse login and access to the system if the username and password is incorrect.
Precondition: Login page displays a text box for user to enter username and password
Post-condition: Login page will display message saying, ‘The username and password used is incorrect please try again’.
Assumptions: Initiator has both a username and password
Main success scenario:
- Display login page
- Administrator or branch secretary logs in with username and password as prompted
- IF the username or password is incorrect THEN
page will display error message
- WHEN error message is displayed, then
it will ask the user to try again
- And the user will be required to type the username and password again.
- END IF
Identifier and name: UC3 Add New Branches
Initiator: Administrator
Goal: Administrator adds new branches to the system
Precondition: Administrator Logs in successfully to add a new branch
Post-condition: A new branch is added to the system, which allows the branch secretary to add properties to the newly added branch.
Assumptions: Individual logging into the system is an admin and can therefore add a branch to the system
Main success scenario:
- Display login page
- Admin logs into the system with username and password.
- IF the username and password is correct THEN
the admin will be successfully logged in.
- ELSE admin will be refused access.
- END IF
- The admin will select add a new branch.
- The admin will give the branch a name, address, phone number, email address, web address.
- The admin will also give the branch a username and password.
- When the admin is finished entering the information for the new branch, he/she will select save.
- The new branch will be added, and the system will be updated.
Includes: Login
Identifier and name: UC4 Delete branches
Initiator: Administrator
Goal: Delete existing branch in the system
Precondition: The branch is stored in the system in the list of branches
Post-condition: The branch is deleted from the system
Assumptions: The branch is no longer needed in the system
Main success scenario:
- Display login page
- Admin logs into the system with the username and password
- IF the username and password is correct THEN
the admin will be successfully logged in
- ELSE admin will be refused access to the system
- END IF
- The administrator will select the delete branch button
- The system will give the admin a list of branches
- From the list the admin will select an option.
- The option selected by the admin will be deleted from the system
Includes: Login
Identifier and name: UC5 Modify branches
Initiator: Administrator
Goal: Change details of existing branch in the system
Precondition: The branch has already been created and stored in the system
Post-condition: The branch will be updated with the new details
Assumptions: Something is wrong with the details of a branch
Main success scenario:
- Display login page
- Admin logs into the system with the username and password
- IF the username and password is correct THEN
the admin will be successfully logged in
- ELSE admin will be refused access to the system
- END IF
- The administrator will select the modify branch button
- The system will give the admin a list of branches
- From the list the admin will select an option.
- The option selected by the admin will display all details of that branch
- The admin will then be able to change any of the details given
- When the admin is finished changing the details then he/she will select save.
- The new details for that branch will be saved to the system
Includes: Login
Identifier and name: UC6 Show details of all houses
Initiator: Branch Secretary
Goal: Display the details of each house on the system
Precondition: The system consists of a list of all the houses
Post-condition: The system shows a list of all the houses and the details for each house
Assumptions: Each house in the system can be found by their address
Main success scenario:
- The branch secretary logs into the system with the branch username and password
- IF the login is successful THEN
the secretary will have access to the properties in each branch.
- ELSE the secretary will be refused access to the system
- END IF
- When the secretary is logged in then he/she can select the houses button.
- The button will take the secretary to the page that displays all the houses with their details.
- The secretary will be able to view all houses on the system and the details about each house.
Includes: Login
Identifier and name: UC7 Show details of all flats
Initiator: Branch Secretary
Goal: Display the details of each flat on the system
Precondition: The system consists of a list of all the flats
Post-condition: The system shows a list of all the flats and the details for each flat
Assumptions: Each flat in the system can be found by their address
Main success scenario:
- The branch secretary logs into the system with the branch username and password
- IF the login is successful THEN
the secretary will have access to the properties in each branch.
- ELSE the secretary will be refused access to the system
- END IF
- When the secretary is logged in then he/she can select the flats button.
- The button will take the secretary to the page that displays all the flats with their details.
- The secretary will be able to view all flats on the system and the details about each flat.
Includes: Login
Identifier and name: UC8 Add properties
Initiator: Branch Secretary
Goal: Secretary adds new properties to the system
Precondition: Branch Secretary Logs in successfully to add a new property
Post-condition: A new property is added to the list of properties on the system
Assumptions: The new property has an address
Main success scenario:
- Display login page
- Branch secretary logs into the system with username and password.
- IF the username and password is correct THEN
the secretary will be successfully logged in.
- ELSE secretary will be refused access.
- END IF
- The secretary will select add a new property.
- The secretary will give the property an address, number of rooms, selling price, sold price, whether it is a flat or house.
- IF the property is a house then the secretary will give it number of floors, whether it has a garden or not and whether it has a garage or not.
- ELSE it is a flat and then the secretary will give details on which floor it is on, and its monthly charge.
- When the secretary is finished entering the information for the new property, he/she will select save.
- The new property will be added, and the system will be updated.
Includes: Login
Identifier and name: UC9 Modify properties
Initiator: Branch Secretary
Goal: Modify properties in the system
Precondition: Various properties are in the system
Post-condition: An existing branch is modified
Assumptions: Property is either a flat or a house
Main success scenario:
- The branch secretary logs into the system using the branch username and password
- IF the username and password is correct THEN
the branch secretary will have access to the properties on the system
- ELSE the secretary will be refused access to the system
- END IF
- The secretary will select a property that already exists on the system by selecting the modify property button
- The system will give the secretary a list of properties
- From the list the secretary will select an option.
- The option selected by the secretary, will display all details of that property
- The secretary will then be able to change any of the details given
- When the secretary is finished changing the details then he/she will select save.
- The new details for that property will be saved to the system
Includes: Login
Identifier and name: UC10 Delete properties
Initiator: Branch Secretary
Goal: Delete existing property in the system
Precondition: The property is stored in the system in the list of properties
Post-condition: The property is deleted from the system
Assumptions: The property is no longer needed in the system
Main success scenario:
- Display login page
- Branch secretary logs into the system with the username and password
- IF the username and password is correct THEN
the secretary will be successfully logged in
- ELSE secretary will be refused access to the system
- END IF
- The secretary will select the delete property button
- The system will give the secretary a list of properties
- From the list the secretary will select an option.
- The option selected by the secretary will be deleted from the system
Includes: Login
Identifier and name: UC11 View sold properties
Initiator: Branch Secretary
Goal: View properties that have been sold
Precondition: System consists of a list of all the properties that have been sold
Post-condition: Branch secretary is able to view the list of properties that have been sold
Assumptions: Each property has a selling price
Main success scenario:
- Branch secretary logs into the system with branch username and password
- IF the username and password is correct THEN
then the secretary will have access to all the properties
- ELSE branch secretary will be refused access
- END IF
- From the options the secretary will select ‘Sold Properties’ button
- This will display a list of all the properties that have been sold and how much they were sold for
Includes: Login
Identifier and name: UC12 Query properties by their address
Initiator: Branch Secretary
Goal: request information about a property by using the property address
Precondition: The property is in the list of houses or flats
Post-condition: The secretary searches for information about a property using its address
Assumptions: Each property is in the system with an address
Main success scenario:
- Branch secretary logs into the system with branch username and password
- IF the username and password is correct THEN
then the secretary will have access to all the properties
- ELSE branch secretary will be refused access
- END IF
- From the options the secretary will select ‘query a property’ button
- This will give the option to search for a property by typing in the property address.
- The secretary will then be able to view the details about the property he/she searched for.
Includes: Login
Identifier and name: UC13 Show details of all properties
Initiator: Branch Secretary
Goal: View all details about a property
Precondition: All properties are in a list and can be found when the properties button is selected
Post-condition: The secretary can view all details about each and every property
Assumptions: Each property is in the system is either a flat or house
Main success scenario:
- Branch secretary logs into the system with branch username and password
- IF the username and password is correct THEN
then the secretary will have access to all the properties
- ELSE branch secretary will be refused access
- END IF
- From the options the secretary will select ‘view properties’ button
- This will send the secretary to a page where there is a list of each and every property in the system
- The secretary will then be able to view the details about all properties
Includes: Login
Identifier and name: UC14 Record sales price of properties and remove from list when sold
Initiator: Branch Secretary
Goal: Add sales prices to a property and remove it from the list of properties once it is sold
Precondition: Each property in the list of properties have no sales price and haven’t been sold yet.
Post-condition: The secretary can add a sales price for properties and delete from the system once sold
Assumptions: All properties in the system haven’t been sold yet
Main success scenario:
- Branch secretary logs into the system with branch username and password
- IF the username and password is correct THEN
then the secretary will have access to all the properties
- ELSE branch secretary will be refused access
- END IF
- From the options the secretary will select ‘record sales’ button
- This will send the secretary to a page where there is a list of each and every property in the system
- The secretary will then be able to select the property that he/she wants to add a sales price to.
- Once the sales price is added to the property the property will be removed from the list.
Includes: Login
The post Administrator and Branch Secretary appeared first on My Assignment Online.