Project Plan, Team Charter Inventory Management System

COMP3059 – Capstone Project I School of Computer Technology

Page 1 of 11

Project Plan, Team Charter

Inventory Management System

Industry Partner N/A

Primary Instructor Anjana Shah

Team Member Rajat Rajat

Team Member Nirav Sorathia

Team Member Muskan Batra

Team Member Gourav Gourav

Document Revision History

Revision # Date 1 October 2,2019 2 October 3,2019


Page 2 of 11

Table of Contents

1 Executive Summary ......................................................................................................................... 3

2 Project Approvers, Reviews and Distribution List ............................................................................. 3

3 Scope ........................................................................................................................................... 3-4

4 Deliverables..................................................................................................................................... 4

5 Assumptions .................................................................................................................................... 4

6 Dependencies .................................................................................................................................. 5

7 Risk Management ............................................................................................................................ 5

8 Communication ............................................................................................................................... 5

8.1 Reportings ........................................................................................................................ 5

8.2 Meetings ....................................................................................................................... 5-6

9 Task Listing (WBS- Work Breakdown Structure)……………………………………………………………..6 10 Gantt Chart .................................................................................................................................. 6-7

11 Milestones....................................................................................................................................... 7

12 RAM – Responsibility Assignment Matrix ............................................ Error! Bookmark not defined.

13 Approval ............................................................................................. Error! Bookmark not defined.


Page 3 of 11

1. Executive Summary

The following describes the project to be executed.

Objective To create an application that meets the needs and desires

of the user to increase cost efficiency as well as minimize

inventory investment.

This app will have all the desired features an individual

want in his company’s inventory management software.

The app will be focusing on the doing on all the

inventory procedures like adding the items, ordering as

well as decrement of items.

The app will make user less reliable on third party so that

the company can manage their data by themselves.

The app will make easy for the user to know the profits

and loss of the sales along with the details of particular

item.

Corporate Goals

Addressed To easily add and delete an item in the app.

To know abut the remaining and the sold stock. To receive the notifications about the short on items. To detect the markup in the sales according to the items. Ability to reorder the items in the stock.

Planned Start Date 11th September,2019

Planned End Date 27th March,2020

2. Project Approvers, Reviews and Distribution List

Approvers, reviewers and distribution list

Project Role Name E-mail Date

Project Manager Nirav Sorathia [email protected] 10/07/2019

Front End Developer Muskan Batra [email protected] 10/07/2019

Programmer Rajat Rajat [email protected] 10/07/2019

Delivery Manager Gourav Gourav [email protected] 10/07/2019

3. Scope

Define the sum total of all of its products and their requirements or features.

In Scope Out of Scope

Point of sales third party dependency

Effectiveness towards running store Customers


Page 4 of 11

Maintaining minimum amount of quantity

Quality of products

structured database

planning for future stock

change in inventory system

4. Deliverables

This project will deliver the following.

Deliverable Description

Check inventory items Manager and employees of the store would

be able to see the items in the inventory.

Add items in inventory Manager will be able to add the items in

the inventory by himself

Remove/sell items Manager can remove the item from the

inventory which he does not want in his

store and the system will automatically

remove an item from the inventory once

the item gets sold.

Order items Manager would be able to order the items

through our system. He will also receive

notifications about the items which would

about to be end soon.

Track sales Our system will generate graphs every

month to keep the track of the sales.

5. Assumptions

1) We are assuming that the store will have full connection with the internet

without any interruptions.

2) We are also assuming the stakeholder to enter all the items by himself

which he wants to add in the inventory web application.

3) We assume the stakeholder to read the guidelines to use the application

for its proper use.


Page 5 of 11

6. Dependencies

1) Our system is fully dependent on the database, we will be using cloud computing

to host our application.

2) Our system will be dependent on the internet connection. In order to run the

application without any problem, client must have good internet connection

because connection problem could cause data lose or some other security

problems.

3) Our application will run on the data provided by the manager/owner of the store.

7. Risk Management

Potential Risk Severity (H/M/L) Likelihood (H/M/L) Management

