Requirements+gathering+and+analysis

=Requirements Gathering and Analysis I= Sunday, October 9, 2011 <>

**Topic overview:**
A shockingly large percentage of failed information systems development projects can trace the root failure of the project back to poor requirements analysis and documentation. The process of analyzing the needs of the business in detail is both more difficult and more important than many IS project teams realize. Fortunately, there are some simple tools and guidelines that you can use to substantially increase the likelihood that your IS project will succeed. In today's class we will cover some fundamental ideas underlying requirements gathering and analysis, look at some basic techniques, and do an in-class exercise to illustrate how to use them.

By the end of today's class you should be able to:
 * Identify where requirements gathering fits into the SDLC
 * Identify common stakeholder categories in a systems development project
 * Write down clear, effective, and unambiguous functional requirements

**Preparation for class:**
You should review the following articles on wikipedia for a quick overview of requirements analysis.
 * Requirements Analysis: @http://en.wikipedia.org/wiki/Requirements_analysis
 * Functional Requirements: @http://en.wikipedia.org/wiki/Functional_requirements

These two articles will be sufficient preparation for class today. In addition to these articles, you will be responsible for the material in Chapter 5 of the book:
 * Alan Dennis, Barbara Haley Wixom, and David Tegarden, Systems Analysis and Design with UML Version 2.0, 2nd Edition, John Wiley and Sons, ISBN: 0-471-34806-6.

You will likely find that the material in Chapter 5 will be helpful for today's class but it will not be required (nor covered on the quiz) until the next class. Chapter 5 is quite a bit of reading, so completing some of this reading before the next class will help you balance out the course workload this week.

A digital reserve version of the chapter is available through a link in the Course Documents section of Blackboard.

**Reference materials:**
Slides:

Pre-class exercise:
As an exercise prior to class, select an information system applications that you use regularly. For that application, precisely specify one Functional Requirement and list some of the stakeholders who are likely to be affected by that requirement.

[Bob Monroe]
 * Application: Apple iTunes
 * Functional requirement: //Customers should be able to listen to a 30 second segment of any song that is available for sale in the iTunes store without purchasing the song//.
 * Stakeholders: iTunes customers, iTunes system administrators and network engineers, iTunes content manager.

[Hind Al Khulaifi]
 * Application: Google Docs
 * Functional requirement: //Users should easily be able to copy and paste content from or to a google doc//.
 * Stakeholders: Users, google doc developers.

[Maryam Al-Subaie]:
 * Application: Mac App Store
 * Functional requirement: //Users should be notified every time an app needs to be updated. This function allows the user to always have the latest improved version of any app they own.//
 * Stakeholders: App developers, Mac users, App Store system administrators and network engineers.

[Orkhan Rustamzade]
 * Application: PayPal
 * Functional requirement: //Users should be able easily to send money to other PayPal accounts or purchase any Ebay item.//
 * Stakeholders: PayPal users, Ebay users, PayPal system administrators and engineers.

[Maryam Al-Thani]:
 * Application: Foursquare - Location based social networking application
 * Functional requirement: Users should be able to select their location from a list of places, once they are logged in to the app.
 * Stakeholders: Foursquare users, companies and locations listed, Foursquare system administrators and network engineers.

[Sara Al-Mannai]:
 * Application: Amazon online book store.
 * Functional requirement: users should be able to view a summary of the book and see other people reviews and ratings.
 * Stakeholders: customers and users, Amazon content manager, Amazon administration.

[Aisha Al-Zaman]
 * Application: Facebook
 * Functional requirement: //Users should easily be able to update their status at any time//.
 * Stakeholders: Facebook users. Facebook developers, programmers and engineers.Facebook content manager.

[Nahan Arif]
 * Application: Google Calender
 * Functional requirement: Users should be able to easily share their calenders with other Google account users along with easily edit their schedules.
 * Stakeholders: Google account user, Google calender programmers, developers and administrators.

[Fatima Abdulla]
 * Application: Schedule Man
 * Functional requirement: //Users should be able to create their semester schedule, and easily share it with others.//
 * Stakeholders: Students, Schedule man Administrators, developers.

[Amal Osman]


 * Application: Qatar Airways online booking
 * Functional requirement: //users should be able to view all the available flight timings of the day and pick the one they want//
 * Stakeholder: Qatar airways customers, the system developers, Qatar airways online system manager

[Walied El Hag Ali]
 * Application: FedEx Tracking System
 * Functional requirement: Users should be able to view the location of their packages at any point of time.
 * Stakeholders: FedEx customers, System and software developers

[Ayah Abujarbou]
 * Application: Wal-Mart
 * Functional Requirement: users should know what items are being sold, how frequent it is being used and how much it costs.
 * Stakeholders: Wal-Mart suppliers, customers and system developers.

[Najla Al-Madhadi]:
 * Application: Qtel ePayment
 * Functional requirement: customers should be able to pay their bells and check the amount and deadline of payments
 * Stakeholders: Qtel customers, system administrators, engineers, developers and content manager

[Mohammed Kamal]
 * Application: SAP
 * Function Requirement: users should be able to enter and process requests for the company's purposes
 * Stakeholders: Employees, customers, system administrators and software developers.

[Khadeejah Al-Husseiny]
 * Application: Blackberry App World
 * Functional Requirement: users should be notified of new applications and whenever they need updates.
 * Stakeholders: App wold customers, content managers, and system administrators

[Fatima Al-Khayat]
 * Application: eazyinternet - QNB's online e-banking service.
 * Functional requirement: Customers should be able to view their account statements, make Local and international transfers and pay their Q-tel bill.
 * Stakeholders: QNB customers, system administrators and engineers.

