Ctts Milestone 2 Detail Template

CTTS – Customer Technology Tracking System

Author (s): _Quoc __ Date: __02/24/2015___

Version: ___________

USE CASE NAME: | View system software configuration information | USE CASE TYPE |

USE CASE ID: | CTTS-04 | Business Requirements: |

PRIORITY: | High | System Analysis: |

SOURCE: | | System Design: |

PRIMARY BUSINESS ACTOR | Technician |

PRIMARY SYSTEM ACTOR | Technician |

OTHER PARTICIPATING ACTORS: | * Technician, Coastline Managements |

OTHER INTERESTED STAKEHOLDERS: | |

DESCRIPTION: | This is an event of viewing the system software configuration, where by the Technician can only see the system software configuration information about their client |

PRE-CONDITION: | The users must have logged on to the system so as to identify the user as technician who has access to retrieve the configuration information from the system. |

TRIGGER: | This is initiated after user login to access the configuration information in the user interface. |

TYPICAL COURSE OF EVENTS: | Step 1: This use case will be implemented when the user have access to selects the option from the system to view all or particular software configuration information. | |

| Step 2: After the user has selects the option to display, the system will respond by showing the information of the system configuration associated with the request. | |

| Step 3: User can view configuration information with the date and time it was last updated in the system. | |

| Step 4: The User has option to edit or update to the configuration information seen on the user interface. | |

| Step 5: There will be an option to update what was written or override back to the previous information by accepting or ignoring the changes. | |

ALTERNATE (ABNORMAL) COURSES: |

| Step 1: the user must have access to the system in order to view the configuration information. |

| Step 2: User can view and update but cannot change the list of standard...