Strategy

Access of Inventory M L Cloud Storage

Security Risk H L Provide

Identification,

Authorization and

Authentication

Theft M H Add Manually to the

system

Connection failure H H Good connectivity

8. Communication

8.1 Reporting

The following reports will be produced;

Report Audience Frequency

Internal information exchange Employee On Every Sprint

Information Management Stack holders Once in month

Project marketing Customers Once

8.2 Meetings

The following meetings/communication will be established;

Meeting Purpose Attendees Frequency

Project initialization

Meeting Project kickoff Project manager and

whole Project team

Once


Page 6 of 11

Stockholders

Meeting

Project work review,

requirement

gathering and other-

user side

requirement updates

Project manager and

Stack holders

Once in month

Project status

Meeting To keep project

moving towards

success

Project manager and

whole Project team

Every week

Project review

Meeting

Lessons learned and

celebration

Project team Once

9. Task Listing (WBS- Work Breakdown Structure) The following resource proposal template summarizes the resource hours committed to

this project, upon final approval of this document.

Reference Tasks Duration Dependency

A Requirement gathering 4 weeks No dependencies

B Structure designing 4 weeks A

C Programming 8 weeks B

D Database handling 4 weeks B, C

E Review and Testing 4 weeks C

F Error Handling 3 weeks E

10. Gantt Chart


Page 7 of 11

11. Milestones

Major Activity or Milestone Estimated

Milestone Target

date

Owner/Reviewer Team

Members

Project vision, business

requirements, user personas and

user stories

03/28/2019 Rajat, Gourav, Nirav, Muskan

Project plan, team charter,

product backlog, sprint backlog

10/06/2019 Rajat, Gourav, Nirav, Muskan

Structure designing Rajat, Gourav, Nirav, Muskan

Making of UI Rajat, Gourav, Nirav, Muskan

Back-End programming Rajat, Gourav, Nirav, Muskan

System implementation 03/27/2019 Rajat, Gourav, Nirav, Muskan


Page 8 of 11

12. RAM – Responsibility Assignment Matrix

13. Approval

The signatures below indicate their approval of the contents of this document.

Project Role Name Signature Date

Project Manager Nirav Sorathia Nirav 10/07/2019

Front End Developer Muskan Batra Muskan 10/07/2019

Programmer Rajat Rajat Rajat 10/07/2019

Delivery Manager Gourav Gourav Gourav 10/07/2019


Page 9 of 11

TEAM CHARTER

Multiple reasons exist for preparing a team charter. One is to document the team's purpose and clearly define individual roles, responsibilities, and operating rules. Next, it establishes procedures for both the team and management/industry partner on communicating, reporting, and decision-making procedures. It lays out a blueprint for conducting business for the acquisition and defines how the team works in an empowered manner, including setting out responsibility and authority. Finally, it facilitates stakeholder buy in by including key members in the decision-making process and obtaining their concurrence along the way. The charter includes the following sections: 1. Purpose the purpose of creating the team is to build a robust application. Each member of team has some specific skills set which helps to implement the plans in a more efficient way. A team helps each other if someone gets struck on some area. Team members actively collaborate which in turn build strong lasting relationships which helps to build meaningful projects. These things result in completion of a successful project. 2. Background Our team is creating an inventory web application which will help general convenience stores to handle their inventory without manually counting the items. our team members are experienced in making this kind of application and each of our team members has a unique skill set. Our application will be used by the employees and the managers of the store. With the help of our application, managers will be able to order the goods, see the left-over items in the store, see the monthly reports and keep the track of the items in the store. Our team is building an application that consists all in itself. The store does not have to use any other application or medium to keep track of the inventory. This, in turn, will help the store to do their work easily and build more customers. 3. Scope Our team has considered the point of sales and the inventory under the scope of this project. we will be considering customers buying the product which will automatically delete the item from the inventory which the customer bought. We have also considered the customer returning or damaging the item. In this way, the manager does not have to count the stuff manually in the store. he will be able to check it through our application. Our application does not consider the third party where the store is buying


Page 10 of 11

