Case Study

There are three main users of the site namely, user selling their clothes, users buying clothes, and administrators of the system. Below is a description on how users interact or benefit from the site:

User selling clothes:

Only users the backend web portal for this.

Account creation, username will be their email ID.

Enter details of the clothes they want to be sold. The form asks for all the pertinent information about the clothes: its category, type, size, its general condition, and the asking price. This will be done in backend portal.

Rate the clothes regarding its use how helpful it was to the class.

Set the parameters necessary to allow bidding if that option is selected.

The system maintains an index of all clothes in the system so buyers can use the search engine to search for clothes.

The search engine allows searches by type, seller, category, and keyword.

User buying clothes:

Only uses the mobile application for this.

Account creation, username will be their email ID. If they decide to buy anything they have to register an account with a credit card to pay for the clothes.

Search the site for clothes they want to buy. This person can search by type, seller, category, and keyword.

Will be given a list of user(s) selling the clothes and information on how to contact them or buyer can bid for the clothes if the seller has that option turned on.

If the clothes are not available, they can log a request for the clothes in case someone does end up selling the clothes, they will then be notified.

Administrator:

Maintain the web portal and mobile app.

Run queries for the request for clothes that are unavailable, if a match is found a notification will be sent to the buyer wanting to buy the clothes.

Note the following:

When a purchase is made, ClothingFashion mobile app sends an e-mail notification to the seller of the clothes about the purchased clothes as well as payment information. It also marks that clothes/items as sold. The app maintains and displays an open order until it receives notice that the clothes has been shipped. After the seller receives notice that a listed clothes has been sold, the seller must notify the buyer via e-mail within 48 hours that the purchase is noted. Shipment of the order must be made within 24 hours after the seller sends the notification e-mail. The seller sends a notification to the buyer and ClothingFashion when the shipment is made.

After receiving the notice of shipment, ClothingFashion maintains and displays the order in a shipped status. At the end of each month, a check is mailed to each seller for the clothes orders that have remained in a shipped status for 30 days. The 30-day waiting period exists to allow the buyer to notify ClothingFashion if the shipment doesnt arrive for some reason or if the clothes isnt in the same condition as advertised.

The ClothingFashion company wants to create mobile app and web portal that is a type of ebusiness exchange that does business entirely on mobile app via the Internet. The company sets a platform for buyers and sellers of used clothes. This project will be a mobile app and web portal that allow users to advertise old or new clothes to other users. This system should also allow a way for users to bid for clothes on sale.

1. Identify and list the System Capabilities and Scope for the case study above(from the SRS document)

1.1. Stakeholders

1.2. Functional Requirements (describe conflicting requirements (if any))

1.3. Non-Functional Requirements (describe conflicting requirements (if any))