Requirements Specifications

Transcription

1 Jupiter Requirements Specifications Essa Imhmed, Hitesh N. Sharma, Sultan Alharthi, Ruth Torres Castillo, Vijaya Pandey 1

2 1. As a user, I want to add user stories to the system so that I can save them. Given a user an interface that makes it possible to add a story: System should show a button that lets user add user story. The interface should show input fields that lets user add various parameters of user stories such as description, priority etc. System should show the add story dashboard. The add story dashboard must show text box to enter story. 2. As a user, I want to save user stories to the system so that I can use them later. Given a user an interface that makes it possible to save a story and that all the parameters for new user story are addede in revelant text boxes or fields: Click a save button on add story dashboard. System must show a confirmation message. Main dashboard must show the new added user stories. 3. As a user, I want to edit user stories so that I can change them. Given a user an interface that makes it possible to edit a story: Click an edit button which is available alongside a list of user story. System should show the picked user story page. After making changes, there should be a button to save the changes. System must show a confirmation message. Main dashboard must show the updated user story. 4. As a user, I want to view the list of all user stories so I can easily navigate between them. Main dashboard must show all saved user stories. 2

3 5. As a user, I want to add developers to the system so that I can link them to user stories. Given a user an interface that makes it possible to add user: Click a add user button in the interface. System must show the add user dashboard that allows user to enter information about the new user. Click a save button that allows to save it. System must show a confirmation message. Main dashboard must show the added user. 6. As a user, I want to edit user information so that I can change them. Given a user an interface that makes it possible to edit developers: Click the edit user button next to the user. System must show the edit user dashboard Click the save changes button. System must show a confirmation message. Main dashboard must show the updated developer. 7. As a user, I want to view the list of all developers so I can easily navigate between them. Main dashboard must show a list of all developers. 8. As a user, I want to link developers to stories so that work is assigned. Given a user an interface that makes it possible to link developers to story. Pick the user story you want to link to. The story page should be visisble and it must show a list of users to be added. Pick the user for this story Click an update button to update the user story. System must show a confirmation message. 3

4 9. As a user, I want to add code to each user story so that I can easily link code lines to this story. Given a user an interface that makes it possible to add code to a story: Pick a story you want to link a code to. The story page should show open and there must be a add code button that allows to select location of the code file in the system. Specify the location of the code and click a button to link it. System must show the code on the story dashboard. 10. As a user, I want to link code lines to stories so that I can easily locate them. Given a user an interface that makes it possible link code lines to story: The interface should show a dashboard that shows details of user story and code on a text box which it was previously linked with. Each code line has a select box. Select the lines of code that you want to link. Click a link button that links that code. System must show a confirmation message. Code box should show the linked lines when you reopen it. 11. As a user, I want to view user stories statistics so that I can keep track of stories progress. Given a user an interface that makes it possible to view stories statistics: Main dashboard must show a summary of progress and status of all stories. 12. As a user, I want the system to generate requirement document from user stories so that I can share/view their status based on user requirement. : Main dashboard must show a generate requirement button. An interface should allow to select user stories and specify the location to save the document and have a button to save it. The generated requirement document should be in the selected folder. 4

5 13. As a user, I want to delete user story from the system so that I can discard it. Given a user an interface that makes it possible to delete user story. The interface should show a list of user stories with a delete button. When the delete button is executed, system should ask for a confirmation message. A confirmation message should be displayed that shows that the user story is deleted. Main dashboard must not show the deleted story. 14. As a user, I want to search user story from the system so that I view it. Given a user an interface that provides a search box. User should be able to select criteria for search i.e, select a parameter on which he wants to search, such as description, priority etc. System should show a list of user stories when a user adds relevant keywords in the text box and performs search. 5

6 6 Domain Model For Jupiter

7 May 2, 2015 Testing Description for Jupiter Essa Imhmed, Hitesh N. Sharma, Sultan Alharthi, Ruth Torres Castillo, Vijaya Pandey