the goods. Our application will also send notifications to the manager about the items which are about to end in the store. 4. Team composition In our application, Mr. Nirav Sorathia is the manager and will be managing our team throughout this project. Miss Muskan Batra will be looking towards the front-end development of this project. Mr. Rajat will be working on the back-end and will be handling java in the project. Mr. Gourav will be handling the errors and will be working on testing and reviewing the application. for gathering all the requirements in this project (sources and all the other stuff) Miss Muskan will be playing the major role along with Mr. Gourav. For structuring and compiling all the data together, Mr. Gourav will be playing the lead role with Miss Muskan. Programming and database management will be done by Mr. Nirav and Rajat collectively. Errors will be handled by Mr. Gourav, Rajat and Nirav and in the end, Testing will be done by the whole team as everybody will be crucial in reviewing their part they did. 5. Team empowerment The team members of our project possess good skills in the work which is given to us. all of our team members are studying together for the last 2 years. everybody knows each other very well. We have done most of our projects together and have successfully finished them. Mr. Nirav is pretty good at handling the database. Mr. Rajat has really good java skills. Miss Muskan makes good UIs and Mr. Gourav is good at detecting and solving the errors. We are perfect as a team and looking forward to completing this project with flying colors. 6. Team operations As a team, we are looking forward to using vision control via Github to compile our project work. Our manager will be taking the major decisions for our project. In our team, all members complete their tasks on time but in case of any emergency, we will be collectively distributing the work amongst each other. Mr. Gourav will be handling the remote repository. We are also learning cloud so that we could host our application on the cloud rather than using some different servers. 7. Team Performance Assessment As a team, we have created the user stories and considered all the requirements of the stakeholder. we will be ticking every user story throughout our project which will keep the track of our progression towards our destination. We will also be testing every functionality of our application during this project. 8. Signature Page


Page 11 of 11


Project Manager Nirav Sorathia Nirav 10/07/2019

Front End Developer Muskan Batra Muskan 10/07/2019

Programmer Rajat Rajat Rajat 10/07/2019

Delivery Manager Gourav Gourav Gourav 10/07/2019

COMP 3059 – Capstone Project 1 School of Computer Technology

Page 1 of 13

COMP 3059 – Capstone Project I

Software Requirements Analysis and Design Assignment

This assignment is an overview to gather the software needs with requirements analysis and help to proceed with the design. The requirements analysis helps to break down functional and non-functional requirements to a basic design view to provide a clear system development process framework. It involves various entities, including business, stakeholders and technology requirements. The design is the activity following requirements specification and before programming. Software design usually involves problem solving and planning a software solution. To work on this assignment you could use the references and a sample template given below. The sample template can be customised to suit the nature of your project. Reference Readings/Example: http://www.uacg.bg/filebank/acadstaff/userfiles/publ_bg_397_SDP_activities_and_steps.pdf www.cse.msu.edu/~chengb/RE-491/Papers/SRSExample-webapp.doc https://nces.ed.gov/pubs2005/tech_suite/part_2.asp Reference template:

http://www.uacg.bg/filebank/acadstaff/userfiles/publ_bg_397_SDP_activities_and_steps.pdf

http://www.uacg.bg/filebank/acadstaff/userfiles/publ_bg_397_SDP_activities_and_steps.pdf

http://www.cse.msu.edu/~chengb/RE-491/Papers/SRSExample-webapp.doc

https://nces.ed.gov/pubs2005/tech_suite/part_2.asp


Page 2 of 13

1.0 Introduction In this project of creating Inventory Management Web Application, we have been creating this document to give an overview of all the possible criteria that can be a part of this web app. In this first part we started with discussing the purpose as well as the scope where this project can or cannot prove useful. Keeping in mind to increase the ease of reading this document we describe all the possible acronyms, abbreviations, references and an overview of the full document.

1.1 Purpose

To provide the clear statement of the problem along with the proposed solution and the high-level features of a product to establish expectations and reduce risk. A key function of inventory management system is to keep the track of each items from manufacturer to store and from store to point of sales as well as to keep records of damaged and returned items.