[Abdullrahman Al-Muftah]
 * Application: CMU-Q blackboard
 * Functional requirement: students should be able to view the classes they're enrolled in, check their assignments, grades, etc.
 * Stakeholders: cmu students, system engineers, cmu staff.

[Anas Ali Chaudry]:
 * Application: Youtube
 * Functional requirement: Users are able to view suggested videos related to the search topic.
 * Stakeholders: Youtube users, Youtube channel owners, advertising agencies

[Patrick Steinhagen]:
 * Application: Google Search Engine
 * Functional requirement: show offers based on search queries
 * Stakeholders: sometimes consumers, advertising companies, google (they gain revenue on a per-click basis)

[Noor Al-Mohannadi]
 * Application: Tumblr
 * Functional requirements: Users should be able to post texts, images, audios and videos to their blogs and they can also follow other blogs.
 * Stakeholders: Tumblr users, Tumblr developers

[Ahmad Al-Sarraf]


 * // Application: // Traffic violation SMS
 * // Functional requirement: // users should be able to know if they commit any traffic violation, as they receive an instant SMS message.
 * // Stakeholder: // customers (drivers), the system developers and Qatar government administration (Traffic Department)

[Layal Al-Alami]
 * Application: Google Music
 * Functional Requirement: Users should be able to upload their own music and listen to it whenever they want.
 * Stakeholders: Google users; Google developers

[Al-Jawhra Al-Mana]:
 * // Application: // Online hotel booking.
 * // Functional requirement: U //sers are able to view different hotels in each country, their price range, location, special offers, availability, etc.
 * // Stakeholder: // Website users, System engineers.

[Noof Al-muzaffar]:
 * // A // pplication : shops SMS and emails service.
 * Functional requirement : users should be able to know the recent information about the shop such as : new collection, shop sales and new branches.
 * Stakeholders : Customers, shop managers , stuff and administration.

[Dua'a Althabatah]
 * Application: iPhone App Store
 * Functional Requirement: iPhone users should be notified of new applications and whenever an existing app needs an update.
 * Stakeholders: iPhone customers/users, App store admins and managers, Apps develope

[Firas Bata]
 * Application: Twitter for Android
 * Functional Requirement: Users should be able to post text as long as it is within 140 characters.
 * Stakeholders: Twitter users, Twitter administrators and managers, Android developers, Twitter developers.

[Ognjen Popovic]
 * Application: iStudiez Pro for iPhone
 * Functional Requirement: //Users should be able to get automatic reminder service, GPA calculation, and planner/organizer service, after they have "fed" system with necessary information.//
 * Stakeholders: Application users, iOS developers, App Store developers, as well as iStudiez development team, administrators, and management.

[Hamsa M Al-Massri]:
 * Application: Google Scholar
 * Functional requirement: users should be able to view the abstract of the article before buying it.
 * Stakeholders: Google Scholar customers, it's network engineers, and the authors.

[Haya Al-Mannai]
 * Application: Twitter
 * Functional requirement: users should be able to tweet different thoughts with less than or equal 140 character s, follow different people, and send or receive messages.
 * Stakeholders: Tweeter users, and tweeter developers.

[Mohammed Al-Rawahi]
 * Application: Ebay
 * Functional requirements: Users should be able to know the price as well a brief description of the product
 * Stakeholders: Customers, sellers and Ebay administration

[Dalia Saleh Hassan]


 * Application: SIO
 * Functional Requirement: //Users should be able to view their grades, tuition fees bills....etc.//
 * Stakeholders: Students, Professors, University staff.

[Mohammed Hadi Takiddin]
 * Application: Blackboard drop box.
 * Functional Requirement: //Users should be able to upload and submit their assignments.//
 * Stakeholders: Students, Professors.

[MUGHEES AHMED]


 * 1) Application: CAKEWALK (Sequencer) Inc
 * 2) Functional Requirement: Musicians, Composers can compose and improve their vocal/instrumental recordings.
 * 3) Stakeholders: Listeners, Musicians, Producers, Artists, Copyright/ Patent holders.

[Meshail Al Misnad]:
 * Application: Basecamp Sites
 * Functional Requirement: Listed users should be notified when progress is being made and messages have been posted.
 * Stakeholders: Basecamp users, Basecamp network engineers.

[Fatima Fikree]:
 * Application: Wiki
 * Functional Requirement: Users should be able to edit information made accessible to them on the page
 * Stakeholders: Wiki site developers, Wiki users, Wiki system administrators.

[Nijat Ibrahimov]
 * Application: Google Calendar
 * Functional requirement: //Users should be able organise their events and share with others and also see other user calendar and modify them.//
 * Stakeholders: Google Calendar Users, remote users and google calendar developers.

[Jim Briggs]
 * Application: YouTube
 * Functional requirement: //Users are able to upload,share and view videos//
 * Stakeholders: YouTube users, YouTube system administrators and network engineers.

[Laura Jaber]
 * Application: eazyinternet - QNB online banking
 * Functional requirement: QNB internet banking offers customers many banking services online. eazy internet offers you the most comprehensive online banking experience in the region. Stay in control of your finances, wherever you are.
 * Stakeholders: QNB investors, QNB employees, QNB customers.

[Nasser Al-Khori]
 * Application: Gmail
 * Functional requirements: provides users with email services (can send, read emails) and other services such as sharing a doc or Google calendar.
 * Stakeholders: Google investors, google users.

[Mohammed Al Ahmadani]:
 * application: Yahoo search engine
 * Functional requirements: gives the user results based on preferred search
 * stakeholders: Yahoo, customers, and companies advertising online with them.