Upload
russell-white
View
215
Download
0
Embed Size (px)
Citation preview
Project DogfoodProject Dogfood
Ian Cook, Mitch Heer, James Lorenz, Tom Navarro, Levi Stanley
Sponsor: Ansync
Ansync is an electronics manufacturer based in El Dorado Hills.
Designs and manufactures custom electronics and hardware for clients in the industrial, medical, and defense sectors.
Contact: Sam Miller, Owner and CEO
Tom – Slide 2
Sponsor Need
Ansync has a large, disorganized inventory. Thousands of different parts in various
locations, all tracked by hand. Inventory counts are done manually, which is
error prone. Orders are often filled in small batches of
varying sizes, making it difficult to track changes.
Tom – Slide 3
Ansync's Inventory Needs
Tom – Slide 4
Ansync's Inventory Needs
Ansync's current inventory management system is inaccurate and prone to failure
Electronics manufacturing is a time-sensitive process that does not tolerate missing materials.
Ansync wastes time and money replacing missing parts and faulty products.
Tom – Slide 5
Meeting Ansync's Needs
Providing the sponsor with a system that increases the efficiency of various tasks performed by Ansync employees and adapts to a changing environment.
Mitch – Slide 6
Meeting Ansync's Needs
Web based database system Interface is familiar and easily understood Convenient access from any computer
This increases the likelihood the sponsor will actually make the transition to our system and ultimately benefit from it.
Mitch – Slide 7
Meeting Ansync's Needs
Benefit Consolidating data into one place
Give faster price quotes Handle purchase orders - “...bane of my
existence” - Sam Miller
Mitch – Slide 8
Meeting Ansync's Needs
Adapt to change Parts and designs have many attributes
X, y and z coordinates Ohms Resistance etc...
Occasionally new types of parts arrive and may require a new field to keep track of a new attribute specific to that part.
Mitch – Slide 9
Major Features
Parts Inventory System Track Purchase Orders of parts Receive shipments of parts into inventory Audit Inventory Design Processing
Ian – Slide 10
Major Features
Circuit Board Design
Ian – Slide 11
Parts Quantity Needed
Quantity On Hand
Difference (OH - Need)
Res 10A 100 120 20
Res 11A 150 500 350
Res 100C 275 200 -75
Cap 1X 100 150 50
Cap 2B 180 300 120
Order more parts before manufacturing design.
Printed Circuit Board. 7 May.2011.<hhttp://electroniccircuit1.com/wp-content/uploads/2011/01/pc-board.jpg>.
Major Features
Customizable Database Alter Database Structure
Data Recovery Automatic Backups Restore Points
Ian – Slide 12
Information Model
No Information Models For Alter Database Structure Data Recovery
Levi – Slide 13
Information Model
Levi – Slide 14
Information Model
Levi – Slide 15
Information Model
Levi – Slide 16
Information Model
Levi – Slide 17
Information Model
Levi – Slide 18
Information Model
Levi – Slide 19
Information Model
Levi – Slide 20
Risk Management
3 Main Risks
Under-estimation of work effort
Incorrect identification of requirements
Technology limits ability to implement feature
James – Slide 21
Risk Management
What are these risks, and how to handle these risks?
Under-estimation of work effort Deadline approaching and it appears the
project will not be completed Reanalyze requirements with sponsor to
meet the deadline Prevention: constant mitigation throughout
the project
James – Slide 22
Risk Management
Incorrect identification of requirements Prevention: SRS approval process will confirm
that the project team and sponsor agree Occurrence would involve assessing the impact
of adding to the scope of the project
James – Slide 23
Risk Management
Technology limits ability to implement feature Chosen implementation technologies don’t
provide appropriate functionality Either features that can’t be implemented are
removed, or new technologies are added This will be done through choosing technologies
that have worked solving similar problems, catching possibly problematic features during requirements analysis
James – Slide 24
Learning Plan
Technologies to be used PHP, MySQL, JavaScript, jQuery At least one member of the team has experience
in each of those areas Main focus of learning: working on a “skeleton”
of database and interface Training sessions by person with most
experience in an area
James – Slide 25
Wrap Up
Learned so far? Scope is important Time flies when busy Team collaboration is key
Any questions? Comments?
James – Slide 26