1.2 Scope The scope will be covering all the essential details, methodologies, deadlines, functions, tasks and costs. It also optimizes the time and cost constrains.

1.2.1 In Scope

In this project, point of sales, effectiveness towards running store, maintaining minimum amount of quantity, structured database, planning for future stock, and change in inventory system are included.

1.2.2 Out of Scope

Any other third party or customers, quality of products, are out of scope.

2.0 System Overview

The System Overview section introduces the system context and design.

2.1 Project Perspective

The inventory app we are creating is a replacement for an existing system. We started by creating an example of circle K that does not have an appropriate application for doing inventory and handling the items in the store. Starting from the circle K and extending the application to create it as a generalised application several features, and ideas were involved. The inventory application will handle everything from managing the stock, placing the orders as well as tackle with the damaged items.

The first feature of inventory management application will allow the Manager to view the current stock of products, along with the capabilities of searching and sorting the products.

The second feature will allow the user to update the inventory during the restocking process.


Page 3 of 13

The third feature will let the Store Manager to scan the items using the barcode and know about the details of the items.

The fourth feature will let the user to know about the selling of items using the graphs that will help to understand the profits and loss.

The fifth feature includes the authorization of user to manage email notifications, get the daily as well as weekly reports.

The main feature includes saving the data of the store using the cloud computing in order to store the data in a safe environment. 2.2 System Context

Uses of Inventory Management Application:

Efficiency and Productivity: Efficiency to manage the stock level in the store is essential to run the business smoothly and maintain positive cash flow in the store. Analytics and reports can help the user to identify which item is selling faster and will help the user to make smarter purchasing decisions.

Minimize Costs and Maximize Sales: The application will help you to manage your sales and manage your stock, this will help you to maximize the sales by taking care of the items in the stock and will minimize the chances of stock damage.

Relieving Manual Work: The task of entering all the data manually into the system will get easy by the feature of bar code scanning. This will save time, reduce efforts and mistakes.


Page 4 of 13

Increased Information Transparency: Know when items are received, shipped, manufactured, etc. Also, know when you need to order more, when you’re over-stocked, or under-stocked.

Increased employee efficiency: Good inventory management solutions save time. Less time spent on managing inventory results in greater productivity.

2.3 General Constraints

Scope: Scope is a very important constraint in the management. The scope of our inventory management is

Quality: Quality is very essential when creating an application, if the

app does not provide the desired quality of the features in the app, then there is a great chance of application failure.

Customer Satisfaction: Customer satisfaction is a key factor for a

sustainable and long-running business in the market. Because, they are the source of money and if you cannot satisfy your customers, you will not be able to stand against competition during time. Therefore, customer satisfaction is a crucial project constraint.

Risk: Several risks are involved while creating an application, such as

the application can crash or the data stored in the inventory application like the information of the stock, order details etc. can be lost.


Page 5 of 13

Therefore, Risk is a very critical project constraint in project management.

Resources: Resources include the information, facilities, material

required etc. for the project management. For the inventory management application, we need several software’s for e.g. Software required for storage of databases.

Time: Management of time is most difficult task. Completing all the

tasks included in the project such as for the inventory app we have been working on various sprints that had specified deadlines.

2.4 Assumptions and Dependencies

Assumptions:

All the team members will be completing their task on time.

All the desired software will have access and will work properly.

Application will work smoothly without any errors or problems in the features

Dependencies:

3.0 Functional Requirements

System must allow to login to manager and employee

System must be able to do register for employee

Manager must be able to add new items to the system

Manager must be able to see list of damaged or returned item

Manager must be able to see the graph of sales

System must be having functionality of ordering and reordering

System home page must show inventory records

Data base must be stored and maintained separately

System must not be machine bound, it should be accessible from anywhere and from any

device

Employee must be able to check available items of quantity

Manager must be notified by system if number of items goes less than certain amount

3.1 <Functional Requirement or Feature #1>

3.2 Use Cases


Page 6 of 13

3.3 Data Modelling and Analysis

Normalized Data Model Diagram