8 Test Plan Jupiter is a desktop application made to create user stories and manage them to create the requirements document and then link them to the code that was developed from them. The present document will describe the complete suite of artifacts that describe the test planning of the system. The Test items used for this plan were the user stories created at the beginning of this project and in order to follow the agile software development process. For each user story, some features were tested, based on acceptance criteria. According to its testing approach each user story did pass/fail the acceptance criteria, in which case a new item was documented on this testing plan. A lot of testing was based on acceptance testing in which a team member acted as an external user. For a subset of tests, we used Junit or Sikuli as described below. After making use of suspension and resumption steps for each testing case we ended with the testing results as deliverables. Moreover because there were different tasks that were performed by every other team member, there was the need to have different environmental needs, such as Junit for functional testing and Sikuli for graphical interface testing. Also different responsibilities were given in order to follow the testing plan, in which case new needs of training were required and taken into consideration for the schedule of this project. Test scripts are also a good idea to have for letting a tester test a feature, but due to time constraints in the project, we did not use test scripts, rather just rely in acceptance criteria of user stories. The next part of the document provides the description of each acceptance criteria for every user story. The part following it will describe the tools used to test each of them according to the functionality of the user story. Further, we mention about issues we encountered once we tested our system and the advantages of using a new tool such as Sikuli. Tests Performed The validation tests for Jupiter were performed to verify the completed functions of the Application according to the expectations defined by the specifications. The overall objective is to uncover situations that could negatively impact the usability and software quality. The test items used for this plan were the user stories that were created at the beginning of this project in order to follow the agile software development process, which are recorded in the Requirement Specifications document, and we have to mention that some of these user stories were merge into one test case for the a better sequence in testing. Because every other team member performed different tasks, there was the need to have different environmental needs, such as Junit for functional testing and Sikuli for graphical interface testing. 2

