sabrieker/swe-573

Software Development Practice Repository

swe-573's Issues

Work Event Frontend Development

The work events ,which are managed by Admin users, should be visible to all users. And they should apply for available slots.

ER Diagram Preparation

According to Requirement Specification Document, required Entities should be addressed via Entity Diagram which will be used at Implementation phase.

Unit Testing

During the implementation phase , Test Driven Methodology(TDD) will be used and all required Unit Tests should be implemented.

Member Management Development

In the Admin Module, admin user should manage member details.

• Manage member registration: With approval or creation member user shall have an id number. And a notification mail should be sent to member e-mail address.

High Level Design

High Level Design should be defined with Design Document which will be used at Implementation phase.

Producer Detail Development

In Kiosk Module, for sales functionality Producer Details should be provided to user. Required details of the Producer should be shown for Salesperson members.

• Name : It can be individuals or groups (i.e. other cooperatives)
• Description : general information about producer.
• Location : Free text area with 255 character. City and town should be given.
• Photos : Photos of producer/workplace/farm.

Sales Function Development

For Kiosk module, sales functionality should be prepared.

• Member user: should be selected from list. If it is public user, it should be blank.
• Items: Salesperson should select items from Product list, identify quantity(kilogram,count,etc.) and add to the cart.
• Calculate: when salesperson hits calculate action, system should show total price of the shopping cart.
• Finalize : After salesperson receive money as cash, end of the shopping session salesperson finalize the session. And sold shopping cart is added to Members shopping carts list if it is not public user.

Template Project Preparation

Base project configuration should be done. #3

Category Management Development

Admin user can create,update,delete Categories
Category will have Name property.

Member Profile Development

Member users should manage their profile details after authentication.
Also according to privileges Profile Details can be seen by all users.

Software Requirement Documentation

Requirement Analysis should be done with stakeholders. And Software Specification Document should be prepared for Design phase.

Framework Identification

According to Design Document, required third party frameworks and their versions should be identified. #3

Work Event Management Development

Admin user will Manage work events. Work events will have;

• Name : Name of the event.
• Description : Details of the event.
• Is Regular: Work events are , by default, regular events.
• Status: If an application is made for the work slot, it should be 'Applied'.If there is no application, it should be 'Open' status.
• Time : Start and End date,time information.
• Attendants : who applied for this work.

User Acceptance Testing

At the each milestone ( Milestone 4 to Milestone 7) a brief Acceptance Testing will be done with stakeholder.

Event Frontend Development

In the website, Events should be visible to users.
Authenticated Member users should apply the events which is available.
Member users who attended the event should create comments.

Announcement Frontend Development

Announcements should be visible at website for all users.

Comment Frontend Development

In the website, member users should be able to comment for;

• Products
• Producers
• Events

And all comments should be visible to all users.

Product Detail Management Development

Create, update, delete Product Details.

Database Implementation

All entities should be created in a Mysql database according to ER Diagram which is prepared at Design phase. #2

Product Detail Frontend Development

In the website, Products will be shown to all users.

Member Detail Development

Every member will have their own profile information related with their purchases.

Members should be defined;

• Member Id: System generated unique id per member.
• E-mail : BOUN mail address of the member
• Name,Surname: Name-Surname of the user.
• Events : Members can create comments for Products, Producers, Events.
• Profile Photo : Member can upload photo for profile.
• Birthday : Birthday of the member
• Description : A brief description of the member .
• Privacy : Member can restrict the profile details which can be seen by public, members and nobody.

Producer Frontend Development

In the website, all the details of the Producer should be visible for users.

• Name : It can be individuals or groups (i.e. other cooperatives)
• Description : general information about producer.
• Location : Free text area with 255 character. City and town should be given.
• Photos : Photos of producer/workplace/farm.

Announcement Management Development

Admin user will manage Announcements. Announcement will have;

• ** Announcement : ** A brief detail of the announce.
• * Start/End Time :* Announcement will be available for a valid time period if required.

Reporting Function (Sales) Development

Required reports defined for Sales functionality should be defined.

Event Management Development

Admin user will manage Events. Events will have;

• Name : Name of the event.
• Description : Details of the event.
• Time : Start and End date,time information.
• Attendants : Member users who applied for this event.
• Photos : Manager users and attendant Members can upload photos of trip event.
• Comments : Members can state comments for event. And these comments only available for member users.

Product Detail Development

In Kiosk Module, for sales functionality Product Details should be provided to user. Required details of the Product should be shown for Salesperson members.

• Name : Name of the product.
• Stock : Amount of the product, will be provided by manager user. Can be view by other users.
• Category : Which category it belongs.
• Quantity : Products can may be based on weight, size, or quantity. It should be identified by manager user and view by other users.
• Price: Manager user will identify the price of the product for public and member users. They can specify specific price or percentage for member users.
• Producer : Producer Name and Location of the product should be shown and linked to Producer page
• Description : General information about the product.
• Rate : Average rate of the product given by member users who bought the product. If it has not rated, it should be stated as 'not rated yet'. And viewable by all type of users.
• Comments: comments shared by member users via free text area. It should be availabe for public users for view. It can not be modified after submit.
• Photo : Photo of the product.
• Specific Properties : Like Organic, Free range etc.

Producer Management Development

Admin user will manage producers details.