Page 7 of 13

Activity Diagrams


Page 8 of 13

Sequence Diagrams


Page 9 of 13

UML Class Diagram

3.4 Process Modelling

1. To Process the Modeling, we will be using the data flow diagram. A data-flow diagram (DFD) is a way of representing a flow of a data of a process or a system. The DFD also provides information about the outputs and inputs of each entity and the process itself. A data-flow diagram has no control flow, there are no decision rules and no loops. Specific operations based on the data can be represented by a flowchart.


Page 10 of 13

We will be using Level-0 ( Context Level DFD) and Level-1 DFD to represent the flow of data in our application.

Level-0 DFD


Page 11 of 13

LEVEL 1 DFD

4.0 Non-Functional Requirements

1. Error-Handling

The Application Shall handle the expected and non-expected errors in ways that prevent loss in information and long downtime period.

More than three attempts at login and failure will produce a red flag to system administrator.

2. Performance Requirement

Response time should be minimum for every event clicked inside the application.

Inventory should automatically update every after 1 minute to be in track with the POS updates.

3. Security Requirements:

Users can just read in the information but they cannot edit or modify anything except their personal and some other information.

System will have two users (manager and employee) and both users has constraints.

System must be secured from virus, worms, bugs, spyware by anti-virus programming.

4. Design Constrains

The Inventory Management System shall be a stand-alone system running in a Windows environment. The system shall be developed using Java Language.


Page 12 of 13

5. Portability

The application shall run in any Microsoft Windows environment as we are serving the database on Cloud.

6. Usability

The system should be interactive and user friendly so that everyone could learn it fast.

5.0 Logical Database Requirements

Yes, Database is the first requirement for our application. Our application fully relies on the Database. For this project, we will be working with the MySQL database and try to serve it on Google Cloud. Our team is currently learning about Cloud Technology and will be using it in further enhancement of this project. Our Application have Three-Tier architecture:

We are considering MySQL to be the best database for our application as our team members are familiar with it. We have made lot of projects using MySQL. The only difference is that we will be serving database on cloud this time.


Page 13 of 13

A logical database must be able to access and identify all files within the storage system to operate correctly. To have a logical database, all given hard disks and information files must be accessible from a single source. Data Retention:

Recordkeeping is important because it provides information to support decision-making by management and is generally required by legal retention requirements. In our application, we will be using Google Azure MySQL which helps in data retention. Our application will be using that data to prepare graphs which will help the manager to keep track of the sales.

Data Integrity:

We will be coding our application in such a way which will be performing data integrity whenever necessary. Data integrity is an important aspect to the design of a database that store records of any relational model. A database that utilizes rules such as data integrity; can increase performance, accuracy and stability. We will be using Java programming language to code our application

6.0 Approval The signatures below indicate their approval of the contents of this document.


Back-end developer

Rajat Rajat Rajat 11/11/2019

Manager Nirav Soratia Nirav 11/11/2019

Front-end developer

Muskan Batra Muskan 11/11/2019

Delivery manager Gourav Gourav Gourav 11/11/2019

Functional Requirements

Functional requirement defines functional definition of system or its component

3.1 Functional Requirement or Feature

System must allow to login to manager and employee

System must be able to do register for employee

Manager must be able to add new items to the system

Manager must be able to see list of damaged or returned item

Manager must be able to see the graph of sales

System must be having functionality of ordering and reordering

System home page must show inventory records

Data base must be stored and maintained separately

System must not be machine bound, it should be accessible from anywhere and from any device

Employee must be able to check available items of quantity

Manager must be notified by system if number of items goes less than certain amount

3.2 Use Cases

3.2.1 Manager Use Case

Use case: sign up

Diagram:

Brief Description

Manager must be able to sign up for the employees working in the store.

Initial Step-By-Step Description

Manager

Sign up

1. Manager takes the employees credentials and makes his account on the sign-up

page.

2. The registration page will have several validations that the user has to follow.

3. The data saves in the Cloud MySQL table.


Use case: login

Diagram:

Brief Description

Manager must be able to login to the system to access the web application data.


