Understanding what our customer wants-slideshare
•Download as PPTX, PDF•
1 like•753 views
This document discusses the two types of requirements for senior design projects - product requirements and process requirements. It emphasizes prioritizing requirements and avoiding vague requirements when developing design documents and source code. The document also asks about the reader's progress on their senior design project.
More Related Content
Viewers also liked
Viewers also liked (20)
More from Xiao Qin
More from Xiao Qin (9)
Recently uploaded
Recently uploaded (20)
Understanding what our customer wants-slideshare
- 1. 1 COMP 4710 Senior Design Project Understanding What Our Customer Wants Dr. Xiao Qin Auburn University http://www.eng.auburn.edu/~xqin xqin@auburn.edu
- 2. 2
- 3. 3
- 4. Two Types of Requirements 4 Product requirements Process requirements
- 6. 6
- 8. 8
- 9. 9
- 10. 10 Design Documents e.g., Create an account: TigerCheck2017
- 11. 11 Source Code
- 12. 12 Source Code
Editor's Notes
- 15 min Reference: http://www.techrepublic.com/article/the-analysis-phase-understanding-what-the-customer-wants/
- Most developers like to follow the Nike creed: Just do it! The customer comes to us with a business need, and we immediately move into problem-solving mode. We want to jump in and start writing code. There is no better feeling than completing an application and showing the customer. Until, of course, the customer informs us that this is not quite what he or she had in mind.
- My Story: gather information from Dr. Dubois – a professor at Auburn’s Nursing School. Developers can sometimes forget that the first phase of any development project is gathering business requirements to understand what the customer wants. It is only when we agree on the business needs that we can move on to the fun stuff—design and construction.
- Product requirements describe the business needs in terms of the main deliverables or products that are created. If you were building a bridge, for instance, most of the requirements would be product based. These might include the number of cars the bridge would hold, the strength of the steel, the water level it needs to span, and the color of the bridge. My Story: TigerCheck – Primary/Back PC Server Process requirements describe how people interact with a product and how a product interacts with other products. For example, when you discuss how data gets moved and how business transactions flow from one point to another, you are describing process requirements. If you need to handle billing transactions, most of the requirements could end up being process oriented. The requirements would include how billing transactions move from orders to invoicing to accounts receivable. They could describe at what points people look up a status, how people manually update an invoice, and what people should do if accounts are out of balance. My Story: Tablet Application – Data Entry Point
- No single customer normally knows all of the requirements up front. You should do a proper follow-up with a number of customers and stakeholders to make sure that you have as complete a picture as possible as to what is needed. My Story: Personality Check – Maybe we need. We propose machine learning and parallel processing. LIWC Apple’s former CEO: Steve Jobs. Create requirements for your customers
- Vague: follow-up meetings. Propose multiple candidate solutions.
- After the requirements are gathered, they should be prioritized and then formally approved by the customer and sponsor Metap
- Interrupt transfers control to the interrupt service routine through the interrupt vector (contains the addresses of all the service routines) Interrupt architecture must save the address of the interrupted instruction A trap or exception is a software-generated interrupt caused either by an error or a user request An operating system is interrupt driven