Dynamic Modeling, Screen Design andTest Plan

Assignment Two
Table of Contents

Extract 2
Introduction 2
Post Job Vacancies 3
Extended Use Case 4
Activity Diagram 5

System Sequence Diagram 6

Track the application 6

Screen Design 10

Test Plan 11

Reference 13

1|Page
Extract
The assignment covers the model of behavior of the system/ subsystem for the two most
complex use cases from the subsystem that I had chosen in former assignment. Two UML
illustration extended use case descriptions, test plan and defenses developed from invision are
handed to make clear analysis of the given script.

Introduction:
In this assignment, I'm modeling one of the subsystems of Australia post. The subsystem that I’m
working on under Australia post is Reclamation and Graduate programs. I've created a use case
illustration for the susystem in former assignment which is shown below;

2|Page
Among the 10 use cases, I'm choosing 2 most complicated use cases i.e. Post a job vacuities and
Track application. I'm going to explore these two use cases and produce an exertion illustration
and system sequence illustration, extended use case and attach a storyboard created in an
invision and write a test plan for the use cases.

The two most complicated use cases are

1. Post job vacuities

2. Track operation

1. Post Job Vacancies

Australia post has new opening ad and au post staff can post opportunity commercial in their
site. There can be one work commercial or can be different opening accessible. Just an Australia
post staff can post the opportunity. Just specific Australia present staff can go on the site and
make changes. For this they should be inked in. When an opening is free it should be posted on
the site. So staff will fill all the expected set of responsibilities which incorporates work title,
work part, time of agreement, number of individuals required and so on. The framework will
approves the subtleties gave and it will instigate a task number and save the post. Furthermore,
it'll be update in the Au post have choice about the gig ready where the client will get declaration
assuming any new position is posted. So assuming that any client has empowered the work
ready, the framework will shoot declaration to them. I've made expanded use case, effort
representation, framework sequrnce delineation and model in invision to give detail model of the
utilization case.

3|Page
Extended Use case

4|Page
Activity Diagram

5|Page
System Sequence Diagram

Track the application

Use case
Track operation colorful job position are available in Australia post. Once the aspirant applies
for a job, he can track the progress of his operation. Tracking the operation will show where
his process of recruiting has reached. To track the operation first of all the aspirant must have
applied for a job position. It can be one or further position. also once the aspirant applies for a
job he'll have his aspirant id number, word and operation id number which is needed to track
the operation further. Once a aspirant go to the job hiring runner of Au post he will see a
option to track the operation. When the stoner click on that he has to enter the aspirant id and
password. The system will corroborate the word and take to coming runner where the aspirant
need to enter the specific operation id which he wants to track. Since one aspirant can have
multiple operation submitted at a time so he needs to be specific about the application. Once the
id is submitted the system will search if there's any progress in the application. If there's any it

6|Page
will show the result. Otherwise it'll notify the stoner that it isn't been reviewed yet. To give a
brief detail about the functionality of the use case I've created an extended use case, exertion
illustration and system sequence illustration for the use case.

Extended Use Case

7|Page
Activity Diagram

8|Page
System Sequence Diagram

9|Page
Screen Designs

10 | P a g e
Test Plan
The ideal of this test plan is to validate the functionality, usability, and performance of the
accommodation service on Airbnb. compass The test plan will concentrate on testing the
following aspects of the accommodation service Searching for lodgment Viewing
accommodation rosters Booking lodgment stoner profile operation Testing Approach The
testing approach will include homemade testing by QA masterminds to insure thorough content
of all scripts and use cases. Automated testing may be considered for repetitious or
retrogression testing in unborn duplications. Test Environment The test terrain will replicate
the product terrain of Airbnb, including the web and mobile platforms supported by the service.
Test Cases Hunt Functionality corroborate that druggies can search for lodgment by
position, dates, and other pollutants. Validate that hunt results are applicable and directly reflect
the stoner's criteria. Test the performance of hunt functionality under colorful network
conditions and cargo situations. Viewing Accommodation rosters insure that druggies can
view detailed information, including prints, descriptions, amenities, and reviews, for each
accommodation table. corroborate that all information displayed on the table runner is
accurate and over- to- date. Test the responsiveness and usability of the table runner on
different bias and screen sizes. reserving lodgment Validate the booking process from opting
dates to completing payment. Test colorful scripts similar as reserving for single or multiple
guests, applying abatements or promo canons, and canceling bookings. corroborate that
druggies admit evidence emails and announcements after completing a booking. stoner Profile
Management Test the functionality to produce, edit, and cancel stoner biographies. Validate
that druggies can modernize their particular information, payment styles, and communication
preferences. corroborate that changes made to stoner biographies are reflected directly across
the platform. Testing Tools use a combination of homemade testing ways and testing tools
similar as Selenium for web robotization and Appium for mobile robotization. Test Data