1. Using the credential provided while registration, manager tries to login to the

system.

2. The log-in page with fetch the data from the user and compare with the database.

3. If credentials are correct, then only user will be able to get into the application.

4. In case of incorrect credentials user will be directed to the error page with

warning message.

3.2.3 Employee Use Case

Use case: login

Diagram:

Brief Description

Employee must be able to login to the system to access the web application data.


1. Using the credential provided by manager, employee tries to login to the system.

2. The log-in page with fetch the data from the user and compare with the database.

Manager

login

Employee

login

3. If credentials are correct, then only user will be redirected to the employee’s home

page.

4. In case of incorrect credentials user will be directed to the error page with

warning message.


Use case: login

Diagram:

Brief Description

Manager should be able to check inventory status whenever he wants to.


1. When manager signs in to see the inventory. A new session opens up which

shows the current items in the inventory.

2. At this moment, if an employee sells some items through the POS, Inventory does

not update itself.

3. To run a new session, manager has to either reload the page or has to log-in again

to the system.


Use case: Notification on sparse items

Diagram:

Brief Description

Manager must be able to get the notifications about the sparse items in the inventory.

Manager

Check

inventory

Manager

Get notify about

sparse items


1. The inventory keeps track of each and every item in it.

2. Whenever the item goes less than some number, the system sends an email

notification on manager’s official email account.

3. When manager opens the application, he gets the separate column of the sparse

items.

4. After one notification, system does not prompt user about that item anymore.\


Use case: Damaged Item List

Diagram:

Brief Description

Manager must be able to see the list of damaged items to know about the wastage of

products


1. If something gets damaged. Employee puts the product in the damaged item list.

2. The items in the damaged list automatically removes the items from the inventory

and goes into the separate column of damaged list.

3. Manages sees and review the damaged items by going to that column.


Use case: Add items manually

Diagram:

Manager

Should see

damaged items

Manager

Should be able

to add items

Brief Description

Manager must be able to add items manually if he wishes to add a new product to be sold

in his store.


1. There will be a separate page in our application which will allow manager to add

the items manually if he wishes to do so.

2. In this way. He could be able to add a new item in the inventory and get all the

benefits of the application such as email notification and barcode reader, etc.


Use case: Remove Items

Diagram:

Brief Description

Manager must be able to remove the items from the application if he thinks that there is

not much sale of any item.


1. Manager can delete the items from the application and the item will get fully

removed from the application without any impact on the application.

2. This will help the store to avoid wastage and prevent it from loss.


Use case: Order Items

Diagram:

Manager

Should be able

to remove items

Manager

Order items

Brief Description

Manager should be able to order items using the application.


1. The application will provide a separate column to the manager to order the items

via the application.

2. For this application, we are not considering the third-party vendors who will send

us the products.

3. As third-party vendors are out of our scope, we will directly add the items to our

inventory once the manager orders an item.


Use case: Item details

Diagram:

Brief Description

Manager must be able to see the details of the items by simply scanning the item.


1. The inventory app provides us a column for barcode reader.

2. If user clicks on that particular column. It activates the barcode reader and then

the user can scan the items through that.

3. Once the user scans the item. He gets to see the details of the item.

4. He could see the availability of the item in the inventory and the past sales record.

5. He also gets an option to sell the item by simply clicking the sell button in the

application.


Use case: generates graph

Diagram:

Manager

able to see item details

of items

Manager

Can see reports

and graph

Brief Description

Manager must be able to see the sales via reports and graphs.


1. The inventory application keeps track of sales of every single item.

2. The application prepares the graphs and reports on the basis of this track.

3. The application provides a separate column which shows the reports and graphs to

the user.

4. The reports are generated for months, years and day basis.

3.2.12 Employee Use Case

Use case: Notification on sparse items

Diagram:

Brief Description

Employee must be able to void the items if the customer cancels the order.


1. If the customer asks employee to cancel the order, in this case employee can void

the item.

2. This will add the item back to the inventory.

Employee

Void Items

Documents

Project Plan, Team Charter Inventory Management System