Home

System Test Plan

1. System Test Plan Consultant Staffing Analysis Tool 6 Requirements Not To Be Tested This section describes the requirements that are not to be tested These requirements fall under two categories either the requirement is technically untestable or the requirement is a non developmental requirement such as the user manual For more information about these requirements please see the full SRS document 6 1 Maintenance and Support Requirements 6 1 1 Source Code Description All source code will be made available to Sogeti in the final product delivery It will be thoroughly documented using comments in the code as well as in the user manual under the Source Code section This section will contain descriptions of classes and data objects used in the code as well as their associated attributes and functions 6 1 2 Software Support Description Team Real shall not be responsible for supporting CSAT after its initial release All known issues and assumptions will be documented in the user guide under the Source Code section 6 1 3 Language Support Description All documents and user guides shall be provided in English 6 2 Other Requirements 6 2 1 Extensibility Description The web application will be designed and implemented taking future growth into consideration as more enhancements and functionality are likely to be added This shall be achieved by developing CSAT such that it is highly modular and all modules are loosely co
2. Request Request object We will submit request with varying High layer objects security levels made by accounts with varying security levels to ensure that authorized request are passed on and unauthorized request are rejected DA Processing Request Completed We will submit all possible Request Critical Layer Object Request Object Types and verify that the correct action has been taken for that type of request IT5 Data Layer User ID Object ID We will submit user IDs to search and Critical verify that it attempts to request the correct object from the database IT6 Data Layer Setsof Filtered objects We will give search a set of objects to Critical Objects anda filter and verify that the objects are filter filtered correctly IT7 Database Data Request SQL Query We will verify that the SQL Query Critical Manager matches the data request layer Table 21 Integration tests 4 9 2015 Real System Test Plan 3 5 System validation ID NI v2 V3 v4 V V6 NI Validation Verify login Verify Add Edit Delete Project Verify Add Edit Delete Account Verify Manual Team Generation Verify Auto Team Generation Verify Search Verify Security 4 9 2015 Input Username and password Project Output The system logs the given user in Relevant data is Information modified in the Changes Account database Relevant data is Information modified in the Changes C
3. 3 4 3 2 4 3 4 3 2 5 3 4 3 2 6 3 4 3 2 7 3 4 3 2 8 3 4 3 2 9 3 4 3 3 3 4 3 3 1 3 4 3 3 2 3 4 3 3 3 3 4 3 3 4 3 4 3 3 5 3 4 3 4 4 9 2015 System Testing Phase II Component Testing User Interface Controller Request Authorization Login External Work Flow Matching Request Handler Search Database Manager System Testing Phase MI Integration Testing Interface Layer Security Layer Processing Layer Data Layer Database Manager Layer System Validation 58 4 27 2015 4 27 2015 4 27 2015 4 27 2015 4 27 2015 4 27 2015 4 27 2015 4 27 2015 4 27 2015 4 27 2015 5 4 2015 5 4 2015 5 4 2015 5 4 2015 5 4 2015 5 4 2015 5 7 2015 Consultant Staffing Analysis Tool 5 1 2015 5 1 2015 5 1 2015 5 1 2015 5 1 2015 5 1 2015 5 1 2015 5 1 2015 5 1 2015 5 1 2015 5 7 2015 5 7 2015 5 7 2015 5 7 2015 5 7 2015 5 7 2015 5 7 2015 18hrs 2hrs 2hrs 2hrs 2hrs 2hrs 2hrs 2hrs 2hrs 2hrs 10hrs 2hrs 2hrs 2hrs 2hrs 2hrs 3hrs Real System Test Plan Consultant Staffing Analysis Tool 11 Approval Name Role Signature Date Sogeti USA Customer Douglas Jones Mike O Dell Program Director Clinton Smith Project Manager Gayatri Tiwari Team Member Mariana Flores Team Member Karma G Gurung Team Member Edward Kuykendall Team Member 4
4. Authentication SR2 Search Request From MROM DR1 Database Request From MROM DR2 Database Request From Search DO Database Query DBQ Formatted SQL Query Table 6 Module Data flows 4 9 2015 Consultant Staffing Analysis Tool Collection of Teams matched to given Project Filtered search results Filtered search results Collection of requested data from the database Collection of requested data from the database Collection of requested data from the database Collection of SQL data from the database 26 Real System Test Plan Consultant Staffing Analysis Tool 3 Test Items Figure 3 1 and the following tables show how testing will be broken down and details about each test Tables will be grouped by testing categories Unit Tests Component Tests Integration Tests and System Validation Tests Each table entry will show an ID the module subsystem layer to be tested an expected input the expected output a testing method and a priority Desktop UI Graph Renderer Request Builder Request Filter Request Authroization User Authentication Mail API Maps API Database Interface SQL Database Implementation 4 9 2015 User Interface Controller Request Authorization External Work Flow Request Handler Database Interface Figure 3 Testing Category Diagram 27 Interface Layer Processing Layer Data Layer Database Manager Layer Real System Test
5. keys in a secure manner The final product shall also be hosted on a secure server protected by Sogeti s VPN Only users who have access to the VPN shall be able to access the system Test Approach We will try to access other consultant information from the consultant account 5 5 Maintenance Support and Other Requirements Maintenance support and other requirements sections are not directly testable and thus are not included in the STP For further information about the maintenance support and other requirements sections of CSAT please see section 7 and 8 of the System Requirements Specification However some specific features may be tested with user input These requirements are outlined below 5 5 1 5 5 2 Troubleshooting Guide Description Team Real shall provide a troubleshooting guide that will provide general troubleshooting steps for the system This guide shall also outline all built in error messages describing their probable cause and suggested resolution Test Approach The guide shall be given to the end user and they will provide feedback on its usefulness Training Description Brief training will be provided for users who will utilize the system This shall be in the form of both a user manual as stated in requirement 4 4 and a brief training demo with Sogeti Test Approach The guide and training materials shall be given to the end user and they will provide feedback on its usefulness 4 9 2015 44 Real
6. Plan 3 1 Hardware Testing Consultant Staffing Analysis Tool There are not Hardware Tests associated with CSAT 3 2 Unit Testing 3 2 1 User Interface UU Module Input Output Test Priority UT11 Desktop User HTML We will test all input forms with data of both Critical UI Interaction Form correct and incorrect format Data UT12 Mobile UI User HTML We will test all input forms with data of both Medium Interaction Form correct and incorrect format Data UT13 Graph Client data Graph We will give the graph renderer various sets Critical Renderer of client data with normal and abnormal values and verify that it displays the correct graph or produces an appropriate error message Table 7 User Interface Subsystem Unit Tests 3 2 2 Controller UU Module Input Output Priority UT21 Request HTML Request We will submit form data and verify that the Critical Builder Form data Object created object is of the correct type and contains the correct data Table 8 Controller Subsystem Unit Tests 4 9 2015 28 Real System Test Plan 3 2 3 Request Authorization Consultant Staffing Analysis Tool UU Module Input Output Test Priority UT31 Request Filter Completed Completed We will submit requests and High request request object security levels and verify that they objects with filtered are filtered correctly data UT32 Request Request Request We will submit re
7. Results of those Once CSAT is installed in the users High Verification actions actions environment validation tests V1 V7 shall be repeated to ensure that CSAT is performing in their environment Table 22 System validation 4 9 2015 36 Real System Test Plan 4 Risks Consultant Staffing Analysis Tool This section will list all the risks associated with the testing phase of the CSAT Table with list of risk impact of a risk severity of a risk and mitigation strategy to resolve a risk is provided below 4 1 Risk Table ID Risk R1 Infinite Input Space Impact Possible missed faults due to untested inputs Severity Mitigation strategy Medium Test key features with R2 Damaged Database Damage R3 Software bugs A missed fault may cause data to be damaged Wrong data is sent from one layer to another Medium High CSAT s database shall have at least one redundant backup Dataflow testing using aforementioned tests Table 23 Risks 4 9 2015 37 Real System Test Plan Consultant Staffing Analysis Tool 5 Features To Be Tested This section describes all the requirements and features in CSAT and how each of them will be tested to ensure the successful completion of the project Brief description of the requirements and a test approach that will be used are given below 5 1 Customer Requirements 5 1 1 Support Multiple User Roles Description The system shall
8. The system shall validate all user input to ensure that the data entered is correct For example the system shall validate inputs to be sure they are not too long too short or of the wrong format Test Approach We will insert incorrect data and see if the system is able to detect it and counter with correct response or notification to the user 5 4 2 Secure Database Access Description The system shall only allow users to access information in the database that is related to their roles For example consultants can only see their data staffing executives can see all consultants data and projects administrators can see all data in the system and clients can only see the consultants general profile and their availability Test Approach We will login as each role and navigate the features provided to see if they are true to their role For example consultant account should not have a create project button 4 9 2015 43 Real System Test Plan Consultant Staffing Analysis Tool 5 4 2 Error Messages Description The application will provide safe error messages that avoid displaying user and application details That is only enough information to adequately explain the error will be shown to the user Test Approach We will input wrong information and see if the proper and safe error message is provided 5 4 2 Sensitive Information Description The application will store sensitive information such as passwords and encryption
9. allow users to login using their username and password Each user shall have a particular role with its own access Supported user roles include consultant staffing executives administrators and clients Each user shall only be displayed information or given features based on their respective roles Test Approach We will create an account for every single role and will test the login and logout for all the account We will also query some data and see the displayed information to ensure the information is based on their respective roles 5 1 2 Visual Representation of Consultant Data Description The system shall allow staffing executives to view consultant s stored data in an easy to use graphical user interface The staffing executive can then click on various icons on the graphs to see details of the consultant s data Test Approach We will login as staffing executive and click on a consultant account and see if the system is able to produce graphical view account information We will then click on various icons on the graphs to see if the details of the consultant s data are displayed 5 1 3 Search Description The system shall allow staffing executives to search the data stored in the system by keyword For example the staffing executive can search for projects by entering the project title or they can search for consultants by entering their name The system shall also allow the user to filter the results based on various fie
10. correct email message to recipient Receives Map request from Request Handler Obtains correct address from Google Maps API Receives a collection of account objects from MROM module Sends a collection of teams to MROM module Successfully receives Request object Sends the request to the correct module Receives user ID from User Authentication Sends requested Account object to User Authentication module Receives set of objects and filter MROM module Sends filtered object s to MROM module Receives data request from MROM module Sends correct data request to SQL Database Implementation module 49 Consultant Staffing Analysis Tool Fails to receive request object from Request Builder Fails to send authorized request to MROM module Allows unauthorized requests Fails to receive request object Sends incorrect Boolean value to Request Authorization module Fails to receive email request Sends incorrect email Fails to send email to recipient Fails to receive Map request Fails to obtain data from Google Maps API Obtains incorrect data from Google Maps API Fails to receive a collection of account objects from MROM module Sends incorrect collection of teams to MROM module Fails to receive Request object Fails to send the request to the correct module Fails to receive user ID from User Authentication module Fails to send the requested Account object to User Authentication Fails to receive objects a
11. database Fields such as username password session ID and employee ID will all be checked to ensure that the user placing any given request is who they say they are If any of these fields do not match the request will be send back up to the User Interface with a failure flag indicating that the user is not authorized to place the request Email API Module The purpose of the Email API Module is to provide a simple interface for CSAT to send emails over a SMTP mail server The Email API Module will take in a Request containing the email address to send the message to the subject of the email and the body of the email Then the Mail API Module shall utilize the Java Mail class to construct an SMTP mail message and send it Maps API Module The purpose of the Maps API Module is to provide a simple interface for CSAT to retrieve distance information from an outside source in this case Google Maps API using a stable interface The Maps API Module will take in two addresses and return either the longitude and latitude coordinates of the addresses or the distance between the addresses depending on the function called Matching Module The purpose of the Matching Module is to generate optimal teams based on a given projects requirements and the available consultants who can work on that project The Matching Module will take in a collection of available consultants accounts and a project to match them against It will then generate teams b
12. ee 20 Table 6 Mo d l ID Ata TL OWS hepa ns hig ee ds ga la rc ed ot ca as erst eae e 26 Table 7 User Interface Subsystem Unit Tests risotto 28 Table 8 Controller Subsystem Unit TES nia 28 Table 9 Request Authorization Subsystem Unit Tests 29 Table 10 L gin Subsystem Unit KEE 29 Table 11 External Work Flow Subsystem Unit Tests 29 Table 12 Matching Subsystem Unit Testi iii ico 30 Table 13 Request Handler Subsystem Unit Tests ii dais 30 Table 14 Search Subsystem Unit KE 30 Table 15 Database Implementation Subsystem Unit Tests 31 Table 16 Interface Layer Component Tests sssessseesseessessseseseeeessetsstesseesseeesseetsseesseesseeeseeessseessresseessee 31 Table 17 Security Layer Component Tests veronica ri an dre 32 Table 18 Processing Layer Component Tests s ciicssasieciss secasssessansncnsoceea tsvadevenssaceaateeess laccdnsasessadeveessces 32 Table 19 Data Layer Component EE 33 Table 20 Database Manager layer Component Tests 33 4 9 2015 6 Real System Test Plan Consultant Staffing Analysis Tool Table 2 Intesration ee 34 able 22 iS ystems Valid EE 36 Table 23 Ree 47 Table Integration tests pass test criteria secundada d 53 Table 22 System validation pass test criteria s cccss s zenciensivcsansaieatcrdeaseeessesvedeaavesadeetnbenuesseaguasenevenceesoasees 54 4 9 2015 7 Real System Test Plan Consultant Staffing Analysis Tool 1 Introduction This document describes the system test plan o
13. of the STP For further details on the detailed design of CSAT please see the full DDS document 2 3 1 Module Descriptions Desktop User Interface Module The purpose of the Desktop User Interface Module is to render all CSAT pages using a combination of HTML and CSS The CSS for these pages shall be coded in such a way as to provide an easy to use interface on high resolution widescreen desktop monitors The CSS shall also be coded such that the pages match the existing Sogeti website s colors and theme Mobile User Interface Module The purpose of the Mobile User Interface Module is to render all CSAT pages using a combination of HTML and CSS The CSS for these pages shall be coded in such a way as to provide an easy to use interface on lower resolution mobile devices The CSS shall also be coded such that the pages match the existing Sogeti website s colors and theme Graph Renderer Module The purpose of the Graph Renderer Module is to render the various graphs throughout CSAT using calls to the requesting pages to get data The Graph Renderer Module will utilize the Dojo graphing utility developed by IBM to render each graph before displaying it in either the Desktop or Mobile User Interfaces Request Builder Module The purpose of the Request Builder Module is to create Request objects base on the user inputs into the HTML forms in either the Desktop or Mobile User Interfaces The Request Builder shall be a Java Server Page tha
14. reflect the level of security of the user The user will be allowed to perform authorized actions The user will not be allowed to perform unauthorized actions Table 25 System validation pass test criteria 4 9 2015 54 Consultant Staffing Analysis Tool Teams will fail to auto generate Teams will be generated that do not match the given criteria Search results will not match the given criteria Search results will not reflect data from the database Information displayed in the UI will not reflect the level of security of the user The user will be allowed to perform unauthorized actions The user will not be allowed to perform authorized actions Real System Test Plan 9 Test Deliverables Consultant Staffing Analysis Tool A record of all tests performed will be kept while developing the CSAT system This section will include what will be documented what and how each test will be performed 9 1 Deliverables 9 1 1 System Test Plan Includes the entirety of this document to specify how each unit and component will be tested as well as the system as a whole 9 1 2 Test Cases Each test case recorded will include the following information 4 9 2015 Test ID Tester Name Description Pre condition Post condition Input Expected output Actual output Test Steps Test Result Notes Comments 55 Real System Test Plan 9 1 3 Test Case Result Each test case result will include the fol
15. see the consultants general profile and their availability 6 3 Error The application will provide safe error messages that avoid 3 Moderate Messages displaying user and application details That is only enough information to adequately explain the error will be shown to the user 6 4 Sensitive The application will store sensitive information such as 4 High Information passwords and encryption keys in a secure manner The final product shall also be hosted on a secure server protected by Sogeti s VPN Only users who have access to the VPN shall be able to access the system Table 4 Security Requirements 2 1 4 Maintenance Support and Other Requirements Maintenance support and other requirements sections are not directly testable and thus are not included in the STP For further information about the maintenance support and other requirements sections of CSAT please see section 7 and 8 of the System Requirements Specification 4 9 2015 15 Real System Test Plan Consultant Staffing Analysis Tool 2 2 Architectural Design Specification The Architectural Design Specification or ADS describes the high level architecture of CSAT as it is broken down into five distinct layers and their corresponding sub systems It also defines major data flows between the layers and described sub systems Included in the STP are the Architectural Design Diagram Data Flow Diagram and a brief description of each layer these elem
16. shall be achieved by creating a dedicated mobile friendly sub domain with all the features of the primary site Test Approach We will test the system on mobile web browser like Chrome Safari Firefox and IE 4 9 2015 42 Real System Test Plan Consultant Staffing Analysis Tool 5 3 3 Browser Compatibility Description The system shall be compatible with most internet browsers These include Google Chrome Firefox Safari and Internet Explorer Priority shall be given to Chrome and Firefox as they are the most common browsers used by Sogeti Test Approach We will test the system on all major internet web browsers like Chrome Firefox Safari and IE 5 3 4 Android Compatibility Description The Android application shall be compatible with the latest Android APIs Test Approach We will use the latest Android API s for the application to be compatible 5 3 5 Database Scalability Description The CSAT database shall be scalable to allow for growth within Sogeti For example the system shall allow the user to add more user accounts teams and projects as the need arises without impacting performance Currently the system shall support a minimum of 1000 consultant accounts and projects Test Approach We will test the CSAT with 1000 consultant for the time being We will also test the system with 100000 consultants to see the impact of 100 times the growth 5 4 Security Requirements 5 4 1 Malicious Input Protection Description
17. test case succeeds and the negative one fails This will help to reduce the necessary tested input space to a manageable level 1 3 2 Test Environment Due to the fact that CSAT is a web application and not a physical product there are some components of its runtime environment that cannot be tested as they are under the control of the end user Because of this we will be defining our own runtime environment for testing purposes However this environment will be as close to the end users environment as possible and it will include the following major items e Apache Tomcat 7 0 web server e Java Runtime Environment 6 e MySQL Server on localhost e Google Chrome Firefox web browsers e Stable internet connection for API modules 4 9 2015 10 Real System Test Plan Consultant Staffing Analysis Tool 2 References 2 1 System Requirements Specification The system requirements specification or SRS describes all requirements of CSAT derived by both the customer and the development team The following is a condensed list of all of the requirements of CSAT to be used as a reference in the following sections of the STP For further details please see the full SRS document 2 1 1 Customer Requirements Req Requirement Description Priority 3 1 Support The system shall allow users to login using their username 5 Critical Multiple User and password Each user shall have a particular role with its Roles own access Supported user roles in
18. to receive data request from Processing and Data Layers e Fails to send correct data requested to Processing and Data Layers 8 5 System validation ID NI v2 V3 V4 Validation Verify login Verify Add edit Delete Project Verify Add edit Delete Account Verify Manual team Generation 4 9 2015 Pass Criteria e User will be logged in if username and password correct e User will be notified if credentials are invalid e UlLand database will reflect changes as projects are deleted or new projects are created e Ul and database will reflect changes as accounts are deleted or new accounts are created e UI and database will reflect changes as teams are deleted or new teams are created 53 Fail Criteria e User will be logged in if credentials are invalid e User not be logged in if credentials are valid e Ul and database will not reflect changes as projects are deleted or new projects are created UI and database will not reflect changes as accounts are deleted or new accounts are created e Ul and database will reflect changes as teams are deleted or new teams are created Real System Test Plan V5 Verify Auto Team Generation V6 Verify Search V7 Verify Security Teams will be auto generated to match a given set of criteria Search results will match given criteria Search results will reflect database data Information displayed in the UI will
19. 16 Interface Layer Component Tests 4 9 2015 31 Real System Test Plan Consultant Staffing Analysis Tool 3 3 2 Security Layer ID Subsystem Input Output Test Priority CT21 Request Completed Completed We will submit requests and High Authorization request request object security levels and verify that they objects with filtered are filtered correctly data CT22 Request Request Request object We will submit request with j High Authorization objects varying security levels made by accounts with varying security levels to ensure that authorized request are passed on and unauthorized request are rejected CT23 Login Request Account object We will submit a request for High object Request account object check that it requests the correct account Table 17 Security Layer Component Tests 3 3 3 Processing Layer ID Subsystem Input Output Test Priority CT31 External Email Request Email We will submit a request for an High Work Flow email to be sent to a specific account and verify that the email was sent B 8 J CT32 External Map Request Longitude We will submit a request object and Critical Work Flow and latitude verify that the address information 1t returns is correct CT33 Matching Collection of Set of We will submit sets of account High account matched objects and verify that the teams objects teams created make sense CT34 Request Request Object Specific W
20. 9 2015 59 Real
21. Department of Computer Science and Engineering The University of Texas at Arlington System Test Plan Team Real Project Consultant Staffing Analysis Tool C S A T Team Members Clinton Smith Gayatri Tiwari Mariana Flores Karma G Gurung Edward Kuykendall System Test Plan Consultant Staffing Analysis Tool Last Updated 4 9 2015 Table of Contents Document Revision Historia A adit ended A A da ead pete iced tenis 4 ET E ins Doe 5 Eristof Tables TEE 6 MeO e EE 8 O st Ss A a Ee 8 2 Product Scope Sit 9 A EE 10 AS e en o de e e a e e 11 2 1 System Requirements Spee liCAU OM o us 11 2 2 Architectural Design Specification so a05 552 7eecace sac swsenceoas yeas eevseaeecusgemreesuesaceeyesorces ant teqoed tasaeeiaas 16 2 3 Detailed Design Speciation nisinsin ieissa sede REENEN Eed NES 21 EK 27 3 1 Hardware Testing EEN 28 3 2 Unit Testing eee neri Arda 28 3 3 Component Tests ee ee a iii id 31 S EE Eegen 34 SEET 35 Ah RUS O 37 A ARIS Vale A E A elaine GROG ae aly AA ae eileen 37 S Features To B Tested EE 38 Del Customer EELER ietie een aen e ae aa ae Sr 38 4 9 2015 2 Real System Test Plan Consultant Staffing Analysis Tool 52 Parka Gare RES ee 41 E ER Ee EE 42 JA SSC UTI Y EIERE 43 5 5 Maintenance Support and Other Reourements 44 6 Requirements Not To Be Tested i asscccsetssveieetwessccesnczcctarbavsanavedsnevedsavestavssadeassascdesSedesansauersceesnsyecenseencs 45 6 1 Maintenance and Support Requirements oooo
22. a thorough user guide outlining how the various users are to use the system This will include step by step breakdowns of use cases list of user types and their features as well as other pertinent information required by the The Android application shall be published on the Google Play Store to allow the users to easily download the app to their 4 1 Software Packaging 4 2 Installation Guide up the application on a server 4 3 Administrator Guide 4 4 User Guide end users 4 5 Google Play Publication Android devices Table 2 Packaging Requirements 4 9 2015 13 3 Moderate 2 Low Priority 5 Critical 4 High 5 Critical 5 Critical 2 Low Real System Test Plan Consultant Staffing Analysis Tool 2 1 3 Performance Requirements Req Requirement Description Priority 5 1 Response The system shall provide a fast and responsive user interface A 4 High Time delay of more than a second will have a percent done indicator to keep the user s attention Delays of more than ten seconds are not acceptable 5 2 Mobile The application will be compatible with most mobile screen ES High Browser sizes and mobile web browsers Priority shall be given to phone Compatibility compatibility utilizing the Chrome and Safari mobile browsers This shall be achieved by creating a dedicated mobile friendly sub domain with all the features of the primary site 5 3 Browser The system shall be compa
23. aking the staffing process much faster and more efficient CSAT shall also allow clients of Sogeti to connect to the system and see available consultants They will be able to create teams and select individual consultants they would like to invite to speak at their business Clients will only be able to see who is available and their skills but no specific personal information A client would gain access to CSAT by receiving an invite from Sogeti in the form of a link that directs them to the system 4 9 2015 8 Real System Test Plan Consultant Staffing Analysis Tool 1 2 Product Scope CSAT shall consist of a scalable web based application allowing the user to view the system on both a standard PC and a mobile device a database to hold the relevant client and consultant information and a web server to host the application and the database The application itself shall be written using standard web languages such as HTML CSS and Java and the database will be a MySQL database to allow for easy data access These features shall increase the system s maintainability and portability by allowing it to be hosted on almost any type of web server The end users of CSAT primarily the staffing executives shall have many features available to them Primarily the system shall provide a graphical interface where the staffing executives can see consultant and team data in an easy to read fashion that allows them to quickly make staffing choices For ex
24. ample when a staffing executive searches for a consultant to add to a project they see graphs for each consultant that shows their appropriateness for a particular project based on certain criteria such as experience career goals cost and distance These graphs provide a brief overview of each consultant however the graphs are dynamic and the staffing executive can click on the icons on the graph to see more details concerning that particular consultant for example if they click the cost icon they will see a breakdown of that individuals pay based on their position as well as other things such as travel costs Using the graphical user interface the staffing executive shall also be able to create teams by adding individual consultants to a project They can then use the same graphs to analyze different teams based on the same criteria as the individual consultants thus allowing them to create the most effective team possible The system shall also provide automatically generated teams for each project That is the system shall create suggested teams based on certain project attributes For example if a project requires a lower cost team then the system shall provide the most optimal team to achieve the lowest cost or if a project is extremely difficult the system shall provide a suggested team with more experience The system shall also provide features for the consultants themselves It shall allow them to set their preferences For example t
25. ased on that project teams such as most cost effective most skill effective most happiness effective overall most effective and so on Once calculated it will return a sorted collection of teams back to the caller 4 9 2015 22 Real System Test Plan Consultant Staffing Analysis Tool Master Request Observer Module The purpose of the Master Request Observer Module or MROM is to process and route all authorized requests through CSAT Its structure follows the Observer Pattern That is the Master Observer contains a collection of individual Concrete Observers that process each different type of Request individually For example there would be a Login Observer a Logout Observer an Add Account Observer and so on When a Request is passed into the MROM it cycles through each Observer until the correct one is found and then that Observer processes the Request either by performing the action or routing parts of the action to the subsystems needed Once the Request is fully processed it is passed back up to the Request Filter Module to be filtered and then sent back to the user to be displayed Search Module The purpose of the Search Module is to process all requests for filtered data from CSAT The Search Module will take in a search parameter and a collection of filters It will then call the Database Interface Module which will return the results from the database The Search Module will then further filter the results before passing the r
26. ate the system in Android studio so that when ready it could be published on the Google Play Store 5 2 Packaging Requirements 5 2 1 Software Packaging Description The system shall be delivered as a single zip file containing all source code and resources used Test Approach We will extract the zip file and check if all the source code and resources used are included 5 2 2 Installation Guide Description The zip file will contain a text file clearly describing how to set up the application on a server Test Approach We will each try to follow a text file that is included with the zip file to see if we could set up the application on a server We will also ask some friends from other team to volunteer to set up the application on a server given a text file and see if they are able to successfully set up the application 5 2 3 Administrator Guide Description The zip file shall contain a text file clearly describing the features available to an administrator that will not be included in the normal user guide For example adding new 4 9 2015 41 Real System Test Plan Consultant Staffing Analysis Tool accounts deleting accounts resetting passwords etc It shall also include the initial system administrator passwords and instructions on how to change them once the system is installed Test Approach We will ask some friends from other team to volunteer to navigate as an administrator using administrator guide provided wi
27. clude consultant staffing executives administrators and clients Each user shall only be displayed information or given features based on their respective roles A3 Visual The system shall allow staffing executives to view 5 Critica Representation consultant s stored data in an easy to use graphical user of Consultant interface The staffing executive can then click on various Data icons on the graphs to see details of the consultant s data 3 3 Search The system shall allow staffing executives to search the 5 Critical data stored in the system by keyword For example the staffing executive can search for projects by entering the project title or they can search for consultants by entering their name The system shall also allow the user to filter the results based on various fields 3 4 Create Projects The system shall allow staffing executives to create new 5 Critical projects by entering project information into the system Project information to be stored in the system includes client title description cost start end date and team size 4 9 2015 11 Real System Test Plan 3 5 Edit Projects 3 6 Delete Projects 3 7 Generate Proposed Teams 3 8 Manual Creation of Teams 3 9 Edit Teams 3 10 Delete Teams 3 11 Manage Profile 3 12 Manage Skills 3 13 Invite Clients 4 9 2015 Consultant Staffing Analysis Tool The system shall allow staffing executives to edit projects that are stored i
28. conoccccnoccnononanononononononnnnccnonono conocio nono no cnnn non ne non ncnnnnnnnnonnss 45 6 2 Other Requirements iii airada 45 Te Testing Approach ainia 46 A E 46 DELLA a A A A E E A A id 46 Teo MOTE UMC A esas oak cote cunsied Gabe E parte na gaak gases sbed cia ata cae Coty E 47 E TEE 47 eem Pass Fail Eed 48 S L Hardware KEE 48 9 2 Ee EELER EE 48 8 3 Component Ma 50 BA ntesration KEEN 52 e ele Eet EE 53 9 Pest Deli E 55 ERR 55 d ENK EE 57 10 1 MS Project Plan System Testing Kee 57 Wee EE 59 4 9 2015 3 Real System Test Plan Consultant Staffing Analysis Tool Document Revision History Revision Revision Number Date 3 25 15 Initial draft of STP Began work on first draft of STP 3 29 15 Continued work on STP draft Completed sections 1 2 and 3 Description Rationale 3 30 15 Continued work on STP draft Completed sections 6 and 7 3 31 15 Completed work on STP version 1 0 Added remaining sections of STP 4 9 15 STP version 2 0 Modified STP as per feedback 4 9 2015 4 Real System Test Plan Consultant Staffing Analysis Tool List of Figures Figure 1 ADS Diagram 18 Figure 2 Module Breakdown Diagram 24 Figure 3 Testing Category Diagram 27 4 9 2015 5 Real System Test Plan Consultant Staffing Analysis Tool List of Tables able Ms Customer REG USNS rh O E O a 13 Table 2 Packagine Requitenents it a A A OS a A A EAS 13 Table 3 Performance Requirements A Vow E 14 El e GE e 15 Table 3 2D Sata Pos enee
29. cutives to edit teams They shall be able to add additional team members and delete team members Test Approach We will login as a staffing executive and edit team by changing the team member We will then go to project details to see if the new changes have been saved to verify 5 1 10 Delete Teams Description The system shall allow staffing executives to delete teams from the system Test Approach We will login as a staffing executive and delete a team from a project We will then go to project details to see if there are any teams associated with it 5 1 11 Manage Profile Description The system shall allow all users to manage their profile Users shall be able to set their preferences such as distance to client overtime availability types of projects etc Also they will be able to edit their personal information such as their skill set and address Test Approach We will set different preferences for a user We will then go to user details to see if the system is able to save it We will also edit a skill set and address and then go to user details to verify that the system has updated the address and has sent a skill change request to the admin 5 1 12 Manage Skills Description The system shall allow users to manage their skills Users shall be able to add skills and their skill level The skill shall then be approved or disapproved by an administrator of the system Test Approach We will add a new skill set in a user acco
30. e Interface Implementation CSAT Database 24 Real System Test Plan 2 3 1 DDS Data Flows Consultant Staffing Analysis Tool This table describes each dataflow between modules in CSAT These dataflow descriptions are at a very high level For a more detailed description of each dataflow please see each individual module s section later in this document Dataflow Passes Returns UI User inputs for Desktop UI N A U2 User inputs for Mobile UI N A DUI Rendered HTML page for N A Desktops MUI Rendered HTML page for Mobile N A Devices DG if Desktop graph data Rendered graph MG Mobile graph data Rendered graph MRD Mobile UI Request data Processed Request data DRD Desktop UI Request data Processed Request data R Request to be processed N A FR Filtered and processed Request N A UA User data from Request T F Boolean if user is authenticated EM Email data T F Boolean if email was sent from SMTP mail server MC Address or set of addresses Float longitude and latitude of address or distance between addresses from Google Maps MR Mail Request T F Boolean if email was sent MaR Map Request Float longitude and latitude of address or calculated distance between addresses RA Request that has been authorized N A PR Processed Request N A 4 9 2015 25 Real System Test Plan TM Collection of Consultants accounts and a Project SR1 Search Request From User
31. e will submit different request Critical Handler Request objects and verify that MROM sends the request to the correct module Table 18 Processing Layer Component Tests 4 9 2015 32 Real System Test Plan Consultant Staffing Analysis Tool 3 3 4 Data Layer ID Subsystem Input Output Test Priority CT41 Search User ID Object ID We will submit user IDs to search and High verify that it attempts to request the correct object from the database CT42 Search Sets of Filtered We will give search a set of objects to High Objects anda objects filter and verify that the objects are filtered filter correctly Table 19 Data Layer Component Tests 3 3 5 Database Manager Layer ID Subsystem Input Output Test Priority CT51 Database Data SQL We will verify that the SQL Query Critical Interface Request Query matches the data request Table 20 Database Manager layer Component Tests 4 9 2015 33 Real System Test Plan Consultant Staffing Analysis Tool 3 4 Integration Tests ID Layer Input Output Test Priority TTT Interface User Request Object We will perform each action available Critical Layer Interactions to a user and verify that an appropriate request object is created IT2 Security Completed Completed We will submit requests and security High l Layer request request object levels and verify that they are filtered objects with filtered correctly data 113 Security
32. ee personal information about Consultants but can see Consultants skills and availability Processing Layer The purpose of the Processing Layer is to process all user requests of the system and their corresponding backend functions This layer is also responsible for creating and maintaining all data objects in the system For example if the user requests to add a project and has sufficient access to do so the Processing Layer will create the Project data object populate it with the data passed in the request and pass it to the Database Manager Layer to be saved 4 9 2015 16 Real System Test Plan Consultant Staffing Analysis Tool Data Layer The purpose of the Data Layer is to process all requests for data by the system it also handles all post database query data calculations for example calculating distance between a Consultant s address and a Client s address The Data Layer expects a request and a set of search parameters to search with The Data Layer will then request the needed data from the Database Manager Layer Once the requested data is received the Data Layer will format the data to match the corresponding request and pass that information back to the requester Database Manager Layer The purpose of the Database Manager is to provide an interface to the actual database In this way the database itself is abstracted from the system allowing for increased modularity The system shall pass in a request for data or a r
33. ents are to be used as references in later sections of the STP For further details on the architecture of CSAT please see the full ADS document 2 2 1 Layer Descriptions Interface Layer The purpose of the Interface Layer is to provide an easy to use user interface for the CSAT system These interfaces will accept user requests and send the corresponding data to the Security Layer to be verified then the data will move on to the rest of the system to be processed This layer is also responsible for displaying the output of CSAT and formatting that output data to match the user s specific device For example a desktop computer or a mobile phone or tablet Security Layer The purpose of the Security Layer is to provide authorization of user commands based on roles as well as authenticate users upon login When a user makes a request of the system the request is sent to the Security Layer At that point the Security Layer verifies that the user has sufficient permission to execute the request If they do the request is sent on to the rest of the CSAT system to be processed if not a message is returned to the Interface Layer to notify the user that they do not have permission to perform the request The Security Layer is also responsible for performing output filtering CSAT will pass in the output requested by the user and the Security Layer will filter it based on their respective role For example an admin can see all data while a Client cannot s
34. equest to save data to the Database Manager Layer and the Database Manager Layer shall convert that into its corresponding database query Once the request is processed by the database the Database Manager Layer shall format the results and send it back to the requester of the data 4 9 2015 17 Real System Test Plan Consultant Staffing Analysis Tool 2 2 2 ADS Diagram Desktop UI Du12 SMTP Mail Server 1 Google Maps API WF S Database Interface CSAT Database Figure 1 ADS Diagram 4 9 2015 18 Real System Test Plan Consultant Staffing Analysis Tool 2 2 3 ADS Data Flows Data Flow ID Description Ul User request or action to the desktop UI U2 User request or action to the mobile UL DUU Desktop output to user DUI2 Request to be authorized sent from desktop UI MUD Mobile output to user MUR Request to be authorized sent from mobile UI RAI CSAT system output formatted for a desktop UI RA2 CSAT system output formatted for a mobile UI RA3 Request to verify user login credentials RAA Authorized request to be processed by the Request Handler subsystem LI Users profile once verified by login subsystem L2 Request for users profile from Search subsystem WEI _ Notification in the form of an SMTP mail message WF2 Address to get the longitude and latitude coordinates of WF3 Longitude and latitude coordinates of requested address G1 Longitude and latitude coordinates of r
35. equested address from Google API Mi Collection of teams matched to a given project RH1 Project and a collection of consultants to be matched to that project RH2 Raw CSAT output for a given request RH33 Request for a collection of data and a set of filter parameters RH4 Request to save a data object to the database BUS Request for external processing either sending an email notification or getting coordinates from Google Maps API 4 9 2015 19 Real System Test Plan Consultant Staffing Analysis Tool S1 Requested collection of data based on given filters S2 Requested user s profile for authorization S3 Request a collection of data from the database Dil Result of saving a data object to the database True or False with error message DI2 Result of database query for given search parameters and formatted for the Search subsystem DI3 Database query to save or get information from the database DB1 Raw database query results Table 5 ADS Data Flows 4 9 2015 20 Real System Test Plan Consultant Staffing Analysis Tool 2 3 Detailed Design Specification The Detailed Design Specification or DDS describes the detailed systems of CSAT broken down into individual modules It also describes the specific data flows between those subsystems and their format Included in the STP are the Detailed Design Diagram Data Flow Diagram and a brief description of each module these elements are to be used as a reference in later sections
36. er 4 9 2015 Receives request objects from Security Database and Data layers Sends processed data to correct layer Receives account request from Security layer Sends account request to Database Manager Layer Receives requested account from Database Manager Layer 52 e Fails to receive request objects from Interface layer Fails to send data to Interface Layer Fails to filter data in accordance to user s security level Fails to receive Request object from Interface Layer Fails to send authorized requests to Processing Layer Sends unauthorized requests to Processing Layer Fails to receive request object from Security Database or Data layer Fails to send processed data to correct later Fails to receive account request from Security layer Fails to send account request to Database Manager Layer Receives incorrect account from Database Manager layer Real System Test Plan IT6 Data Layer IT7 Database Manager layer Receives set of objects and filter from Processing Layer e Sends filtered object s to Processing Layer e Receives data request from Processing and Data Layers e Sends correct data requested to Processing and Data Layers Table 24 Integration tests pass test criteria Consultant Staffing Analysis Tool e Fails to receive objects and filter from the Processing layer e Fails to send the requested object s to the Processing layer e Fails
37. esults back to the module that called it Database Interface Module The purpose of the Database Interface Module is to provide a stable interface for CSAT to access the physical database The Database Interface Module and the specific database implementation follow the Bridge pattern as such the Database Interface Module does not actually do any processing It simply defines the interface by which all specific database implementations must be designed thus allowing for easy database changes without changing the system as a whole Database SQL Implementation Module The purpose of the Database SQL Implementation Module is to provide all access to the physical MySQL database based on the template provided by the Database Interface Module The Database SQL Implementation Module will take in a Request for some piece of data and it will then construct a query and submit that query to the database It will then format the output as needed by the specific Request and return the results to the requesting module 4 9 2015 23 Real System Test Plan Consultant Staffing Analysis Tool 2 3 1 DDS Diagram SMTP Mail Server EM Google Maps API Figure 2 Module Breakdown Diagram 4 9 2015 Controller Request Builder Internet Request Aut Request User O Ri External Work Flow Matching Request Handler MaR y DR1 DR2 Database Interface Request Filter Database SQL Databas
38. hey could select the types of projects they would like to work on their maximum commute distance and their availability for overtime The system shall also provide features for the clients of Sogeti It shall allow them to see available consultants create teams and invite consultants to speak at their business However clients will not be able to see all information in the system they will only have access to the consultant s names skills and availability Lastly the administrators of the system shall have features allowing them to generate user accounts as well as delete and edit them 4 9 2015 9 Real System Test Plan Consultant Staffing Analysis Tool 1 3 Testing Scope This section describes the testing scope of CSAT as it pertains to the tests that are contained within later sections of this document The testing scope consist of two primary components test inputs and the test environment Each of which is outlined below in further detail 1 3 1 Test Inputs Due to the nature of CSAT some inputs are impossible to test fully as they have an infinite input space As such measures must be taken to reduce the input space to a manageable level This shall be achieved by limiting the test input scope for all user tests to a simple positive and negative input That is for example if the system expects a string in email format then CSAT shall be tested with one valid and one invalid string The test shall be said to pass if the positive
39. ized requests to e Fails to send authorized requests Request Handler subsystem to Request Handler e Sends unauthorized requests to request handler CT23 Login e Receives Request object from e Fails to receive Request object Request Authorization subsystem from Request Authorization e Requests and receives correct subsystem account object from Search e Receives incorrect account subsystem object from the Search subsystem CT31 External Work e Receives email request from e Fails to receive email request Flow Request Handler subsystem from Request Handler subsystem e Sends correct email to correct e Sends incorrect email recipient e Sends email to incorrect recipient CT32 External Work e Receives map request from e Fails to receive map request from Flow Request Handler Request Handler e Receives correct address from e Fails to receive incorrect address Google Maps API from Google Maps API 4 9 2015 50 Real System Test Plan CT33 Matching CT34 Request Handler CT41 Search CT42 Search CT51 Database Interface Receives a collection of account objects from Request Handler Sends correct collection of teams to Request Handler Receives request objects Sends request to correct subsystem Receives account request from Login subsystem Sends account request to Database Interface subsystem Receives requested account from Database Interface subsystem Receives set of objects and filter Request Handler Sends filtered object s to Req
40. lds Test Approach We will login as a staffing executive and search the data by entering a few different keyword and see if the system produces the desired result We will search using different filter using a same keyword to see if the system produces the desired result 4 9 2015 38 Real System Test Plan Consultant Staffing Analysis Tool 5 1 4 Create Projects Description The system shall allow staffing executives to create new projects by entering project information into the system Project information to be stored in the system includes client title description cost start end date and team size Test Approach We will login as a staffing executive and create a new project by entering project information into the system We will then go to current project tab to see if the new project we just created is listed to verify 5 1 5 Edit Projects Description The system shall allow staffing executives to edit projects that are stored in the system Test Approach We will login as a staffing executive and edit a project by changing the project information We will then go to project details to see if the new changes have been saved to verify 5 1 6 Delete Projects Description The system shall allow staffing executives to delete projects that are stored in the system The system shall store deleted items in the database even after deletion to facilitate data recovery if needed However deleted items will not appear in search res
41. lowing information Test ID Date and time Pass fail inconclusive verdict Notes Comments 9 1 4 Defects Consultant Staffing Analysis Tool In the case of a test case failure a defect will be created with the following information 4 9 2015 Test ID Particulars of error Error messages line of error etc Possible solution 56 Real System Test Plan 10 Test Schedule 10 1 MS Project Plan System Testing Phase Consultant Staffing Analysis Tool WBS Task Name Planned Start Planned Finish BCWS 3 4 3 System Testing Phase 3 4 3 1 System Testing Phase I Unit 4 20 2015 4 24 2015 28hrs Testing 3 4 3 1 1 Desktop UI 4 20 2015 4 24 2015 2hrs 3 4 3 1 2 Mobile UI 4 20 2015 4 24 2015 2hrs 3 4 3 1 3 Graph Renderer 4 20 2015 4 24 2015 2hrs 3 4 3 1 4 Request Builder 4 20 2015 4 24 2015 2hrs 3 4 3 1 5 Request Filter 4 20 2015 4 24 2015 2hrs 3 4 3 1 6 Request Authorization 4 20 2015 4 24 2015 2hrs 3 4 3 1 7 User Authentication 4 20 2015 4 24 2015 2hrs 3 4 3 1 8 Mal API 4 20 2015 4 24 2015 2hrs 3 4 3 1 9 Maps API 4 20 2015 4 24 2015 2hrs 3 4 3 1 10 Matching 4 20 2015 4 24 2015 2hrs 3 4 3 1 11 MROM 4 20 2015 4 24 2015 2hrs 3 4 3 1 12 Search 4 20 2015 4 24 2015 2hrs 3 4 3 1 13 Database Interface 4 20 2015 4 24 2015 2hrs 3 4 3 1 14 SQL Database Implementation 4 20 2015 4 24 2015 2hrs 4 9 2015 57 Real System Test Plan 3 4 3 2 3 4 3 2 1 3 4 3 2 2 3 4 3 2 3
42. mobile screen Receives input from the UI modules Successfully sends the correct graph or error message to UI display Receives form data from the UI subsystem Sends correct Request Object to Request Authorization subsystem Receives request object from the MROM module Sends filtered data to Request Builder module 48 Ul is not displayed on the desktop screen Ul is not displayed on the mobile screen Fails to receive input from the UI modules Unable to send graph or error message to the UI display Sends incorrect graph or message to UI display Fails to receive data from the UI subsystem Sends the incorrect object to the Authorization subsystem Fails to send object to Request Authorization subsystem Fails to receive request object from the MROM module Sends unfiltered or incorrect data to the Request Builder module Fails to send request object to Request Builder Real System Test Plan UT32 UT41 UT51 UT52 UT61 UT71 UT81 UT82 UT91 Request Authorization User Authentication Mail API Maps API Matching MROM Search Search Database Interface 4 9 2015 Receives request object from Request Builder Sends authorized request to MROM module Sends error message if unauthorized request is made Receives request object from Request Authorization module Sends correct Boolean value to Request Authorization module Receives Email request from Request Handler Sends
43. n the system The system shall allow staffing executives to delete projects that are stored in the system The system shall store deleted items in the database even after deletion to facilitate data recovery if needed However deleted items will not appear in search results in the system Deleted projects can be completely removed by the administrator only The system shall automatically generate teams for a given project The system shall create the teams based on criteria within the project such as cost experience availability etc In addition to the automatically generated teams the system shall allow staffing executives to manually create their own teams by selecting team members from the pool of available consultants The system shall allow staffing executives to edit teams They shall be able to add additional team members and delete team members The system shall allow staffing executives to delete teams from the system The system shall allow all users to manage their profile Users shall be able to set their preferences such as distance to client overtime availability types of projects etc Also they will be able to edit their personal information such as their skill set and address The system shall allow users to manage their skills Users shall be able to add skills and their skill level The skill shall then be approved or disapproved by an administrator of the system The system shall allow staffing executi
44. nd filter from the MROM module Fails to send the requested object s to the MROM module Fails to receive data request from MROM module Fails to send correct data request to SQL Database Implementation module Real System Test Plan Consultant Staffing Analysis Tool UT92 SQL Database e Receives data request from e Fails to receive data request Implementation Database Interface module from Database Interface module e Generates correct SQL query e Generates incorrect SQL query Table 8 Unit testing pass fail criteria 8 3 Component Testing ID Subsystem Pass Criteria Fail Criteria CT11 User Interface e Displays data correctly in webor e Fails to display data correctly in mobile browsers web or mobile browsers CT12 Controller e Receives HTML Form Data from e Fails to receive HTML Form the User Interface Data from the UI e Sends correct Request object to e Fails to send correct Request Request Authorization subsystem object to Request Authorization subsystem CT21 Request e Receives request objects from e Fails to receive request objects Authorization Controller subsystem from Controller subsystem e Sends filtered data to Controller e Fails to send data to Controller subsystem in accordance to user s e Fails to filter data in accordance security level to user s security level CT22 Request e Receives Request object from e Fails to receive Request object Authorization Login subsystem from Login subsystem e Sends author
45. ount e Add Edit Delete Project e Add Edit Delete Team Manually e Auto Generate Team e Search Email Notifications 7 4 Test Metrics The below metrics will vary according to the priority levels which are listed in the following table Priority Description Success Failure Criteria Criteria Critical Features that need to be completed for core 100 lt 100 requirements to function High Features that are important to the system but it can gt 90 lt 90 still function without them Medium Features that help polish and refine the system the gt 75 lt 75 system will still fully work without these features Low Features that are listed in future requirements or are gt 50 lt 50 extra add on functionality to existing system Table 23 Test Metrics 4 9 2015 47 Real System Test Plan Consultant Staffing Analysis Tool 8 Item Pass Fail Criteria This section provides a detailed description of the pass and fail criteria for all tests included in section 3 hardware tests unit tests component tests integration tests and system validation 8 1 Hardware Testing There are not Hardware Tests associated with CSAT 8 2 Unit Testing ID Module Pass Criteria Fail Criteria UT11 Desktop UI UT12 Mobile UI UTI3 Graph Renderer UT21 Request Builder UT31 Request Filter 4 9 2015 Ul is successfully displayed on the desktop screen Ul is successfully displayed on the
46. quest with varying High Authorization objects object security levels made by accounts with varying security levels to ensure that authorized request are passed on and unauthorized request are rejected with the appropriate error messages Table 9 Request Authorization Subsystem Unit Tests 3 2 4 Login UU Module Output Priority UT41 User Request Account We will submit a login request and High Authentication object object ensure that the submitted account is Request logged in Table 10 Login Subsystem Unit Tests 3 2 5 External Work Flow ID Module Input Output Test Priority UT51 Mail Email Email We will submit a request for an email to be High API Request sent to a specific account and verify that the email was sent UT52 Maps Map Longitude and We will submit a request object for an Critical API Request latitude address get and verify that the address information it returns is correct Table 11 External Work Flow Subsystem Unit Tests 4 9 2015 29 Real System Test Plan Consultant Staffing Analysis Tool 3 2 6 Matching ID Module Input Priority UT61 Matching Collection of Set of We will submit sets of account objects High account objects matched and verify that the teams created are teams correct based on the given data Table 12 Matching Subsystem Unit Tests 3 2 7 Request Handler UU Module Input Output Priority MROM Request Specific We will submit different request objects and Critical Request verify that MROM sends the
47. r STP of CSAT the Consultant Staffing Analysis Tool for Sogeti USA The following section will outline the product concept and scope of the design of CSAT to be used as a reference for the following sections of the STP 1 1 Product Concept CSAT has one primary function to make the process of selecting a team for a software project easier and more intuitive Currently Sogeti uses a very manual system to select their teams for projects Staffing executives analyze availability tables consultant profiles and project documents to create the most effective team possible While this system does work it is very labor intensive which leads to a Staffing by availability problem This is where the team will be built solely based on who is available at any given point and not necessarily their appropriateness for the project This is what CSAT intends to address CSAT will make the team building process easier by removing the need for tedious tables and documents for staffing analysis and instead replace them with an easy to use graphical interface that will allow the staffing executives to see at a glance which consultants would best suit a particular project Not only that the system will also generate suggested teams by analyzing the consultant data and comparing it to the needs of the client thereby automating a large portion of the staffing process The executives would then be able to look over entire teams instead of individual consultants m
48. reate a team by selecting consultants by hand A project Keywords and filter User actions database Database is updated with a saved team associated with a project A set of possible teams for the given project The correct data from the database Results of those actions 35 Consultant Staffing Analysis Tool Test We will submit Correct and incorrect data for username and password and verify that the correct action is taken in each situation We will add edit and delete a project and verify that the information in the database has changed We will add edit and delete an account and verify that the information in the database has changed We will create a team and save it to the database We will submit a project and have the system generate a set of possible teams and verify that those teams make sense for the given project We will submit keywords and filters into the system some that should be found and some that should not be found and verify the results are correct with what is in the database We will use an account for each security level and verify that all request made by an account of that security level are fulfilled while request that account is not authorized to submit are rejected Priority Critical Critical Critical Critical Critical High High Real System Test Plan Consultant Staffing Analysis Tool V8 Installation User
49. request to the correct module Table 13 Request Handler Subsystem Unit Tests 3 2 8 Search ID Module Input Output Test Priority UT81 Search UserID Object ID We will submit user IDs to search and verify High that it attempts to request the correct object from the database UT82 Search Sets of Filtered We will give search a set of objects to filter High Objects anda objects and verify that the objects are filtered filter correctly Table 14 Search Subsystem Unit Tests 4 9 2015 30 Real System Test Plan Consultant Staffing Analysis Tool 3 2 9 Database Interface ID Module Input Output Test Priority UT91 Database Interface Data Data We will verify that data request sent to Critical Request Request the database interface are being routed to the SQL database Implementation UT92 SQL Database Data SQL We will verify that the SQL Query Critical Implementation Request Query matches the data that has been requested Table 15 Database Implementation Subsystem Unit Tests 3 3 Component Tests 3 3 1 Interface Layer ID Subsystem Input Output Test Priority CT11 User User Input HTML We will perform all actions available toa Critical Interface Form Data user and verify that the produce the expected result CT12 Controller HTML Request We will submit form data and verify that Critical Form Data Object the created object is correct Table
50. t after accessing the data from the User Interfaces packages that data and then passes the Request on to the Security Layer for processing The Request data type shall be described in more detail in later sections of this document Request Authentication Module The purpose of the Request Authentication Module is to ensure that all requests passed into CSAT are authentic and that the user placing the request has sufficient privileges to perform the action represented by the request This module is a Java class that will be called by the Request 4 9 2015 21 Real System Test Plan Consultant Staffing Analysis Tool Builder Module and will be run on the server side of CSAT Thus adding an extra layer of security between the user and the system Request Filter Module The purpose of the Request Filter Module is to filter CSAT output such that for any given user request the output shall only contain information they are authorized to see For example an admin of CSAT will have no restrictions while a Client user may only be able to see very basic information The module will take in a fully processed Request which contains it produced output and it will then filter it based on the user who placed the request and output the filtered Request to the proper User Interface to be displayed to the user User Authentication Module The purpose of the User Authentication Module is to check user credentials against the credentials stored in the CSAT
51. th the zip file 5 2 4 User Guide Description The zip file shall contain a thorough user guide outlining how the various users are to use the system This will include step by step breakdowns of use cases list of user types and their features as well as other pertinent information required by the end users Test Approach We will ask some friends from other team to volunteer to navigate as various user using the user guide to see if they are able to successfully perform the task 5 2 5 Google Play Publication Description The Android application shall be published on the Google Play Store to allow the users to easily download the app to their Android devices Test Approach We will download the app into an android phone via Android studio which will ensure that the application is able to be published on the Google Play Store 5 3 Performance Requirements 5 3 1 Response Time Description The system shall provide a fast and responsive user interface A delay of more than a second will have a percent done indicator to keep the user s attention Delays of more than ten seconds are not acceptable Test Approach We will navigate through all the features of the system to test the response time 5 3 2 Mobile Browser Compatibility Description The application will be compatible with most mobile screen sizes and mobile web browsers Priority shall be given to phone compatibility utilizing the Chrome and Safari mobile browsers This
52. tible with most internet browsers 5 Critical Compatibility These include Google Chrome Firefox Safari and Internet Explorer Priority shall be given to Chrome and Firefox as they are the most common browsers used by Sogeti 5 4 Android The Android application shall be compatible with the latest 2 Low Compatibility Android APIs 5 5 Database The CSAT database shall be scalable to allow for growth within 5 Critical Scalability Sogeti For example the system shall allow the user to add more user accounts teams and projects as the need arises without impacting performance Currently the system shall support a minimum of 1000 consultant accounts and projects Table 3 Performance Requirements 4 9 2015 14 Real System Test Plan Consultant Staffing Analysis Tool 2 1 4 Security Requirements Req Requirement Description Priority 6 1 Malicious The system shall validate all user input to ensure that the 3 Moderate Input data entered is correct For example the system shall Protection validate inputs to be sure they are not too long too short or of the wrong format oi Secure The system shall only allow users to access information in 3 Moderate Database the database that is related to their roles For example Access consultants can only see their data staffing executives can see all consultants data and projects administrators can see all data in the system and clients can only
53. uest Handler Receives data request from Request Handler and Search subsystems Sends correct data requested to Request Handler and Search subsystems Table 20 Component tests pass test criteria 4 9 2015 51 Consultant Staffing Analysis Tool Fails to receive a collection of account objects from Request Handler Fails to send correct collection of teams Fails to receive request objects Fails to send request to correct subsystem Fails to receive account request from Login subsystem Fails to send account request to Database Interface subsystem Receives incorrect account from Database Interface subsystem Fails to receive objects and filter from the Request Handler Fails to send the requested object s to the Request Handler Fails to receive data request from Request Handler and Search subsystems Fails to send correct data requested to Request Handler and Search subsystems Real System Test Plan 8 4 Integration Tests ID Layer IT1 Interface Layer Pass Criteria Displays data correctly to the user Consultant Staffing Analysis Tool Fail Criteria Fails to display data correctly re Security Layer Receives request objects from Interface layer Sends filtered data to Interface layer in accordance to user s security level IT3 Security layer Receives Request object from Interface Layer Sends authorized requests to Processing Layer IT4 Processing Layer ITS Data Lay
54. ults in the system Deleted projects can be completely removed by the administrator only Test Approach We will login as a staffing executive and delete a project by clicking delete project button We will then check the current project tab to see if the project we deleted is taken off of the list and we will also go the past project tab to see if the project we deleted is listed 5 1 7 Generate Proposed Teams Description The system shall automatically generate teams for a given project The system shall create the teams based on criteria within the project such as cost experience availability etc Test Approach We will click generate team button on the project page to see if the system is able to generate the team based on criteria provided by the project 5 1 8 Manual Creation of Teams Description In addition to the automatically generated teams the system shall allow staffing executives to manually create their own teams by selecting team members from the pool of available consultants Test Approach We will try click on add team member button on the project page to see if it will provide us with the list of consultant with radio button or a check box We will then click 4 9 2015 39 Real System Test Plan Consultant Staffing Analysis Tool either a radio button or a check box and then click submit to see if the manual creation of team is successfully executed 5 1 9 Edit Teams Description The system shall allow staffing exe
55. unt and then go to user details to verify that the system has sent a skill update request to the admin which will show pending next to skill added We will also check admin email to see if the skill update email has surfaced from the user 5 1 13 Invite Clients Description The system shall allow staffing executives to invite clients to use the CSAT system The system shall send the invite in the form of an email with a link directing the client to the CSAT system 4 9 2015 40 Real System Test Plan Consultant Staffing Analysis Tool Test Approach After creating a project we will send a client access link along with username and password to client from staffing executive account then we will try to access that link as client using that username and password to see if we are able to see the project details and update it 5 1 14 Invite Consultants to Speak Description The system shall allow clients to invite available consultants to speak at their businesses The client must provide a description of the topic to be spoken on Then the system should notify the admin of the client s request Test Approach From client account we will invite one of the available consultants and then we will check admin email account to see if the request email has surfaced 5 1 15 Android Application Description The system shall be provided in an Android application that will be published on the Google Play Store Test Approach We will try to simul
56. upled 6 2 2 iOS Mobile Application Description The system shall be converted to an iOS app to allow the users to access the system on their mobile iOS device 4 9 2015 45 Real System Test Plan Consultant Staffing Analysis Tool 7 Testing Approaches This section describes the testing approaches that shall be employed during the development and deployment of CSAT Included in this section is the general test strategy that will be used tools core functions to be tested as well as the testing metrics 7 1 Strategy The testing phase for CSAT will have to be done during implementation The team will test our code and core functionality to ensure that it is working as anticipated during implementation The team will try to test their code at the time of implementation so we do not have any code error and bug in future If there is time towards the end of the product development then there will be extra testing done to catch any bugs or mistakes that may been unaccounted for Mobile UI We do not have any hardware part to test it 7 2 Tools The development team will be using the following tools to test CSAT e JUnit For unit testing of individual functions and features as well as for backend integration testing e Selenium For regression testing and feature validation at the user level 4 9 2015 46 Real System Test Plan Consultant Staffing Analysis Tool 7 3 Core Functionality e Login Logout e Add Edit Delete Acc
57. ves to invite clients to use the CSAT system The system shall send the invite in the form of an email with a link directing the client to the CSAT system 12 5 Critical 5 Critical 5 Critical 5 Critical 5 Critical 5 Critical 5 Critical 3 Moderate 3 Moderate Real System Test Plan 3 14 3 15 Invite Consultants to Speak Android Application Consultant Staffing Analysis Tool The system shall allow clients to invite available consultants to speak at their businesses The client must provide a description of the topic to be spoken on Then the system should notify the admins of the client s request The system shall be provided in an Android application that will be published on the Google Play Store Table 1 Customer Requirements 2 1 2 Packaging Requirements Req Requirement Description _ The system shall be delivered as a single zip file containing all source code and resources used The zip file will contain a text file clearly describing how to set The zip file shall contain a text file clearly describing the features available to an administrator that will not be included in the normal user guide For example adding new accounts deleting accounts resetting passwords etc It shall also include the initial system administrator passwords and instructions on how to change them once the system is installed The zip file shall contain

System Test Plan

Contents

Download Pdf Manuals

Related Search

Related Contents