Iteration Plan Team No. 3 Istartonmonday.com Team members Role Kandarp Nyati Project Manager Fei Li Operational Concept Engineer Tanya Gautam Requirement Engineer Bharat Shugani Software Architect Thammanoon Kawinfruangfukul Life Cycle Planner Ying Li Tester Mark Villanueva IIV&V /30/20
Version History Date Author Version Changes made Rationale 0/22/ TK.0 Initial iteration plan Initialize the information of WWW.ISTARTONMONDAY.CO M Web Enhancement v.0 /9/ TK 2.0 Update iteration and iteration test plan Capability goals in OCD are updated /30/ TK 2. Update table 3 Correct CCD stakeholders ii
Table of Contents ITERATION PLAN... I VERSION HISTORY... II TABLE OF CONTENTS... III TABLE OF TABLES... IV TABLE OF FIGURES... V. Iteration Overview... 6. Capabilities to be Implemented... 6.2 Capabilities to be Tested... 7.3 Capabilities not to be tested... 9 2. CCD Preparation Plans... 9 2. CCD Stakeholders... 9 2.2 CCD usage scenarios... 0 2.3 CCD preparation plans... 2.4 CCD preparation site and dry run... 2 2.5 Feedback form... 2 2.6 CCD risk management plans... 2 iii
Table of Tables Table : Iteration Plan... 6 Table 2: Iteration Test Plan... 7 Table 3: CCD Stakeholders... 9 Table 4: CCD usage scenarios... 0 IP_TRR_Fa_T03_V2..doc iv Version Date: /30/
Table of Figures No table of figures entries found. IP_TRR_Fa_T03_V2..doc v Version Date: /30/
. Iteration Overview Iteration plan is used as a guideline for all stakeholders such as developers and testers to follow and monitor their progress in the project. Moreover, it helps to decide which requirements will be implemented depended on the time constraints, resources, and their priorities. The development of the project is divided into two iterations, and the main milestone is the Core Capability Drive-through (CCD). The capabilities which have higher priorities and risks will be implemented in the first iteration, and the less priority capabilities will be implemented in the second iteration, which occurs after the CCD.. Capabilities to be Implemented The capabilities shown in table below are going to implement in the project. Each capability can be implemented in different iteration and have different priority. Table : Iteration Plan Capability requirement (CR) Priority Iteration The website have a login page Must have 2 Google AdSense advertisement from current website Must have should maintain as they are 3 The website should maintain links to other job-related sites Must have as shown on current website. 4 The site should allow users to subscribe or unsubscribe Must have from email notifications (for all job postings). 5 The site should display employers or organizations logos. Must have 6 The UI should allow the user to easily search for jobs. Jobs Must have should be sorted into categories. All the categories should not be there in the front page, and it is possible to have multiple categories for one job. 7 Simple and intuitive user interface Must have 8 Employers have the ability to post jobs on the site. Must have 9 The main page should resemble the current site and contain a list of general job postings and announcements. Must have 0 Key word search is able to search on any match in the job Would have 2 listing and then the results could pop-up any references in the job listing. The site should be usable on mobile devices: smart phones Would have with 3.5inch or larger screen and tablets (optimized for viewing on mobile devices) 2 The site enable the client, Dean, to show a list of employers and their application documents (similar to jobapplications.com's layout/design) to maintain the website easily. Would have 6
3 Default 30 day expiration for job postings (i.e. Remove Would have visibility of the posting from the website) 4 Job seekers can provide testimonials once they get the job. Could have 2 5 The site should have a sign-up/registration page for Could have employers, which allow them to upload jobs, add profile information. 6 Employers should be able to search the job preference data Could have 2 of job seekers. 7 The site should have a registration page for job seekers. Could have Moreover, non-functional capabilities such as level of service (LOS) need to be implemented for supporting the system. Non-functional capability (NFC) Priority Iteration Security for website users information which must be Would have 2 private and need to be secured. 2 Maintainability: The system should allow administrator Would have 2 to update new features by using Wordpress. 3 Backup: The system should automatically backup database. Would have 2.2 Capabilities to be Tested All capabilities will be tested in order to ensure the results and qualities of the capabilities. Each capability is developed and tested in the same iteration. Table 2: Iteration Test Plan Capability requirement (CR) Description Iteration The website have a login page The login page can identify the type of authorized users which are job seekers, employers, and administrator correctly. 2 Google AdSense advertisement from current website should maintain as they are Tracking Google AdSense by using SysSense Google Adsense Monitor 3 The website should maintain links to other job-related sites as shown on current website. 4 The site should allow users to subscribe or unsubscribe from email notifications (for all job postings). Having webpage and database used for management links The site provides an option for users to subscribe to receive email notification. For canceling subscription, the users will login to their profiles and then inactivate email notification. 7
5 The site should display employers or organizations logos. Employers' or organizations' logos will be shown at the first page. 6 The UI should allow the user to easily Job search need to be flexible for search for jobs. Jobs should be sorted getting input from the users and into categories. All the categories should should have drop-down menu to not be there in the front page, and it is select the job category and location. possible to have multiple categories for one job. 7 Simple and intuitive user interface The user interface should be simple and intuitive like Microsoft word or excel. This capability can be used the previous prototypes to follow and reduce the risks. 8 Employers have the ability to post jobs The site allows the employers to on the site. 9 The main page should resemble the current site and contain a list of general job postings and announcements. 0 Key word search is able to search on any match in the job listing and then the results could pop-up any references in the job listing. The site should be usable on mobile devices: smart phones with 3.5inch or larger screen and tablets (optimized for viewing on mobile devices) 2 The site enable the client, Dean, to show a list of employers and their application documents (similar to jobapplications.com's layout/design) to maintain the website easily. 3 Default 30 day expiration for job postings (i.e. Remove visibility of the posting from the website) 4 Job seekers can provide testimonials once they get the job. 5 The site should have a signup/registration page for employers, which allow them to upload jobs, add profile information. 6 Employers should be able to search the job preference data of job seekers. login to their page and post the job. The proposed system is designed based on the current site and features. The site requires having algorithms to detect and report of results from key word search. The site should design for displaying and using on mobile device, which consume less processing power and having small screen. This capability will be shown at the first page by showing employer's logo, job description, and link to job application document. Adding default expiration for each job posting allow the job posting to show on or remove from the site. When job seeker login to the system, the site provide option for submitting testimonials. The site has the option for the employers to sign up and register in every page. After the users are in employer role, they can upload and post the jobs. After employers login, they can use job candidate search function. 2 2 2 8
7 The site should have a registration page for job seekers. The site has the option for the job seekers to register in every page. Moreover, non-functional capabilities such as level of service (LOS) are important and need to be tested. Non-functional capability (NFC) Description Iteration Security for website users information Website users information is 2 which must be private and need to be secured. private and need to be secured by encrypting the password 2 Maintainability The system should allow the 2 administrator to update new features by using Wordpress. 3 Backup The system should automatically backup database. 2.3 Capabilities not to be tested All capabilities listed above will be tested and fix defects after finishing development. 2. CCD Preparation Plans 2. CCD Stakeholders All stakeholders who will be involved in Core Capability Drive-through are summarized as followed. Table 3: CCD Stakeholders Stakeholder name Role Dean L. Jones Client/ Maintainer 2 Kandarp Nyati Developer 3 Bharat Shugani Developer 4 Thammanoon Kawinfruangfukul Developer 5 Tanya Gautam Developer/Tester 6 Fei Li Tester 7 Mark Villanueva IIV&V 8 Ying Li Tester 9
2.2 CCD usage scenarios Capabilities shown in table 4 will be demonstrated in CCD. Table 4: CCD usage scenarios Capability Description The website have a login page. input user and password. 2. press login button 2 Google AdSense advertisement from current website should maintain as they are 3 The website should maintain links to other job-related sites as shown on current website. 4 The site should allow users to subscribe or unsubscribe from email notifications (for all job postings). Using SysSense Google Adsense monitors and tracks Google AdSense.. log in to the website as administrator role 2. go to link menu to add/update/delete links Subscription. click to job alert 2. register email address to enable the email notification Cancel subscription. log in as the job seeker 2. press deactivated button in Job Alert area. 5 The site should display employers or organizations logos. Employers' or organizations' logos will be shown at the first page. 6 The UI should allow the user to easily search for jobs. Jobs should be sorted into categories. All the categories should not be there in the front page, and it is possible to have multiple categories for. input job title or company name 2. select job category at drop-down job function menu 3. select job location at drop-down location menu one job. 7 Simple and intuitive user interface All stakeholders can use easily without needed many guidelines. 8 Employers have the ability to post jobs on the site. The site allows the employers to login to their page and post the job. 9 The main page should resemble the current site and contain a list of general job postings and announcements.. go the first page of the site 2. view job postings or announcements 0 The site should be usable on mobile devices: smart phones with 3.5inch or larger screen and tablets (optimized for viewing on mobile devices) Using mobile devices such as iphone go to the site. 0
The site enable the client, Dean, to show a list of employers and their application documents (similar to jobapplications.com's layout/design) to maintain the website easily. 2 Default 30 day expiration for job postings (i.e. Remove visibility of the posting from the website) 3 The site should have a signup/registration page for employers, which allow them to upload jobs, add profile information. 4 The site should have a registration page for job seekers. This capability will be shown at the first page by showing employer's logo, job description, and link to job application document.. log in as employer or administrator 2. click add more job 3. add new job 4. view the expiration of new job posting Sign up for employers. click login link 2. input user and password. 3. press login button Registration for employers. click register link 2. fill in required information 3. select employer application 4. press register button Upload jobs and Add profile information. Log in the system as employer 2. Click on add more jobs/edit at Employer information. click register link 2. fill in required information 3. select job seeker application 4. press register button 2.3 CCD preparation plans. Implement and test all capabilities in the first iteration, using both informal unit testing and formal testing with test plan by Testers 2. Prepare test data on the development server for using in the CCD session This data includes sample job postings, test user accounts for employer and job seekers, and anything else that would mimic everyday usage. 3. Prepare user manual and feedback form for all participants 4. In the CCD session, the team introduce and explain the capabilities, test data, and provide all participants with user manual which is on how to use the new system, and feedback form which will focus mainly on the design and usability of the website. 5. While participants are using the system, the team observe and record the result and behavior of the participant. 6. Gather the feedback form
2.4 CCD preparation site and dry run Before performing the CCD session, the team will setup the system with test data to the setting environment by connecting the server and client devices (such as a computer or mobile device) via Wireless connection. In CCD session, the team will present and demonstrate all capabilities in the first iteration of the project and then give the user manual to a participant. Participants test the proposed system following the user manual. After CCD session, the participant give feedback by filling in the feedback form. 2.5 Feedback form Feedback form should include at least entities shown below Content Description No Document number Time Document time Capability Which capability will be tested Description Detail and guideline for testing Reliability Reliability of module in scale of 0-0 Performance Performance of module in scale of 0-0 Satisfaction Satisfaction of module in scale of 0-0 Overall The overall result of testing in scale of 0-0 Comment Suggestion or comment added Signature Signature of the participant Date Date Note 0 for the lowest score and 0 for the highest score 2.6 CCD risk management plans Unrealistic schedule Risk Risk description Risk management plan Underestimate time for developing and testing some capabilities lead to be not able to finish all capabilities in the first iteration Requirement mismatch The team and client may misunderstand the concept of the requirements, so some user interfaces may not easy to use or some capabilities cannot perform properly. Prioritize the capabilities according to business value, detail of implementation, and risks. 2. Implement and test the higher prioritized requirements. If there is not enough time to finish all capabilities, the rest of capabilities will be implemented in next iteration. Buy information by implementing prototypes and getting feedback from the client 2