9 Test Items for JUnit Junit was used to test the three main functions Add, Edit and Delete a User Story into a *.csv file. A test suite was created with these three classes. The example below is a part of one of the main functions Add User Story public class testaddmethod public void testadd() { ArrayList<String> newinput = new ArrayList<String>(); newinput.add("id1"); newinput.add("subject1"); newinput.add("userrole1"); newinput.add("description1"); newinput.add("reason1"); newinput.add("acceptancecriteria1");; newinput.add("elaboration1"); newinput.add("createdby1"); newinput.add("assignedto1"); newinput.add("requirementtype1"); newinput.add("duration1"); newinput.add("status1"); newinput.add("parentuserstory1"); newinput.add("priority1"); newinput.add("type1"); UserStory test=new UserStory(newinput); List<String> result=test.adduserstory(); String index=newinput.get(0); rwfile read=new rwfile(); String ex=read.searchfor(index); //asserts that the read result is the same we input assertequals(ex, result.tostring()); } 3

10 Test Items and acceptance criteria for Sikuli testing 1. As a user, I want to create a new project so that I can have a new file that stores user stories. System must enable all the other features that include the following user stories A new file has been created on the application running folder with the name of the project. assuming the user has not created any project: Click the button Create New Project. Enter the project name. Click the Create button. Click the Save Project button. Revise that the new *.csv file is created 2. As a user, I want to open project so that I can work on it. System must enable all the features that include the following user stories US 3 - US15. The name of the opened file should be shown in the interface. assuming the user has not opened any project: Click the button Open Project. Select the.csv file to work with. Click the Open button. The options to Add, Edit, Delete, Story Hierarchy and Requirement Document are now enabled 3. As a user, I want to add user stories so that I can capture the requirements. Given a user an interface that makes it possible to add a story: System must show fields to enter story. assuming the user has already opened a project: Click the button Add User Story. Fill all the fields of the User Story. Go to test case 4 4

11 4. As a user, I want to save user stories so that I can use them later. Given a user an interface that makes it possible to save a story: System must show the new added user story. assuming the user has already fill all the fields: Click the Save button The edit/add screen closes and click the Save Project button. Revise the.csv file to see the updated user Story. 5. As a user, I want to edit user stories so that I can change them. Given a user an interface that makes it possible to edit a story: System should allow user to pick user story to edit. System must show fields to change story. System must show the updated user story. assuming the user has already opened a project and picked one user story: Click the button Edit Story. Modify the desire fields of the User Story. Go to test case 4 6. As a user, I want to delete user story from the system so that I can discard it. Given a user an interface that makes it possible to delete user story. System should allow user to pick user story to delete. System should ask to confirm the deletion. System must show a confirmation message. Deleted user story must not be in the system anymore. assuming the user has already opened a project and picked one user story: Click the button Delete Story. The grid containing the User Stories is updated and the deleted User Story is deleted from the list. Click the Save Project button. Revise the.csv file to see the changes. 5

12 7. As a user, I want to view all the user stories so I can easily navigate between them. System must show all saved user stories. assuming the user has opened or created a new project: The grid displays all the Story Users that belong to that project. Click the User Story to select it Revise the whole information of that User Story in the frame below it. 8. As a user, I want to view all users so that the User Stories can be assigned. System must show all the users on the upper left corner assuming the user has opened or created a new project: Go to test case 7 Revise the whole information of the Users in the frame of the upper left. 9. As a user, I want to add code to each user story so that I can easily link code lines to this story. Given a user an interface that makes it possible to add code to a story: The story page should allow adding a code from a location in the system. System must display the code on the story dashboard. assuming the user has already opened a project and picked one user story: Click the button Edit Story. Click the button Open Code. Select a *.java file to read and display. Click the button Open. Go to test case 10 6

13 10. As a user, I want to link code lines to stories so that I can easily locate them. Given a user an interface that makes it possible link code lines to story: Each code line can be selected. Code box should show the linked lines when you reopen it. assuming the user has already opened a project, picked one user story and open a *.java file to add code lines linkage: The *.java file should be displayed as lines of codes. Select the lines that will be linked to that User Story Click the button Link. Verify the new link in the dropdown list Go to test case 4 Verify the code lines added on the *.csv file 11. As a user, I want the system to generate requirement document from user stories so that I can share/view their status based on user requirement. Given a user an interface that makes it possible to generate requirement: The generated requirement document should be in the selected folder after generating it. assuming the user has already opened a project: Click the button Requirement Document. Select the options to display on the Requirement Document. Select the Sorted by criteria to display on the Requirement Document. Click the button Generate Document. Go to test case 4. Revise that the new *.pdf file is created. Verify the selected options on the *.pdf file. 12. As a user, I want to view all user stories in hierarchical form so that I can capture all the relationship between them. Given a user an interface that makes it possible to display user stories tree: User story tree should be displayed on the dashboard. assuming the user has already opened a project: Click the button Story Hierarchy. Select the arrow next to All Stories. Select the arrow next to Parent Story to display down the tree the corresponding children Select the arrow next to Parent Story to un expand the tree 7

14 13. As a user, I want to view an alert message so that I know when all options are disable because no project is opened. Given a user an interface that makes it possible to display alert messages: System should display Error message. assuming the user has not opened or created any project: Click the button Add User Story. A pop up message should be displayed. Close the pop up window Click the button Story Hierarchy. A pop up message should be displayed. Close the pop up window Click the button Requirement Document. A pop up message should be displayed. Close the pop up window 14. As a user, I want to view an alert message so that I know when all options are disable because no user story has been selected. Given a user an interface that makes it possible to display alert messages: System should display Error message. assuming the user has not opened or created any project: Click the button Edit Story. A pop up message should be displayed. Close the pop up window Click the button Delete Story. A pop up message should be displayed. Close the pop up window. 8

15 Sikuli Testing Sikuli is an open-source research project originally started at the User Interface Design Group at MIT. It automates anything you see on the screen. It uses image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code. Below is a sample Sikuli Test Script of Adding a User Story. 9

16 10

17 A sample of Sikuli Testing of Adding user story. 11

18 12

19 Our experience with Sikuli Like mentioned above, we used Sikuli for testing all the user stories, and it helped us a lot in test and maintain user friendliness of the software. Using Sikuli testing we could verify if our application was user friendly, and easy to navigate and use. With this tool we were able to build step by step procedures for testing each of our main user stories. Further, user stories which were very difficult to test using unit testing were easily tested using Sikuli e.g, Viewing User stories in hierarchical tree form, generating and viewing Requirements Document in as pdf document, linking User story to code lines. The main difficulties when Sikuli testing was being performed arose when there were two or more similar pieces of UI (e.g., two "Accept" buttons, one on an error and one on a standard configuration screen), and also when something on the UI was changing among different versions. Hence, in order to have the Sikuli scripts running correctly, the interfaces should be stable otherwise Sikuli script needed to be redone. Hence, it is advisable to use Sikuli at the end or when you are sure that the interfaces will not change anymore. Further, this might also be a way to know that user interface has changed over time. Testing System We tested our application in the following systems: Operating System Windows 8, 7 Mac OS X 10 Device type Laptop Laptop 13

20

21

22

23

24

25

26

27