- s you already know, at the end of CS 700, you should have a had a complete system design of a project…and now that some time has passed, you may have thought about changes that you want to make to the project…or you might think that you want to do a completely different project!…
For your next assignment, we need to make sure our project is “up to date”…
Using your Project Charter from last semester as a base, update your charter to include any changes you would like to make to your project…you should also update the tools and resources that you plan on using…your “updated” proposal should contain details about the functionality of your project and the tools to be utilized…
You should also include a one to two page summary of the changes you want to make…
Of course, if you make changes to your Charter, that means there are potential changes to your Project Plan, Gantt Chart, and Budget…Review your changes and update your project plan, Gantt Chart, and budget accordingly…
Remember, the plan must be a DETAILED plan, showed all major tasks and subtasks…make sure you maintain ORIGINAL, REVISED, and ACTUAL Start and End Dates…MS-Project is probably the best software for this, as it contains many templates that you can work from…but there are others such as Smartsheet and MS-Visio…any of these is fine…
When you submit your project plans, please submit both the ORIGINAL document AND a PDF or SCREENSHOT of the plan…this way I can review the plan if I am having difficulties with the original…
I will review all updates, and either approve them or reject them with explanations…if I feel there are major issues with your revisions, I will reach out to you via email to schedule some time to review and discuss…What if you do not want to make any changes?…that is fine also…just tell me that…but keep in mind…your final product must match the Project Charter…so no major changes can be made without the Project Sponsor’s approval…
Please do not forget to submit your status EVERY WEEK…there is a separate folder for your status…
2
Table of Contents
Project Scoping Document 2
Project Authorization 2
Project Sponsor Approval of Scope Statement 2
Gantt Chart 3
Project Plan 4
Project Budget 4
Data Flow Diagram with Use Cases 5
Context DFD 5
Level 0 DFD 6
Level 1 DFD 7
User Stories 7
Network Diagram 11
Security Measures 11
E-R Diagram 12
Screen Shots 15
Screen Map 15
Screen Design 16
Web View 16
Mobile View 19
Project Scoping Document
Project Authorization
This section outlines who has the power to approve the project’s scope statement, grant project amendments, and accept project deliverables; this power may vary from project to project; if known, the person’s name should appear after their title.
The Scope Statement will be approved by
• Project Manager: Santhosh Kumar Dullapally Srinivas
• Project Owner: Santhosh & co Inc.
• Project Sponsor
: Oluwole Omole-Ohonsi
Project deliverables will be approved/accepted by
• New York Supermarket Associations
• Project Sponsor
• Key Stakeholders
Project Sponsor Approval of Scope Statement
The goal of this document is to act as a vehicle for recording the project’s planning efforts. Before major resources are committed and costs are incurred, it is used to obtain a satisfactory level of mutual agreement between the project manager, project sponsors, and all impacted users on the objectives and scope of the project.
This section lists the scope statement’s approvers and the version of the scope document they approved. No matter how many versions there are, you should keep a history of version signoffs.
The content in this document has been reviewed and approved according to the signatures below.
REVISION ID
REVIEWR NAME
REVIEWER ROLE
APPROVED DATE
REVEG – 0001
Review and approve
Gantt Chart
Project Plan
Stage 1. Developing a project Idea / Develop business case / Create Project Charter
Stage 2. Developing Scope Documentation with Project requirements specifications /
Product characteristics and requirements, product deliverables.
Stage 3. PROJECT PLAN / GANTT CHART / BUDGET approval – 8th October
Stage 4. Concepts are required to be considered.
Stage 5. Finalizing design patterns is needed.
Stage 6. Creation of data flow diagrams and UML diagrams
Stage 7. UML / DFD / User stories through wireframe
Stage 8. Database development
Stage 9. Development of user interfaces for each module
Stage 10. Development of UI and database components.
Stage 11. Building inter-module connections
Stage 12. Progress in module-decomposition
Stage 13. Evaluating the program design n
Stage 14. Tracking system design
Stage 15. Installation on local systems
Project Budget
· Costs, Direct and Indirect
· Explicit costs
· Indirect expenses
· Capital expenses
· Operation expenses
· Cost of Deliverables/Management
· Cost of Project Deliverables
· Cost of Project Management
Data Flow Diagram with Use Cases
Context DFD
This is Context DFD of online vegetable supermarket, it’s a basic overview of the whole online vegetable supermarket or the process being analyzed or modeled. It’s designed to be at a glance view of payment, stock and delivery showing the system as a single high-level process, with its external entities of Customer, Administrator and Seller. It should be easily understood by a wide audience in zero level DFD of online vegetable supermarket.
Level 0 DFD
Level 0 DFD of online vegetable supermarket shows how the system is divided into sub-system processes, each of which deals with one or more data flow to or form an external agent and which together provide all of the functionality of the online vegetable supermarket system a whole. It also identifies internal data stores of customer, orders, payments, products that must be present in order in the online vegetable supermarket to do its job and show the flow of data between the various parts of vegetables, stock, delivery, payment of the system.
Level 1 DFD
Level 1 DFD then goes one step deeper into the part of level 0 of online vegetable supermarket. It may require more functionality of vegetable store to reach necessary level of details about the online vegetable supermarket functioning. Level 0 DFD of online vegetable supermarket shows how the system divided into sub-system. The Level 1 DFD contains more details of updating cart, processing orders and payments.
User Stories
The user’s product journey is divided into several phases. Additionally, if there is any friction along the way, you risk permanently losing the client.
User stories are useful in this situation. They are a crucial component of the agile process and by placing oneself in the user’s position, they aid in understanding their expectations.
From the moment they visit your website for the first time to the point when they become devoted clients—will help you better understand their demands. In order to draw in and keep consumers, you can identify features and solutions for each phase by creating user stories.
Step 1: Searching for Solutions
Users go online for potential solutions to the problems and difficulties they typically face throughout the discovery phase. Additionally, they are contrasting your product with several platforms to see which best suits their requirements. At this point, writing user stories helps you decide which features to include in your product and how to display them online.
User Story: Activities connected with inventory management so I can free up my schedule and concentrate on more important things. I’m an E Commerce business owner.”
As a project manager at a big organization, I need a platform with reporting capabilities and the ability to delegate tasks so I can monitor the development of my remote team more effectively.
I need a payment solution with cheap transaction fees that enables me to charge businesses as a freelancer that works with clients outside of my nation in order to stop losing money on each assignment I finish.
Step 2: Registering & Creating an Account
The user has a few goals and expectations in mind as they prepare to sign up and use your product for the first time, which you must address beforehand. These frequently concern integrations, security, and welcoming users to the platform
.
User Story: In order to avoid having to manually add all of my products later, as the owner of an E Commerce company, I want to effortlessly connect my store with the inventory management platform after registration.
“As a project manager, I want to invite other team members to this project management platform so they can help me review it and see if it makes them more productive,” the project manager said.
As a freelancer, I would like the option to add two-step verification to the registration process to increase login security and ensure that only I have access to my money and invoices.
Step 3: Purchasing Your Product
There must be no friction involved in the purchase process for users to convert into paying customers. You’ll be left with empty shopping carts and missed opportunities otherwise. These problems are identified in user stories beforehand so that the product experience may address them.
User Story:
In order to know when to make my final decision, I want to be reminded how many days are left in my free trial of the inventory management application as the owner of an e Commerce firm.
“I need a specific price plan because I oversee numerous individuals in several departments at once and have complex needs,” a project manager claims.
As a freelancer, I want to have a variety of payment options (PayPal, credit card, bank transfer, etc.) so I may select the one that works best for me
.
Step 4: On boarding
Your user retention could be made or broken during the onboarding process. At this point, the objective is to get customers up and running as soon as possible and to point them toward the aspects that are most crucial to them.
User Story:
I want to be able to take a product tour of the inventory management solution as an owner of an eCommerce firm so that I can fully grasp its main advantages.
In order for me to recognize the value that the product has to provide right away, I want to create and assign my first job as soon as I can (within the first 10 minutes).
“As a freelancer, I want to first make a sample invoice to have a sense of what the procedure would be like when billing clients and getting paid.”
Step 5: Retaining Users
The success of your product hinges on keeping clients over the long term. A high retention rate is evidence that your product is addressing the needs of your target market in addition to increasing income.
User Story:
As the owner of an eCommerce company, I need an inventory management system that will enable me to scale, so I can prepare my shop for long-term growth.”
“I want access to a knowledge base with tools like webinars to better understand how my team can make the most of the project management platform,” a project manager says.
“As a freelancer, I want my invoice/payment platform to offer me weekly information on complicated accounting procedures (including budgeting, cash flow, payment safety, and more), so I can gradually learn to handle my invoicing better.”
Network Diagram
· Customer
s are connected to the internet and access the website.
· The requests go through the firewall and connects to the server.
· The customer care team and admin team are connected to the intranet which is connected to the router, switch and then to the servers.
· A firewall is connected to monitor and control incoming and outgoing network traffic based on predetermined security rules
· Customer care team handles the communication from the customers and provide assistance.
Security Measures
• Firewall: A firewall is a network security system that monitors and controls incoming and outgoing network traffic based on predetermined security rules.
• Intrusion Detection System (IDS): An IDS is a system that monitors a network or system for malicious activity or policy violations.
• Vulnerability Scanning: Vulnerability scanning is the process of identifying and assessing weaknesses in an organization’s information systems.
• Multi-Factor Authentication: Multi-factor authentication (MFA) is a security system that requires multiple forms of authentication, such as a password and a security token, to verify a user’s identity.
• Encryption: Encryption is the process of transforming plaintext into ciphertext in order to protect data from unauthorized access.
• Data Loss Prevention (DLP): Data loss prevention (DLP) is a security strategy that monitors, detects, and prevents the unauthorized transmission of sensitive information.
• Anti-Malware: Anti-malware is a type of software that is designed to detect and remove malicious software, such as viruses, Trojans, and worms, from a computer system.
E-R Diagram
Step 1: Identify all the entity sets related to your database. The entity sets for an online vegetable supermarket are:
· Website or Mobile Application
· Customer
· Admin
· Product
· Login/ Registration
· Shopping Cart
First of all, we need to start with the Mobile Application or website. This shows that the system is based on the software, and the main bridge between the customer and the store is the website or application.
Step 2: Now, we need to assign attributes to each of these entities like those given below:
·
Customer
Attributes: CustomerID, FirstName, LastName, Address, City, State, Zip, Mobile,Email, LoginID.
·
Roles
Attributes: RoleID, RoleName, Description
·
Vegetables/Products
Attributes: Vegetable/ProductID, StockID, Name, Type, Description, Weight, Price
·
Stocks
Attributes: StockID, StockItems, StockNumber, StockType, Description
·
Login/ Registration
Attributes: LoginID, RoleID, Username, Password
·
Orders
Attributes: OrderID, CustomerID, OrderDate, ShippingAddress, ShippingCity, ShippingState, Zip, VegetableID, Quantity, TotalPrice.
·
Payment
Attributes: PaymentID, BillID, OrderID, CustomerID, DateofPayment, Amount, PaymentMethod, PayerFirstName, PayerLastName, CardNumber, CardType, Expiry, BankName, AccountNumber, RoutingNumber.
·
Bill
Attributes: BillID, BillNumber, PaymentID, BillReceipt, Description.
Customers will need to register and log in first in order to purchase veggies. They can select the veggies online and put them in the shopping cart. The shopping cart will identify the product and its price immediately. An admin needs to be on the other end, ensuring the transaction goes smooth and there are no possible bugs. The admin can also offer support when needed and add new products or remove any old ones.
Step 3: Identify the key attributes. The key attribute is one specific attribute that uniquely identifies one entity from another in an entity set.
The key attribute for each of these will be:
· Vegetables/Product: Vegetable/Product ID
· Customer: Customer ID
· Login: Login ID
· Roles: Role ID
· Orders: Order ID
· Payment: Payment ID
· Bill: Bill ID
· Stocks: Stock ID
Screen Shots
Screen Map
Screen Design
Web View
Home Page: Home page of the website
Veggies: Click Veggies link
Cart page: Click cart to view the veggies added
About page: Click About page to view
Mobile View
Home screen:
Login/Sign Up page:
Existing User:
New User Account creation:
image3
image4
image5
image6
image7
image8
image9
image10
image11
image12
image110
image13
image130
image14
image15
image16
image17
image18
image19
image20
image21
image1
image2
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
