Home Inventory Project Final Presentation
Contents
1. Admin Data 29 Page Server Functionality n Admin Persistent Connection Direct Access to the Database Ability to Add or Remove Users Can modify user information if needed XML used for all a Browse Items Insert Items adr 0000000000 ogo Users 30 Page Class Diagrams The following are the class diagrams for the Client and the Server Due to the depth of the client side code the class diagrams for the client are presented in different views The diagrams for the client consist of a general overview of the entire project structure and different views of the code segments from both the Admin and User perspective 31 Page General Client Overview All Classes Generated by UModel www altova com 32 Page Home Inventory Client User Overview lt lt constructor gt ModifyUser Page _Loaded in sender object in e RoutedEventArgs void a Confirm Modify Button Click in sender object in e RoutedEventArgs void a HomeButton_Click in sender object in e RoutedEventArgs void a Logout_Click in sender object in e RoutedEventArgs void O lt lt constructor gt gt BrowseMenu finished cick in sender object in e RoutedEventArgs void a ModifyMenu_Button_Click in sender object in e RoutedEventArgs void a Page_Loaded in sender object in e RoutedEventArgs void a ItemBox_SelectionChanged in sender object in e SelectionChangedEventArgs void a Browselenu_delete_button_Cli2. a 11 Page The Admin selects the Print Item menu q ep 0 h The System prompts the Admin to enter in the UserID of the account to print items from The Admin enters in the UserID The System prompts the Admin to select the item to print The Admin selects items to be printed The System prompts the Admin to confirm the print job The Admin confirms the Print The items are printed 6 Modify Item Prerequisite Login and Browse menu a sm mm AOS i j The Admin selects Modify Item menu The System prompts the Admin to enter in the UserID of the account to modify the items of The Admin enters in the UserID The System prompts the Admin to select the item to modify from the Browse field The Admin selects the item to modify The system displays the attributes of the item The Admin modifies the item s Attributes The System prompts the Admin to confirm the modification of the item s attributes The Admin confirms the modification The System saves the attributes 7 Modify User ID and Password Prerequisite Login a m 07 20 0 h The Admin selects the Account Settings menu The System Prompts the Admin for the User ID and Password of the account to modify The Admin enters the UserlD and Password of the account The System displays account information The Admin modifies the account settings The System prompts the Admin to confirm the new settings The Admin co
3. effort My teams choose to use this experience not only to increase our knowledge of team oriented development but also to acquire firsthand skill in technologies we had little practice in We perceived this endeavor as more of a learning opportunity then as an effort to develop a marketable product The first seemingly odd design choice is the fact that the client and server in our project are written in different languages The reason we wrote the client in C was to allow us to gain some experience in Microsoft s NET framework and the Visual Studio development environment We choose to write the Server in Java because of our familiarity with the synchronization features of the language The final questionable design choice is the fact that we choose to develop a client server application rather than a web app The reason for this design choice is the fact that we planned to develop the program as a mobile application we than wanted to deploy the software on a small portable device like a Kindel book reader Neither of these ideas worked out mostly due to monetary issues and we stuck with the original design in order to stay on schedule With the background information presented above we will now present the documentation for our project The documentation breaks down into a requirements section design section and a testing section Each section contains different documents that we used to develop our project Below we present our requi
4. gt HomelnventoryOpenTag String lt Homelnventory gt lt lt const gt gt HomelnventoryCloseTag String lt Homelnventory gt lt lt const gt gt MessageOpenTag Strino lt Message gt lt lt const gt gt MessageCloseTag String lt Message gt lt lt const gt gt MessageTypeOpenTag String lt MessageType gt lt lt const gt gt MessageTypeCloseTag String lt MessageType gt lt lt const gt gt ParameterO penTag String lt Parameter gt lt lt const gt gt ParameterCloseTag String lt Parameter gt lt lt const gt gt UserNameOpenTag String lt UserName gt lt lt const gt gt UserNameCloseTag String lt UserName gt lt lt const gt gt UserNamePasswordOpenTag String lt Password gt lt lt const gt gt UserNamePasswordCloseTag String lt Password gt lt lt const gt gt MessageNumberOpentag String lt MessageNumber gt lt lt const gt gt MessageNumberClosetag String lt MessageNumber gt lt lt const gt gt MessageSenderOpentag String lt MessageSender gt lt lt const gt gt MessageSenderClosetag String lt MessageSender gt lt lt const gt gt InsertMessageUPCOpenTag String lt UPC gt lt lt const gt gt InsertilessageUPCCloseTag String lt UPC gt lt lt const gt gt InsertilessageDescripOpentag String lt Description gt lt lt const gt gt InsertMessageDesripClosetag String lt Description lt lt const gt gt InsertMessageSizeOpenTag String lt Size g
5. lt lt const gt gt USER_INVALID String 30494 lt lt const gt gt INSERT_SUCCESS String 92341 lt lt const gt gt INSERT_FAILED String 124543 lt lt const gt gt MODIFY SUCCESS String 234543 lt lt const gt gt MODIFY_FAILURE String 823456 lt lt const gt gt DELETE_SUCCESS String 14256 lt lt const gt gt DELETE_FAILURE String 235769 lt lt const gt gt LOGOUT_SUCCESS String 34534 lt lt const gt gt LOGOUT_FAILURE String 785654 lt lt const gt gt VALID_USER String 123422 lt lt const gt gt ADMIN_VALID String 758434 lt lt const gt gt CREATE_USER_SUCCESS String 213324 lt lt const gt gt CREATE_USER_FAILURE String 576874 lt lt const gt gt ADMIN_DELETE_ITEM_SUCCESS String 33241 lt lt const gt gt ADMIN_DELETE_ITEM_FAILURE String 93842 lt lt const gt gt ADMIN_INSERT_ITEM_SUCCESS String 32345 lt lt const gt gt ADMIN_INSERT_ITEM_FAILURE String 54665 lt lt const gt gt ADMIN_MODIFY_USER_SUCCESS String 3245575 lt lt const gt gt ADMIN MODIFY USER FAILURE String 586788 lt lt const gt gt ADMIN MODIFY TEM SUCCESS String 43654 lt lt const gt gt ADMIN MODIFY TEM FAILURE String 96675 lt lt const gt gt REMOVE USER SUCCESS String 80154 lt lt const gt gt REMOVE USER FAILURE String 10364 lt lt const gt gt UPC SUCCESS String 65678654 lt lt const gt gt UPC_FAILURE String 1212378 BB BBB BB BBB BB lt lt construc
6. 4 Delete Items Prerequisite Login and Browse menu a b c d e f The User selects the Delete Item button from the Browse Menu The System prompts the User to select the item s to delete The User finds the item to be deleted in the Browse field The System prompts the User to confirm the deletion The User confirms the item deletion The System removes the item from the inventory 5 Print Items Prerequisite Login and Browse menu a b c d e f The User selects the Print Item button The System prompts the User to select the item to print The User selects items to be printed The System prompts the User to confirm the print job The User confirms the Print The items are printed 6 Modify Item Prerequisite Login and Browse menu a b The User selects Modify Item menu The System prompts the User to select the item to modify from the Browse field 8 Page c d e f g h The User selects the item to modify The system displays the attributes of the item The User modifies the item s Attributes The System prompts the User to confirm the modification of the item s attributes The User confirms the modification The System saves the attributes 7 Modify User ID and Password Prerequisite Login a b c d e f g h The User selects the Account Settings menu The System Prompts the User for the User ID and Password The Us
7. By clicking on the Delete Item button the selected item is deleted from the user s table The screen is refreshed and the item is no longer listed since it no longer exists Modifying Items To modify any item simply replace the text in the right side boxes and click Modify Item 23 Page Inserting Items E RT Insertltem Menu Description UPC BarCode Insert Manual Insert For Users insert consists of Manual and Barcode inserts For Barcode insertion simply enter the UPC number and choose Barcode Insert If the item is found in the database it it inserted automatically Otherwise the item must be inserted manually 24 Page 25 Page Design Documents Section Design Diagrams XML Protocol Documents 26 Page General Description The purpose of the home Inventory project is to produce a software product that can be used to inventory the household items of a home A description of the items in a home will be stored in a database on a central server that will keep track of the inventory of multiple homes The core features of the product will include but are not limited to 1 A networking functionality consisting of an automatic product suggestion feature that will return product suggestions based on current contents of database The system will also interface with a central server to store the contents of a particular household 2 Acentral server that store the contents of a household in a database The
8. Description gt A brief description lt Description gt lt Size gt Used by DB admin lt Size gt lt Upload Date gt Date item was added 23 Mar 2009 lt Upload Date gt lt Item gt lt Parameter gt lt Message gt lt Home Inventory gt 42 Page Client C gt Server login lt Home Inventory gt lt Message gt lt Message Type gt login lt Message Type gt lt Parameter gt lt username gt what s my user name lt username gt lt pass gt don tell people your passwords lt pass gt lt Parameter gt lt Message gt lt Home Inventory gt Client gt Server login response Server Response lt Home Inventory gt lt Message gt lt Message Type gt loginResponse lt Message Type gt lt Parameter gt lt status gt 46534 for success 30494 for failure lt status gt lt reason gt String representing the reason for failure lt reason gt lt usertype gt 758434 for Admin 123422 for Normal user lt usertype gt lt Parameter gt lt Message gt 43 Page lt Home Inventory gt Client lt gt Server Modify item message un All attributes of an item that are NOT modified will be set to an empty string lt Home Inventory gt lt Message gt lt Message Type gt Modify lt Message Type gt lt Parameter gt lt ltem gt lt Table gt Home tablenumber lt Table gt lt ID gt lt ID gt lt UPC gt lt UPC gt un lt Description gt lt Description g
9. Insert Button Click in sender object in e RoutedEventArgs void Q lt lt constructor AdminCresteUserScreen a Create User Button in sender object in e RoutedEventArgs void D Admin CreateUser LogoutButton Clck in sender object in e RoutedEventArgs void D Admin CreateUser HomeButton_Click in sender object in e RoutedEventArgs void lt lt constructors gt AdminHomePage D Create_User_Button_Click in sender object in e RoutedEventArgs void D Browse User Button Clck in sender object n e RoutedEventArgs void D Admin Home Page Inserttems Button Click in sender object in e RoutedEventArgs void D Admin_HomeMenuLogoutButton_Click in sender object in e RoutedEventArgs void Generated by UModel www altova com 34 Page ZD Q 35 Page Home Inventory Client Utility Classes Overview 1 firstName String lastName String userName String password String primPhone int altPhone int email String address String userType int userList LinkedList lt T1 gt User gt new LinkedList lt User gt lt lt constructor gt gt User in givenFirstName String in givenLastName String in givenUserName String in givenPassword String in givenEmail String in givenAddress String in givenPrimPhone int in given lt lt GetAccessor SetAccessor property gt gt userFirstName String lt lt GetAccessor SetAccessor property gt gt userLastName String lt lt Get
10. clients logged into the Homelnventory have access to a variety of commands Homelnventory stores each user s items safely and privately without worry that others will see their additions Why Home Inventory Homelnventory allows for multiple users to store their belongings privately into a shared database With the Homelnventory you can track your accumulated purchases by entering Logging In When first running the client application you ll be greeted with the following page Welcome To Your Ho Inventory UM Entering your credentials will log you into the system Be sure as to not leave either field blank If you attempt a login with incorrect credentials you ll be prompted with an appropriate message Below is an example of logging in with an invalid username 16 Page Welcome To Your Ho Inventory A el Admin Usage Navigating the Home Screen In Homelnventory Users and Administrators have different home pages catering to the features of each First we ll take a look at the Administrative features Below at the Home Menu there are four major options 2 Admin Home Menu Create User Menu Admin Insert Items 17 Page Creating A New User eee 4 Create User Screen Like most of the menus the Create User screen is very intuitive With this feature Administrators supplies the new information required to create a new user Such as below Administrators fill in the fields and cli
11. database will consist of UPC codes that will precisely identify each household item by serial number 3 A user interface that will be very intuitive to even the most novice computer user The goal of the user interface design is to allow convenient access to the database and encourage regular use of the system The above features are to be considered the core design goal for the project Given the fact that new features can be thought of as the project progresses it is entirely possible that more enhancements to the system can be made 27 Page Detailed Design As stated above the system will consist of three core features namely a network function a database function and a user interface The implementation of the system will be broken down into these three categories each category will consist of specific task and design goals The tools used to implement each task in different categories will vary but in general each task will be completed using the same general tools The general programming language used to implement the system is Microsoft C This particular language was chosen in order to utilize the graphical user interface feature found in NET products As a option the use of Java will be left open to the developers of the system Java will only be used when specific network functionality dictates 28 Page User 3 Laptop Workstation Laptop
12. developers of the system interpret as normal use of the systems functionalities Test procedures will consist of very precise steps that intentionally don t seek to cause anomalies in functionality of the system Put simply These tests don t seek to break the system just to ensure that the system is not easily broken e Freelance testing This phase of testing will provide the freedom of the testers to implement their own improvisational testing steps In this phase the testers should try to crash the system all while documenting each step they take thoroughly in order to assist in debugging e Network load testing This phase of testing has the primary objective of ensuring that the system can handle a reasonable amount of users accessing it in parallel This is a major requirement for the success of the system since the Home Inventory project was developed with parallel use in mind Each test phase described above will be completed in a sequential fashion The ideal flow of testing will involve following the test procedure test failure reporting to the developers and 68 Page finally the developer resolving the failure and publishing the actions to the testers If for some reason the developers find themselves in a squeeze for time while debugging it is assumed that the problem at hand can be set aside while other test are performed The objective of the test phases it to perform all of the test procedures and report failures to th
13. for duplicate User Name value Status in Progress Test Failure Severity Low Test Failure 27 Apr 2009 Admin browse user Description After a user is deleted from the system the screen still displays the user credentials Status fixed User Name and ID are removed after removal of User Test Failure Severity Low Test Failure 27 Apr 2009 Admin Create User Description After a User is created input fields still contain values Status fixed fields clear after create action 87 Page Test Failure Severity Severe Test Failure 27 Apr 2009 Admin Browse User Items Description System crashes if user attempts to delete an item withour selecting an item from the Item list box Status fixed System will prompt User if error occurs Test Failure Severity Low Test Failure 27 Apr 2009 Admin Insert Item Screen Description Barcode lookup button and insert button labeled wrong Status fixed Test Failure Severity low Test Failure 23 Apr 2009 Enter wrong password at Login Screen Description Message box displays wrong user name even if the password was wrong Status Fixed Message box now displays both Wrong user name and password Test Failure Severity low Test Failure 23 Apr 2009 User view items menu has a print button Description Print option was removed from System design Status Fixed Removed Print button 88 Page Load Test Report In order to test the ability of our server to handle multiple s
14. if 1 Manuel 65 Page Modify Item Chane Account Settings Account Settin os Mod Save Settinos 66 Page Testing Documents Section 67 Page Home Inventory Project Software Test Plan Written by Thomas D Elliott The purpose of this document is to specify a testing plan for the Home Inventory project of CIS 4329 Spring 2009 This document will explain in a high level the reasons and objectives of the procedures to be carried out in the actual testing of the system This document is split into three sections firstly it defines and explains a method of testing secondly it lays out a schedule to perform the test so that they debugging can coincide with testing and lastly we explain the responsibilities of the testers and those of the debuggers Part 1 Methods of Testing The testing of the Home Inventory project will not follow any formal software testing methodology instead testing will be performed in a manner that is best suited for the time constraints and resources of the developers The testing of the system can be best described as Workability Testing in essence the objective of all software testing is to ensure that the product works for the user Workability Testing is just a streamlined version of steps needed to achieve that goal In testing the Workability of the system we will break the testing procedure up into three phases namely e Casual Use phase This phase will consist of what the
15. is not found e Description varchar lt vital information used to identify product such as name and manufacturer This is determined by the RPC e Size varchar or null e Upload Date varchar 60 Page Sqlite Vs MySQL Sqlite e Serverless e Embedded in your code e Inthe public domain e Pretty much ignores types This gives a certain type of flexibility in certain situations e Perfect for low load websites or desktop applications e Makes debugging really easy Fire up the console on the file your application is writing to and watch the inserts deletes etc as they happen e No configuration necessary and no XML parsing e No security except for native file system security on the data file e Best for single user use only one person accessing a database at a time After reading the above pros and cons of Sqlite it would be perfect for our first database model which is at the current time the following e One database stores usernames and passwords as of right now in unencrypted form but this may change if time allows Since the verification thread simply reads from the user database and the admin function to create username password only writes to the user database we will most likely not run into any problems due to multithreading The problems would only occur when multiple writes occur at the same time e Each user has his her own database to contain their items Since Salite is so light weight a database is c
16. lt UserName gt user name lt UserName gt lt Password gt password lt Password gt lt UserType gt 1 for Admin 2 for regular User lt UserType gt lt User gt lt Message gt lt Home Inventory gt Admin Create User Message Server gt Client lt Home Inventory gt lt Message gt lt Message Type gt CreateUser Message Type gt lt Status gt 213324 for success 576874 for failure lt Status gt lt Message gt lt Home Inventory gt 48 Page Admin Browse User Message Server Client lt Home Inventory gt lt Message gt lt Message Type gt BrowseUserResponse lt Message Type gt lt User gt lt UserlD gt ID lt UserlD gt lt UserName gt username lt UserName gt lt User gt lt User gt lt UserlD gt ID lt UserlD gt lt UserName gt username lt UserName gt lt User gt lt User gt lt UserlD gt ID lt UserlD gt lt UserName gt username lt UserName gt lt User gt lt Message gt Admin Browse User Message Client gt Server lt Home Inventory gt lt Message gt lt Message Type gt BrowseUser lt Message Type gt lt Message gt 49 Page lt Home Inventory gt Admin Browse User Items Client gt Server lt Home Inventory gt lt Message gt lt Message Type gt BrowseUserltems lt Message Type gt lt Parameters gt lt UserName gt The User Name lt UserName gt lt UserlD gt The Users ID lt UserlD gt lt Parameters lt Message gt lt Home Inventory g
17. 9 Try the following situational tests a Modify the same item b Leave an item blank c Leave all items blank 20 Records results 21 Log out or back to Home Page 84 Page Test Reports 85 Page Home Inventory Bug Report Test Failure Severity Severe Test Failure 23 Apr 2009 HomeButton not working on Modify User Page Description Home button unresponsive Status Fixed Test Failure Severity Severe Test Failure 23 Apr 2009 HomeButton not working on Browse User Page Description Home button unresponsive Status Fixed Test Failure Severity Low Test Failure 23 Apr 2009 View User Attributes Description Click on View User Attributes takes you to Modify User You are then forced to modify the user and the login name must be changed due to uniqueness rule Status Fixed Test Failure Severity Severe Test Failure 27 Apr 2009 Insert items Admin UI Description If the Item fields are empty the system will still return success status for an attempted item insert Status Fixed code 86 Page Test Failure Severity Moderate Test Failure 27 Apr 2009 Admin browse user items Description The Item upload date displays inaccurate values Status User enters values prior to insert database no longer automatically sets field Test Failure Severity Severe Test Failure 27 Apr 2009 Admin modify user attributes Description Unable to modify Users attributes due to server side error Sever incorrectly checks
18. Accessor SetAccessor property gt gt userUserName String lt lt GetAccessor SetAccessor property gt gt userPassword String lt lt GetAccessor SetAccessor property gt gt userEmail String lt lt GetAccessor SetAccessor property gt gt userAddress String lt lt GetAccessor SetAccessor property gt gt userPrimPhone int lt lt GetAccessor SetAccessor property gt gt userAltPhone int lt lt GetAccessor SetAccessor property gt gt userUserType int UPC String D String Description String Size String UploadDate String itemsList LinkedList lt T1 gt em gt new LinkedList lt item gt lt lt constructor gt gt tem in givenUPC String in givenlD String in givenDescription String in givenSize String in givenUploadDate String lt lt GetAccessor SetAccessor property gt gt itemUPC String lt lt GetAccessor property gt gt itemiD String lt lt GetAccessor SetAccessor property gt gt itemDescription String lt lt GetAccessor SetAccessor property gt gt itemSize String lt lt GetAccessor property gt gt itemUploadDate String lt lt constructor gt LoginScreen Button Click in sender object in e RoutedEventArgs void Button_Click_1 in sender object in e RoutedEventArgs void Generated by UModel www altova com Home Inventory Client Utility Classes Overview 3 pkg Homelnventory 36 22222222 G 22 23 23 2 2222222322222 lt lt const gt
19. Home Inventory Project Final Presentation CIS 4398 Projects in Computer Science Thomas D Elliott Thomas Manigly Roy Zuniga 1 Page Introduction Computer Software is currently being used in almost every area of everyday life Cell Phones televisions stoves cars and even some of our toasters use software to make them easier to use and thereby improve life for the people that use them With the influx of smart technology into our cars and cell phones it seems odd that the place where we spend the most time is lagging behind in this trend Our homes are the next facet of our lives that we should improve using electronics Imagine waking up in the morning and as soon as your alarm goes off the shower in your bathroom warms the water to a temperature of your liking After you shower your home tells you this morning s news and weather at the same time sending a signal to your car to warm up for your commute to work All of these improvements are possible with current technology there has just never been a strong initiative to implement them The Smart House is a home that utilizes technology to make life easier for its occupants No matter if you re a senior citizen living alone or a college student rooming with four classmates everyone can use technology in their homes to improve the quality of their life Before we can build an actual smart house with have to develop the components that will be the foundation of the system On
20. Item button the selected item is deleted from the user s table The screen is refreshed and the item is no longer listed since it no longer exists Modifying Items To modify any item simply replace the text in the right side boxes and click Modify Item 20 Page Modifying Users Modifying users works in the same manner as modifying items From the Browse Users menu select a user and click on View User Attributes The screen is nearly identical to the Create User menu The users information is displayed in the fields to modify change values and choose Confirm Modify Inserting Items From the Home Screen navigate to the Insert Item Menu via the Admin Insert Items button E i a Insert Item Menu Description 1 estuser 2 cjames 3 admin UPC i Users 26 jjames 25 user3 24 jjose Size mese 23 rzuniga BarCode Lookup Insert Item Inserting an item into a users table consists of simply selecting a user and supplying the item information For ease of use and consistency using barcode lookup checks the supplied UPC code against a UPC database and retrieves the information 21 Page Users Home Screen Navigation Home Menu Insert Items The User Home screen is substantially more limited than the Administrator page 22 Page Browsing Items Browse Menu Computer 5 Description Oak Desk 6 Size Upload Date Tiffany Lamp 7 ey Delete Item Modify Item Deleting Items
21. Message gt lt Message Type gt UPC Lookup lt Message Type gt lt Status gt Success 65678654 Failure 1212378 lt Status gt lt Parameter gt lt ltem gt lt UPC gt item upc lt UPC gt lt Description gt item description lt Description gt lt Size gt item Size lt Size gt lt Reason gt item not found lt Reason gt lt Item gt lt Parameter gt lt Message gt lt Home Inventory gt 58 Page Data Base Design Documents 59 Page DATABASE SCHEMA User List Table The master table that holds relevant information pertaining to each user making use of our inventory system The schema is the following e ID integer primary key e Last Name varchar e First Name varchar e E Mail varchar e Address varchar e Phone Number integer e Secondary Phone Number integer or null e login name varchar e password varchar containing HexString of digest e user type varchar either admin or user Home Inventory Table This is created for each user separately so that everyone s data is separated from each other s Each table s name will be Home User ID and will be spawned upon the creation of a user s account Since the table is linked directly by the User ID there is no need to add a column for the User ID because a foreign key is not necessary for our system to link the tables e ID integer primary key e UPC integer null if not applicable lt not applicable if user opts to manually input item or item
22. The System displays account information The Admin modifies the account settings The System prompts the Admin to confirm the new settings The Admin confirms the settings The System saves the account settings Modify User ID and Password Prerequisite Login The Admin selects the System Settings menu The System prompts the Admin for the Admin UserID and Password The Admin enters the UserID and Password The System confirms UserID and Password and displays System Settings menu with Create account Modify account Delete Account and System Attributes buttons s The Admin selects the Delete Account menu The System displays the Delete Account menu The Admin enters in the Userld and Password of the account to be deleted The system deletes the Account Create User Account Prerequisites Welcome Menu 14 Page Admin accesses Browse Items menu The System prompts the Admin for the UserID of the Account to access e The Admin enters the UserID of the account to access The System lists the items to be browsed in a display field on the screen e The System also lists the Delete Items Modify Items and Print Items buttons Admin browses items in System Browse Items Prerequisite Login The Admin selects the Print Item menu The System prompts the Admin to enter in the UserID of the account to print
23. ck in sender object in e RoutedEventArgs void a BrowseMenuHomeButton_Click in sender object in e RoutedEventArgs void BrowsellenuLogoutButton_Click in sender object in e RoutedEventArgs void Q lt lt constructor gt gt Inserthenu Q lt lt constructor gt gt Homehenu InsertButton_Cick in sender object in e RoutedEventArgs void 87 Button Cict n sender object in e RoutedEventArgs void InsertMenuHomeButton_Click in sender object in e RoutedEventArgs void Button Click 1 in sender object in e RoutedEventArgs void InsertMenuLogOutButton_Click in sender object in e RoutedEventArgs void HomeMenuLogoutButton_Click in sender object in e RoutedEventArgs void 87 Button Clck in sender object in e RoutedEventArgs void O lt lt constructore gt LoginScreen a Button_Click in sender object in e RoutedEventArgs void a Button Click 1 in sender object in e RoutedEventArgs void Generated by UModel www altova com 33 Page Home Inventory Client Admin Overview pkg Homelnventory selectedUsertlame Strino selectediD Strina lt constructor AdminsBrowseltemMenu L Admin_Browse_Menu_Page_Loaded in sender object in e RoutedEventArgs void L ItemBox_SelectionChanged in sender object in e SelectionChangedEventArgs void L BrowseMenu_delete_button_Click in sender object in e RoutedEventArgs void L Admin BrowsellenuLogoutButton Click in sender object n e RoutedEventArgs
24. ck on Confirm ES ie es ou barr Create User Screen 23 Main St 0 249 2350 4 910 9024 jjames james123 d 18 Page IAT ee AI Assume the username supplied if the user does not already exist the user will be created granting immediate access to the system Once a user is created the Home Screen will refresh onto the screen Navigating to the Browse Users screen will display the existant Users in the system Browse Users Ee SCCI Browse User 1 testuser 2 cjames 3 admin 26 jjames 25 user3 24 jose 23 rzuniga View User Items View User Attributes Navigating to the Browse Users menu the list of Users is displayed with the options to View Users Items Remove Users and View User Attributes 19 Page Removing Users For Remove User the currently selected user will be deleted All items belonging to the user will also be deleted Viewing Users Items M tome 2 xay x VINA Loc out Admin Browse Menu 5 Computer Description Oak Desk 6 0ak Desk 86034 7 Tiffany Lamp UR Size User o Upload Date 2009 04 30 Delete Item Modify Item The Browse Users Items screen provides a great deal of information The left side on the screen lists the items belonging to a given user By selecting an item the information pertinent to that item is distributed to the boxes on the right The owner of the items displayed is shown in the User box Deleting Items By clicking on the Delete
25. cosmetic failure is a flaw in the system that visually detracts from the User s experience when using the program An example of a cosmetic failure is a button is a different color then the other buttons in the system When reporting test failures the tester must be sure to include the severity of the failure along with the failures test procedure name and the actual test procedure step that was being performed at the time of the failure An example failure report is displayed below Test Failure Severity Severe Test Failure 20 Apr 2009 Login screen test procedure step 4 Description login button doesn t respond when clicked 70 Page Test Case Documents for Phase 1 Testing 71 Page Home Inventory Test Procedure Procedure 1 Login Screen This document describes the test procedure for the Home Inventory project Login screen This document is to be used for the Casual Testing phase of the testing procedure described in the Home Inventory project testing plan document If at any point in the test procedure the system fails to act in the proper manner the tester should write down in detail what they found be following the error reporting guidelines found in the test plan document All questions about this document should be forwarded to the development team Login Screen Test Prerequisite Server Up and running 1 User starts Home Inventory client program 2 User should verify success of program launch by being able
26. criptions presented in the table above Some Narratives require prerequisites of another use case before they can be accomplished The Use case title is displayed in blue and the Home Inventory system itself is referred to as System Menus are highlighted in green 7 Page Use Case narrative for User 1 Login a b c d The User enters ID and Password into the system The System verifies ID and Password The System allows or denies the User entry The System displays the Welcome Menu which contains buttons to access the Browse Items Insert Items and Account Settings menus 2 Browse Items Prerequisite Login a b c d User accesses Browse Items menu The System lists the items to be browsed in a display field on the screen The System also lists the Delete Items Modify Items and Print Items buttons User browses items in System 3 Insert Items Prerequisite Login a b c d e User selects Insert Item menu The System displays Insert Item menu options The User can choose to insert manually or by bar code scanner The User chooses bar code scanner i The User scans item bar code ii The System looks up Bar Code ID of item iii The System adds the item to the inventory The User chooses Manuel Input i The System displays Manuel Input screen ii The User enters in item information iii The System adds the item to the inventory
27. e lt Home Inventory gt lt Message gt lt Message Type gt LogOut lt Message Type gt lt Message gt lt Home Inventory gt Client lt gt Server Log Out message Server response lt Home Inventory gt lt Message gt lt Message Type gt LogOut lt Message Type gt lt Parameter gt lt Status gt 34534 for success 785654 for failure lt Status gt lt Parameter gt lt Message gt lt Home Inventory gt 46 Page Admin gt Server Browse Menu lt Home Inventory gt lt Message gt lt Message Type gt BrowseUsers lt Message Type gt lt Message gt lt Home Inventory gt Admin gt Server Browse Menu Response lt Home Inventory gt lt Message gt lt Message Type gt BrowseResponse lt Message Type gt lt UserList gt lt User gt lt table gt tablename lt table gt lt login gt login lt login gt lt firstname gt first name lt firstname gt lt lastname gt last name lt lastname gt lt User gt lt UserList gt lt Message gt lt Home Inventory gt 47 Page Admin Create User Message Client gt Server lt Home Inventory gt lt Message gt lt Message Type gt CreateUser lt Message Type gt lt User gt lt FirstName gt tablename lt FirstName gt lt LastName gt login lt LastName gt lt Email gt first name lt Email gt lt Address gt last name lt Address gt lt PrimPhone gt phone lt PrimPhone gt lt AltPhone gt phone lt AltPhone gt
28. e of the components of vital importance is a way of organizing and keeping track of the items in the home A Home Inventory system is a simple idea that can be used as one of the components of the smart home Imagine that a terrible accident destroys the home of an individual it is often the case that an exact account of the home owner s personal belongings becomes an issue between the home owner and the insurance company The Home Inventory solves this problem by keeping track of every item in the home thereby making recovery of loses in an accident a much simpler process Above we have noted some advantages of the Homelnventory Keep in mind that the Home Inventory is only a component of a Smart House By using your imagination you can envision many improvements that can be made to your home using technologies such as the Home Inventory As technology advances it 2 Page won t be long before fictional homes from some of our favorite movies become a reality 3 Page Home Inventory Project Report The Home Inventory project was developed for our CIS 4339 Projects in Computer Science Course at Temple University The ultimate goal of the course was to allow students to utilize the fundamentals of Software Engineering in a group environment An alternative goal for the project was to allow students to employ most of the facets of computer science they have learned in their undergraduate career in a substantial programming research
29. e developers A test phase is considered complete when all failures have been addressed by the developers Part 2 Schedule The testing of the home inventory project has a time frame of less than four weeks The first three phases of the testing Casual Use Freelance and Network load should each take one week this leaves an additional week for any unforeseen issues that may arise during the testing of the system The test phases can be further broken down into the actual components of to be tested Each phase will be carried out with the objective of ensuring the functionality of the specific screens in the system work as expected In this manner of thinking testing can be broken down into discrete blocks of time where each of the screens on the client side of the project are tested and debugged A preliminary schedule can be viewed below e 13 April 2009 Casual testing phase Login Screen Home Screen Browse Menu reports and debugging e 15 April 2009 Casual testing phase insert Menu All admin menus reports and debugging e 17 April 2009 Casual testing phase Finish any testing and compile reports e 20 April 2009 Freelance testing All User screens reports and debugging e 22 April 2009 Freelance testing All Admin screens reports and debugging e 24 April 2009 Freelance testing Finish any testing and compile reports e 27 April 2009 Load testing Run Server with many Clients e 29 April 2009 Fix a
30. e in UserName String in Password String String IsLoginValid in loginResponse String String XMLLoadBrowse XmiDocument Q InsertMessage in UPC String in Description String in Size String Boolean Q Modifvitemtin ID Strina in UPC String in Description String in Size Strina Boolean AdminModifylemiin userid Strina in D String in UPC String in Description String in Size String Boolean deketetemilessage n O String Boolean CreateUserMessage in firstName String in lastName String in email String in address String in primaryPhone String in altPhone Strina in userName Strina in password String in userType Strina Bool loadUserBrowseMenu XmiDocument XuLBrowseUsertems in givenUserName String in givenUseriD String XmlDocument XMLAdminDeletettem in qivenUseriD Strina in givenfemiD String Boolean Admininserttems in givenUseriD String in givenUPC Strina in aivenDescrip Strina in givenSize String Boolean O badModifyUseriWenu in givenUserD String XmiDocument ModifyUserMessage in givenUserlD Siring in firstName String in lastName String in emaitString in address String in primaryPhone String in atPhone String in userName String in 4 RemoveUserllessage in givenUseriD Strina Boolean O UPC Lookup in givenUPC String String XULLogOut void Page socket Te StreamReader System IO StreamReader streamWriter m I0 iter lt lt const gt gt IS_A_USER String 46534
31. er enters the UserlD and Password The System displays account information The User modifies the account settings The System prompts the User to confirm the new settings The User confirms the settings The System saves the account settings 8 Logout Prerequisite Login a b User Selects Logout System Logs User out 9 Page The User enters ID and Password into the system The System verifies ID and Password The System allows or denies the User entry The User selects the Delete Item menu The System displays the items in the inventory The User finds the item to be deleted The User selects to deletes the item The System removes the item from the inventory Delete Items Prerequisite Login e User accesses Browse Menu The System lists the items on the screen User browses items in System Browse Items Prerequisite Login The User selects Print Item menu The System displays items in the inventory The User selects items to be printed The items are printed Print Items Prerequisite Login e User selects Insert Item menu The System displays Insert Item menu options The User can choose to insert manually or by bar code scanner The User chooses bar code scanner The User scans item bar code The System looks up Bar Code ID of item The System adds the item to the inventory The User chooses Manuel Input The Sys
32. gt lt Message gt lt Home Inventory gt 52 Page Admin Browse Insert Item Client gt Server lt Home Inventory gt lt Message gt lt Message Type gt Admin Insertltem lt Message Type gt lt Parameter gt lt UserlD gt Users ID lt UserlD gt lt UPC gt 123456467 lt UPC gt Can be null lt Description gt This item is a HDTV etc lt Description gt lt Size gt an item description lt Size gt lt Parameter gt lt Message gt lt Home Inventory gt Admin Browse Insert Item Response Server gt Client lt Home Inventory gt lt Message gt lt Message Type gt Admin Insertitem lt Message Type gt lt Parameter gt lt Status gt 32345for success 54665 for failure lt Status gt lt Reason gt Reason for fail lt Reason gt lt Parameter gt lt Message gt lt Home Inventory gt 53 Page Admin Modify User Page Loaded Client gt Server lt Home Inventory gt lt Message gt lt Message Type gt ModifyUserPageLoad lt Message Type gt lt UserlD gt ID of the user lt UserlD gt lt Message gt lt Homelnventory gt 54 Page Admin Modify User Page Loaded Message Sever Client lt Home Inventory gt lt Message gt lt Message Type gt ModifyUserPageLoad lt Message Type gt lt User gt lt FirstName gt Firstname lt FirstName gt lt LastName gt LastName lt LastName gt lt Email gt email lt Email gt lt Address gt Address lt Address gt lt PrimPhone gt phone lt PrimPh
33. imultaneous connections a few tests had to be conducted The steps of the tests and outcome will be listed below The first step is universal to all test and this is running our server on babyhuey TEST 1 1 Open 20 copies of our client executable on the same computer Result PASS All instances of our exe caused babyhuey to spawn a new thread to handle the connection TEST 2 1 Open 20 copies of our client executable on one computer 2 Open 10 copies on another computer Result PASS All instances of our exe caused babyhuey to spawn a new thread to handle the connection TEST 3 1 Open a copy of our executable on five different computers 2 Perform client functions at the same time to see if they all get serviced Result PASS Note Since all of our customers are assumed to only have one account and they each have their own table in the database we assume that they will be updating modifying deleting items amongst themselves with no interference from the admin The admin should only be performing these functions when the client has a problem and contacts the admin for help Thus the order of which their updates occur does not matter 89 Page 90 Page
34. ion gt This item is a HDTV etc lt Description gt lt Size gt an item description lt Size gt lt Parameter gt lt Message gt lt Home Inventory gt Client C gt Server Insert response lt Home Inventory gt lt Message Type gt Insert lt Message Type gt lt Parameter gt lt status gt 46534 for success 30494 for failure lt status gt lt reason gt String representing the reason for failure lt reason gt lt Parameter gt lt Home Inventory gt 41 Page The Following is the message sent when the browse menu is loaded this message is used to load the list in the browse screen with the User s items Client gt Server Load browse Menu lt Home Inventory gt lt Message gt lt Message Type gt LoadBrowse lt Message Type gt lt Table gt Home_tablenumber lt Table gt lt Message gt lt Home Inventory gt Client lt gt Server Load Browse Menu Server Response lt Home Inventory gt lt Message gt lt Message Type gt LoadBrowseResponse lt Message Type gt lt Parameter gt lt ltem gt lt ID gt Integer value for primary key in DB lt ID gt lt UPC gt Items UPC code can be null lt UPC gt lt Description gt A brief description lt Description gt lt Size gt Used by DB admin lt Size gt lt Upload Date gt 23 Mar 2009 lt Upload Date gt lt Item gt lt ltem gt lt ID gt Integer value for primary key in DB lt ID gt lt UPC gt ltems UPC code can be null lt UPC gt lt
35. items from The Admin enters in the UserID The System prompts the Admin to select the item to print The Admin selects items to be printed The System prompts the Admin to confirm the print job s The Admin confirms the Print The items are printed Print Items Prerequisite Login and Browse menu The Admin selects the System Settings menu The System prompts the Admin for the Admin UserID and Password The Admin enters the UserID and Password The System confirms UserID and Password and displays System Settings menu with Create account Modify account Delete Account and System Attributes buttons The Admin selects the Create Account menu The System displays the Create Account menu The Admin enters in the Userld and Password of the accountto be created The system creates the Account Create User Account Prerequisites Welcome Menu The Admin selects the System Settings menu The System prompts the Admin for the Admin UserID and Password The Admin enters the UserID and Password The System confirms UserID and Password and displays System Settings menu with Create account Modify account Delete Account and System Attributes buttons The Admin selects the System Attributes The System displays the System Attributes The Admin modifies the System s Attributes The S
36. m Test Test Procedure 5 This test procedure will test the functionality of the Remove feature The user will navigate to the Browse screen and try to remove an item Prerequisites iii User must have an account iv Logged into the Home page Procedure 8 Press the Browse button Insert Items 9 Select an item to remove 10 Click on the Delete button to delete an item 81 Page Delete Item Modify Item Print Item 11 If the item is now gone then the Remove feature works 12 Records results 13 Log out or back to Home Page 82 Page Modify Feature Test Test Procedure 6 This test procedure will test the functionality and limitations of the Modify feature The user will navigate to the Browse screen and try to modify items with various combinations of data into the required fields Prerequisites i User must have an account ii Logged in and must have items entered Procedure 14 Press the Browse button iP fa e Home Menu Insert Items 15 User should select an item on the left On the right the fields will be populated a UPC the barcode of the scanner b Description written description of what the item is c Size the size 83 Page Delete Item Modify Item Print Item 16 Change the value of any field and click on Modify 17 User is greeted with a message saying Update successful 18 If the new values are now on the right the operation succeeded 1
37. ms 2 User selects the Browse Menu button 3 User should be able to view Browse Menu The Browse Menu should display a list of items in the List box of the screen 74 Page Delete Item Modify Item Print Item User selects the Home button at the top left o the browse menu User can view the Home Menu User selects the Insert Items button NOW User can view the Insert Item Menu E pr e nn Log Out Insertitem Menu BarCode Insert Insert Manuel 8 User selects the Home button in the top left of the screen 75 Page 9 User can view the Home Menu screen 10 User selects the Logout button at the top right of the screen 11 User logs out of the system 76 Page Insert Screen Test Test Procedure 3 This test procedure will test the functionality and limitations of the Insert feature The user will navigate to the Insert screen and try to insert various combinations of data into the required fields Prerequisites i User must have an account ii logged into the Home page This test is verified and also verifies the functionality of the Browse Screen Test Procedure 1 Press the Insert Item button oS as a in e Home Menu Insert Items 2 User is now prompted for the following fields a UPC the barcode of the scanner b Description written description of what the item is c Size thesize 77 Page MA Ne la
38. ms to be browsed in a display field on the screen The System also lists the Delete Items Modify Items and Print Items buttons Admin browses items in System 3 Insert Items Prerequisite Login a b C d e Admin selects Insert Item menu The System prompts Admin to enter the UserID of the account to insert items into The System displays Insert Item menu options The Admin can choose to insert manually or by bar code scanner The Admin chooses bar code scanner i The Admin scans item bar code ii The System looks up Bar Code ID of item iii The System adds the item to the inventory The admin chooses Manuel Input i The System displays Manuel Input screen ii The admin enters in item information iii The System adds the item to the inventory 4 Delete Items Prerequisite Login and Browse menu a sm 0 0 G The Admin selects the Delete Item menu from the Browse Menu The System prompts the Admin to enter in Userld of the account to Delete items from The Admin enters the UserID The System refresh the browse field with the items of the UserID just entered The System prompts the Admin to select the item s to delete The Admin finds the item to be deleted in the Browse field The System prompts the Admin to confirm the deletion The Admin confirms the item deletion The System removes the item from the inventory 5 Print Items Prerequisite Login and Browse menu
39. n Leg Out Insertitem Menu BarCode Insert Insert Manuel 3 Fill out the fields and Press the Insert Manual button You ll be greeted with a message saying Insert Succeeded 5 Try the following situational tests a Insert the same item b Insert a blank item c Insert an item with blank fields 6 Records results 7 Log out or back to Home Page 78 Page Browse Screen Test Test Procedure 4 The browse feature is designed to display all the items a user currently owns in the database This feature is also used to demonstrate the functionality of the Insert Delete and Modify features Prerequisites i User must be logged in ii User must have entered items 1 Press the Browse Items button ng Home Menu Insert Items 2 View the items listed in the left panel 3 Click on any item verify the information is correctly dispersed from the panel to the individual boxes on the right side Verify for all items a UPC should be in UPC box b Description should be in the Description box c Size should be in the Size box 79 Page Delete Item Modify Item Print Item 4 Click back to the Home Screen 5 Follow the User Test Procedure Insert steps to add an item 6 Return to Browse Screen to view the new item 7 Follow the User Test Procedure Remove steps to remove an item 8 Ifthe new item is gone then the browse works 9 Records results 10 Log out 80 Page Remove Ite
40. nfirms the settings The System saves the account settings 8 Create User Account Prerequisites Welcome Menu a The Admin selects the System Settings menu b The System prompts the Admin for the Admin UserID and Password c The Admin enters the UserlD and Password d The System confirms UserlD and Password and displays System Settings menu with Create account Modify account Delete Account and System Attributes buttons e The Admin selects the Create Account menu f The System displays the Create Account menu g The Admin enters in the Userld and Password of the account to be created h The system creates the Account 9 Create User Account Prerequisites Welcome Menu 12 Page a The Admin selects the System Settings menu b The System prompts the Admin for the Admin UserID and Password c The Admin enters the UserlD and Password mm gt j The System confirms UserID and Password and displays System Settings menu with Create account Modify account Delete Account and System Attributes buttons The Admin selects the Modify Account menu The System displays the Modify Account menu The Admin enters in the Userld and Password of the account to be modified The System displays the account attributes The Admin modifies the account attributes The System Saves the modification 10 Create User Account Prere
41. ny problems that were found in testing e 1 May 2009 Fix any problems found in testing and compile final report 69 Page Part 3 Responsibilities Each member of the development team will be responsible for an equal amount of testing and debugging Test cases will be generated and evenly distributed between teammates upon completion of a test case the developer may be responsible for debugging of a failure found during testing Since certain parts of the system are best understood by those that coded that particular section of the program certain debugging task may need to be forwarded to the developer with that specific domain knowledge Test plan generation will be performed by all team members no one should perform the test of a plan they wrote Test Failure Reporting The severity of a test failure will fall into one of three categories namely severe functional or cosmetic failures A failure categorized as severe is a failure that crashes the system causes lost or unintentional modification of data or places the User in a deadlock situation in which they can no longer navigate from page to page A functional test failure is a failure in which the User s goals for using the system cannot be obtained because of some incorrect functionality of the system An example of a functional failure is a User attempts to enter an items name in the system perhaps the system will not accept the name for some unspecified reason Lastly a
42. on between the components of the Home Inventory Project The XML in the project will be used to pass messages and commands between the three core components of the Home Inventory Project The following is the basic structure for the XML to be used lt Home Inventory gt lt Message gt lt Message Type gt The message type can be either a command or an object If the Type is a command you place the command here Such as Insert or delete If the message type is an object you would place object in this tag lt Message Type gt lt Parameter gt Each message will include a tag for all of its parameters Some parameters may be set to null lt Parameter gt lt Parameter gt lt Parameter gt lt Parameter gt lt Parameter gt lt Message Number gt 234 lt Message Number gt lt Message Sender gt 123532 lt Message Sender gt ID of User who sent message lt Message gt lt Home Inventory gt Each message that we create will have a unique set of parameters that are distinct to that particular message type When parsing the message the message type should be used to identify the tags contained in the XML The following is the message outline for the Insert Message 40 Page Client gt Server Insert lt Home Inventory gt lt Message gt lt Message Type gt Insert lt Message Type gt lt Parameter gt lt Table gt Home_tablenumber lt Table gt lt UPC gt 123456467 lt UPC gt Can be null lt Descript
43. one gt lt AltPhone gt phone lt AltPhone gt lt UserName gt user name lt UserName gt lt Password gt password lt Password gt lt UserType gt 1 for Admin 2 for regular User lt UserType gt lt User gt lt Message gt lt Home Inventory gt 55 Page Admin Modify User Client gt Server lt Home Inventory gt lt Message gt lt Message Type gt ModifyUser lt Message Type gt lt User gt lt FirstName gt Firstname lt FirstName gt lt LastName gt LastName lt LastName gt lt Email gt email lt Email gt lt Address gt Address lt Address gt lt PrimPhone gt phone lt PrimPhone gt lt AltPhone gt phone lt AltPhone gt lt UserName gt user name lt UserName gt lt Password gt password lt Password gt lt UserType gt 1 for Admin 2 for regular User lt UserType gt lt User gt lt Message gt lt Home Inventory gt 56 Page Admin Create User Message Sever Client lt Home Inventory gt lt Message gt lt Message Type gt ModifyUser lt Message Type gt lt Status gt 3245575 Success 586788 for failure lt Status gt lt Message gt lt Home Inventory gt Admin UPC Lookout Message Client Server lt Home Inventory gt lt Message gt lt Message Type gt UPC_Lookup lt Message Type gt lt Parameter gt lt UPC gt item upc lt UPC gt lt Parameter gt lt Message gt lt Home Inventory gt 57 Page Admin UPC Lookout Message Server Client lt Home Inventory gt lt
44. ord The System confirms UserID and Password and displays System Settings menu with Create account Modify account Delete Account and System Attributes buttons The Admin selects the System Attributes The System displays the System Attributes The Admin selects the Print Attributes button The System prints the attributes The Admin enters ID and Password into the system The System verifies ID and Password The System allows or denies the Admin entry The System displays the Welcome Menu which contains buttons to access the Browse Items Insert Items System settings and Account Settings menus s The Admin selects the Delete Item menu from the Browse Menu The System prompts the Admin to enter in Userld of the account to Delete items from The Admin enters the UserID The System refresh the browse field with the items of the UserID just entered The System prompts the Admin to select the item s to delete The Admin finds the item to be deleted in the Browse field The System prompts the Admin to confirm the deletion s The Admin confirms the item deletion Delete Items Prerequisite Login and Browse menu The Admin selects the Account Settings menu The System Prompts the Admin for the User ID and Password of the account to modify The Admin enters the UserID and Password of the account
45. quisites Welcome Menu a ao G ga h The Admin selects the System Settings menu The System prompts the Admin for the Admin UserID and Password The Admin enters the UserlD and Password The System confirms UserID and Password and displays System Settings menu with Create account Modify account Delete Account and System Attributes buttons The Admin selects the Delete Account menu The System displays the Delete Account menu The Admin enters in the Userld and Password of the account to be deleted The system deletes the Account 11 Modify System attributes Prerequisites Welcome Menu Qo n ga h The Admin selects the System Settings menu The System prompts the Admin for the Admin UserID and Password The Admin enters the UserlD and Password The System confirms UserID and Password and displays System Settings menu with Create account Modify account Delete Account and System Attributes buttons The Admin selects the System Attributes The System displays the System Attributes The Admin modifies the System s Attributes The System saves the modification 12 Print System attributes Prerequisites Welcome Menu 13 Page a p n G 3a The Admin selects the System Settings menu The System prompts the Admin for the Admin UserID and Password The Admin enters the UserID and Passw
46. reated at relatively the same cost as a regular data file e Server based e Not embedded in your code e Not in public domain but it is open source e Perfect for high load websites where database is accessed concurrently e Best for multi user use wasteful for single user access e Must be configured although the process is fairly simple from what have been told 61 Page After reading the above pros and cons of MySQL it would be perfect for both our first and second database model which is at the current time the following e One database for all users separated into tables linked by userid For example our main database will contain the relevant user information such as userid primary key login password etc This will be linked to user tables that contain the rest of the user s information 62 Page UI Design Documents 63 Page The following is a high level visual representation of the UI In general each screen will represent a class and each button will represent a function of that class This design does not represent the actual UI it is only a basic design template used to simplify the latter detailed Design of the UI Login Screen Home Inventory Login Forgot Password Welcome Screen Welcome Screen Account Settings Insert 64 Page Browse Menu Browse Menu n fs M Modify tem Insert Item Insert Items tem Name Item Info Item Info Item Info Scan item Insert
47. rements documents 4 Page Requirements documents Use Case Narrative User Manual 5 Page Home Inventory Use case Narrative The Home Inventory system will generally be used by two types of users a home user and a system admin Home users will consist of individuals who use the system for everyday inventory purposes System Admins are a very select group of users who have access to the full system and can modify any aspect of the system Below are the general activities attributed to each type of Actor Browse items User browses through the items in their inventory Delete Item User deletes an item from the inventory Modify Item User modifies the attributes of an item Logout Logout of the system Modify UserlD Password User modifies their UserID and password for their system 6 Page The Admin has all the functionality of the User plus advanced administrative capabilities Below we summarize the actions of the Admin Admin Insert Item Admin inserts an item into Any inventory Print Items User prints items from Any Login Log into Any system Create User Account Admin creates Any user account Access system attributes Admin accesses statistical data about system and users Use Case Narratives The following definitions will be use to generally describe in a high level what each use case is trying to accomplish The narratives are intended to add upon the brief des
48. sword The System confirms UserID and Password and displays System Settings menu with Create account Modify account Delete Account and System Attributes buttons The Admin selects the Modify Account menu The System displays the Modify Account menu The Admin enters in the Userld and Password of the account to be modified The System displays the account attributes The Admin modifies the account attributes The System Saves the modification Create User Account Prerequisites Welcome Menu The Admin selects the System Settings menu The System prompts the Admin for the Admin UserID and Password The Admin enters the UserID and Password The System confirms UserID and Password and displays System Settings menu with Create account Modify account Delete Account and System Attributes buttons The Admin selects the System Attributes The System displays the System Attributes The Admin selects the Print Attributes button The System prints the attributes Print System attributes Prerequisites Welcome Menu User Manual 15 Page Home Inventory User Manual About Home Inventory The Homelnventory Project consists of a customized front end user application and a Java application server manipulating a MySQL database for data storage With two types of roles Users and Administrators
49. t 50 Page Admin Browse User Items Server gt Client lt Home Inventory gt lt Message gt lt Message Type gt BrowseUserltems lt Message Type gt lt Parameters gt lt UserName gt The User Name lt UserName gt lt UserlD gt The Users ID lt UserlD gt lt Items gt lt ltem gt lt UPC gt The UPC lt UPC gt lt Description gt Item Description lt Description gt lt Size gt ltem Size lt Size gt lt Upload gt Upload Date lt Upload gt lt Item gt lt Items gt lt Parameters lt Message gt lt Home Inventory gt Admin BrowseUserltems Client gt Server lt Home Inventory gt lt Message gt lt Message Type gt BrowseUserltems lt Message Type gt lt UserlD gt ID of the user lt UserlD gt lt Message gt lt Homelnventory gt 51 Page Admin Browse Item Menu Delete Item Client gt Server lt Home Inventory gt lt Message gt lt Message Type gt AdminDeleteltem lt Message Type gt lt Parameters gt lt UserName gt The User Name lt UserName gt lt UserlD gt The Users ID lt UserlD gt lt ItemID gt The Items ID lt Items gt lt Parameters lt Message gt lt Home Inventory gt Admin Browse Item Menu Delete Item Server gt Client lt Home Inventory gt lt Message gt lt Message Type gt AdminDeleteltem lt Message Type gt lt Parameters gt lt Status gt 867554 for success lt Status gt lt Reason gt reason for failure lt Reason gt lt Parameter
50. t lt lt const gt gt InsertMessageSizeCloseTag String lt Size lt lt const gt gt IDOpenTag String lt ID gt lt lt const gt gt IDCLOSE_TAG String lt ID gt lt lt const gt UserOpenTag String lt User gt lt lt const gt gt UserCloseTag String lt User gt lt lt const gt gt UserDOpenTag String lt UserD gt lt lt const gt gt UserDCloseTag String lt UserD gt lt lt const gt gt FirstNameOpenTag String lt FirstName gt lt lt const gt gt FirstNameCloseTag String lt FirstName gt lt lt const gt gt LastNameOpenTag String lt LastName gt lt lt const gt gt LastNameCloseTag Strino lt LastName gt lt lt const gt gt EmailOpenTag String lt Email gt lt lt const gt gt EmailCloseTag Strino lt Email gt lt lt const gt gt AddressOpenTag String lt Address gt lt lt const gt gt AddressCloseTag String lt Address gt lt lt const gt gt PrimPhoneOpenTag String lt PrimPhone gt lt lt const gt gt PrimPhoneCloseTag String lt PrimPhone gt lt lt const gt gt AltPhoneOpenTag String lt AltPhone gt lt lt const gt gt AltPhoneCloseTag String lt AltPhone gt lt lt const gt gt PasswordOpenTag String lt Password gt lt lt const gt gt PasswordCloseTag String lt Password gt lt lt const gt gt UserTypeOpenTag String lt UserType gt lt lt const gt gt UserTypeCloseTag String lt UserType gt XMLLoginMessag
51. t lt Size gt This attribute is changed lt Size gt lt Item gt lt Parameter gt lt Message gt lt Home Inventory gt Client lt gt Server Modify Item Server Response All attributes of an item that are NOT modified will be set to NULL lt Home Inventory gt lt Message gt lt MessageType gt Modify lt MessageType gt lt Parameter gt lt Table gt Home_tablenumber lt Table gt lt ModifyDate gt date lt ModifyDate gt lt Result gt success or failure lt Result gt lt Reason gt 46534 for success 30494 for failure lt Reason gt lt Parameter gt lt Message gt lt Home Inventory gt 44 Page Client gt Server Delete item message All attributes of an item that are NOT modified will be set to NULL lt Home Inventory gt lt Message gt lt Message Type gt Delete lt Message Type gt lt Parameter gt lt Table gt Home tablenumber lt Table gt lt ID gt item ID lt ID gt lt Parameter gt lt Message gt lt Home Inventory gt Client lt gt Server Delete item message Server Response lt Home Inventory gt lt Message gt lt Message Type gt DeleteResponse lt Message Type gt lt Parameter gt lt ID gt item ID lt ID gt lt Result gt success or failure lt Result gt lt Reason gt 14256 for success 235769 for failure lt Reason gt lt Parameter gt lt Message gt lt Home Inventory gt 45 Page Client lt gt Server Log Out message Client messag
52. tem displays Manuel Input screen The User enters in item information The System adds the item to the inventory Insert Items Prerequisite Login The User selects Modify Item menu The System displays the items in the inventory The User selects the item to modify The system displays the attributes of the item The User modifies the item s Attributes Modify Item Prerequisite Login The User selects the Manage Accounts menu The System Prompts the User for the User ID and Password The User enters the UserID and Password The System displays account information The User modifies the account settings The System saves the account settings User Selects Logout System Logs User out Modify User ID and Password Prerequisite Login Logout Prerequisite Login 10 Page Use Case narrative for Admin The Admin enters ID and Password into the system The System verifies ID and Password The System allows or denies the Admin entry The System displays the Welcome Menu which contains buttons to access the Browse Items Insert Items System settings and Account Settings menus 2 Browse Items Prerequisite Login a b C d e L Admin accesses Browse Items menu The System prompts the Admin for the UserID of the Account to access The Admin enters the UserID of the account to access The System lists the ite
53. to see the Login Screen on their monitor If client failed to connect to Server User we notice a prompt box with failure status Welcome To Your Ho Inventory 3 User enters the string Bad username in the Username Box 4 User enter the string Bad Password in the Password Box 72 Page 5 User hits the Login button System should display a prompt box with a message informing the User that an incorrect user name or password was entered 7 User enters the string Admin in the Username Box 8 User enters the string 12345 in the Password box 9 User hits the Login button User should be able to view the User Homepage screen which indicates 73 Page Home Inventory Test Procedure Procedure 2 User Home Menu This document describes the test procedure for the Home Inventory project User Home Menu screen This document is to be used for the Casual Testing phase of the testing procedure described in the Home Inventory project testing plan document If at any point in the test procedure the system fails to act in the proper manner the tester should write down in detail what they found be following the error reporting guidelines found in the test plan document All questions about this document should be forwarded to the development team User Home Menu Test Prerequisite User logged into system 1 User views the Home Menu RR 3 L sci tei e ai M Sr Home Menu Insert Ite
54. tor gt NetworkStuff ue itemsList Generated by UModel www altova com Home Inventory Server Class Diagram 5 Admin e Attributes lt lt interface gt gt private int userid Runnable Operations package Admin public void setUserlD int id User Sting lastname Sting fstname int user ype Client Attributes package Connection con fi Jblic int Delete Item String id ail N Monit item trini H N 37 Page Server Utility Class Diagram El StatusCodes Attributes public int userLoginGood 46534 public intuserLoginBad 30494 public intuserAdmin 758434 public int userNormal 123422 public intitemld 1000 public intinsertGood 92341 nlc ODE SUCCESS 264 Operations public String loginResponseXML int code String reason int user type public String insertResponseXML int code String reason public String deleteResponseXML int code String reason String ID public String browseResponseXML ArrayList results inj public String modifyResponseXML int code String reason String ID public int CRE TE USER SUCC 9 13304 ublic Sting logOutResponseXHL int code ui I CREATE USER FALURE sR subi Sting CreteseResponse i code Sting mun hie int E LISER IIPfE Otrin 4 e Sti X 38 Page Design Document XML Protocol 39 Page Home Inventory Project XML Protocol The purpose of this document is to establish a basic structure for the XML to be used as a means of communicati
55. void L Admin_BrowseMenuHomeButton_Click in sender object in e RoutedEventArgs void L Button Click in sender object in e RoutedEventArgs void Q lt lt constructor gt BrowseUser Page Loaded sender object in e RoutedEventArgs void D BrowseUserListBox_SelectionChanged in sender object in e SelectionChangedEventArgs void D View_User_tems_Button_Clcik in sender object in e RoutedEventArgs void D Admin_Browse_User_LogoutButton_Click in sender object in e RoutedEventArgs void D Admin_Browse_Menu_ViewUserAttributes_Click in sender object in e RoutedEventArgs void HomeButton_Cictin sender object ne RoutedEventArgs void D RemoveUser Click in sender object in e RoutedEventArgs void mm Q lt lt constructor gt ModifyUser Page_Loadedn sender object in e RoutedEventArg void D Confirm Modify Button_Click in sender object in e RoutedEventArgs void HomeButton_Cictin sender object ne RoutedEventArgs void D Logout_Click in sender object in e RoutedEventArgs void D finished click in sender object in e RoutedEventArgs void C lt lt constructors gt AdminhserttemsMenu D InsertMenuHomeButton_Click in sender object in e RoutedEventArgs void D Page_Loaded in senier object in e RoutedEventArgs void a Admin_InsertMenu_LogOut_Button_Click in sender object in e RoutedEventArgs void D Admin_Inserthlanual Insert_Button_Click in sender object in e RoutedEventArgs void D Admin Barcode
56. ystem saves the modification Modify System attributes Prerequisites Welcome Menu Admin selects Insert Item menu The System prompts Admin to enter the UserID of the account to insert items into The System displays Insert Item menu options The Admin can choose to insert manually or by bar code scanner The Admin chooses bar code scanner The Admin scans item bar code The System looks up Bar Code ID of item The System adds the item to the inventory The admin chooses Manuel Input The System displays Manuel Input screen The admin enters in item information The System adds the item to the inventory Insert Items Prerequisite Login The Admin selects Modify Item menu The System prompts the Admin to enter in the UserID ofthe account to modify the items of The Admin enters in the UserID The System prompts the Admin to select the item to modify from the Browse field The Admin selects the item to modify The system displays the attributes of the item s The Admin modifies the item s Attributes The System prompts the Admin to confirm the modification of the item s attributes s The Admin confirms the modification The System saves the attributes Modify Item Prerequisite Login and Browse menu The Admin selects the System Settings menu The System prompts the Admin for the Admin UserID and Password The Admin enters the UserID and Pas
Download Pdf Manuals
Related Search