Web Engineering Design Essay: Improving A Web Site/sub-site And Shortening Its Length To 70 Characters Without Any Extra Information.

Product Roadmap

In this assignment , you have investigated and analyzed a Web site/sub-site, and addressed the issues that need to be improved or re-designed (if required). Consider that your analysis report has been submitted to a board of the company (the owner of the Web site).

After reading your Web site/sub-site analysis report, the board of the company has decided to improve the existing Web site in order to provide better services to its users. You have been assigned to accomplish this job. The outcome of this assignment is therefore continuation of your work from the analysis stage to the design stage on the same Web site/sub-site and then prepare a design report.

This design report must be prepared using Web engineering principles and methodologies. You can use Enterprise Architect as the CASE tool to prepare all your design diagram for content, navigation, function and other models or any other tools.

Your report should contain the following sections:

1. Write the product vision statement
2. Present your product backlog

You have used different modeling artefacts including use case diagram, description, usage scenario, activity diagram, domain analysis and your selected website as a prototype in your assignment-1. If required prepare more mockups, prototypes and modeling diagrams. Then complete following tasks.

1. Decompose your epics and features into sufficient user stories and write those in appropriate format
2. Write acceptance criteria for each of those

• Use planning poker estimate approach to estimate those

1. Use a priority scheme based on ROI

1. Complete your Product backlog. You need to identify 20 user stories by using your initial product backlog in Assignment-1. Each feature needs to be decomposed at least two user stories.

2. Working towards your sprint backlog- Design tasks:

You are required to prepare a product roadmap which has at least three releases. Consider each epic can be released in one release. 

Each release in the roadmap should have clear goal which depends on following factors.

1. Market map (target customer, business value),
2. Market event,
3. Architecture map,
4. Feature/benefit map.

1. UML Profile: You are required to develop an UML profile. In the profile, you needto create stereotypes for your own web application project. You can create following types of stereotypes:

1. Content classes

This can be different types of content (e.g. clothing product one type, book product another type etc.).

1. b) Navigation classes

This can be different types (e.g. menu, search, index, home, any other navigation node, navigation link and process link)

1. c) Process classes

The functions required to complete the users’ goals, these can be 1) user observable function 2) Function which are required for internal processing of classes -- (class collaboration and manipulation of attributes) 3) integrate application functions (i.e., business processes) which will be needed into the navigation structure as part of user actions.

1. Design Class Diagrams using your UML profile
2. Prepare a content class diagram using UML profile and data tree that you prepared in your assignment-1. Include contents related to one of the epics in your product backlog.
3. Prepare a process class diagram using UML profile which are required for one of the epics in your product backlog

2. Sequence diagram: Prepare a sequence diagram from a use case description relatedto one of the epic used in (2. B) that you prepared in assignment-1, content and process classes in (2.B)

1. Navigation and functional design:
2. Create navigation views using navigation classes and links (from stereotyped) and user visible functions from your process classes (in your process class diagram) and content classes (from your content class diagram) in order to represent the Navigation semantic units (NSUs). Use your UML profile in your project as a resource for process class diagram and your content class diagram.
3. Prepare a functional design view. Follow the steps of creating views as demonstrated in practical classes and as described in the help documents of Enterprise Architect in order to describe the functional design of your web application. In this case, you need to use Web-Modeling language tool of Enterprise Architect. You need to associate your process classes and navigation classes from navigation design with the corresponding web-modeling classes.

You are required to use principles, techniques and models of n avigation and functional design in this section.

Refer to WAE example models provided in the book: Roger S. Pressman and David Lowe (2009): Web Engineering: A Practitioners Approach. McGraw-Hill, Function design chapter or teaching materials for more details and examples.]

3. Sprint planning and sprint backlog

First, relate your release goal with the product backlog items, assume your team velocity and estimate number of sprints per release. Demonstrate which PBIs are in which release in your product backlog.

Sprint planning: Use a two-part sprint planning scheme

1. Sprint goal: Write the goal of each sprint. Consider each release will require two sprints.

2. Capacity determinations: Determine the capacity of team and describe capacity estimation in detail

Sprint backlog:

3. Prepare detail task breakdown for all feature-PBIs of one of the epics from your product backlog, estimate, and refine your sprint goal if required. Considers all analysis models and design while completing the task breakdown. These are the actual tasks those will be accomplished in each sprint by the scrum members. The tasks describe and indicate more detail for the implementation.

You need to breakdown all user stories of one of the epics from the product backlog. Each user story needs to be decomposed into at least three tasks.

Product Roadmap

In the web application using to booking for rooms. It contains the home page, contact page and login page. The login page contains customer details and booking details. The home page contains the room details. In the customer booking the room through the website (Chiou, Lin and Perng, 2011).

Home Page

Account Page 

Reservation Page 

Booking Page

User Hierarchical Diagram

Use Case Classified by User Hierarchical

Product vision statement

In our website based on travel and tourism. In the web application mainly used to booking the international flights. Our product visions are dedicated work and satisfy the all passenger expectation. We have the world tour package.So, our service depend upon the international flights.

Use case diagram

Use case name: Rom booking

• Use case scenario: Login scenario
• Scenario Description

The User maintain the database. Both are access the login page. But the database page only access by user. The customer create the account for booking the rooms and the database maintain by the user. The customer login the page using username and password. The customer create an account. They enter the first name, last name, gender, and contact no, address, username and password for create an account. The username and password created in particular customer. They are book the room easily through username and password (Choi, Ok and Choi, 2015).

• Primary actor: Customer
  • Pre-conditions: Customer need to login to the website to booking process
