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.