On 27th. February 2008 we had a second project meeting according to our project plan, and among other things, our customers agreed with the current stage of the impelementation and, suggested some interesting functionalities to be added to the application to make it even better.
So far so good, we got to solve some critical problems with the help of some ITmill specialists and now everything is back on trac an we are rolling on with few remaining stuffs.
stay in touch.
Thursday, February 28, 2008
Monday, February 25, 2008
CLASS DESCRIPTIONS
The description of the Ticket
| Class name | Ticket | |
| Specification | A class that defines a collection of attributes that makes a ticket. Ticket is a term used in internet support to submit a problem specification. | |
| Super Class | No super class | |
| Attributes | id | An identification number of a ticket |
| type | type of the ticket, if it is a defect, enhancement or task | |
| time | this shows when the ticket was created to the system | |
| changetime | this shows the most current time when the last comment was posted, or attachement | |
| component | In this case this shows which component is concerned in a ticket | |
| severity | this describes how critical is the problem | |
| priority | this describes how is the priority of the ticket | |
| owner | this is the name of the person who will be responsible for the ticket | |
| reporter | name of the person who creates a ticket | |
| cc | Carbon copy to someone else than owner | |
| version | version of the system reported | |
| milestone | this denotes how far the issue has been resolved | |
| status | Shows the stage process of the ticket issue. | |
| resolution | Like status but shows that the ticket is valid, a duplicate or fixed. | |
| summary | Short title of the ticket. | |
| description | Short explanation of the ticket. | |
| Keywords | this are map words to be used for indexing or searching tickets | |
| Associations | No associations | |
The description of the TicketAttachment
| Class name | TicketAttachment | |
| Specification | This is an extra file which is added to the ticket as a supporting document or a reference. it can be any type of document file in electronic form. | |
| Super Class | No super class | |
| Attributes | type | This defines to what is the attachment attached to. e.g. ticket or wiki |
| id | identification number of the attachment | |
| filename | This is a name of the attachment. | |
| size | size of the attachment in bytes | |
| time | The time an attachment has been added. | |
| description | short summary about the attachment | |
| author | the name of the person who added an attachment | |
| ipnr | ip number | |
| Associations | No associations | |
The description of the TicketComment
| Class name | TicketComment | |
| Specification | Test description added as extra information to the ticket, it can be an advice, or criticism. | |
| Super Class | No super class | |
| Attributes | ticketId | unique identification of a comment |
| createTime | The time when the comment was added. | |
| owner | This is the name of the person who will be responsible for the ticket. | |
| content | The text content of the comment. | |
| Associations | No associations | |
Saturday, February 23, 2008
Chabo screen shots
The following are some screen shots taken from the current version of chabo for trac implementation.
Screen showing ticket details
Screen showing a search option
Screen showing create new ticket panel
Wednesday, February 13, 2008
Chabo Use case model
1. USE CASE MODEL
1.1 Use case map
The use case map describes the main use case chabo for trac system. The use case maps are described for each sub-system contains the services of the chabo for trac and all the services provided by the application.
Picture 1.1: the use case map of chabo for trac application..
1.2 Main use case descriptions
1.2.1 Create ticket.
Using this use case a user can create a new ticket into the system, no user registration is required, which means a user can create a ticket anonymously.
The selections are:
· Create new ticket.
1.2.2 View ticket
Using this use case a user can view a ticket by selecting from a list of listed tickets, or by using a search use case then after the use case returns all the available tickets according to the search results, user can use this use case to view the details of a single ticket.
Selections are:
· View ticket
1.2.3 Search ticket
Hundreds of tickets will be saved in the application database, so by using this use case a user may search tickets from the trac database by different criteria’s. And the use case will return any results found from the database for the user to select a single ticket and view details by using view details use case. This use case provides results only when tickets exist in the system.
Selections are:
· Select criteria
· search ticket
1.2.4 Add comment
All tickets in the system can have comments, and these comments can be added by any one who is viewing the ticket. Any user viewing a ticket and feels like commenting on a ticket or putting some new ideas to the ticket issue, then this is the use case to serve that purpose. But it is used only when there is a ticket existing in a system which a comment is going to be bound with, so no comments without a ticket.
Selections are:
· Add comment
1.2.5 Add attachment
All tickets in the system can have attachments, and these attachments can be added by any one who is viewing the ticket. Any user viewing a ticket and feels its necessary to add an attachment to the ticket or putting some new ideas to the ticket issue through an attachment, then this is the use case to serve that purpose. But it is used only when there is a ticket existing in a system which an attachment is going to be bound with, so no attachments without a ticket.
Selections are:
· Add attachment
1.3 Actor descriptions
There is only one actor for chabo for trac application, which is any user who can access the service. The following are the descriptions of the main actor of the application.
| Actor/user role | Description | Authorities | Amount |
| The User | The user creates new ticket to the system, adds comments to tickets in the system, search tickets according to criteria’s also add attachments to the tickets. | Any user has permission to create a new ticket, add comment and attachment so the system | About 0 to 1m personnel |
1.4 Use cases
The following are the detailed description in diagrams and descriptions. The use case diagrams describe structures of the main use cases and include all sub-use cases, actors (user roles and external systems) and dependencies between the use cases.
1.4.1 Create ticket.
Descriptions
| Overview |
| Using this use case a new ticket is added to the system. A new ticket maybe added to the system even if the ticket of the same topic does exist in the system, so user my need to search for the topic first before creating a new ticket. |
| Use case selections | |
| |
| Actors | Usage |
| user | New tickets are crated every time any user wants to. |
Create ticket- selection 1:
Create new ticket to the system.
| Preconditions |
| No preconditions. |
| Results |
| A new single reservation with customer data ,and a play turn is added to the system |
| Flow of activities |
| Select create new ticket–function The system displays the new ticket template. |
| Enter relevant information of the new ticket, also give a brief description of the ticket, after all the details has been added, then user may submit the ticket for it to be created in the system. |
1.4.2 View ticket
Descriptions
| Overview |
| The user use this use case to view tickets, by default the application shows a list of most recent tickets, user may choose from a list to view the details of a single ticket. Or user may use the search ticket use case to enter a search criteria and search for a list of all available tickets matching the search keyword. After the result of a search has been returned, user may use this use case to view the details of a single ticket from a list of tickets. |
| Use case selections | |
| 1. view ticket | |
| Actors | Usage |
| user | many tickets can be viewed everyday |
| Additional information | |
| Screens: Printouts: | |
View ticket- selection 1:
| Preconditions |
| A ticket must be existing in the system in order for it to be viewed |
| Results |
| A user views all details of a selected ticket including all its comments if any and attachments if any.. |
| Description (Flow of activities.) |
User selects a ticket from a list of active tickets, or from a search result of tickets. |
The system displays details of a ticket including all its comments and attachments if any. |
1.4.3 Search ticket
Descriptions
| Overview |
| Using this use case; user may find and browse tickets from the system using different search criteria and keywords, in the search option user can select if user wants to search by i.e. component, type, description etc. all the possible selection are listed in a control so that use may easily pick the most suitable selection, after that there is a an option to put a keyword to accompany the selection and make the search more specific on what a user want to find. |
| Use case selections | |
| |
| Actors | Usage |
| user | Any time user want to search for a ticket this use case is used. |
| Usability requirements | |
| Some search criteria should be provided to facilitate the search process | |
search ticket- selection 1:
| Preconditions |
| No pre-conditions |
| Results |
| Ticket records in form of rows are displayed in a table structure and the rows are clickable to allow user to view ticket details. |
| Description (Flow of activities.) |
|
1.4.4 Add comment
Overview
using this use case, use may add comments to tickets, for the purpose of sharing ideas, additional information, corrections to the tickets and any other issues which are relevant to the ticket can be commented using this use case. This use case extends view tickets use case, so a use has to be in a view ticket screen to access this use case. There is no any other direct way to comment a ticket without being in its view screen.
Use case diagram
Descriptions
| Overview | |
| using this use case, use may add comments to tickets, for the purpose of sharing ideas, additional information, corrections to the tickets and any other issues which are relevant to the ticket can be commented using this use case. This use case extends view tickets use case, so a use has to be in a view ticket screen to access this use case. There is no any other direct way to comment a ticket without being in its view screen. | |
| Use case selections | |
| |
| Actors | Usage |
| user | Ticket can have as many comments as possible, and user may add many comments to the ticket with no limitations. |
| Usability requirements | |
| ticket must exist in the system for it to be commented | |
Add comment- selection 1:
Add comment
| Preconditions |
| A ticket to be commented must exist in the system before a comment. |
| Results |
| A ticket with comments |
| Description (Flow of activities.) |
i. The system displays ticked details. |
i. The system display comment text editor |
| |
1.4.5 Add attachment
Overview
using this use case, use may add attachments to tickets, for the purpose of sharing ideas, additional information, corrections to the tickets and any other issues which are relevant to the ticket can be attached using this use case. This use case extends view tickets use case, so a use has to be in a view ticket screen to access this use case. There is no any other direct way to attach to a ticket without being in its view screen
Use case diagram
Descriptions
| Overview | |
| using this use case, use may add attachments to tickets, for the purpose of sharing ideas, additional information, corrections to the tickets and any other issues which are relevant to the ticket can be attached using this use case. This use case extends view tickets use case, so a use has to be in a view ticket screen to access this use case. There is no any other direct way to attach to a ticket without being in its view screen | |
| Use case selections | |
| |
| Actors | Usage |
| user | Ticket can have as many attachments as possible, and user may add many attachments to the ticket with no limitations. |
| Usability requirements | |
| ticket must exist in the system for it to be added an attachment | |
Add comment- selection 1:
Add comment
| Preconditions |
| A ticket to be added an attachment must exist in the system. |
| Results |
| An attachment in the system |
| Description (Flow of activities.) |
i. The system displays ticked details. |
i. The system displays browse and upload component. ii. Browse for a file to attach iii. click upload to upload the attachment |
| |
Monday, February 11, 2008
Testing!
After the implementation of some basic functionality of the chabo application, Che is creating some test classes for testing most of the functionality of the app. He is using JUnit API for creating test classes.
Subscribe to:
Posts (Atom)