Scribd
Upload
6 views

Software PJW

Uploaded by

jenkinsmeck16
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
6 views

Software PJW

Uploaded by

jenkinsmeck16
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
You are on page 1/ 6

SOFTWARE DEVELOPMENT

(ASSIGNMENT)CSD 41.7
Explanation of the Sitemap Structure
Home: The landing page of the website.

About Us: A page that provides information about the company and its mission.

Shop: The main section for browsing products, which includes:

Categories: Different product categories for easy navigation.

Product Listing: Displays products with filter and sort options.

Product Details: Detailed information about each product.

Shopping Cart: Where users can manage selected items before checkout.

Checkout: The process for completing a purchase.

User Account: Section for user registration, login, and account management.

Customer Service: Information for customers, including FAQs and contact details.

Blog: A section for articles, tips, and updates related to the shopping experience.

LINK TO SITEMAP: http://go.bubbl.us/e5e838/b9f8?/HOME


USE CASE DESIGN

User (Customer) Use Cases:

• Register Account: Users can create a new account.

• Log In: Users can log into their accounts.

• Browse Products: Users can view products by categories.

• Search Products: Users can search for specific products.


• View Product Details: Users can see detailed information about a product.

• Add to Cart: Users can add products to their shopping cart.

• Checkout: Users can complete their purchase.

• View Order History: Users can view their past orders.

• Manage Profile: Users can update their personal information and payment
methods.

• Submit Reviews: Users can leave reviews for products.

Worker (Administrator) Use Cases:


• Log In: Administrators can log into the admin panel.

• Manage Products: Administrators can add, edit, or remove products.

• Manage Orders: Administrators can view and process customer orders.

• Manage Users: Administrators can view and manage user accounts.

• View Reports: Administrators can generate reports on sales and user activity.

Developer Use Cases:


• Implement Features: Developers can add new features based on requirements.
(Implement: the process of translating design documentation and specifications
into a working software product)

• Fix Bugs: Developers can address issues reported by users or administrators.

• Maintain System: Developers can perform regular maintenance and updates.


• Monitor Performance: Developers can track web

Requirement

SPIRAL MODEL

The Spiral Model is a way to develop software (or any project) that involves repeating steps in a circular
pattern.

Steps Under the Spiral Process Model

1. Planning Phase

• Objective: Define project scope and gather requirements.


• Activities:

Requirement gathering through user interviews and surveys.

Define the scope of features (user registration, product catalog, etc.).

Identify stakeholders (users, developers, etc.).

Create a project plan with timelines and resources.

2. Risk Analysis Phase

• Objective: Identify and mitigate risks.

• Activities:

Assess technical, market, and operational risks.

Develop mitigation strategies for identified risks.

3. Engineering Phase

• Objective: Design and develop the website.

• Activities:

Create system architecture and database design.

Develop user interface wireframes.

Implement front-end and back-end development.

4. Testing Phase

• Objective: Validate the website's functionality.

• Activities:
Conduct unit, integration, and user acceptance testing.

Perform performance testing

5. Evaluation Phase

• Objective: Review progress and gather feedback.

• Activities:

Conduct review meetings with stakeholders.

Analyze feedback and identify areas for improvement.

You might also like