11 | P a g e
Prepare a set of test data including valid and invalid inputs for different test scripts similar as
searching for lodgment in different locales, reserving lodgment for colorful dates, and
managing stoner biographies. Test prosecution Execute test cases totally, establishing the
results of each test case including any blights or issues encountered. disfigurement operation
Track and manage blights using a disfigurement tracking system similar as Jira or Bugzilla.
Prioritize blights grounded on inflexibility and impact on the stoner experience. Retrogression
Testing Perform retrogression testing after each release to insure that new updates or changes
don't introduce any retrogressions or break living functionality. Acceptance Criteria Define
acceptance criteria for each test case grounded on the anticipated issues and conditions of the
accommodation service. Exit Criteria Determine exit criteria for the test plan, specifying the
conditions under which testing can be considered complete and the accommodation service can
be supposed ready for deployment. By following this test plan, we can insure thorough testing
of the accommodation service on Airbnb, helping to identify and resolve any issues before
deployment and icing a positive stoner experience for guests.

12 | P a g e
Reference
[1] Roger T. Alexander and Jeff Offutt. Criteria for testing polymorphic relationships. In
Proceedingsofthe 11th International Symposium on Software Reliability Engineering, pages 15–23,
San Jose CA, October 2000. IEEE Computer Society Press.

[2] Paul Ammann and Jeff Offutt. Coverage Criteria for Software Testing. In preparation, 2004.

[3] Paul Ammann, Jeff Offutt, and Liu Ling. Touring prime paths. In preparation, 2004.

[4] Anneliese Andrews, Jeff Offutt, and Roger Alexander. Testing Web applications. Software
and Systems Modeling, 2004. To appear.

[5] Michael Benedikt, Juliana Freire, and Patrice Godefroid. Veriweb: Automatically testing
dynamic Web sites. In Proceedingsof11thInternationalWorldWideWebConference(WWW’2002), Honolulu,
HI, May 2002.

[6] Stefano Ceri, Piero Fraternali, and Aldo Bongio. Web modeling language (WebML): A
modeling language for designing Web sites. In WWW9 Conference, Amsterdam, Netherlands,
May 2000.

[7] Stefano Ceri, Piero Fraternali, Aldo Bongio, Marco Brambilla, Sara Comai, and Maristella
Matera.Designing Data-Intensive Web Applications. Morgan Kaufmann, December 2002.
Information available online at: http://webml.elet.polimi.it/webml/book.html.

[8] M. H. Chen and M. H. Kao. Testing object-oriented programs - An integrated approach. In

Proceedings of the Tenth International Symposium on Software Reliability Engineering, pages 73–83,
Boca Raton,FL, November 1999. IEEE Computer Society Press.

[9] Sebastian Elbaum, Srikanth Karre, and Gregg Rothermel. Improving Web application testing
with user session data. In Proceedingsofthe25thInternationalConferenceonSoftwareEngineering, pages 49–59,
Portland, Oregon, May 2003. IEEE Computer Society Press.

[10] S. Feldman. Electronic marketplaces. IEEE Internet Computing, pages 93–95, 2000.

[11] P. Frankl and E. J. Weyuker. An applicable family of data flow testing criteria. IEEE
Transactions on Software Engineering, 14(10):1483–1498, October 1988.

[12] Russell Gold. Httpunit home. online: SourceForge, 2003. http://httpunit.sourceforge.net/,

last access February 2004.

[13] M. J. Harrold and Gregg Rothermel. Performing data flow testing on classes. In
Symposium on Foun-dations of Software Engineering, pages 154–163, New Orleans, LA,
December 1994. ACM SIGSOFT.

13 | P a g e
[14] M. J. Harrold and M. L. Soffa. Selecting data flow integration testing. IEEE Software,
8(2):58–65, March 1991.

[15] Erik Hatcher and Steve Loughran. Java Development with Ant. Manning Publications,
August 2002.

[16] Rick Hower. Web site test tools and site management tools, 2002.
www.softwareqatest.com/qatweb1.html, last access February 2004.

[17] Xiaoping Jia and Hongming Liu. Rigorous and automatic testing of Web applications. In
6th IASTED International Conference on Software Engineering and Applications (SEA 2002),
pages 280–285, Cam-bridge, MA, November 2002.

[18] Zhenyi Jin and Jeff Offutt. Coupling-based criteria for integration testing. Journal of
Software Testing,Verification, and Reliability, 8(3):133–154, September 1998.

[19] D. Kung, C. H. Liu, and P. Hsia. An object-oriented Web test model for testing Web
applications. In Proc. of IEEE 24th Annual International Computer Software and Application
Conference (COMPSAC2000), Taipei, Taiwan, October 2000.

[20] Suet Chun Lee and Jeff Offutt. Generating test cases for XML-based Web component
interactions using mutation analysis. In Proceedingsofthe12thInternationalSymposiumonSoftwareReliability
Engineering, pages 200–209, Hong Kong China, November 2001. IEEE Computer Society
Press.

[21] C. H. Liu, D. Kung, P. Hsia, and C. T. Hsu. Structure testing of Web applications. In
Proceedingsof the 11th Annual International Symposium on Software Reliability Engineering, pages
84–96, San Jose CA, October 2000

14 | P a g e