
System Analysis & Design Project
In this project we create various documents and resources for the company Chefsworld. The parameters for this project have been provided by the professor.
Project Parameters and Guidelines
Bob Stolard is successful entrepreneur who has built and sold many businesses. He is also a cooking enthusiast, as he trained to be a chef at one point in his life. He has now decided to combine his hobby with a new business venture. His new venture is called "ChefsWorld". He is planning to market a community site to chefs around the world where they can exchange their recipes. Bob will make money by charging a monthly subscription fee. He believes that top chefs will want to collaborate on recipes - exclusively with each other. He really believes in this mission and that he can become the first of the kind and a leader.
The site will require chefs to fill out a very thorough application before being approved for the site. There will be a vetting process where an employee from ChefsWorld can approve them as members, or deny them if they don't think they qualify.
Members will be required to submit one recipe a month. If they don't reach that quota, their accounts will be flagged, and the ChefsWorld staff may suspend them from seeing other recipes until they are all caught up posting their own.
Users of the site will be able to search for recipes, comment on them and have discussions on them. They will also be able to rate each other's recipes. The recipes will also contain ingredients
ChefsWorld staff will need the ability to delete comments, recipes, and ratings if they find them inappropriate. There is, of course, a need for the site to take credit card payments.
Bob wants to get this project done quickly - before someone steals his idea. He travels quite a bit and can't always be available to the team. He also has never attempted to build a website and knows very little about how it gets done.
Bob is budget conscience. He wants to keep the budget down to $400,000.
The CEO of this new site,
Bob Stolard will be appearing at our class to get help building a site for this new company. He heard about the great talent in our class and would like to work with us. the CEO believes in this venture and believes that he will get great market share.
Your job as the business analyst (i.e., the assignment for this final project):
1- Create a decomposition diagram of the business.
What are the major areas of this business? how do they break out into processes?
2- Create a BRD
This BRD should follow the same format as the one we did in week three. You don't need to do every single requirement you can think of, but make sure each area of the business is recognized with requirements that can carry through all the way to the use case. For non-functional requirements, think of what the site will need. The BRD should include all elements of the scope document (goals, objectives, risks, constraints, scope items, out of scope items).
3- Create Activity Diagrams
Pick two of the functional areas (EXCEPT ADMIN) and create process flows for them. Choose carefully, as you will be using these down the chain of analysis stages.
4- Create a data model for the two process flows you have created
Create a Crow's feet diagram
5- Create Wireframes for the two processes.
Create wireframes for your processes. You don't have to create every wireframe for a process, just show that you can build an appropriate interface and represent the business.
6- Use case statements
You don't need to do a use case diagram, just the use case statements for the wireframes that you built
Really important:
Your submission should be ONE DOCUMENT with all the different parts combined. It can either be a word document or a PDF. A submission with multiple documents will not be accepted.
Other really important stuff:
Check your submission carefully, as there will be no resubmissions allowed.
The functional areas for the final project are:
-
Registration
-
Payment
-
Recipes
-
Admin
-
Forum
Step 1
Creating a Scope statement
The first part of this project is to understand the company, it's scope, objectives, goals, risks and constraints. We also need to decide what should be included in the scope statement based on the constraints provided. Out of scope consists of those items which will not be included in the initial release as they are not a requirement or a need for this project at the current time.



Step 2
Creating a Decomposition Diagram
A decomposition diagram presents the entire process in brief. In our decomposition diagram we have 5 important functional areas which are:
-
Registration
-
Payments
-
Recipes
-
Admin
-
Forum

Step 3
Creating a Business Requirement Diagram
The Business Requirements Document indicates all the components a business wants to include and achieve. It consists of Functional and Non Functional requirements. Our BRD is based on the 5 functional areas mentioned earlier. I have mentioned the stakeholders involved and the approval for reference purposes.







Creating Activity Diagram
Step 4
Based on the project guidelines mentioned by our professor, we need to pick 2 functional areas out of the 5 mentioned above and create activity diagrams for them.
An activity diagram indicates a detailed process based on the BRD. The numbers mentioned in the diagram reference to the points in the BRD.
I have selected Registration and Payments.
​
1. Registration Activity Diagram - In the registration process, the user first signs up and creates an account by providing basic details such as email id, phone number, password etc. Once the account is created, the user can then fill out an application which will be evaluated by the admin based on which the user will be accepted or rejected from using the site. If the applicant is rejected, he can fill out another application through the same account he created.

2. Payments Activity Diagram - The user first selects the billing address and then moves on to the payment method section. The user has the option of selecting between saved billing address and adding a new address. The user also has the liberty to select between online transfer and Debit/Credit card from which the user can select between saved card and add a new card.

Step 5
Step 6
Step 7
Creating Data Models
Data models represents how the tables are related to one another in a database. We have used the same functional areas we used while creating activity diagrams.
​
1. Registration Data Model

2. Payments Data Model

Creating Wireframes
Wireframes are blueprints that give us a glimpse as to what the final product may look like.​
​
1. Registration Wireframe
​
a. Signup/Creating an Account - The user creates an account with the website

b. Application Process - The user fills out an application in order to access the website

c. Evaluation - The admin evaluates the application filled by the user and accordingly grants or rejects access to the website.

2. Payments

Creating Use Case Statements
Use Case Statements help explain how the system should behave.
​
1. Registration Use Case Statements
​
a. Signup/Creating an Account - The user creates an account with the website


b. Application Process - The user fills out an application in order to access the website


c. Evaluation - The admin evaluates the application filled by the user and accordingly grants or rejects access to the website.

2. Payments