• Post conditions:
  • After login the webpage the customer see the rooms details.

Use case name: User

• Use case scenario: Support the customer
• Scenario Description: The customer database maintain by the user. The user can be login the user page and customer page. First the customer login the homepage and they enter their details. The data will be stored the backend database. Every database store the user page. The customer booking for roms. The data stored the user page and user allotted the seats.
• Primary actor: customer
• Pre-conditions: customer needs to login
• Post conditions:
  • The customer login the page for booking.
  • They are given the information and verify the customer information. Finally the user conform the booking.

Activity diagram for customer is shown below.

Domain analysis is illustrated as below.

• The customer create an account for book the rooms.
• The username and password created the particular customer.
• The customer login the page using username and password.
• The data can be stored the user page.
• The customer book the rooms and the information stored the user page. The information can be verified by the user and conform the booking.

Epic - Product	Theme	Story	Priority	Estimation
Admin	Administration	Admin Database The admin maintain the rooms and customer database.	9	1
		Search Rooms The customer search room by price.	5	1
	Simple Search	Search by price The customer price is various from one to another room.	8	1
		Search by location The customer searches the room in available place.	4	1
		Compare Rooms The customer compares the each room by price.	9	2
		Select Date Book the room in particular date.	7	2
		Rooms Details The room details maintain by the admin.
User Management	User Setup	User Database The user has user id and password	5	5
		Booking Rooms Details The booking rooms database maintain by the admin.	9	2
		Booking Conformation The booking conformed by the admin.	6	3
	Payment Setup	Debit or credit card payment The customer pays the amount through the debit or credit card.	9	2
		Payment with PayPal The customer pays the amount with PayPal.	5	3
	Account setup	Account Setup The account details connect to the admin.	5	2
		User Information The user information maintain by the admin.
	Booking Process	Change quantity The customer can be change the quantity of booking.
		Continue Booking The customer changes the details before and after booking.
		Cancel the Booking      The booking cancels by the customer.
		Due for Cancelation The customer pays the due for cancelation.
	Administration setup	Help Desk If the customer have any feedback the they report the feedback to the help desk.
		Customer Service The service provide to the customer.

Market map

Market Event

In the web application using to book the rooms. Most of the people are using social media. So, we are marketing our product through Facebook, twitter and YouTube.

UML Profile

The content classes are listed in below.

• Rooms Booking
• Customer
• Login
• User
• Payment
• Contact
• Booking
• Database

The navigation classes are listed below.

• Home
• Login
• Contact
• Search Rooms
• Select Date

The process class are listed below.

• Rooms Booking Classes – Booking Process
• Customer classes – Create Account
• Login classes - Log on to Travel and tourism website.
• Booking classes - customer add booking, edit booking and cancel booking.
• User Classes – Users are needs to store the booking information using database.
• Database classes – Store Booking data and customer details.

Content Class Diagram

The Content and class diagram is shown below (Chong and Law, 2018).

The process class diagram is illustrated as below.

The sequence diagram is illustrated as below. 

Navigation Design is shown below.

Functional Design is shown below.

Sprint Goal

The sprint Goal is implement the product backlog. In the product backlog define the only outside of the process. But the sprint backlog define the overall process. The sprint backlog depend upon the product backlog.

In the capacity depend the team member work.

Epic - Product	Theme	Story	Priority	Estimation	Status
Admin	Administration	Admin Database The admin maintain the rooms and customer database.	9	1	Sprinting
		Search Rooms The customer search room by price.	5	1	Sprinting
	Simple Search	Search by price The customer price is various from one to another room.	8	1	Sprinting
		Search by location The customer searches the room in available place.	4	1	Sprinting
		Compare Rooms The customer compares the each room by price.	9	2	Groomed
		Select Date Book the room in particular date.	7	2	Groomed
		Rooms Details The room details maintain by the admin.	9	5	Groomed
User Management	User Setup	User Database The user has user id and password	5	5	Sprinting
		Booking Rooms Details The booking rooms database maintain by the admin.	9	2	Sprinting
		Booking Conformation The booking conformed by the admin.	6	3	Sprinting
	Payment Setup	Debit or credit card payment The customer pays the amount through the debit or credit card.	9	2	Sprinting
		Payment with PayPal The customer pays the amount with PayPal.	5	3	Groomed
	Account setup	Account Setup The account details connect to the admin.	5	2	Groomed
		User Information The user information maintain by the admin.	5	3	Sprinting
	Booking Process	Change quantity The customer can be change the quantity of booking.	9	2	Sprinting
		Continue Booking The customer changes the details before and after booking.	5	2	Groomed
		Cancel the Booking      The booking cancels by the customer.	4	3	Groomed
		Due for Cancelation The customer pays the due for cancelation.	9	2	Sprinting
	Administration setup	Help Desk If the customer has any feedback then they report the feedback to the help desk.	5	3	Sprinting
		Customer Service The service provide to the customer.	5	1	Groomed

Conclusion

This process successfully created the website for booking the rooms and this website contains the home page, contact page and login page. The login page contains customer details and booking details. In the customer booking the rooms through the website.

References

Chiou, W., Lin, C. and Perng, C. (2011). A strategic website evaluation of online travel agencies. Tourism Management, 32(6), pp.1463-1473.

Choi, J., Ok, C. and Choi, S. (2015). Outcomes of Destination Marketing Organization Website Navigation: The Role of Telepresence. Journal of Travel & Tourism Marketing, 33(1), pp.46-62.

Chong, S. and Law, R. (2018). Review of studies on airline website evaluation. Journal of Travel & Tourism Marketing, pp.1-16.