Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Question 1:
Identify the stakeholders for the case study. For each stakeholder list their name, title, role on the
project (provider, reviewer, approver of requirements), influence on the project, and how they
might be affected by the project.
Question 2:
Identify at least 10 functional and 5 non-functional solution requirements for the case. Are your
requirements effective? Write your requirements as narrative statements that are SMART:
specific, measurable, achievable, relevant, and testable. Number each requirement.
Functional Requirements:
1. Michelle needs her application to display shoes to her users. Preferably in a way where
they could filter the shoes by size, color, price, style, and/or brand. The display could
include pictures of the shoes in a design similar to that shown below. The display would
list the shoe size and price. It would allow the user to click on the listing for further
investigation of the product.
2. Michelle needs a way to upload her shoes onto the application. She needs to be able to
add shoes to her site as she receives new purchases. Ideally, she could fill out a form
where she lists the brand, price, size, and a photograph. Later down the road, this process
could potentially be automated as her method for purchasing shoes evolves.
3. Michelle needs a way for her users to rent or subscribe to the shoes on the
application. The users need to be able to select a shoe for rent. This could be as simple as
an add to cart button (shown in the photo below).
4. Michelle needs a way for her users to create an account. Ideally, the account would
require the user to enter an email address so Michelle could contact them about rentals
and shipping. The user account would also establish a way for Michelle to keep track of
which customers currently have which shoes.
5. Michelle needs a payment method so that she can charge users for the shoes. The
payment method would require users to enter their credit/debit card number or potentially
connect the direct bank account to their account.
6. Michelle needs a method for returning a rental or subscription item. Michelle would need
a process put in place so that when the users rental was overdue, the user would receive
an email reminding them to send back the shoes. The reminder could also include a
packaging label so that the user would only have to box up the shoes, print out the label,
and drop them in the mail box to be sent back to Michelle.
7. Michelle could have a way for users to interact with one another and write comments on
their experiences with different shoes. Her application could have a customer review
section, similar to the one shown below. Customers could write a review that states the
overall comfort and likeability of the shoes. It could include an overall star rating so
future buyers could see what the general opinion on the shoes was.
8. Michelle could have a customer support email or chat method so that users can report
issues with their payment, delivery, or shoes. The process could be similar to that shown
below, where a user enters their phone number and has a customer service representative
contact them. It could also simply be an email address that users could send their
complaints to or potentially a chat box where the user could live chat with a
representative.
9. Michelle needs a place to store and care for her shoes when they are not being rented. As
her company grows, she will most likely not be able to store the shoes at her home. She
will need a place to keep the shoes when they are not being rented out. Preferably, a safe
place where they cant be stolen or damaged.
10. Michelle needs a way to deter patients from keeping rentals past their return date. She
could charge them a fee based on how long the rental is overdue. The application would
have to be able to recognize that the shoes are overdue and automatically charge the user
based on the preset late fee.
Non-Functional Requirements:
1. The application must be scalable. Since Michelle wants to get her business up and
running as quickly as possible, she needs a design that will allow her to start small, but
assume that it can support more users as her business grows. The app would have to
support multiple users placing orders at once.
2. The application must have high security. Michelles customers will be placing
debit/credit transactions to order the shoes through her application. This will require tight
security because she wouldnt want people hacking into her app and seeing users
transaction history or card numbers.
3. The application should have high performance. Michelle wouldnt want her app to freeze
when users navigated to different pages or tried to place an order. She would want her
application to be sleek and user friendly. She would also want it to be easy to learn so
that users could open it up right away and start using it.
Question 3:
What strategy would you use in this project to prioritize the requirements? Prioritize the
requirements found previously according to your strategy.
For prioritizing the requirements, I would use a categorical priority scale made up of the
following categories: critical, important, and desirable. Michelle wants to get her application out
as quickly as possible and she is open to releasing the application features in versions. Therefore,
I would make sure that during the first release of the application all the critical requirements are
included because they would be necessary for the application to run. During the next release, the
important requirements could be included and in the following releases the desirable
requirements could be added based on cost and time benefit.
I would use the Delphi Process to rank the requirements within the categories. I would
present the requirements to the group of stakeholders and have them anonymously estimate
which category each requirement belonged in based on their experiences and opinions. I would
then discuss each requirement with the group and order the requirements based on the general
consensus.
Question 5:
Using a mind mapping tool such as FreeMind create a mind map for a 3-5 page paper on the
following topic: Offshore Outsourcing of Software Development: Does It Really Reduce
Software Development Costs?. This outline will be a set of discussion points and a preliminary
outline for a blog entry for your IS blog. Write the blog using your previously brainstormed
ideas. Keep the blog to 1000-1500 words. Be sure to cite (and link) your sources.
Blog Post:
http://is3500portfolioloomis.weebly.com/blog/offshore-outsourcing-of-software-development-
does-it-really-reduce-software-development-costs
Resources:
http://www.tiempodev.com/corporateblog/the-hidden-costs-of-offshore-software-development
https://www.thebalance.com/top-6-outsourcing-disadvantages-2533780
https://www.flatworldsolutions.com/articles/advantages-disadvantages-outsourcing.php
http://searchcio.techtarget.com/definition/offshore-outsourcing
http://www.apoyocorp.com/13-ultimate-pros-and-cons-of-outsourcing-and-offshoring
http://smallbusiness.chron.com/pros-cons-outsourcing-offshore-companies-76794.html
Question 6:
Create a 10-minute presentation of a requirements management tool (as assigned/picked via
Blackboard).
Presentation:
https://docs.google.com/presentation/d/15GoRD8xBm65G9PxrIQELJgq7dqYIgBycVXq9tblrTe
s/edit?usp=sharing
Question 7:
Develop a checklist that can be used during peer review sessions by an analyst to ensure that
requirements activities (elicitation, management, prioritization, etc.) were done properly. The
checklist must contain at least twenty items. Use the web to help you find rules of thumb. The
following are two examples:
Were insights garnered from previous project retrospectives incorporated into the
requirements activities?
Were preconditions elicited to assure that missing requirements have not been missed?
Use online resources and your own experiences to find these heuristics.
Were steps taken to ensure that all users needs were addressed within the listed
requirements?
Were the requirements reviewed for unclear, incomplete, ambiguous, or contradictory
language?
Was a process set in place to manage change of the requirements as the product
develops?
Was the traceability for each requirement documented (who suggested it, why it exists,
what other requirements its related to)?
Was signoff received on the final requirements list from all major stakeholders?
Were SMART objectives developed for each requirement?
Was a proper requirements gathering technique used to discover the requirements
(Brainstorming, Mind Mapping, Use Case Workshop, Interviewing)?
Were the requirements documented in a place where all stakeholders and project
members can easily access the list to reference later?
Did the analyst fully understand the project domain and the process of application
development before gathering the requirements?
Was the requirements language consistent throughout the elicitation and prioritization
process?
Were diagrams, pictures, or sample data used to reinforce requirements meanings?
Were requirement dependencies documented?
Were requirements ordered by overall business value (benefit, risk, priority, etc.)?
Does each requirement have an owner to ensure stakeholder support and adequate
information?
Are requirements broken down into their simplest components by separating capabilities,
conditions, and associated business rules?
Was the requirements solicitor familiar with the organizations language and how it
operates?
Were existing applications of the same or similar function researched for comparison
prior to requirements discovery?
Was an impact and feasibility analysis performed on each requirement?
Do the requirements fit the project budget and timeline?
Are the requirements possible with the current technology?
Resources:
http://www.slideshare.net/menameissa/business-requirements-gathering-and-analysis
https://www.batimes.com/articles/verifying-requirements-documentation.html
https://en.wikibooks.org/wiki/Business_Analysis_Guidebook/Documenting_and_Managing_Req
uirements#Gather.2FElicit_Requirements
http://www.theitba.com/category/checklist/