Merge pull request #19 from microsoft/joelhulen-patch-1

Remove the paragraph about mobile app development from the case study

README.md

@@ -29,8 +29,6 @@ When retrieving submissions for a registered user, they would like the ability t
 
 The expectation is that Humongous software engineers will implement all API endpoints for the Health Checks initiative (beyond what you will create for the proof of concept), and multiple, independent teams may implement different endpoints over time.  Both Molly and the architects would like this system to be as simple to manage as possible. While there is an Operations team in the Engineering department, that group tends to be overwhelmed with existing tasks and they have very limited time available to manage new software solutions.  Ideally, the software engineers should be able to instrument, monitor, and manage these endpoints themselves, but Humongous Healthcare does not have a great DevOps culture today.  They are moving in that direction, but would appreciate any tooling, processes, or product selections which could make the process of instrumentation, monitoring, and management easier for their software engineers.
 
-Antonio's Business Analysts would like to develop applications to facilitate the communication between customers in the Humongous health care network and their health care providers.  They aim to develop systems which let customers input vital metrics from mobile, tablet, or desktop devices.  For mobile and tablet devices, they would like to make the health check applications mobile apps rather than having customers navigate to a website for data entry.  This mobile application interface should be as close to native Android or iOS as possible, but Antonio warns us that Humongous does not have much experience developing mobile applications and the Engineering department would need a significant ramp-up time to move on an initiative like this, making code-heavy mobile development a non-starter at this time for Humongous Healthcare.
-
 Although Antonio's team will work with partners do much of the front-end application work, Molly does not want this to become a "shadow IT" initiative.  She would like, as much as possible, to have Antonio's team working in a single, collaborative environment, where her Engineering department can review application security, ensure that everything is configured properly, and manage costs most efficiently.  They are very concerned with security breaches based on misconfiguration.  As Antonio put it, "I don't want one of my people to check the wrong box and suddenly we have governments fining us due to regulatory violations."
 
 Molly and the Engineering team also wish to have all data stored in a single database, as this will simplify security and open opportunities for their data scientists to analyze the data most efficiently.  In addition, they would like to centralize management of any access points to the data.  Different Engineering teams will work on separate API endpoints and Molly is interested in anything which can improve the coordination between teams and make their architecture group's lives easier.  Molly strongly prefers centralized solutions, and she does have a concern around the overlapping capabilities in Azure services.  She does not want to spend the time combining a lot of applications to get to Humongous's desired solution, so the fewer the number of working parts, the better it is in her mind.